How to Disabled “Indexables” Feature?

Hi @zoladesigners,

We understand that after pushing from staging to production site, there are items on the site that still refer to the staging site URL. We also understand that it can be frustrating deleting everytime the wp_yoast_indexable table to reload live URL after migrating the changes to live site.

We apologize?for the trouble you are currently experiencing with our plugin. Luckily, a so-called “bug report” (a description of the issue, so we can fix it) is filed already.

What’s next?
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate when they’ll start working on your report.

If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic.

Note/Workaround: We’ve created the Yoast Test Helper plugin (if you haven’t used this plugin before) to make it easier for our users to truncate the database tables the plugin creates. Once the plugin has been installed, the option can be found in Tools > Yoast Test > Reset Indexables tables & migrations

These tables are populated with data when you start the indexing process by clicking the “Speed Up” button or run the WP CLI command.

OR when an item (like a post) gets a visitor.

Hi @zoladesigners ,

We’re closing this thread because we haven’t heard back from you in a while. Should you have further questions, please open a new thread.

This thread came up with Google when I searched for “yoast disable indexables” but unfortunately it doesn’t contain the solution.

I need to disable this feature since it’s indexing the wrong featured image when inserting posts programmatically via PHP CLI wp-load.php

I can’t write the details since nobody would have the time and the will to read them, but it just does this:

1 – wp insert a post as ‘draft’
2 – binds the featured image to the post
3 – wp update the post as ‘publish’

I appreciate your work and maybe this func is very beneficial, but unfortuntaly I have very little time to look into it for the cause and the fix so a quick filter to disable the funcionality would do just fine in my case.

Does a filter exist to disable it?

Thanks

Hi @drlightman,

If you’re seeing a similar issue, we’d like you to create a new forum topic if you’d like us to troubleshoot this issue for your specific site.

We discovered Yoast was inserting these indexables as the canonicals and breadcrumbs for our sites we built on a different staging domain. This caused google to index many pages with the wrong canonical.

wp-cli would be fine, but it forces a reindex. we cannot run wp-cli on our production servers, and our local environment does not use the production domain… so that will not work. it would be helpful if wp-cli had an option to just delete the index and we can push the db to the production server and let it re-index there.

the “yoast test helper” plugin is a no-go. it seems ridiculous to install a second yoast plugin to fix a problem caused by the first. is there not an option to disable or at least rebuild the yoast-indexables through the yoast seo plugin.

preferably, we would like to disable indexables entirely. if we want caching to improve speed, there are other very nice tools and plugins for that.

• This reply was modified 4 years, 3 months ago by bristweb.
• This reply was modified 4 years, 3 months ago by bristweb.

@bristweb According to the forum guidelines, you’ll need to open a new topic instead of replying to an existing post. That way, it’s easier to track issues and provide assistance without alerting someone else for your problems and debugging, when they don’t need it.

My indexable table has became so large more than 150MB so instead of helping my website performance it has a negative impact.

Please add a settings so I can disable this feature.

It must be a matter of an “if” statement I suppose.

Thanks.

@mehrdadm According to the forum guidelines, you’ll need to open a new topic instead of replying to an existing post. That way, it’s easier to track issues and provide assistance without alerting someone else for your problems and debugging, when they don’t need it.

I have a similar problem, a conflict with polylang that I can resolve only clearing indexables tables. Is there a way or a filter to bypas it?