# Mobile-first indexing: what to check on mobile

> Compare mobile and desktop content, links and directives through a missing purchase condition and an editable parity register.


**Mobile-first indexing means that Google uses the mobile version of content for indexing and ranking.** A complete desktop page can therefore give a misleading picture of what Google obtains if important conditions are absent on mobile.

[Google’s mobile-site guidance](https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) calls for equivalent main content, accessible resources and consistent directives. Responsive design makes sharing HTML and URLs easier, but calling a template “responsive” does not verify what it delivers or loads.

## Materials are included, but the mobile page omits them

This is a hypothetical case. On desktop, a class page says “Clay and firing included; collection at a later date”. A mobile template change removed that condition to shorten the page. Both versions still show the booking button.

The chosen fix is to restore the condition on mobile. It can sit in a collapsible section if the information remains accessible and loaded; placement and design need not be identical. The team verifies equivalent information before celebrating the higher position of the button.

| Element | Scenario comparison | Decision |
| --- | --- | --- |
| Materials and collection | Complete on desktop; missing on mobile | Restore the information |
| Price | Visible in both versions | Keep it and check that values match |
| Requirements link | HTML link on desktop; button fetching text after a click on mobile | Make main content available without that action |
| Robots directive | Allowed on desktop; test-template `noindex` remains on mobile | Remove the accidental exclusion from the public version |

The rows illustrate content, loading and configuration defects. They are not findings from a HeyMark or client audit. Adapt the [mobile/desktop parity CSV](/resources/mobile-parity-en.csv), which preserves all four cases and the evidence needed after a fix.

## A collapsed section is not necessarily missing content

Google distinguishes presentation from content availability. A section collapsed to save space can retain equivalent information. The example’s issue arises when pressing a control is necessary to fetch the main content for the first time: Google warns that it does not load content requiring interactions such as clicking or typing.

The website team should compare what the smartphone crawler receives and can process, rather than merely narrowing a desktop screenshot. The [JavaScript SEO article](/en/guides/javascript-seo/) helps distinguish initial HTML, the browser DOM and Google’s processing.

## What each check establishes

Visual inspection can reveal the missing condition. Reading the HTML and rendered result helps locate where it disappeared. Search Console URL Inspection supplies Google’s information about that URL and, when using the live test, current accessibility; a successful test does not promise indexing or a ranking.

After the change, open the public page on mobile and confirm that materials, collection and requirements can be understood before booking. Also review relevant images, alt text and headings. A font-size change or Lighthouse score does not replace that comparison; performance and content availability need different checks.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
