Pagup
Forum Replies Created
-
Forum: Reviews
In reply to: [Automatic Internal Links for SEO by Pagup] ⚠️ WarningHello,
After auditing our plugin and checking with our community of more than one thousand users, no similar issue to the situation you mentioned with your sites has been reported to us.
Are you sure you are not confusing our plugin with another one?
Also, this sounds more like a situation involving a potentially abandoned plugin, or one outside the scope of ww.wp.xz.cn, which is not at all the case with our plugin, whose latest update is recent.
We regret that you are accusing our plugin of being the cause of your situation, even though no other similar case has been reported by the community. We remain convinced that this is a case of confusion with another plugin.
Regards
Hi Alex,
You are correct.
In the free version of the plugin, the AI crawler preset is intentionally restrictive and blocks most AI training bots by default. This preset cannot be modified in the free version.
The ability to fully control AI crawlers, including allowing them to access and collect data from your website, is available in the Pro version of the plugin.
So if your goal is to allow AI systems to train on your content, you would need to upgrade to the Pro version where the “Allow All AI Search” option becomes available and configurable.
The free version focuses on providing a safe default configuration, while the Pro version gives full control over AI crawler policies.
Hope this clarifies things.
Best regards
Hi Alex,
Thanks for your question.
There is a common misunderstanding around “AI bots” and what they actually do.
Most AI crawlers (such as GPTBot or ClaudeBot) are primarily used to collect data for training AI models, not to “index” websites the way search engines do.
In other words, allowing those bots usually means allowing your content to be used as training data, rather than improving visibility in AI systems.
AI assistants that answer questions typically rely on search engine indexes or retrieve specific pages on demand. They don’t maintain a public web index in the same way search engines do.
Version 3 of the plugin focuses on controlling those AI training crawlers. Blocking them does not necessarily prevent AI systems from accessing or referencing your site.
If your goal is to allow AI training crawlers, you can adjust the preset rules in the plugin settings.
Hope this clarifies things!
Let us know
Forum: Plugins
In reply to: [Better Robots.txt - AI-Ready Crawl Control & Bot Governance] Fatals in 2.0.3Hi,
We are working on it !
We will let you know soon !
Hello Yoast Team,
I just wanted to confirm that the JavaScript error
(0, t.select(...)).getPostType is not a functiondisappears completely after rolling back Yoast SEO to version 24.9.
This means the issue was introduced in a later release — likely from v25.x onward.
No cache, CDN, or other plugins are involved; the rollback alone resolves the problem instantly.You might want to review changes made in the recent versions regarding how the plugin enqueues its block-editor assets (
yoast-seo-post-edit, etc.) even when Gutenberg is disabled.Best,
Hello,
Thanks for your reply. I can confirm that this issue is not related to caching.
Here’s the situation in detail:- All plugins have been fully deactivated, except Yoast SEO, and the problem still occurs.
- There is no caching active on the site: WP Rocket is disabled, no object cache is running, and Cloudflare’s cache has been purged.
- The issue happens in the WordPress admin, when editing a page using WPBakery / Classic Editor, not Gutenberg.
- The JavaScript console shows the Yoast script attempting to call
(0, t.select(…)).getPostType is not a function
which is a function that only exists in the Gutenberg editor (
wp.data.select('core/editor')).- Since Gutenberg is completely disabled site-wide, this function cannot exist, and the error stops the Yoast metabox from loading properly.
This means the problem is not cache-related, but caused by Yoast loading its block-editor (Gutenberg) assets even when the editor is disabled.
Could you please escalate this to your technical team?
Ideally, the Yoast script should check whetheruse_block_editor_for_post_type()returnstruebefore loading Gutenberg-dependent bundles likeyoast-seo-post-editoryoast-seo-premium-post-edit.Thank you for reviewing this
I’ll be happy to provide full console logs or stack traces if needed.
Best regards,
Hi,
Thank you for contacting our support.
Regarding your question, our plugin must remain active to ensure that all internal links created continue to function properly.
This applies to both the FREE and PRO versions.
Hope this helps.
Best regards,
Hello,
We have received your various emails regarding this matter and are currently investigating the issue. For efficient handling of communications, we kindly ask that you avoid using multiple channels to contact us about this.
We will respond by email as soon as we have an update.
Best regards,
Hi,
Thank you for contacting our support.
Could you please provide more details about your issue ?
Let us know
Regards
Hi,
Thank you for contacting our support.
Regarding your issue, we have analyzed both pages:
- On this page: https://www.drinkhacker.com/2008/12/18/review-kirkland-macallan-18-year-sherry-cask-finish/, all
alttags are set to:alt="Review: Kirkland Macallan Sherry Cask Finish 18 Years Old"
which corresponds to the post title (and not the file name, which is:kirkland-macallan-18-year.jpg). - On this post: https://www.drinkhacker.com/2025/05/05/book-review-drink-your-garden/, the
alttag currently appears as:alt="Book Review: Drink Your Garden"
again matching the post title.
Are you not seeing these?
Please try clearing your browser cache and let us know if the issue persists.
Best regards,
Hi,
Could you forward to this email: [email protected] the details of the email received from WordPress about this critical error?
Thanks
Hi,
Regarding our plugin, Bialty uses the
the_contentfilter, and in the case of WooCommerce, it also uses other filters for the product gallery images. Therefore, at the moment, it is not possible to add alt tags to related products, posts, the website logo, or images in the sidebar or footer, as these are outside the scope of the filters we use to add alt tags to images.That being said, considering how our plugin works—using either the “focus keyword” or the page title as the “Alt tag” for the image, such as for a product—from an SEO perspective, using the Alt tag of a specific product (its name, in this case) as the Alt tag for other products doesn’t make sense.
This means that using the Alt tag corresponding to a product’s name (via its Meta tag keyword—aka Focus keywords, or the page title) for other products is not a good SEO practice. What matters to search engines is consistency and the reinforcement, through the Alt tag, of a page’s meaning. Diluting this understanding with a specific alt tag for different images other than the original product is not necessarily a good idea.
For example, would it be relevant if, in a Google Images search, these other products appeared for a query related to your initial product?
I hope this information helps you better understand how our plugin and Alt tags work for SEO.
Best regards.
Forum: Plugins
In reply to: [Auto Focus Keyword for SEO] Remove all the existing Focus KeyphraseHi,
Thank you for contacting our support.
About your issue, we are looking at this …
We will let you know as soon as possible.
Thanks
Forum: Plugins
In reply to: [Auto Focus Keyword for SEO] Running out local Hard Drive Space When UsingHi,
Thank you for contacting our support (and sorry for the delay).
We do not understand your issue … Is your website hosted on your computer ? Our plugin does not interact at all with your personal hard drive. It’s really not how it works.
LEt us know if you have more details about this.
Thanks