Mobile SEO and Mobile-First Indexing

Google crawls and indexes your site using a smartphone Googlebot user agent. The HTML, JavaScript, structured data, internal links, and metadata that Google sees are all the mobile versions. If your mobile site hides or strips content that exists on desktop, that content is functionally invisible to Google.

This is different from "mobile-friendly" (a much older concept). Mobile-friendly meant the site rendered acceptably on mobile. Mobile-first indexing means Google treats the mobile version as canonical.

If your site uses responsive design with no mobile-specific content stripping, you're already fine. If you have a separate mobile site (m.example.com) or use mobile-specific JavaScript that hides content, audit for parity. Critical checks:

• Same primary content on mobile and desktop (don't hide product descriptions, FAQs, or specs on mobile).
• Same structured data on mobile and desktop.
• Same internal links on mobile and desktop (don't strip the footer link section).
• Same metadata: title tags, meta descriptions, canonicals, hreflang.
• Same images with same alt text and structured data.

Responsive design (one HTML, CSS reflows for screen size) is Google's recommended pattern and the simplest to maintain. Adaptive design (server detects device and serves different HTML to mobile vs desktop) works but requires careful parity. Separate mobile sites (m.example.com) are legacy and add complexity; migrate to responsive when you can.

Mobile-specific UX failures Google penalizes: intrusive interstitials (full-screen popups that block content), text too small to read without zooming, tap targets too close together, content wider than the viewport. The Mobile Usability report in Search Console flags these directly.

Mobile networks and devices are slower than desktop. Core Web Vitals on mobile are usually 30–50% worse than desktop on the same site. Optimization energy should disproportionately target mobile, where the user base is and where the SEO bar is harder.