SEO meta data not updating

  • Resolved Rolf Allard van Hagen

    (@ravanh)


    2 months, 4 weeks ago

    Hi, I’m encountering on multiple sites this weird issue: Once a SEO title, description or “noindex” on a page is set, I cannot change it anymore. The only way to change these meta values, is either to go into the database or activate the “Custom Fields” section in the editor and modify or remove the data from there…

    I should mention: this is not happening on all sites, but on many. And I cannot find any common denominator like similar other plugins or themes…

    Is this a known issue?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Rolf Allard van Hagen

    (@ravanh)

    2 months, 4 weeks ago

    Oh hang on, I found the common denominator… This happens only on sites where I have activated the Custom Fields option in my page editor settings. Once Custom Fields is deactivated, the SEO options set from the sidebar update fine.

    It looks like the custom field values keep overwriting (and thus reverting) changed SEO settings…

    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    2 months, 4 weeks ago

    Thanks for the detailed follow-up @ravanh.

    I was able to reproduce this behavior on my end as well. I’ve flagged this for our development team so they can investigate further.

    We’ll update here once we have more information. Thanks again for helping us track this down.

    Ref: Linear JETPACK-829

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    2 months, 2 weeks ago

    Hi @ravanh –

    Our development team has confirmed the issue and will fix it in a future version of Jetpack. When the fix is released, it will be indicated in the changelog.

    For now, the solution would be to deactivate Custom Fields.

    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    2 months, 2 weeks ago

    For now, the solution would be to deactivate Custom Fields.

    Yes, that or change the values in Custom Fields instead of the settings bar 😉

    In any case, thanks for fixing!

    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    2 months, 2 weeks ago

    Yes, that’s also a valid workaround for now @ravanh, but the upcoming fix should address the root cause directly so users don’t have to rely on it.

    Best,

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

You must be logged in to reply to this topic.