Should you show the same number of products on mobile and desktop for mobile-first indexing?

Why does this mobile-desktop difference pose a real problem?

Since the shift to mobile-first indexing, Google crawls and indexes the mobile version of your pages as a priority. If your desktop category showcases 50 product listings with their title tags, meta descriptions, and internal links, but the mobile version only displays 10, Googlebot will only see these 10 products during indexing.

Direct consequence: the other 40 products lose out on SEO visibility. Their pages no longer receive the PageRank passed from the category page, their crawl frequency drops, and their positioning gradually erodes. This is particularly critical for large e-commerce catalogs where the information architecture relies on these pillar pages.

What does Google mean by “identical essential content”?

Mueller intentionally remains vague on this notion. It can be inferred that it refers to structural elements: product titles, short descriptions, main images, prices, availability. If these data points are present in both versions, even with a different number of items, the SEO impact remains limited.

On the other hand, if the mobile version hides blocks of editorial content, navigation filters, or rich snippets present in desktop, that’s a problem. Google cannot index what it doesn't see — and what it can't see on mobile no longer exists for its algorithm.

How is this rule applied to sites with pagination or lazy loading?

Pagination remains technically acceptable if it is crawlable: clean rel="next"/"prev" tags, accessible URLs, functional JavaScript rendering. Lazy loading poses more issues if products only load upon scrolling — Googlebot mobile does not actively scroll.

Mueller has previously clarified that Google tries to trigger lazy loading, but with no guarantee. If your additional 40 products only appear after three scrolls on mobile, they are unlikely to ever be indexed. The solution? Implement server-side pre-rendering or, at a minimum, render the first 20-30 items directly in the DOM.

• Mobile-first indexing means that Google exclusively indexes the mobile version — not an average between mobile and desktop.
• A difference in the number of items displayed is only problematic if the strategic content diverges (titles, links, metadata).
• Lazy loading and infinite scroll must be technically crawlable; otherwise, dynamically loaded products will not be indexed.
• Category pages pass on PageRank: reducing the number of visible internal links on mobile weakens the overall SEO architecture.
• Google provides no numerical metrics on what constitutes an “acceptable difference” — it’s up to the SEO to test and observe.

Is this recommendation consistent with field observations?

Yes, but with important nuances. E-commerce audits repeatedly show sites that have lost 20-30% of organic traffic after switching to mobile-first, precisely due to mobile versions lacking internal linking. Categories with aggressive mobile pagination (10 products per page vs. 50 in desktop) experience measurable erosion of crawl budget.

However, sites that maintained strict link parity — even while visually reducing the number of items through CSS or well-implemented lazy loading — did not suffer any notable losses. The issue is not the number of items displayed, but the number of crawlable links present in the DOM at the time Googlebot visits.

What gray areas remain in this statement?

Mueller does not specify a quantitative threshold. At what ratio does the difference become penalizing? 50 vs 10 seems problematic, but what about 50 vs 30? Or 50 vs 40? [To be verified] in real cases through A/B testing with monitoring of crawling and positions.

Another ambiguity is the notion of “essential content”. For a fashion site, do facet filters (color, size, price) count as essential content? If the mobile version hides these filters in a non-crawlable dropdown menu, does Google ignore them? The answer likely depends on the sector and search intent — but Google provides no clear analytical framework.

In what cases does this rule not fully apply?

On sites with well-implemented infinite scroll (pagination via distinct URLs + history API), the difference in initial display does not penalize if the subsequent URLs are crawlable. Google can follow pagination links and reconstruct the entire catalog.

Similarly, sites using a modern JavaScript framework (Next.js, Nuxt) with SSR or pre-rendering can serve the complete DOM to Googlebot while progressively displaying content to the user. In this case, the mobile version viewed by Google contains all 50 products, even if the UX only displays 10 at the initial load. This is technically compliant, but requires an advanced technical stack.

What should you prioritize auditing on your category pages?

Start with a comparative crawl mobile vs. desktop using Screaming Frog or Oncrawl in mobile user-agent mode. Compare the number of internal links detected on each version of your key category pages. If the gap exceeds 30%, you likely have a mobile-first indexing issue.

Next, use the URL Inspection tool in Search Console in mobile mode on 5-10 key categories. Check the rendered HTML: how many products appear in the initial DOM? If you expect 50 and only see 10, that’s what Google is indexing — even if your pagination or lazy loading loads the others afterward.

How can you correct a mobile-desktop difference without breaking UX?

Three proven strategies. First option: implement crawlable pagination with distinct URLs (category?page=2, page=3…) and clean rel="next"/"prev" tags. Display 10-15 products per page on mobile, but ensure that Googlebot can follow links to subsequent pages. It’s simple, robust, and compatible with all CMS.

Second option: use lazy loading with pre-rendering. The 50 products are in the initial DOM (crawlable), but only the first 10 load their images/CSS above the fold. This requires careful front-end development but offers the best UX without compromising SEO.

Third option: server-side rendering (SSR) if you're on a modern framework. The server generates the complete HTML with 50 products for Googlebot while the client progressively hydrates content for the user. This is the premium solution but demands an advanced technical stack and high-performance hosting.

What KPIs should you track to measure the impact of a correction?

Monitor the number of indexed pages in Search Console after your deployment. If you had an indexing deficit on long-tail products, you should see a gradual increase over 4-8 weeks. Also compare the crawl rate of product URLs before/after: an increase indicates that Googlebot is rediscovering these pages via the restored internal linking.

On the traffic side, segment your categories in GA4 and observe the evolution of non-brand organic traffic on these pillar pages. A successful correction generally results in +10% to +25% organic visits over 3 months, especially if you had a large catalog with many “invisible” products on mobile.

• Crawl your site in mobile user-agent and compare the number of internal links per category page vs. desktop
• Test 10 key categories with the URL Inspection tool (Search Console, mobile mode) to see the rendered DOM by Google
• Check that pagination is crawlable (distinct URLs, rel next/prev tags, links accessible without JavaScript)
• Implement pre-rendering or SSR if you are using aggressive lazy loading on mobile
• Monitor the evolution of the number of indexed pages and the crawl rate over 8 weeks post-deployment
• Segment organic traffic by category in GA4 to measure the actual impact on conversions