If it isn’t on mobile, it isn’t indexed
Structure and markup refreshed for current answer engines; the original analysis is preserved.
Google has set the end of March 2021 as the point when every remaining site moves to mobile-first indexing. From then on it reads, indexes, and ranks your site from the mobile version — and, as Google has said plainly, anything that exists only on desktop is dropped. If your mobile site is a trimmed-down copy, that copy is now the whole site as far as Google is concerned. The work for the next three months is parity.
the short answer
At the end of March 2021, Google moves all remaining sites to mobile-first indexing: it reads and ranks you from the mobile version, and — in Google’s own words — drops anything that’s only on desktop. There’s no separate mobile index. If your mobile site is lighter — less text, missing structured data, blocked resources — that gap leaves the index. The work now is parity.
key takeaways
- Google plans to move every remaining site to mobile-first indexing at the end of March 2021, finishing a transition most sites are already part of.
- From then on, Google reads, indexes, and ranks your site from the mobile version — and, in Google’s own words, drops anything that exists only on desktop.
- There is no separate mobile index. Mobile-first just means which version of your page Google uses to build its single index — and that version is now mobile.
- The sites most at risk are those with a lighter mobile version: less text, omitted structured data, blocked resources — because everything missing from mobile leaves the index.
- The work before March is parity: the same primary content, headings, structured data, and metadata on mobile as on desktop — a complete site, not a courtesy copy.
what Google now reads
After the switch, the right-hand version is the only one Google sees — so every gap between it and the left-hand version is content quietly leaving the index. Parity closes the gap.
The change, in four parts
What lands at the end of March; what it means for your content; why it is really about parity; and what to do before the deadline. Open each part.
01 What lands at the end of March
Google has set the end of March 2021 as the point at which it intends to move essentially every remaining site to mobile-first indexing. It is worth putting this in context, because for many sites it is not news at all. Google began this transition years ago, introducing mobile-first indexing in 2016, switching sites steadily ever since, making it the default for newly discovered sites in mid-2019, and by the start of this year it had already moved most crawled sites over. The original plan was to finish for all sites in September 2020; Google then extended the timeframe to the end of March 2021, acknowledging that the year had made it hard for everyone to focus on the work. So the deadline approaching is the last step of a long migration, not a sudden new policy. What it means concretely is this: mobile-first indexing is simply Google crawling your site with its smartphone Googlebot and using the mobile version of your pages to index and rank you, rather than the desktop version. One clarification heads off a common confusion — there is no separate mobile index. Google maintains a single index; mobile-first only describes which version of your page it reads to build that index. If your site was switched long ago, the March deadline changes nothing for you. But if you are among the sites still indexed from desktop, March is when Google starts reading you from mobile instead — and whether that is uneventful or disruptive depends entirely on one thing: how closely your mobile version matches your desktop one. That is the question this deadline really asks, and the next three months are the time to answer it.
02 What it actually means for your content
The heart of mobile-first indexing, and the part most often underestimated, is what happens to content that lives only on your desktop version. The intuitive assumption is that Google treats mobile as the primary view but still keeps desktop content in reserve, seeing everything either version offers. That assumption is wrong, and Google has said so without hedging. John Mueller stated it plainly: once a site is shifted to mobile-first indexing, Google will drop everything that is only on the desktop site and essentially ignore it, so anything you want indexed needs to be on the mobile version. Read that carefully, because it is stronger than it sounds. The mobile version is not the primary source with desktop as a backup; under mobile-first indexing the mobile version is effectively the only source Google consults. The implications cascade. If your mobile page carries less body text than your desktop page, the difference is simply absent from Google’s understanding of you. If your mobile template drops the structured data your desktop template carries, that markup no longer exists as far as the index is concerned. If a block of content is hidden on mobile, collapsed behind a tap the crawler will not perform, or injected by a script the crawler does not run, it is functionally invisible. None of this is punitive — Google is looking at the version your users actually see, which is a reasonable thing to do. But the rule it produces is unforgiving and worth stating flatly: whatever is not present in your mobile version is not present in Google’s index, full stop. That single sentence is the whole reason this deadline deserves attention.
03 Why this is really about parity
Step back and the issue underneath mobile-first indexing is a mismatch problem: the danger is not mobile itself but any gap between your mobile and desktop versions, because that gap is exactly what falls into the void when Google stops reading desktop. For a long time the prevailing practice cut directly against parity. It was considered good craft to give mobile users a lighter experience — trim the text, drop some images, simplify the navigation, sometimes strip back the markup — on the sensible-sounding theory that small screens and slower connections deserved a leaner page, with the full version reserved for desktop. Under desktop indexing none of that cost you anything, because Google read the complete desktop version no matter what mobile displayed. Mobile-first indexing turns that arrangement inside out: the lean mobile version becomes the one Google reads, and every piece of content and markup you deliberately kept only on desktop drops out of the index. The cruel irony is that the sites most exposed are often the ones that took mobile seriously enough to build a carefully reduced experience, because their mobile-desktop gap is the widest. This is why the right framing is parity rather than mobile-friendliness. The question is not merely whether your mobile site is usable; it is whether your mobile site is complete — whether the primary content, the headings, the structured data, the metadata, and the meaningful internal links all exist in the mobile version, even if styled and laid out for a small screen. A leaner presentation is perfectly fine. A leaner body of indexable substance is the failure mode. Parity of substance, not identical pixels, is the standard mobile-first indexing actually demands.
04 What to do before the deadline
The preparation is a checklist with a single principle behind it: make your mobile version a complete representation of your site, because in a few months it will be the only version Google reads. Begin with primary content — confirm the mobile page carries the same main text, the same headings, and the same meaningful images as desktop, not a trimmed subset. Then structured data: verify that every piece of markup on your desktop template also appears in your mobile template, since anything present only on desktop will be lost when the switch happens. Make sure Googlebot can fetch all the resources the mobile page depends on, because a common and quiet failure is a robots.txt that blocks CSS, JavaScript, or images for the mobile site, leaving the crawler unable to render the page as a person would. Scrutinise lazy-loading and any content placed behind a tap or click: if primary content appears only after an interaction the crawler does not perform, it will be treated as absent, so load it such that it is present without interaction. Confirm that titles, descriptions, and robots meta tags match across versions — a stray noindex sitting on the mobile template alone becomes a disaster the moment mobile-first takes over. And use Search Console, which notifies you when Google moves your site and which reports, through the URL inspection tool, whether a given page was crawled by the smartphone or the desktop Googlebot, so you can confirm where you stand. Underneath every item is the same correction of mindset: stop thinking of the mobile page as a reduced courtesy version of the real, desktop site, and start treating it as the canonical, complete site it is about to become. Building your mobile version as the full, authoritative representation of your content — not an echo of it — is the structural discipline the AC Group has worked by for 27 years.
Why this is a structure problem, not a design one
It is tempting to file mobile-first indexing under design — something for whoever owns the responsive layout to worry about. But the thing at stake is not how the page looks on a phone; it is what exists in the page’s markup and content when the smartphone crawler reads it. A site can look flawless on mobile and still be quietly amputated in the index, because the missing pieces — the structured data on a stripped template, the section that only renders after a tap, the resource the crawler cannot fetch — are invisible to a human reviewer admiring the layout. This is why parity has to be checked at the level of content and markup, not appearance: the question is not is the mobile page nice but does the mobile page contain everything the index needs.
That framing matters beyond this one deadline, because mobile-first indexing is an early, concrete instance of a principle that keeps recurring: the version of your page a machine actually reads is the version that counts, and it is often not the version a person is looking at. Whatever Googlebot fetches and parses — not what renders beautifully for a user — is what becomes your presence in search. Building pages whose structure and substance are fully present for the crawler, rather than assuming a good-looking render is enough, is the discipline this deadline forces early and the AC Group has worked by for 27 years.
What to do with this
Between now and the end of March, audit your mobile version against your desktop version for parity of substance, not appearance. Walk through the list: is the primary content — main text, headings, meaningful images — fully present on mobile? Is every piece of structured data from the desktop template also in the mobile template? Can Googlebot fetch all the CSS, JavaScript, and images the mobile page needs, or does robots.txt block them? Is any primary content hidden behind a tap, a click, or a lazy-load the crawler will not trigger? Do titles, descriptions, and robots meta tags match, with no stray noindex on the mobile side? Each gap you find is content that will leave the index the moment Google switches you over.
Then watch Search Console: it tells you when your site is moved to mobile-first, and the URL inspection tool reports whether a page was crawled by the smartphone or desktop Googlebot, so you can confirm your status rather than guess at it. Above all, make the mental correction this change requires — the mobile version is not a reduced courtesy copy of the real site, it is about to become the real site, the canonical and complete representation of everything you want Google to know about you. Building your mobile version as that full, authoritative site rather than an echo of a desktop original is the structural discipline the AC Group has worked by for 27 years.
Mobile-first indexing, plainly: quick answers
What is mobile-first indexing, and what changes at the end of March?
Mobile-first indexing means Google crawls your site with its smartphone Googlebot and uses the mobile version of your pages — not the desktop version — to index and rank you. This is not new in itself: Google has been moving sites to it for years, it became the default for newly discovered sites back in mid-2019, and by early this year most crawled sites were already on it. What changes at the end of March 2021 is that Google plans to move essentially all remaining sites over, finishing the transition it had originally aimed to complete in September 2020 before extending the timeframe. So for many sites nothing changes — they were switched long ago. But for any site still being indexed from its desktop version, the end of March is when Google starts reading it from mobile instead, and that switch can be consequential if the mobile and desktop versions are not equivalent. It is worth being clear about one common confusion: there is no separate mobile index. Google has only one index; mobile-first simply refers to which version of your page it uses to build that index. The practical question every site owner should ask before March is therefore simple — if Google looked only at my mobile version and ignored my desktop version entirely, would it still see everything that matters? For a lot of sites, the honest answer is no, and that is the gap to close.
Does Google really ignore my desktop content under mobile-first?
Yes, and Google has been unusually blunt about it, which is why this matters more than it first appears. Google’s John Mueller put it directly: once a site is shifted to mobile-first indexing, Google will drop everything that is only on the desktop site and essentially ignore it — so anything you want indexed needs to be on the mobile version. That is the whole point people miss. A widespread assumption is that Google will still see desktop content as a fallback, treating mobile as merely the primary view; that is not how it works. Under mobile-first indexing the mobile version is not the primary source, it is effectively the only source. If your mobile page carries less text than your desktop page, the missing text is missing from Google’s view of you. If your mobile template omits the structured data your desktop template includes, that markup is gone. If a section of content is hidden on mobile, collapsed behind an interaction Googlebot does not trigger, or loaded in a way the crawler does not execute, it may as well not exist. None of this is a penalty and none of it is hostile — Google is simply looking at the version most of your users see. But the consequence is strict: the mobile version defines what you are to Google, and whatever is not in it is not in the index.
My mobile site is a lighter version of desktop — is that a problem?
It can be a serious one, because a lighter mobile version is exactly the situation mobile-first indexing punishes, even though no penalty is involved. For years it was common practice to give mobile users a streamlined experience — less text, fewer images, simplified navigation, sometimes stripped-back markup — on the reasonable theory that mobile screens and connections warranted a leaner page, while the full content lived on desktop. Under desktop indexing that was fine, because Google read the full desktop version regardless of what mobile showed. Under mobile-first indexing it inverts: the lean mobile version is now the one Google reads, and all the content and markup you kept only on desktop falls out of the index. The sites most at risk are precisely the ones that invested in a careful, trimmed mobile experience, because their gap between mobile and desktop is largest. The fix is not to bloat the mobile page back up thoughtlessly, but to ensure parity of substance: the primary content, the headings, the structured data, the metadata, and the internal links that matter should all be present in the mobile version, even if presented in a mobile-appropriate way. A leaner layout is fine; a leaner body of indexable content and markup is the problem. Closing that gap before the end of March is the single most important piece of preparation for most sites.
What should I check before the end of March?
Check, on your mobile version specifically, that nothing important is missing or hidden from Googlebot. Start with the primary content: confirm the mobile page contains the same main text, the same headings, and the same images that carry meaning, not a reduced subset. Confirm your structured data is present in the mobile template, not just the desktop one, since markup that exists only on desktop will be lost. Make sure Googlebot can actually fetch all the resources the mobile page needs — a frequent failure is a robots.txt that blocks CSS, JavaScript, or images for the mobile site, so the crawler cannot render the page as a user would. Be careful with lazy-loading and content tucked behind taps or clicks: if primary content only appears after an interaction the crawler does not perform, treat it as invisible and load it so it is present without interaction. Check the same metadata — titles, descriptions, robots meta tags — matches across versions, because a stray noindex on the mobile template is a catastrophe under mobile-first. And watch Search Console, which notifies you when Google moves your site over and which shows, in the URL inspection tool, whether a page was crawled by the smartphone or desktop Googlebot. The throughline is one idea: your mobile version is now your site, so make it a complete site rather than a courtesy version. Treating the mobile page as the canonical, complete representation of your content — not a reduced echo of it — is the structural discipline the AC Group has worked by for 27 years.
A note on sources and timing
This is written in December 2020. We have described mobile-first indexing as Google has set it out — introduced in 2016, the default for new sites since mid-2019, already covering most crawled sites, and planned to extend to all remaining sites at the end of March 2021, after the original September 2020 target was pushed back. The key point — that Google drops content existing only on desktop once a site is switched — comes from Google’s John Mueller, speaking this year, and the preparation items (primary content, structured data, crawlable resources, lazy-loading, matching metadata, Search Console signals) follow Google’s own guidance for getting ready. The durable point outlasts the deadline itself: the version a machine reads is the version that counts, so whatever is not on your mobile site is not in the index — the parity discipline the AC Group has worked by for 27 years.