TL;DR
Mobile and desktop rankings can diverge when mobile-specific issues create different user experiences. Google uses mobile-first indexing, meaning mobile experience is the primary ranking factor even for desktop searches. But ranking differences between devices occur when mobile-specific problems (viewport issues, touch target sizing, intrusive interstitials, mobile page speed) affect only mobile user satisfaction. Desktop rankings stay stable because desktop users don’t experience these issues. Diagnosing requires device-specific testing, not just “responsive” verification.
The Conversation
Raj, web developer at a B2B services company, noticed ranking split: Our desktop rankings are solid. But when I check mobile rankings, we’ve dropped significantly. Same pages, different rankings. I thought mobile-first indexing meant they’d be the same.
SDC SEO Brain: Mobile-first indexing means Google primarily uses your mobile version to evaluate ranking factors. But user experience signals on mobile can differ from desktop, creating ranking differences. The algorithm sees the same content but measures different satisfaction signals.
Raj: The site is responsive. It works on mobile.
SDC SEO Brain: “Works” and “provides equivalent experience” are different things. A responsive site can have mobile-specific problems that don’t exist on desktop: slower load times on mobile networks, touch targets that are too small, interstitials that block content, or layouts that require zooming. Any of these can tank mobile engagement while desktop stays fine.
Raj: How do I find out what’s wrong specifically?
SDC SEO Brain: Start with Search Console’s Core Web Vitals report, filtered by mobile. Compare mobile CWV scores to desktop. If mobile shows poor scores but desktop shows good scores, you have a device-specific performance problem.
Raj: Let me check… Mobile LCP is 4.2 seconds. Desktop LCP is 1.8 seconds. That’s a big difference.
SDC SEO Brain: There’s your primary culprit. 4.2 seconds is well into the “poor” range for LCP. Google’s threshold is 2.5 seconds for good. Desktop users experience a fast page; mobile users experience a slow page. Same HTML, different performance, different rankings.
Raj: Why would the same page be slower on mobile?
SDC SEO Brain: Several possibilities. First, mobile devices have less processing power, so heavy JavaScript takes longer to execute. Second, mobile networks have higher latency than typical desktop connections, so connection-dependent resources load slower. Third, your largest contentful element might be different on mobile due to responsive images or layout changes.
Raj: We serve different images on mobile using srcset.
SDC SEO Brain: Check if your mobile images are actually smaller or if they’re just being scaled down visually. If you’re serving a 2000px image that displays at 400px on mobile, the full file still downloads. Also check if the LCP element is even an image. On mobile, LCP might be a different element than desktop due to layout changes.
Raj: How do I check what the LCP element is?
SDC SEO Brain: Chrome DevTools, Lighthouse panel, run an audit in mobile mode. The performance section shows which element was identified as LCP. Run the same audit in desktop mode and compare. If LCP elements differ between devices, optimize the mobile LCP specifically.
Raj: What about touch targets? You mentioned those earlier.
SDC SEO Brain: Touch target issues happen when clickable elements are too small or too close together. Google’s standard is at least 48×48 CSS pixels for touch targets with 8 pixels of spacing between adjacent targets. Run a Lighthouse mobile audit; it flags touch target issues specifically.
Raj: We have some small links in our footer and sidebar.
SDC SEO Brain: Those could contribute. But footer links probably aren’t your primary problem. Check your main navigation, CTAs, and in-content links. If core interaction elements are frustrating on mobile, users either struggle or give up and return to search.
Raj: What about intrusive interstitials?
SDC SEO Brain: Google penalizes interstitials that cover most of the mobile viewport immediately on page load. Cookie consent banners get an exception if they’re legally required, but pop-ups for newsletter signups, promotions, or app downloads that block content on arrival hurt mobile rankings.
Raj: We have a pop-up asking visitors to schedule a consultation. It appears after 5 seconds.
SDC SEO Brain: After 5 seconds is better than immediately, but if it covers the main content and doesn’t have an easy dismiss option, it’s still an experience problem. Consider replacing full-screen pop-ups with bottom banners or delayed slide-ins that don’t obstruct content.
Raj: How do I test the actual mobile experience systematically?
SDC SEO Brain: Four-layer testing. First, Chrome DevTools device emulation for layout and visual issues. Second, Lighthouse mobile audit for performance and accessibility. Third, actual device testing on various phones since emulation doesn’t capture real device performance. Fourth, user behavior data from analytics comparing mobile versus desktop engagement metrics.
Raj: We don’t have a lot of mobile traffic anyway. B2B traffic skews desktop.
SDC SEO Brain: Doesn’t matter for rankings. Google uses mobile-first indexing regardless of your traffic split. Even if 90% of your visitors are on desktop, your rankings are primarily determined by mobile experience. The 10% mobile visitors affect how everyone finds you.
Raj: That seems unfair for B2B sites.
SDC SEO Brain: It’s Google’s perspective on how the web should work. They’re incentivizing mobile-first design universally. From a ranking standpoint, you need to optimize mobile even if your audience is mostly desktop.
Raj: What if we have content that only appears on desktop?
SDC SEO Brain: That’s a mobile-first indexing problem. Google indexes what it sees on mobile. If content, navigation, or structured data exists only on desktop, Google may not see it at all. Check that your mobile version has all the content you want indexed.
Raj: We hide some sidebar content on mobile to keep pages cleaner.
SDC SEO Brain: Hidden with CSS (display: none or visibility: hidden) is often ignored by Google. Hidden with lazy loading or interaction requirements is seen but may be deweighted. Content completely absent on mobile isn’t indexed. Check what content you’re hiding and whether it’s important for rankings.
Raj: How do I verify what Google sees on mobile versus desktop?
SDC SEO Brain: Search Console’s URL Inspection tool. Test a URL and look at “View Crawled Page.” This shows what Google actually saw when it crawled. Compare the mobile and desktop crawl if you’ve had recent crawls of both versions.
Raj: What’s my priority fix order?
SDC SEO Brain: First, fix LCP since 4.2 seconds is severely hurting you. Check image optimization, lazy loading below-fold content, and JavaScript execution timing. Second, audit touch targets and fix navigation and CTA sizing. Third, review that consultation pop-up and make it less intrusive. Fourth, verify all important content is present on mobile version. Fifth, test on actual devices, not just emulation.
Raj: Timeframe for ranking recovery?
SDC SEO Brain: Core Web Vitals changes take 2-4 weeks to process after Google recrawls and reevaluates. More significant UX changes might take longer to affect engagement signals and rankings. Expect 1-3 months for mobile rankings to recover if you fix the core issues, assuming no other problems.
Raj: Should I expect mobile and desktop rankings to converge?
SDC SEO Brain: Ideally yes, but not always. Some queries have device-specific intent. “phone repair near me” might rank local results differently on mobile versus desktop. For your B2B service pages, once mobile experience equals desktop experience, rankings should converge.
FAQ
Q: Why do mobile and desktop rankings differ?
A: User experience signals differ between devices. Mobile-specific issues (slow LCP, small touch targets, intrusive interstitials) affect mobile engagement while desktop engagement stays fine. Google measures satisfaction differently for each device’s user experience.
Q: What is mobile-first indexing?
A: Google primarily uses your mobile version to evaluate content and ranking factors. Even if most of your traffic is desktop, rankings are determined by mobile experience. Content that exists only on desktop may not be indexed at all.
Q: How do I find mobile-specific performance issues?
A: Search Console Core Web Vitals report filtered by mobile. Chrome Lighthouse audit in mobile mode. Actual device testing (not just emulation). Compare mobile versus desktop engagement metrics in analytics.
Q: What LCP threshold matters for mobile rankings?
A: Google’s threshold is 2.5 seconds for “good” and 4 seconds for the boundary of “poor.” Mobile LCP above 4 seconds severely impacts rankings. A 4.2-second mobile LCP puts you in the “poor” category.
Q: What about B2B sites where traffic skews desktop?
A: Google applies mobile-first indexing regardless of your traffic composition. Even with 90% desktop visitors, your rankings are primarily determined by mobile experience. Optimize mobile regardless of who actually visits.
Q: How long until mobile rankings recover after fixing issues?
A: Core Web Vitals changes process within 2-4 weeks after recrawl. Broader UX improvements affecting engagement signals take 1-3 months to show ranking impact. Expect gradual convergence of mobile and desktop rankings as experience equalizes.
Summary
Mobile and desktop rankings diverge when user experience differs between devices. Google uses mobile-first indexing, but measures satisfaction separately for each device’s users. Desktop users experiencing a fast, usable page send different signals than mobile users struggling with a slow, cramped version.
Mobile-first indexing applies regardless of your traffic split. Even B2B sites with 90% desktop traffic are ranked primarily on mobile experience. Google is incentivizing mobile-first design universally.
LCP differences are the most common culprit. Same HTML can perform dramatically differently across devices due to network latency, processing power, and image handling. A 4+ second mobile LCP severely impacts rankings while 1.8 second desktop LCP is fine.
Content hidden on mobile may not be indexed. CSS hiding, lazy loading, and mobile-specific content removal can prevent Google from seeing your most important content. Verify that mobile and desktop versions contain the same indexable content.
Four-layer testing catches device-specific issues. DevTools emulation, Lighthouse audits, actual device testing, and analytics comparison. Emulation alone misses real-world performance problems.
Sources
- Google Search Central: Mobile-first indexing documentation
- Google Search Central: Core Web Vitals thresholds
- Chrome DevTools: Mobile performance testing
- Web.dev: Touch target sizing guidelines