Google indexes and ranks the mobile version of your site, so any content that exists on desktop but not on mobile does not count. The fix is a parity check: the same primary content, headings, robots tags, structured data and metadata on both versions, with nothing important hidden behind a tap. Layout may differ; content should not.
Mobile-first indexing is old news that still catches businesses out, because the way it fails is quiet. No error appears. A designer makes the mobile page “cleaner,” the content that got trimmed was the content that ranked, and traffic slides for months before anyone connects the two.
This is a checklist, built from Google’s own documentation, for the business owner who wants to confirm that the mobile version of their site says everything the desktop version does.
1. What mobile-first indexing actually means
Google indexes and ranks the mobile version of a site. That sentence from Google’s documentation is the whole concept, and it is more specific than “your site should be mobile friendly.” A mobile-friendly design is about how pleasant the page is on a phone. Mobile-first indexing is about which version of your content Google reads to decide what the page is about.
A separate mobile version is not required, though Google strongly recommends one. Of the three ways to build one, responsive design is the one Google recommends because it is the easiest to maintain and serves the same content and metadata on every device.
2. Three myths that cause trouble
“My site is responsive, so I am safe.” Responsive design removes most of the risk, because the same HTML is served to every device. It does not remove it. Page builders let you hide individual sections on small screens, and themes sometimes swap in a shortened block on mobile. A responsive site can still have a thinner mobile page than desktop page.
“Most of my customers use desktop, so mobile does not matter.” Your audience mix is irrelevant to which version Google reads. Even if every customer you have books from a desktop, the mobile version is the one that defines what Google knows about the page.
“Mobile-first means my desktop design has to be worse.” It does not. Layout is allowed to differ between versions. The requirement is about content parity, so a rich desktop experience is fine as long as the same information is available on mobile.
3. The one rule that matters
Google indexes only what appears on the mobile version. Content that exists on desktop and not on mobile does not contribute to indexing, and Google warns that intentionally keeping less content on mobile can cost you some traffic.
That scenario is common. We see it most often after a redesign, where a designer shortens the mobile page for a cleaner look, and again with the “hide on mobile” switch that many page builders provide. If the hidden element carries real content, treat it as missing from the version Google reads. Both mistakes are invisible when you review the site on a laptop, which is why the check below starts on a phone-sized view.
4. The checklist
Work through these in order. Items one to four cause most of the damage we find.
- Primary content matches. The mobile page should carry the same main content as the desktop page. Layout can differ, and accordions and tabs are fine.
- Headings match. Same structure, same wording, so Google reads the same outline.
- Robots meta tags match. Mobile pages must not carry noindex or nofollow where desktop does not, since that can stop crawling or indexing.
- Nothing important waits for a tap. Google will not swipe, click or type to trigger content. Lazy loading that needs a user action will hide that content from the index.
- Structured data matches. Both versions should carry the same markup. Google’s guidance suggests prioritizing Breadcrumb, Product and VideoObject if you cannot cover everything.
- Titles and meta descriptions are equivalent.
- Images and video are accessible. Use supported formats and stable URLs, and keep alt text and captions the same. Changing image URLs on mobile can cause a temporary loss of image traffic.
- Google can crawl what it needs. Do not block CSS, JavaScript or image files with robots.txt, and generally use the same rules for both versions.
5. What you are allowed to change
Nothing here means a mobile page must look like the desktop page. Google’s documentation states that layout may differ, for example by using accordions or tabs, as long as the content and headings are the same. It even suggests hiding content in accordions or tabs rather than removing it when a page feels long.
This is also where mobile performance enters the picture. Heavy images and scripts that were tolerable on a desktop connection fail on a phone, which is why the mobile pass rate in our Core Web Vitals guide is eight points lower than desktop.
6. If you still run a separate mobile site
A separate mobile site on its own address, usually an m-dot version, needs extra care. Google’s guidance for that setup includes: keep error page status consistent between versions, avoid URL fragments, do not redirect several desktop pages to a single mobile page, verify both versions in Search Console, keep hreflang links pointing between matching versions, set the desktop URL as canonical with the mobile URL as its alternate, and make sure the mobile server can handle a higher crawl rate.
Our honest advice is to retire it. Maintaining two versions of every page doubles the places a mismatch can hide. If you do retire it, treat the change as a migration and follow our guide to website migration without losing rankings, because every mobile URL needs a redirect to its responsive equivalent.
7. A twenty-minute test you can run today
Pick your five most valuable pages: the ones that bring in enquiries. Open each on a phone, or in your browser’s device view, and scroll the whole page. Write down every section that appears on desktop and is missing here. Then run the URL Inspection live test in Search Console on each page and look at the rendered result Google gets. If a section is missing from that view, it is missing from the index.
Finish by looking at Settings in Search Console, which tells you which crawler Google uses for your site. If the mobile and desktop versions of your content differ and you are unsure which should win, the answer is always mobile.
If your site was built years ago or by a page builder with many mobile overrides, we can run this checklist across your key pages and report the gaps as part of a website design and development review.
Make sure Google is reading everything you wrote
We compare your mobile and desktop pages, test what Google actually renders, and list every gap, ranked by the pages that bring in leads.
Request a mobile parity reviewFrequently asked questions
What is mobile-first indexing?
It means Google primarily uses the mobile version of a page’s content for indexing and ranking. It is about which version Google reads to understand the page, not about how attractive the mobile design is.
Does my desktop content still count if it is missing on mobile?
No. Google says it indexes only what appears on the mobile version, so content missing from mobile does not contribute to indexing. If you must shorten a mobile page, Google suggests placing the content in accordions or tabs rather than removing it.
Do I need a separate mobile website?
No. Google says a mobile version is not required but strongly recommended, and it recommends responsive design as the easiest setup to maintain because content and metadata are the same on every device.
Can I use accordions and tabs on mobile?
Yes. Google’s documentation says layout may differ between versions, for example with accordions or tabs, provided the content and headings match. The risk is content that is removed or that needs a tap or swipe to load.
Should structured data be on the mobile version too?
Yes. Google says both versions should carry the same structured data, with mobile URLs in the markup where they are separate. If you cannot cover everything, its guidance suggests starting with Breadcrumb, Product and VideoObject.
How do I check what Google sees on my mobile pages?
Use the URL Inspection live test in Search Console on each key page and review the rendered result. Compare it with the page on a phone-sized view. Any section missing from the render is missing from the index.
Sources
- Google Search Central: “Mobile-first indexing best practices” (page last updated December 10, 2025). Statements that Google indexes and ranks the mobile version, that content and headings should match, robots meta tags, lazy loading, structured data, metadata, image and video guidance, separate mobile URL guidance, crawlable resources, and desktop-only content not being indexed.
- HTTP Archive, Web Almanac 2025, Performance chapter (July 2025 Chrome field data): 48% of mobile and 56% of desktop websites passing all three Core Web Vitals.
Note: the order of the checklist and the common causes we mention (trimmed mobile pages, “hide on mobile” switches) come from our audit experience. The mobile and desktop examples in Figure 1 are illustrative and not client data.
Reference: Read the original research or documentation.

Muhammad Asjad Khan is a seasoned digital marketer and the Chief Operating Officer at Digital Age, where he leads strategy, innovation, and client success. With years of experience in SEO, content marketing, and performance-driven digital campaigns, Asjad is passionate about helping brands grow their online presence and achieve measurable results. When he’s not optimizing websites or scaling marketing strategies, he’s exploring the latest trends in tech and digital media