Google now indexes every site using its mobile version. However rich your desktop site is, ranking decisions are made from the phone version.
The practical consequence fits in one sentence: content that is not visible on mobile does not exist.
The most common content losses
- Hidden sections. Descriptions, FAQ blocks and product details removed with
display: noneon mobile. - Truncated copy. Content behind a "read more" toggle is indexed; content removed entirely is not. Know the difference.
- Divergent structured data. Schema markup present on desktop but absent on mobile is simply lost.
- Missing images. Images not loaded on mobile drop out of image search.
- Different internal links. Links absent from the mobile menu carry no equity.
Parity checks
- Fetch the desktop and mobile HTML of the same page and compare word counts. A large gap means you are losing content.
- Validate structured data blocks in both versions.
- Compare internal link counts.
If you run a separate mobile site
The m.site.com pattern is no longer recommended. Responsive design uses a single URL, which is easier to maintain and removes parity problems entirely. If you still run a separate mobile site, start planning the migration.
Mobile usability is a separate concern
Beyond indexing, the mobile experience itself drives conversion:
- Tap targets should be at least 44×44 pixels
- Body text should never fall below 16 pixels
- The page body must never scroll horizontally
- Full-screen interstitials hurt both users and rankings
- Set the right
inputmodeon form fields so phone inputs open a numeric keypad
How to test
Device emulation in browser dev tools is a reasonable start but not sufficient. Test on a real phone over a real mobile connection. A site that feels fast on office wifi behaves very differently on 4G.