Duplicate content

Whether you use /amp, /?amp or amp=1 for the AMP versions of your content doesn’t impact on SEO. Which one is used is dependent on the mode you’re using and the content type being service.

Note that we’re planning to use ?amp=1 by default going forward for both reader and transitional modes, with users also being able to customize the query param if preferred. You can subscribe to the below GitHub issue for more details:
https://github.com/ampproject/amp-wp/issues/2204

moreover my subpages of type / page / 2 /? amp returns to a 404 error in desktop, why?

Can you share an example URL with this behavior, a non AMP URL? I can then check the AMP version. As you’re using a TagDiv theme with their own transitional mode templates there may be some configurations you can apply. The URLs I checked all seem to be working fine, with this page and it’s follow on page links loading without issue.

Hello
What I don’t understand is that the urls are accessible via? Amp and? Amp = 1 … Is this normal? Why is this considered an error for SemRush which counts me duplicate content for H1 for example ?

for the 404 page error :
https://www.handirect.fr/category/culture-et-handicap/pa
ge/26/?amp

Thanks !

Nicolas

It’s normal for the URL to accessible with ?amp=1 an ?amp however if you check the amphref link in any non AMP URLs you’ll find the defined AMP URLs with.

For SEO purposes when using reader or transitional mode you’ll notice a “canonical” (non AMP) reference URL, indicating this is an AMP version of your content, ensuring no duplicate content issues. This works in a similar way to language and other plugins may create different versions of a URL for different conditions.

for the 404 page error: https://www.handirect.fr/category/culture-et-handicap/page/26/?amp

The 404 error seems to be related to the non AMP version, with the URL you provided loading fine. As TagDiv have their own category pages which may be impacting this can you check whether the same issue occurs with a default WordPress theme?

Ok very well so you confirm to me that everything is working fine and that there is no duplication error? Otherwise I have HTML code issues. For example: The mandatory ” style ” attribute is missing in the markup
e ” i-amphtml-sizer ” or the ” disable-inline-width ” attribute may not be displayed
er in the ” amp-img ” tag.
url example: https://www.handirect.fr/10-conseils-pour-ecopher-a-lepi
half-of-gastro-enteritis /? amp

Thanks !

Nicolas

You won’t have any duplication errors in realtion to your AMP URLs when using the plugin.

Otherwise I have HTML code issues. For example: The mandatory ” style ” attribute is missing in the markup e ” i-amphtml-sizer ” or the ” disable-inline-width ” attribute may not be displayed er in the ” amp-img ” tag.

I don’t encounter any AMP errors from the URLs I’ve checked. If you want to provide a full link to a URL with that error I can take a look, the URL you shared previiously is incomplete.

Thanks !

This an url exemple : https://www.handirect.fr/10-jeux-pourenfants-autistes/?amp=1

Problems :
– The mandatory ” style ” attribute is missing in the ” i-amphtml-sizer ” tag.
– The ” img ” tag can only appear as a descendant of the tag ” noscript ”. Do you mean ” amp-img ”?

Unfortunately this link is not valid. Have you published the post, or can you share another example?

Oups sorry : the valid link : https://www.handirect.fr/10-jeux-pour-enfants-autistes/?amp

No problem. I’ve checked that link and it’s a fully valid AMP URL, no action is required.

If you encountered any errors or warnings from Search Console these results may be stale. You can check for validation errors yourself using the below:
https://search.google.com/test/amp

ok thanks !

Last question, sorry :

the test on google pagespeed insight for the url : https://www.handirect.fr/1-000-choeurs-pour-un-regard-2/?amp

I have this :
URL
Taille de transfert
économies potentielles
/v0.js(cdn.ampproject.org)
70,6 KiB
34,4 KiB
…src/service/url-replacements-impl.js
2,7 KiB
3,1 KiB
…src/service/history-impl.js
2,2 KiB
1,8 KiB
…src/service/viewport/viewport-impl.js
2,6 KiB
1,7 KiB
…src/service/resources-impl.js
4 KiB
1,7 KiB
…src/service/navigation.js
1,3 KiB
1,6 KiB
/v0/amp-analytics-0.1.js(cdn.ampproject.org)
30,6 KiB
22,1 KiB
…extensions/amp-analytics/0.1/events.js
3,8 KiB
3,6 KiB
…extensions/amp-analytics/0.1/visibility-manager.js
2,5 KiB
2,6 KiB
…extensions/amp-analytics/0.1/visibility-model.js
1,1 KiB
1,3 KiB
…extensions/amp-analytics/0.1/requests.js
1,2 KiB
1,2 KiB
…extensions/amp-analytics/0.1/analytics-root.js
1,2 KiB
1,1 KiB

It’s possible to reduce time loader ?

Looking at your AMP site it already performs very well, while following the suggested steps in PageSpeed Insights or using web.dev will allow you to perform some additional optimizations.

You’ll also find an article in optimising your AMP URLs here and you can subscribe to the below GitHub issue in relation to the AMP component scripts being flagged in PageSpeed Insights:
https://github.com/ampproject/amphtml/issues/28638