What Is Mobile First Indexing?
Complete rather than pending, which stopped being news some time ago. The mobile version of your page is the version assessed, which turns this into a question about content rather than layout: if something is missing from the mobile version, it is missing.
This Is Now Just How It Works
Mobile first indexing is not a change coming to your site. It happened, it finished, then the mobile version of a page became simply the version assessed. Guidance treating it as an approaching deadline is describing something that concluded.
What it means. One version is the reference.
Where a site presents differently on a phone and a desktop, the phone version is the one taken as the site. Anything only on the desktop version is effectively not there.
Why it happened. Where people are.
Most searching happens on a phone, so assessing a desktop version was assessing something most visitors would never see. The change aligned the assessment with the reality.
Why it stopped being news. Everybody moved.
Sites converged on designs that adapt to any screen, which removed the problem for most of them. The transition is complete and the discussion moved on.
What still catches sites out. Differences nobody intended.
A responsive design does not guarantee the two views are equivalent. Content can still be hidden, shortened or dropped at smaller sizes without anybody deciding to, which is blocks two and four.
Why this page is mostly about that. It is what remains.
The concept is settled. The practical question of whether your mobile version is genuinely as good as your desktop one is not. On many sites the answer is no.
Which Makes It A Content Question
If content, links or descriptions are missing from the mobile version, they are missing. That is the practical issue here. It is nothing to do with how the page looks.
Content. The obvious case.
Text shortened or removed on smaller screens is text your page no longer has. A page with three paragraphs on a phone and twelve on a desktop is a three paragraph page.
Links. The one nobody checks.
Navigation simplified for mobile can drop links to sections that are then harder to reach. That affects how the whole site is understood rather than one page.
Descriptions. The quiet one.
Structured descriptions present on one version and not the other. Rarely deliberate and entirely possible where the two versions are built separately.
Why this is not a design failure. Nobody made this decision.
These differences accumulate from reasonable individual choices about small screens. No single decision looks wrong. The aggregate is a smaller site.
What the check is. Compare the two.
Look at an important page on a phone and on a desktop and ask what is present on one and absent on the other. That is the whole diagnostic and almost nobody performs it.
Responsive Design
One page that adapts to whatever screen requests it. It became standard because it avoids the entire problem of versions differing, which is a structural advantage rather than an aesthetic one.
What it means. One address, one page.
The same page arrives on every device and arranges itself for the space available. There is no separate mobile site and no decision about which version to serve.
What it replaced. Separate mobile sites.
Sites once maintained a distinct mobile version at its own address. Two sets of pages, two sets of content and a permanent question about whether they matched.
Why the old approach caused trouble. Drift.
Two versions maintained separately diverge, because updates get made to one. Every problem in block two existed permanently rather than occasionally.
Why it does not solve everything. Adapting can still mean hiding.
A responsive page can rearrange or conceal content at smaller sizes. Being one page removes the version problem and does not remove the content problem.
What we will not recommend. A framework.
How a site achieves this is a development decision. Naming a technology here would be advice we are not positioned to give about a site we have not seen.
Hiding Content On Mobile
Content collapsed, tabbed or removed on smaller screens is a design decision with a search consequence. The three are not equivalent. The distinction is worth understanding before anybody panics.
Collapsed content. Present but folded.
Text behind an expander, still in the page and reachable by tapping. This is generally fine, since the content exists and a visitor can get to it.
Tabbed content. Usually present.
Sections behind tabs, where the content is normally all there and only one part is displayed. Similar to collapsed content in most implementations.
Removed content. The genuine problem.
Content that is not delivered at all on smaller screens, else loaded only if somebody performs an action. That content is absent rather than hidden, which is a different situation entirely.
Why the distinction matters. Panic in the wrong direction.
Businesses are told that hidden content is penalised and respond by unfolding everything, producing an unusable page. Folding is not the problem. Not delivering is.
The usability point underneath. Expanders exist for a reason.
A phone screen genuinely cannot show everything at once, so collapsing is a sensible answer. Designing as though it were forbidden makes the mobile experience worse for the visitors it was meant to serve.
What Mobile SEO Covers Now
Largely usability and speed rather than a separate discipline. The idea of mobile SEO as its own specialism belongs to the period when sites had two versions.
What it used to mean. A separate exercise.
When a mobile site was a distinct property, it needed its own attention: its own addresses, its own content and its own problems. That situation has largely disappeared.
What it means now. Ordinary quality on a small screen.
Whether the page loads quickly, whether it can be used with a thumb and whether it contains what the desktop version contains. None of that is a separate discipline.
Where speed belongs. The hosting pillar.
Loading time is mostly determined by the server and by page weight, which how web hosting affects SEO covers. It is not a mobile subject as such, although a phone on a poor connection feels it first.
Where usability belongs. Design.
Tap targets, readable text and forms that can be completed on a phone are design work with a search consequence rather than technical work.
Why the term persists. It sells.
Mobile SEO sounds like a distinct service that can be bought separately. In practice, a business buying it is buying usability review and performance work under another name.
Testing
A dedicated tool once gave a straightforward answer about whether a page was mobile friendly. It was retired, along with the report and the interface that supported it.
What went. Three things together.
From 1 December 2023, Google retired Search Console's mobile usability report, the mobile friendly test tool and the associated interface for it. Access was removed and the tool stopped returning results.
What Google said about it. Not that it stopped mattering.
The announcement stated that mobile usability remains critical for users, that it remains part of Google's page experience guidance, adding that many other robust resources for evaluating it had emerged in the nearly ten years since the tools launched.
What replaced it. Broader auditing.
Google pointed at general purpose auditing tools built into browsers, which assess performance, accessibility and usability together rather than answering one question. More useful and less convenient.
What to check now. The same things.
Whether text is readable without zooming, whether tap targets are far enough apart, whether the page fits the screen without sideways scrolling and whether anything is missing. The criteria did not change when the tool went.
Why this block exists. The advice persists.
Guidance still directs people to a tool retired years ago. Anybody sent to it will find it gone, which is confusing rather than merely unhelpful.
Usability Errors
Four problems account for nearly all of what gets flagged. Each has a different level of seriousness. None is a search problem first.
Text too small to read. The serious one.
Content requiring somebody to zoom before they can read it. That is a real failure and visitors leave rather than pinching, which makes it worth fixing regardless of anything else.
Tap targets too close together. The frustrating one.
Links or buttons packed tightly enough that a thumb hits the wrong one. Worst in navigation and on forms, where the wrong tap costs somebody their progress.
Content wider than the screen. The obvious one.
A page requiring sideways scrolling, usually caused by one oversized element such as a wide image or table. Visible immediately on any phone.
Fixed width layouts. The legacy one.
A page built for a desktop screen and shown shrunk. Rare now and unmistakable, indicating a site that has not been touched in a long time.
What they have in common. Visitors notice first.
Every one is a problem for a person before it is a problem for a search engine. Where the reports live is covered in our Google Search Console material.
Accelerated Mobile Pages
A stripped-down page format built for speed on phones. The requirement that drove its adoption was removed, many sites have retired it, then a business still maintaining it should ask why.
What it was for. Speed, plus access.
A restricted format that loaded very quickly. Its real appeal was that using it was required to appear in the news carousel at the top of mobile results.
What changed. The requirement went.
In June 2021 the page experience update removed the requirement to use the format to appear in that carousel, which was the single biggest reason publishers adopted it. The badge distinguishing these pages in results was also removed.
What followed. Publishers left.
Major publishers migrated away once the incentive was gone. The framework still exists and pages built with it still work, so this is a withdrawal of incentive rather than of function.
What it cost to maintain. A second version.
Effectively a parallel version of every page, with the drift problem block three describes. That was tolerable when it bought access to something and is difficult to justify now.
The question for anybody still on it. What is it doing.
If the answer is that it was set up years ago and nobody has revisited it, that is a maintenance burden with no remaining purpose. Removing it is a migration and should be treated as one.
Test On An Actual Phone
A browser window made narrow is not a phone. Speed differs, interaction differs and the connection differs. This is the check almost nobody performs before launching.
What a narrow window shows. Layout only.
Resizing a desktop browser confirms things rearrange sensibly. That is genuinely useful and it is one of three things that matter.
What it cannot show. Speed on a real connection.
A desktop on office broadband loads everything instantly. A phone on a weak signal in a car park is the actual condition many of your visitors are in.
What else it misses. Using it with a thumb.
Whether targets can be hit accurately, whether forms can be completed one-handed and whether anything important sits where a thumb naturally rests. A mouse cannot tell you this.
Who should do it. Somebody who did not build it.
The person who built the page knows where everything is. Handing a phone to somebody unfamiliar with the site reveals more in two minutes than any tool.
What to do. Complete a real task.
Find a service, read the page and submit an enquiry, on a phone, on mobile data. Any friction you meet is friction a customer meets.
Where this leaves the subject. Settled, with one job left.
The technical question is finished. The remaining work is making sure the mobile version genuinely serves people, which the technical SEO guide sets alongside everything else.
Open your own site
on a phone, on
mobile data.
Find a service, read the page and submit an enquiry. Any friction you meet is friction a customer meets. A browser window made narrow confirms the layout rearranges and tells you nothing about speed on a weak signal or whether a thumb can hit anything.
What we compare:
Mobile SEO as a separate service is usability review and performance work renamed.
Every guide.
One practice.
How search finds and stores a site, what your own files are telling it, addresses and duplication, status codes, mobile, hosting and what a real audit contains.
