Content revised 21 October 2026.
If a website uses AMP versions, review the pair whenever templates or content change. Keep technical relationships and the visitor’s available information consistent.
Inventory the pairs
Record which public AMP page corresponds to which canonical page. Open both directly and inspect current output. A pairing that was correct before a redesign can become stale after a template or routing change.
Compare the important journey
Check the main explanation, media and next-step controls. Verify any access or paywall behaviour appropriate to the publisher. Do not leave a mobile visitor with a shorter claim that omits material conditions.
Test before release
Use supported validators and representative device checks. Keep the results and change owner documented. Validity supports implementation quality without promising inclusion, a badge or a ranking advantage.
Official guidance: Google AMP requirements.