Is it true that AMP or canonical really captures the SEO signals?

What should you prioritize checking in your current architecture? <\/h3>

Start by auditing the canonical declaration <\/strong> on all your AMP pages. Use the URL inspector in Search Console to confirm that Google correctly recognizes the relationship. A disparity between your declaration and the engine's interpretation can block the transfer of signals.<\/p>

Next, compare the Core Web Vitals of your canonicals <\/strong> via PageSpeed Insights (CrUX data) with those of your AMP pages. If the gap is significant, you know where to focus your efforts: it’s the scores of the canonical that count for ranking, not those of AMP.<\/p>

How to optimize your canonical to capture all the benefits? <\/h3>

If you were maintaining AMP primarily for performance reasons, it's time to transfer those optimizations to the canonical <\/strong>. Adopt AMP best practices (optimized images, critical inline CSS, deferring non-essential JavaScript) directly on your standard page.<\/p>

Test frameworks such as Nuxt or Next.js <\/strong> that allow server-side rendering with progressive hydration. You achieve loading times comparable to AMP without the constraint of a dual architecture. And above all, you are working on the only version that matters for CWV.<\/p>

In what cases should you still keep AMP? <\/h3>

AMP remains relevant if you depend on the Google News carousel <\/strong> or if distribution partners (aggregators, third-party applications) specifically consume this format. In this case, maintain the AMP version but invest heavily in the canonical.<\/p>

For all other sites — e-commerce, corporate blogs, showcase sites — the cost/benefit ratio of AMP no longer justifies its maintenance. It’s better to gradually migrate to a high-performing standard architecture and monitor the evolution of Core Web Vitals post-migration.<\/p>

• Audit the consistency of canonical tags between AMP and standard pages via Search Console <\/li>
• Compare the Core Web Vitals CrUX of your canonicals vs AMP to identify discrepancies <\/li>
• Transfer AMP optimizations (images, critical CSS, lazy loading) to the canonical <\/li>
• Test the deactivation of AMP on a low-traffic section and measure the CWV impact for 28 days <\/li>
• Assess whether your dependence on the News carousel still justifies keeping AMP <\/li>
• Document backlinks pointing to AMP URLs to anticipate potential redirects <\/li><\/ul>
  The absolute priority is now the performance of your canonical page <\/strong>. All signals converge towards it, and only its Core Web Vitals matter for ranking. If your team lacks the expertise to carry out these complex technical optimizations — restructuring architecture, improving CWV, gradual migration — it might be wise to rely on a specialized SEO agency that can manage these projects without degrading your visibility during the transition.<\/div>