wpseo_taxonomy_meta option is auto-loaded – Is it necessary to be?

  • Resolved BERJAYAMarco Almeida | Webdados

    (@webdados)


    1 month, 2 weeks ago

    I just noticed that the wpseo_taxonomy_meta is auto-loaded and it has 340 Kb in my database.

    I looked at the plugin code and couldn’t reach a conclusion on whether this setting is actually needed on every WordPress page load.

    Can you please clarify this? I don’t want to make it NOT auto-loaded and cause even more issues, if it’s actually used every time, on the other hand, this represents 31% of my autoloaded options in terms of size

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support BERJAYAMaybellyne

    (@maybellyne)

    1 month, 2 weeks ago

    Hello Marco,

    Thanks for using Yoast SEO. The wpseo_taxonomy_meta field contains the SEO title, a meta description, a focus keyphrase, related keyphrases, and synonyms for taxonomy items, like categories and tags. If you have been using Yoast SEO for a while and deleted any taxonomy term, the wpseo_taxonomy_meta field likely contains information about those previously deleted terms.

    Setting the autoload option to NO might cause poor performance due to additional database queries needed to get the relevant data. You may not notice a difference on smaller sites when setting the autoload option to NO, but larger sites may experience slowness.

    Thread Starter BERJAYAMarco Almeida | Webdados

    (@webdados)

    1 month, 2 weeks ago

    Hi @maybellyne

    I know the consequences of turning this option to autoload = no if its actually loaded on all page loads.

    My question was: is this option needed on all page loads, or just when taxonomies are being edited or shown?

    Plugin Support BERJAYAMaybellyne

    (@maybellyne)

    1 month, 1 week ago

    No, it is not strictly necessary for it to be autoloaded on every single page load

    Thread Starter BERJAYAMarco Almeida | Webdados

    (@webdados)

    1 month, 1 week ago

    Thanks @maybellyne,

    If that’s the case, I recommend this is fixed on the plugin: https://github.com/Yoast/wordpress-seo/issues/23121

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.