Check that your mobile pages contain the same text, headings, images, and structured data as your desktop pages. Content hidden or removed on mobile is now content Google does not see.

What changed this month

Google has been moving sites to mobile-first indexing for several years, site by site, and this month is the point at which it applies broadly rather than selectively.

The practical meaning is straightforward. When Google indexes your site, it fetches and reads the version a phone would receive.

That version is what gets indexed, what gets assessed, and what determines where you appear, including for people searching on a desktop computer.

The desktop version has not become irrelevant to your visitors. It has become largely irrelevant to how you are found.

Why this is only a problem for some sites

If your site is genuinely responsive, meaning one set of pages that reflows to fit the screen, very little changes.

The content is identical either way. It is arranged differently, and arrangement is not what is being read.

Trouble arrives where the two versions differ in substance, which happens in three situations: a separate mobile site at its own address, a theme that hides sections below a certain screen width, and a design where some material is loaded only on larger screens.

In all three, something exists on desktop that does not exist on mobile, and that something is now invisible.

What goes missing most often

The first and last do the most damage. Text removed for tidiness on a phone is text Google no longer sees, and a reduced mobile menu quietly removes the internal linking that connects your site.

Checking your own site

Three checks, none of which takes long.

Open a page on your phone and read it against the same page on a desktop. Not a glance: compare the actual sections and confirm nothing has gone.

Use Google's own inspection tool in your search console to fetch a page and view the rendered result, which shows you what was actually received rather than what you believe is published.

And check a page's structured data on both versions, since it is frequently in a desktop template and absent from the mobile one.

Do this for your homepage, your most important service page, and one deep page, which between them will reveal any pattern.

Hidden is not the same as missing

A distinction worth getting right, because it causes unnecessary rebuilding.

Content inside an accordion or a tab, which a reader expands by tapping, is present in the page. It is generally indexed, and using those patterns on mobile is normal and accepted.

Content removed by the page's styling so it is not delivered at all, or never loaded on smaller screens, is a different matter and genuinely absent.

The test is whether the text exists in what the server sends. If it does, a collapsed section is a presentation choice. If it does not, it is gone.

A worked example

A professional firm had a well-built site whose theme, for tidiness, suppressed two sections on screens below a certain width.

One was a block of body text on each service page running to about three hundred words. The other was a sidebar carrying links to related services.

On a desktop the service pages were substantial and well connected. On a phone they were roughly half as long and linked to almost nothing.

Nobody had noticed, because everybody in the office used a desktop and the mobile version looked clean rather than broken.

They changed the theme so both sections appeared on all screen sizes, the text below the main content and the related links as a list at the foot of the page.

Positions improved over the following two months across the whole services section, from a change that added no new content at all.

Separate mobile sites

The situation that needs the most attention, and it affects a shrinking number of sites.

Where a business runs a separate mobile site at its own address, that version is now the one being indexed, and separate mobile sites were historically built as reduced versions.

Less text, fewer pages, simplified navigation, and often no structured data at all.

The realistic answer is to move to a single responsive site rather than to bring the mobile version up to parity, since maintaining two sets of content in step indefinitely is a burden that always eventually fails.

Where that cannot happen immediately, the interim step is to make the mobile version's content match the desktop one, which is most of the work anyway.

The things worth checking beyond content

Page titles and descriptions, which some themes shorten on mobile.

Image descriptions, which are lost when an image is dropped rather than resized.

Anything blocked from being fetched, such as scripts or stylesheets the mobile version needs, since a page that cannot be rendered properly cannot be assessed properly.

And the mobile page's actual usability: text large enough to read, tap targets far enough apart, and nothing overflowing sideways, which have been assessed for some time and are now assessed on the version that counts.

The counter-case

This is not a reason to redesign anything, and it will be presented as one.

For the large majority of sites built in the last several years, the correct response is to run the checks, confirm the two versions match in substance, and do nothing further.

Nor does it mean the desktop experience should be neglected. Plenty of considered purchases are researched on a phone and completed on a laptop, and for some businesses most actual buying still happens on a large screen.

The change is narrow: it concerns which version is read for indexing. It is not an instruction to prioritise phone users over everybody else, and treating it as one leads to stripping desktop pages, which helps nobody.

What to do this month

  1. Compare three pages on a phone and a desktop, section by section.
  2. Inspect a page in your search console and read the rendered result.
  3. Check structured data is present on the mobile version.
  4. Confirm the mobile menu carries the same internal links.
  5. Restore anything hidden by screen width.
  6. Check nothing needed for rendering is blocked.
  7. Plan a move if you run a separate mobile site.

Most sites will finish the first three and find nothing, which is the outcome to hope for and worth the half hour to confirm.

The earlier stage of this change is covered in Google is reading the phone version.

Frequently asked questions

What is mobile-first indexing?

Google fetches and reads the version of your site a phone would receive, and that version determines where you appear, including for people searching on a desktop.

Does this mean I need a new website?

For most sites built in the last several years, no. If your site is responsive, the content is identical either way and arrangement is not what is being read.

What is the actual risk?

Content that exists on desktop and not on mobile. Hidden body text, dropped sidebars, missing images, absent structured data, and a reduced mobile menu are the common cases.

Is content inside a tab or accordion indexed?

Generally yes, if the text is present in what the server sends. Content removed by styling or never loaded on small screens is genuinely absent.

How do I check my own site?

Compare three pages on a phone and a desktop section by section, then use the inspection tool in your search console to see what was actually rendered.

What if I have a separate mobile site?

That version is now the one being indexed, and separate mobile sites were usually built as reduced versions. Moving to a single responsive site is the realistic answer.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Do your phone and desktop pages match?

Half an hour, three pages, section by section. Most sites find nothing, which is worth confirming.

Start a Conversation