turkeysforlife

Hi @considerthis1 /amp vs ?amp=1 are just two different suffix versions of how the AMP version of your URL ends.

eg:

1) example.com/amp
2) example.com?amp=1

It looks like support are helping you with your issues now on some other threads – and they are much better qualified to help you than I am!

Good luck getting everything sorted out with your site – and have a great weekend!

Hi Milind,

Thanks for that. Attack mode wasn’t activated actually, it was set at medium, but I just switched it off completely and retried, with the same result.

And using Page Speed Insights, it sees the ‘AMP URL discovered’ on both desktop and mobile as /amp rather than ?amp=1, which is now how we should be set up. And that’s with both Cloudflare & our WP caching plugin both flushed.

Can we rule out that it’s a problem with AMP plugin and it’s definitely a Cloudflare issue based on that? ie. Why is Google seeing that a flushed cache page has a /amp version rather than a ?amp=1 version?

Sorry for all of the questions ?? I don’t understand all of this myself, but, if we can rule out that it’s definitely not a plugin issue then I feel like I can reach out to Cloudflare with more ammunition.

Thanks!

Barry

Hi again @jamesosborne

Just to update – I’ve tried an alternative recipe plugin (WP Recipe Maker). I’ve only edited one article so far, but it now passes the rich snippets test completely.

So looks like either EasyRecipe was the culprit, or, at least it was conflicting with another plugin which WP Recipe Maker has no problem with.

Thanks for the help and I’ll mark this as resolved now.

Hi,

I’ve tried using the Twenty Twenty-One theme and the same error occurs. We add the image to the recipe article the same way that you did, using the default featured image rather than uploading through EasyRecipe. Although you can select a different image via the plugin, if you want, be we don’t.

Any other ideas? Plugin conflict possibly?

Okay, thanks for testing that for us James.

I’ll try using a different theme – and update here, probably tomorrow.

Cheers!

Done, thanks!

Great, thanks James. Can I switch back to Reader in the meantime?

Transitional is still active – I never switched back…

Hi James,

Many thanks for the help. Yes, we are using the Easy Recipe Plugin.

I’ve just switched to transitional. The suffix has changed from /amp to ?amp but the AMP and non-AMP versions look exactly the same now. Does that sound right?

Hi,

Thanks for all of that. I can confirm that all plugins and WP are at the latest version. Site Kite updated yesterday and it’s still a problem on the latest version. I also tried clearing all cache from the WP Fastest Cache plugin and Cloudflare – and it didn’t help.

I’ll try a couple of your other suggestions to see if I can find a workaround…

Thanks again!

Hi @pcosta88

Many thanks for the reply and trying to help.

Just to confirm a few things…

1. We are using the official AMP plugin and Google’s official Site Kit plugin to implement AMP and add the GA code. I posted about the issue on the Site Kit support forum last week and they said that our implementation looks correct.

2. I’ve cleared all cache from everywhere (a few times over the last week) and the issue persists.

3. Of course, I can try this, but I’m sure they will say that it’s an issue with one or more of the plugins (Yoast, Site Kite, AMP).

But, with only those 3 plugins active (with Twenty Twenty-One theme) the problem persists.

With only 2 plugins active (Site Kit, AMP) the issue is resolved, except with the original (ie non-Yoast) page title reported in GA, obviously, instead of the Yoast SEO title.

Done!

Great, thanks again for helping me troubleshoot this far James. I’ll mark this as resolved now!

Thank you! I think your suspicions about SEO plugins are correct.

I disabled Yoast, cleared the cache and took a look at GA live reporting.

There were still page titles being reported as ‘not set’ but I guess that’s because most of them were being viewed via Google AMP URLs which are still cached?

I searched Google for one of the terms we rank well for from my phone and clicked into the result. It was still reporting as ‘not set’ in GA, but it was a Google AMP (cached) page, not actually the page on our site. As soon as I then visited our own URL rather than Google’s cached version, the page title appeared correctly in GA.

Then a few other AMP page visits from other users started displaying page titles, rather than ‘not set’, but they were the ‘raw’ page titles – ie not the SEO titles in Yoast. So, I think that sort of proves the issue – if you are still following me ??

Sorry for the long, rambling update report…but I’m sort of just seeing if you think it makes some sort of logical sense, James?

Now, what to do about it…

Okay, thanks James. I’ll try your recommendations and update here if I manage to isolate the issue. Cheers!