#228 – Conflick with Yoast SEO

 Hi.

I recently began having critical errors reported by Google Search Console. In troubleshooting, I determined that when I deactivated Yoast, the problems disappeared. I then created a staging site and had a Yoast engineer look at the issue for me. He identified the issue as being caused by a conflict between Yoast and WeeblrAMP. Below is the text of the email I received from Yoast. Please see if you can resolve this for me. Thanks:

Hi Andy,

Thanks for your patience and for providing clear instructions to access your staging site.

We logged in to your staging site and were able to identify a conflict with the weeblrAMP plugin. When this plugin is active, the Yoast SEO title defined in the Yoast metabox is not outputted in the source code of your pages. We created a draft post here and confirmed that when weeblrAMP is disabled, the SEO title is generated correctly (see image one below). However, when the weeblrAMP is active, the SEO title defined in the Yoast SEO plugin is ignored and the post title ("Yoast test" in this post example) is used instead.

The SEO title is also used by the Video SEO plugin to generate the video name attribute schema markup. Therefore, the problem you were experiencing with faulty structured data also resolves when weeblrAMP is disabled. As you can see in image two below for one of your video pages (link here), the name attribute does get outputted when weeblrAMP is disabled.

We'd recommend you contact weeblrAMP support and bring this issue to their attention. They should be able to investigate why their plugin conflicts with the Yoast SEO title functionality. If they're unable to help, you may consider switching to the official WordPress AMP plugin: https://wordpress.org/plugins/amp/

Please, let us know if you have any other questions.

Image One

cb3f1f95f9e5951a78ddaa2d6a198d17.png

Image Two

63afa05cb2fbe7519234f06b2f3d513f.png




How would you rate my reply?
Satisfaction Rating Icons

Thanks and regards,
Ramon

--
Ramon Bauza
Support Engineer at Yoast

Hi Andy,

Yes, I can see that now. This is coming from the code changes they made in Yoast 14.0, where they changed the API for other plugins to extract data from Yoast.

I have made the changes to adjust to that but it seems it's not enough and the data is not available at the time (during the request processing) where I need it. This will require a very large changes in weeblrAMP so it's not going to happen overnight.

At this time, I can only suggest to disable the Yoast integration from weeblrAMP settings, until I find a way to workaround all those changes, if that's even possible.

Best regards

Hi Andy,

Found a workaround for this, I am now fetching the data from Yoast a bit later in the page rendering processing and that seems to do the trick. You can download an updated version from the development versions download area.
Install over current one and let me know how it goes.

Best regards

Thank you. I have installed the revised plugin and will keep you posted.

Best regards,

Andy

OK. I tested one of the pages with issues using the Google Rich Results tool. No errors structural were found. However, I did get this warning. What do you make of it? Is it related to the delay you mentioned implementing?

"Page partially loaded
Not all page resources could be loaded. This can affect how Google sees and understands your page. Fix availability problems for any resources that can affect how Google understands your page."

Hi

You probably block some parts of your site with a robots.txt, this is what this message is about.

You can use our SEOInfo browser extension (Chrome or Firefox) and look at the resources for that page, it'll tell you which resources are blocked.

Best regards

Per Yoast's recommendation, this is the entire of my robots.txt file:

# This space intentionally left blank
# If you want to learn about why our robots.txt looks like this, read this post: https://yoa.st/robots-txt
User-agent: *

Hi

I cannot comment on this, this is outside of weeblrAMP. Some of the resources (js, images, css) on your page are blocked, that's all this message tells us and there's nothing weeblrAMP is involved in here.
I'd encourage you to use our extension to easily find which resources are blocked - although it won't tell you by what it's blocked.

Best regards

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.