Bad HTTP response code/wrong canonical

  • Resolved lbrownie

    (@lbrownie)


    4 years, 6 months ago

    Hello,
    When I publish blog posts and then try to share them in Facebook, most of the time they load perfectly. However, sometimes they are not loading the correct post and instead point to the homepage. When I run these through Facebook debugger, I see they are getting a bad HTTP response code. The canonical points to the wrong link.

    Is this a plugin error?

    <script async src=”//s.imgur.com/min/embed.js” charset=”utf-8″></script>

    I figured out how to fix this. I just change the SEO keyphrase, update the post, and then run it through the debugger again, and then it loads properly.

    But it should work without me having to do that.

    Does anyone know what is going on? Is this a plugin bug?

    Thank you for your help

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

  • Hello @lbrownie!

    Can you please try resetting the Yoast database tables by doing the following steps?

    1. Install & activate the Yoast Test Helper plugin
    2. Go to Tools > Yoast Test
    3. Hit the “Reset indexables & migrations” button
    4. Go to SEO > Tools, and under SEO data, click the “Process and speed up site” button to allow Yoast to rescan your pages

    Does it fix the canonical issue?

    Let us know the result.

    Thread Starter lbrownie

    (@lbrownie)

    Hi,
    thank you for the response. Before I do all that, will there be any negative consequences to the website from doing this:

    Hit the “Reset indexables & migrations” button

    Please let me know. thanks

    No. It will only correct the data, including canonicals, in the Yoast database tables.

    Thread Starter lbrownie

    (@lbrownie)

    Hi,
    I followed all these steps but still had the issue.

    Interestingly, what fixes the issue is after publishing, hitting the “update” button on WordPress.

    The first time I publish a story, it sets the canonical to the non-permalink version with ?p=post_id, but clicking “update” again will generate the proper canonical.

    Do you have any thoughts on this?

    Thanks

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    Just to clarify, the issue is that when you create a post and then publish it, the canonical that outputs are the non-permalink version with ?p=post_id, but clicking ‘update’ after will generate the proper canonical?

    Could you confirm you are using the latest version of WordPress 5.5 and Yoast SEO for WordPress 14.8.1? Does the issue occur with a default theme and only the Yoast SEO plugin enabled?

    We’re sorry that you are experiencing problems that might be caused by our plugin!

    Just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

    Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

    As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

    Thread Starter lbrownie

    (@lbrownie)

    Yes, that is the issue I am experiencing.

    I am still on the previous version of WordPress, but using the updated version of the Yoast plugin.

    Let me try after updating WordPress. Thanks

    Do let us know how it goes.

    Thread Starter lbrownie

    (@lbrownie)

    Hi,
    I upgraded to the latest version of WordPress and am still having the same issue with the plugin. Any other thoughts?

    Hi @lbrownie,

    Thank you for letting us know you still experience this permalink/canonical issue with the latest 5.5.1 release.

    However, we are not able to replicate this behavior in our test environments. Do you happen to know if you are running any custom integration or plugins that affect the permalinks in your WordPress setup/site? Are your permalinks configured with %postname%? Can you share a screenshot of your permalinks settings under Settings → Permalinks? You can share a screenshot using a service like Snipboard. Thanks!

    Thread Starter lbrownie

    (@lbrownie)

    Hi,
    Here is my permalinks structure:
    mywebsitename.com/%category%/%postname%/%post_id%

    Hi @lbrownie,

    Thank you for letting us know the permalink structure.

    Would you happen to know if you have any specific plugins or custom code on your site that is interfering with permalinks? We ask since we can’t replicate the canonicals pointing the the ?p=ID in our testing sites, unfortunately.

    Thread Starter lbrownie

    (@lbrownie)

    Hi,
    My developer wonders if the “Page Links To” or “Edit Author Slug” plugin could be interfering with Yoast. He suggested sharing a list of all my plugins to see if you could replicate the issue.

    AdSanity
    AdSanity – Custom Ad Sizes
    Akismet Anti-Spam
    Amp
    Classic Editor
    Edit Author Slug
    Lazy Load – Optimize Images
    Page Links To
    Publish to Apple News
    Smart App Banner
    SumoMe
    WordPress Importer
    WP-PageNavi
    XML Sitemap & Google News
    Yoast Test Helper

    Please let me know if this information helps at all.

    Thank you

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    We are not aware of any confirmed conflicts between the 3rd party Page Links To and Edit Author Slug plugins. However, you can verify the conflict by simply disabling these two plugins to see whether this resovles the issue for you.

    Hi @lbrownie,

    We’re marking this issue as resolved due to inactivity. You’re welcome to create a new issue if you need further assistance.

    Thread Starter lbrownie

    (@lbrownie)

    Hi,
    The issue still has not been resolved

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Bad HTTP response code/wrong canonical’ is closed to new replies.