Why do your Top Stories on desktop vanish on mobile?

Does Google really treat desktop and mobile as two distinct worlds?

Yes, and this is a fundamental shift since the move to mobile-first indexing. Google crawls, indexes, and prioritizes the mobile version of your pages. However, this does not mean that the two versions display the same results: ranking algorithms integrate criteria specific to each usage context.

Top Stories in particular apply contextual relevance filters: loading speed on 4G/5G, readability on small screens, mobile user behavior (bounce rate, reading time), content format (length, structure, images). A page optimized for a 24-inch screen with long-format content may fail all these criteria on a smartphone.

What specific signals impact the mobile ranking of Top Stories?

Mobile Core Web Vitals are scrutinized with increased scrutiny: LCP under 2.5 seconds on slow 3G connection, CLS close to zero (jumping ads are a deal breaker on mobile), instant FID/INP. Google measures these metrics in real-world conditions via the CrUX dataset, not in a lab.

The content format also plays a role: short paragraphs, frequent subtitles, adaptive images, absence of intrusive pop-ups, adequately sized clickable buttons. An article with 10-line text blocks without spacing will be penalized on mobile, even if it performs well on desktop. Mobile behavioral signals (scroll depth, engagement, shares from mobile) weigh differently.

Does this divergence apply only to Top Stories?

No, this is a general principle. Top Stories are simply a visible case study because this carousel is closely monitored by publishers. But the logic applies to all SERP features: Featured Snippets, People Also Ask, Local Pack, Image Pack — each includes specific mobile optimization criteria.

The nuance? Google does not maintain two distinct indexes (contrary to what some still believe). There is one single mobile-first index, but the ranking algorithms modulate the results based on the device. This is a crucial technical detail: your server logs will show Googlebot Smartphone as the main crawler, but the ranking scores vary according to the context during display.

• Desktop and mobile display different results, especially in SERP features like Top Stories
• Mobile Core Web Vitals are measured in real conditions (CrUX), not in Chrome DevTools lab
• The editorial format must be specifically designed for mobile: short paragraphs, spacing, adaptive images
• Mobile behavioral signals (engagement, scrolling, shares) influence mobile ranking independently from desktop
• Only one index exists (mobile-first), but ranking algorithms adapt results to the device during display

Is this statement consistent with real-world observations?

Yes, and it is even an everyday observation for anyone auditing news websites. We often see gaps of 30 to 50 positions between desktop and mobile for the same queries, particularly on hot news queries where Top Stories dominate the SERP. Websites that neglect mobile optimization see their visibility collapse on smartphones.

Where Google remains vague — and this is typical — is on the precise thresholds that trigger these divergences. What LCP delta pushes a page out of mobile Top Stories? What mobile bounce rate becomes penalizing? [To be verified] Google never communicates these metrics, forcing empirical A/B tests on large samples.

What biases does this logic introduce into mobile results?

First bias: well-funded major media with dedicated mobile teams mechanically outperform. Fine-tuning for mobile (AMP or not, multi-node CDN infrastructure, on-the-fly WebP/AVIF images, smart lazy loading) is expensive. Smaller publishers or independent blogs, even with superior content, get crushed on mobile by less quality sites that are technically impeccable.

Second bias: over-optimization for mobile can degrade the desktop experience. Typically: splitting a long article into 3 pages to improve mobile LCP deteriorates desktop reading and fragments ranking signals. Or: oversimplifying content for mobile (removing nuances, detailed examples) can impoverish the semantic depth that Google values on desktop.

Should we treat desktop and mobile as two distinct sites?

No, that would be a strategic mistake. Google indexes a single version (mobile), so fragmenting content between two distinct URLs (/mobile/, /desktop/) is counterproductive. The right approach: an intelligent responsive design that adapts not only the layout but also the content structure, order of blocks, and density of paragraphs.

Specifically? Use picture tags with srcset to serve adapted images, CSS Grid to reorder blocks without JS, native lazy loading on images and iframes, and systematically test in real conditions (3G throttling on DevTools is not enough, use WebPageTest with Moto G4/iPhone 8 mobile profiles). [To be verified]: some SEOs test content blocks hidden in CSS on mobile but visible on desktop — Google tolerates this practice if the mobile content remains complete and relevant, but it’s a gray area.

How to effectively audit the desktop/mobile divergence on your Top Stories?

First step: use the Search Console with Device filters (Desktop vs Mobile) over the last 90 days. Export performance data for your URLs appearing in desktop Top Stories, then compare impressions/clicks/positions on mobile. A position gap greater than 10 ranks or a total absence of mobile impressions signals a problem.

Second step: CrUX Dashboard (or PageSpeed Insights API) to compare desktop vs mobile Core Web Vitals on these same URLs. Focus on mobile LCP measured at the 75th percentile — this is the threshold Google uses. If your mobile LCP exceeds 2.5 seconds while the desktop is under 2 seconds, you have found your culprit. Also analyze mobile CLS: a poorly dimensioned image carousel can destroy your mobile ranking.

What technical optimizations should be prioritized to align desktop and mobile?

On loading: implement a CDN with edge computing (Cloudflare Workers, Fastly VCL) to serve pre-optimized content based on the device. Enable Brotli compression at least level 6, serve images in WebP with JPEG fallback, lazy-load everything that is below-the-fold. On WordPress, Perfmatters + WP Rocket configured well do 80% of the job.

On content: segment your paragraphs — nothing above 3-4 lines on mobile. Use frequent H3/H4 subtitles (every 150-200 words) to create visual anchor points. Remove overloaded sidebars on mobile, push related posts to the end of the article, and most importantly: test actual readability on an iPhone SE (small screen) and a Pixel 6 (large screen) — user behaviors differ.

What if your internal resources are limited?

Let’s be honest: finely optimizing a website to perform equally well on desktop and mobile requires cross-disciplinary skills — front-end dev, technical SEO, mobile UX, data analysis. Overloaded internal teams tend to prioritize desktop (out of habit) or apply generic mobile optimizations that are not sufficient for Top Stories.

In this context, bringing in a specialized SEO agency can significantly accelerate results. An experienced agency has playbooks tested on dozens of news sites, proprietary tools to automate cross-device audits, and, most importantly, a strategic vision to balance desktop/mobile trade-offs without sacrificing one for the other. It's an investment that pays off quickly on high mobile traffic sites.

• Audit the Search Console with Device filters (Desktop/Mobile) to identify ranking gaps on your Top Stories URLs
• Compare desktop/mobile Core Web Vitals via CrUX Dashboard, focus on LCP and CLS at the 75th percentile
• Implement a CDN with edge computing and Brotli compression to optimize mobile speed
• Segment paragraphs (max 3-4 lines on mobile), multiply H3/H4 subtitles every 150-200 words
• Test actual readability on physical devices (iPhone SE, Pixel 6) with 3G throttling
• Consider expert support if internal resources are lacking to manage these cross-device optimizations