Support » Plugin: NextScripts: Social Networks Auto-Poster » Not found content posted to Facebook after upgrade to Yoast SEO 14

  • net

    (@krstarica)


    Using “Use WP Cron to Schedule autoposts”.

    After upgrading to the latest Yoast SEO (version 14), auto-posting to Facebook creates “Page not found” posts.

    Facebook Sharing Debugger shows: “URL returned a bad HTTP response code” (404) and shows Canonical URL (from og:url): https://www.website.com/?p=123456

    Such page really does not exist.

    When click “Scrape again” button in Facebook Sharing Debugger, the page is fetched again and looks fine. Canonical URL becomes normal permalink, such as https://www.website.com/some/article

    Posting to Twitter is fine.

    When revert back to Yoast SEO 13.5 posting to Facebook is fine.

Viewing 15 replies - 1 through 15 (of 21 total)
  • Plugin Author NextScripts

    (@nextscripts)

    We will check that. It sounds like new Yoast now takes time to set OG tags and other new post/page info.

    You can try to set a several minutes delay (https://www.nextscripts.com/snap-features/scheduled-and-delayed-posting/) to give Yoast some time to finish your post.

    net

    (@krstarica)

    Can you fix this issue please?

    Scheduled and Delayed posting is available in Pro version only.

    Many thanks.

    net

    (@krstarica)

    Still experiencing the same with Yoast SEO 14.6.1.

    Any updates on this issue? Did you manage to solve it? I’m experiencing the same behavior. @krstarica

    net

    (@krstarica)

    @jaydoe96 Didn’t find solution for this and reverted back to old Yoast SEO.

    Please @nextscripts fix this. Many thanks!

    Thanks for your response @krstarica . Which version of Yoast are you currently using?

    net

    (@krstarica)

    Yoast SEO 13.5 is the latest one working fine.

    Plugin Author NextScripts

    (@nextscripts)

    Can anyone with this problem share a log after the post? We are using latest Yoast SEO 14.6.1 and can’t replicate this problem.

    net

    (@krstarica)

    @nextscripts There is nothing strange in the log, it says “OK – Message Posted”.

    Since Yoast SEO 14 introduced some indexing feature, probably auto-posting happens before it finishes the work?

    I messaged Yoast and asked for this issue. I told them this problem of “yoast taking too long to setup the meta tags” and they say that’s not happening, that once you save/publish the post, yoast immediately saves the meta tags.

    Mind sharing the list of plugins that you’re using on your blog? Maybe we have some plugins in common that are causing the problem. Since there isn’t much information about this issue on the internet, it could be worth trying to figure this out.

    net

    (@krstarica)

    Using so many plugins…

    Maybe we should focus on what Facebook Sharing Debugger reports: “URL returned a bad HTTP response code” (404) and Canonical URL (from og:url): https://www.website.com/?p=123456

    Why SNAP submits https://www.website.com/?p=123456 to Facebook instead of proper URL like https://www.website.com/topic/somepage?

    This doesn’t happen when Yoast SEO 13.5 is used.

    Plugin Author NextScripts

    (@nextscripts)

    Why SNAP submits https://www.website.com/?p=123456 to Facebook instead of proper URL like https://www.website.com/topic/somepage?

    SNAP Does not submit anything other than URL.

    Here how it works.
    1. You publish the post.
    2. SNAP tells Facebook – “hey, here is the new post and a URL of the new post this person wants to share to his Facebook page”.
    3. Facebook comes to your new post/page and gets all info it needs from your OG tags.
    4. Facebook adds a “Shared Post” block to new post using info from step 3.

    OG tags MUST be on your site at the time Facebook comes to check it.

    net

    (@krstarica)

    here is the new post and a URL of the new post

    How does SNAP get URL of the new page? There must have been some changes in Yoast SEO 14 regarding that.

    The thing is that URL https://www.website.com/?p=123456 does not exist for public. Facebook tries to open that page and properly receives 404 Not found.

    • This reply was modified 3 months, 3 weeks ago by net.

    In which file/line of the plugin are the URLs that are going to be used for facebook gotten?

    I was checking the code this morning but I had a hard time finding the exact place. Maybe there’s something that change between in Yoast that affects NextScripts. I would like to help checking that.

    Let’s say that the cause is not Nextscript but Yoast, at least knowing where the URL is being gotten will allow me to run some custom code, so if I get an URL like http://www.site.com/?p=XYZ, I could discard it, or use some workaround to get the proper pretty URL.

    • This reply was modified 3 months, 3 weeks ago by jaydoe96.
    net

    (@krstarica)

    I think we are looking for is function nxs_getURL.

Viewing 15 replies - 1 through 15 (of 21 total)
  • You must be logged in to reply to this topic.