Mobile-first indexing, from 2016 test to 2023 completion

Mobile-first indexing is not a 2026 story so much as a finished one: Google announced the switch essentially complete in October 2023, nearly seven years after the first public test. What is current in 2026 is Google’s own documentation describing what that switch means day to day, and the parity failure mode it still warns sites about.

The rollout, in Google’s own dated posts#

Google first announced it was testing mobile-first indexing on 4 November 2016, on the Search Central (then Webmaster Central) blog. The idea: since most searches happen on mobile devices and most sites still built desktop-first, Google would start basing indexing on the mobile version of a page’s content rather than the desktop version, for the sites it selected for the experiment.

The public, site-by-site rollout followed in “Rolling out mobile-first indexing,” published in March 2018, and continued through further posts in May 2019 (mobile-first indexing set as the default for newly created domains) and March 2020 (“Announcing mobile first indexing for the whole web”). Google extended its own deadlines more than once as sites it had flagged were not yet ready; a July 2020 post and a November 2021 update both describe the same pattern of pushing the remaining sites over individually rather than on a single fixed date.

Google declared the transition complete on 31 October 2023, in a post titled “Mobile-first indexing has landed.” Google did not publish a completion percentage. The post instead describes a small remaining category of sites - those broken on mobile devices, blocking the mobile crawler via robots.txt, or redirecting all mobile traffic to a homepage - that Google would keep crawling with the legacy desktop Googlebot indefinitely, because there is no usable mobile version to index. Search Engine Land’s coverage of the same announcement quotes the post’s framing directly: the “trek to Mobile First Indexing is now complete.”

What it means in practice, and the common failure mode#

Google’s current mobile-first indexing documentation states the mechanism plainly: Google crawls, indexes and ranks using the mobile version of a page’s content, fetched with the smartphone crawler. Its Googlebot documentation adds the crawl-side consequence of that: for most sites, the majority of Googlebot crawl requests now use the smartphone crawler, with a minority still using the desktop crawler for the exceptions described above.

The parity requirement is the part that produces real ranking losses. Google’s documentation is explicit that structured data must match between mobile and desktop versions of a page, that title elements and meta descriptions must be equivalent across both, and - most consequentially - that “if your mobile site has less content than your desktop site” the fix is updating the mobile version so its primary content is equivalent to desktop’s. Content that exists only on the desktop version of a page is not indexed at a discount; under mobile-first indexing it is not indexed at all, because Google never sees it. Sites that once built a stripped-down “mobile view” as a performance shortcut, or that still hide secondary content behind a mobile accordion that never loads in the DOM, are describing exactly the failure mode this documentation names.

Why we care#

Mobile-first indexing is not a project with an open action item for most sites anymore; Google finished the rollout in 2023 and now treats it as the default mechanism, not a migration in progress. The item worth auditing in 2026 is narrower and easy to miss: pull up your own mobile rendering with Search Console’s URL Inspection tool and compare it, section by section, against desktop. Any text, image, or structured-data block present on desktop and absent on mobile is invisible to Google, not merely deprioritized - and that gap is the one Google’s own documentation still calls out by name.