Part of the Technical SEO Audit series. For the full picture, start with Technical SEO audit: the complete guide and checklist.
A desktop page can contain an excellent product description while its mobile template shows only a short grid. A quick visual check might call the mobile page “fine.” A mobile-first indexing audit asks a different question: what can Smartphone Googlebot actually access, render and use?
What does a mobile-first indexing audit check?
Google says it uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking. Its mobile-first indexing best practices focus on accessible resources, equivalent primary content, matching metadata and structured data, and usable images and videos. Audit those signals on representative pages, especially templates where desktop and mobile are served differently.
Start with one high-traffic page from each template: homepage, category, product, article, and any special page type. Compare the server response and rendered DOM at mobile and desktop sizes. Include a page with long content, one with pagination, and one with media. A template-level omission can affect far more URLs than a one-off broken image.
Is the primary content present on mobile?
The main text, headings, product details and important links should be equivalent across versions. Equivalent does not mean identical layout. Google explicitly allows mobile content in tabs or accordions, but warns against loading primary content only after a user interaction such as clicking or swiping. If JavaScript creates the content, use Search Console URL Inspection to inspect Google’s rendered page rather than trusting a desktop browser view.
| Audit area | Mobile failure to look for | Evidence to collect |
|---|---|---|
| Main content | Shortened description or missing article sections | Rendered mobile DOM beside desktop |
| Links | Category or pagination links absent on mobile | Crawlable <a href> links in both renders |
| Metadata | Different title, description or robots directive | Response HTML and rendered head |
| Structured data | Product or Breadcrumb markup missing | Rich Results Test or rendered source |
| Media | Missing primary image, alt text or video | Mobile render and resource requests |
The JavaScript SEO guide covers rendering failures. The technical SEO audit pillar puts this audit in a larger fix order.
Can Smartphone Googlebot access the page and its assets?
Check robots.txt and robots meta rules for the mobile response, as well as resource URLs loaded only on mobile. Google’s guidance warns that a mobile-only noindex or nofollow can prevent intended indexing, and that blocked assets may prevent Google from seeing important content. Test HTTP status, redirects and robots directives as the smartphone crawler, not only as a desktop browser.
Inspect lazy-loaded content carefully. Images and sections that load as they enter the viewport can be compatible with crawling, but content that requires a click, swipe or typing to load is a different risk. The lazy-loading SEO guide covers that distinction.
Do titles, structured data and images match?
Google recommends equivalent titles and meta descriptions, the same relevant structured data, and comparable image content on mobile and desktop. For separate mobile URLs, structured-data links should use the correct mobile URLs. Compare important image URLs, alt text, captions and file availability. A tiny or missing product image is not repaired by identical page text.
Prioritize discrepancies on pages with search demand and on shared templates. A missing Product object on every mobile product page is more urgent than a single decorative image mismatch. Validate a few affected URLs after the template fix, then re-crawl the whole segment.
What changes for separate mobile URLs?
If the site uses m.example.com, audit each desktop/mobile pair. Google’s separate-URL guidance uses a canonical from the mobile URL to the desktop URL and an alternate annotation from desktop to mobile. Check that redirects lead to the corresponding page, not a generic mobile homepage; that both versions return the intended status; and that hreflang, when used, connects mobile versions to mobile versions.
A responsive one-URL site avoids these pairing details but still needs content and rendering checks. Mobile-first indexing is not a reason to create an m-dot site. It is a reason to verify the mobile experience you already serve.
Mobile-first indexing audit checklist
- Sample important URLs from every major template
- Compare mobile and desktop primary content, headings and crawlable links
- Inspect Smartphone Googlebot’s rendered page and resource access
- Check mobile robots.txt behavior, meta robots and HTTP responses
- Confirm titles, descriptions and structured data are equivalent
- Verify primary images, alt text and video availability
- For m-dot, test canonical, alternate, hreflang and page-to-page redirects
- Recheck representative pages and affected templates after fixes
The goal is parity of useful information and signals, not pixel-for-pixel parity of layout.
Frequently asked questions
Is mobile-first indexing the same as mobile page speed?
No. Mobile-first indexing concerns which version of page content Google primarily uses for indexing. Page speed and Core Web Vitals are separate experience measures, although the same mobile page can have problems in both areas.
Must mobile and desktop pages look identical?
No. Layout can change for a small screen, including use of tabs or accordions. Keep the primary content and important signals equivalent and accessible without requiring a click to load them.
What if my site uses responsive design on one URL?
Responsive design avoids many separate-URL annotation issues, but it can still hide or omit content, links or assets at mobile widths. Inspect the rendered mobile DOM and Smartphone Googlebot's view of representative pages.
Should an m-dot mobile page canonicalize to itself?
For Google's separate-URL setup, the mobile URL normally points via canonical to the desktop URL, while the desktop page marks the mobile URL as its alternate. Verify the current pairing guidance rather than applying a one-URL responsive template to m-dot pages.