AMP in Google Results: Why Does Your Mobile Version Matter More Than You Think?

Is AMP a Ranking Factor for Standard Organic Results?

No, and this is where many misunderstand. Google uses AMP pages solely for the Top Stories carousel, a visual format that appears at the top of results for news queries. For all other search results, the engine completely ignores your AMP version.

The standard ranking algorithm evaluates your standard mobile or responsive version. If you have a responsive site, it is this version that Googlebot crawls and indexes to determine your position. AMP does not provide any ranking bonus in the 10 blue links.

What’s the Difference Between Top Stories and Standard Results?

The Top Stories carousel appears for hot news queries (politics, sports, recent events). It displays 3 to 8 articles in a visual carousel, usually with images. Historically, only AMP pages could feature here.

The standard results are the famous 10 organic blue links. Here, Google evaluates your content, your Core Web Vitals, your internal linking, and your backlinks based on your normal mobile version. AMP plays no role in this evaluation.

Why Does Google Maintain This Separation?

AMP was designed to serve ultra-fast content in a news context where speed is crucial. AMP specs impose strict technical constraints (no custom JavaScript, limited CSS) that ensure near-instant load times. This is ideal for reading a breaking news article on mobile.

For classic organic results, Google prefers to evaluate your actual site, with all its features and complete user experience. Enforcing AMP across the web would have stifled innovation and the richness of interactions. The separation makes sense: AMP for pure speed in news context, normal mobile version for everything else.

• AMP does not boost your organic ranking in standard results
• The Top Stories carousel remains the only placement where AMP is required (or strongly favored during certain periods)
• Your mobile/responsive version is what matters for your overall positioning
• Investing in AMP only makes sense if you are a news media aiming for Top Stories
• The Core Web Vitals of your normal mobile site are far more strategic for your overall traffic

Is This Statement Consistent with What Is Observed in the Field?

Yes, completely. A/B tests conducted by sites that abandoned AMP show no loss of organic traffic on non-news queries. However, some media outlets have indeed observed a visibility drop in Top Stories after removing AMP, which validates Google's statement.

The issue is that Google has long maintained a deliberate ambiguity regarding the role of AMP. Between 2016 and 2021, many e-commerce sites or blogs invested in AMP believing they would gain a ranking advantage. They lost time and resources. This clarification comes late, but it is welcome.

What Nuances Need to Be Added to This Claim?

Google states that it uses “the mobile or responsive version,” but in practice, it is still the mobile version that counts since the Mobile-First Index. If you still have a separate desktop site and a weak mobile version, you will be penalized even with AMP. The order of priorities is clear: mobile first, AMP possibly for Top Stories.

Another nuance: saying AMP “is not a ranking factor” is true directly, but speed remains a factor. An AMP site is often faster than a poorly optimized normal mobile site. If your competitor has AMP and you do not, and their AMP loads in 0.8s compared to your 3.2s on mobile, they will likely have an indirect advantage via Core Web Vitals. [To be verified] on significant volumes, as the correlations remain blurred.

In Which Cases Does This Rule Not Apply?

If you are a pure news media (press, news site, political or sports blog covering hot news), AMP remains relevant to maximize your presence in Top Stories. This carousel generates high click rates on mobile. Ignoring AMP potentially deprives you of this traffic source.

For all other sectors (e-commerce, SaaS, local services, non-news thematic blogs), AMP is a waste of time. It is better to invest those hours in optimizing your normal mobile site: image compression, lazy loading, CSS/JS minification, CDN. The gains will be superior and applicable to all your traffic, not just a niche.

What Should You Do If You Have Already Implemented AMP?

First, ask yourself this question: how much traffic actually comes from Top Stories? Analyze in Google Search Console (Performance > Appearance in Results > Top Stories). If it is less than 5% of your total traffic and you are not a media outlet, disable AMP. You will gain simplicity in maintenance.

If you decide to remove AMP, do it cleanly: remove the rel="amphtml" tags from your canonical pages, set up 301 redirects from old AMP URLs to your normal mobile URLs, and submit a new sitemap without the AMP pages. Monitor your positions for 2-3 weeks. Normally, there should be no negative impact on standard results.

What Mistakes to Avoid in Mobile Optimization Without AMP?

The first mistake: believing that a responsive site is sufficient without optimization. Responsive design does not guarantee performance. A site that visually adapts but loads 3 MB of assets on mobile is a burden. Test your actual Core Web Vitals with Chrome UX Report, not just PageSpeed Insights in the lab.

The second mistake: neglecting server-side rendering or pre-rendering. If your site is a React/Vue SPA that sends an empty shell and loads content in JS, Googlebot may struggle. The Time to Interactive explodes. Invest in Next.js, Nuxt, or a SSR solution that suits your stack. It is more cost-effective than AMP for 99% of sites.

How to Ensure That My Mobile Site Is Properly Evaluated by Google?

Use the URL Inspection Tool in Search Console. Paste a URL, run a live test, and check which version Google is crawling (desktop or mobile). Since the Mobile-First Index, it should be the mobile version. Also look at the rendered screenshot: if any elements are missing or broken, that’s what Google sees.

Compare your index coverage between your mobile URLs and your old AMP URLs if you had any. If AMP pages remain indexed after you’ve removed them, force their removal via the URL removal tool, then ensure that the canonicals point correctly to your normal mobile pages.

• Analyze Top Stories traffic in Search Console to quantify AMP impact
• Test the Core Web Vitals of the mobile version (LCP < 2.5s, FID < 100ms, CLS < 0.1)
• Check that Googlebot is indeed crawling the mobile version via URL inspection
• Audit server-side JavaScript rendering if the site is a SPA
• Remove rel="amphtml" tags and redirect old AMP URLs if abandoning
• Update the sitemap to exclude AMP pages if they are disabled