The phone version is the version that counts

What changed

Search engines now fetch and evaluate the phone version of a page as the primary one, because that is how most people browse.

The desktop version is not what gets indexed. If the two differ, the phone version wins every time.

For a responsive site this changes nothing at all, because both versions are the same content laid out differently.

It also means a site that looks fine on desktop and thin on a phone is being judged on the thin version, whatever effort went into the other one.

For a responsive site this changes nothing at all, because both versions are the same content laid out differently.

Where sites get caught

Content removed on small screens to simplify the layout. A comparison table, a section of detail, a block of frequently asked questions hidden to save space.

Structured data present on desktop and omitted on mobile, which removes any search feature it supported.

Navigation reduced on phones to the point that internal links disappear, which changes how the engine sees your site structure.

Images swapped for smaller ones without alt text, which removes both the accessibility and the understanding a description provides.

• Content removed on small screens to simplify the layout
• Structured data present on desktop and omitted on mobile
• Navigation reduced until internal links disappear
• Images swapped for smaller ones without alt text
• A separate mobile site that has drifted behind the desktop one
• Interstitials that cover the content on arrival

Hidden is not the same as removed

Content inside a collapsed section that a visitor can expand is still indexed. Accordions and expandable panels are fine.

Content genuinely removed from the phone version is not there to be read. The distinction is whether it exists in what the browser receives.

So simplifying a phone layout by collapsing sections is safe. Simplifying it by omitting them is not.

Content inside a collapsed section a visitor can expand is still indexed. Simplifying by collapsing is safe; simplifying by omitting is not.

Separate mobile sites

A separate address serving a different site to phones was a common approach and is now a liability. Two sites to maintain, two sets of content that drift apart.

The mobile version becomes the indexed one, so any content only on the desktop version is lost, and it is usually the desktop version that gets updated.

If you still have one, moving to a single responsive site is worth doing and is not usually a large project at small scale.

What to check

Open your site on a phone and compare it against desktop, section by section. Anything missing is a candidate problem.

Use the inspection tool to see what the crawler received on mobile, which is more reliable than resizing a desktop browser.

Check that internal links, headings and structured data all survive. Those three are the ones most often trimmed for tidiness.

Search Console also reports usability problems found on mobile, which is a faster way to find tap targets that are too close together.

Use the inspection tool to see what the crawler received on mobile, which is more reliable than resizing a desktop browser — see URL inspection.

Beyond indexing

Most visitors to a small business site arrive on a phone, so the mobile version is also the one that has to convert.

That means the phone number, the contact route and the main answer should be reachable without scrolling past a large image.

Designing for the phone first and expanding for desktop tends to produce a better result than the reverse, because the constraint forces priorities.

Most visitors arrive on a phone, so the mobile version is also the one that has to convert.

How ours are built

Sites here are a single responsive layout, so the phone and desktop versions carry identical content, links and structured data by construction.

Layouts are checked for horizontal overflow across a range of widths before anything publishes, which is the common phone layout fault.

Every page passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards.