Advanced mobile SEO: parity, schema and log checks
Short answer Once your site works on a phone, advanced mobile SEO is checking. Google indexes the version its smartphone crawler sees, so compare that version with desktop: text, headings, titles, robots tags, images and structured data. Then confirm in your server logs that Googlebot Smartphone does most of the crawling. Each gap is a page Google reads with less information.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat is advanced mobile SEO, past the basics?
It is checking that the phone version of each page carries everything the desktop version does, because the phone version is the one Google reads. Google's mobile indexing guide puts it plainly:
"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile site and mobile-first indexing best practices)
Google announced on October 31, 2023 that the move to mobile-first indexing was complete. Only a very small set of sites that don't work on phones at all are still crawled with the old desktop crawler (Google Search Central Blog).
The basics (responsive layout, readable text, fast pages) make a site usable. The advanced work is four checks a basic audit skips:
| Check | What you compare | Where it goes wrong |
|---|---|---|
| Content parity | Text, headings, images, links on phone vs desktop | Mobile theme hides sections or loads them only on tap |
| Tags and metadata | Title, meta description, robots tags, canonical | A plugin adds `noindex` or a different title on mobile |
| Structured data | Schema markup on both versions | Markup lives only in the desktop template |
| Server logs | Which Googlebot visits, and how often | Desktop crawler still doing most of the visits |
Speed is its own topic. Note that Google's responsiveness metric is now Interaction to Next Paint (INP), with a "good" target under 200 milliseconds; it replaced First Input Delay in March 2024 (Google Search Central). See Core Web Vitals and ranking.
How do I check content parity between mobile and desktop?
Compare what each version shows, section by section. Google's guide asks for the same content, "the same clear and meaningful headings", and title and meta description that "are equivalent across both versions of your site" (Google Search Central).
Which check you need depends on how your site is built:
- Responsive design (same page, layout changes with screen size): Google says the content and metadata are then the same on both. Your risk is content hidden in ways Google can't reach, covered below.
- Dynamic serving (same address, different HTML for phones) or separate mobile site (an m. address): the two versions can drift apart. Check every template.
What to compare on a key page, such as your main service page:
- Text and headings. Open the page on a phone and on a computer. Every heading and paragraph on desktop should exist on mobile. Tucking text into tabs or accordions is fine; Google suggests that instead of removing it.
- Content loaded on tap. Reviews behind "Load more", or prices that appear only after a tap, may as well not exist for Google (quote below).
- Images. Same alt text, same captions, and image addresses that don't change on each page load. Google warns that different image addresses on mobile can cause a temporary drop in image traffic.
- Robots tags. A `noindex` on the mobile version means Google may not index the page at all.
- Rendered view. In Search Console, the URL Inspection tool shows the page as Google rendered it. Google's own troubleshooting advice is to use it to confirm the content is visible there.
"Google won't load content that requires user interactions (for example, swiping, clicking, or typing) to load." (Google Search Central: Mobile site and mobile-first indexing best practices)
For separate mobile sites, Google adds rules: the desktop address is always the canonical, the mobile page is its alternate, error status must match on both, and mobile pages that all redirect to the home page drop out of the index.
How do I check structured data on the mobile version?
Make sure the same schema markup sits on both versions, with the right addresses inside it. Google's guide:
"Make sure that your mobile and desktop sites have the same structured data." (Google Search Central: Mobile site and mobile-first indexing best practices)
Google lists "missing structured data" as a common mobile indexing error: the mobile page lacks markup the desktop page has. On a separate mobile site, URLs in the markup should point to the mobile addresses.
Two limits to keep expectations honest:
- Markup makes a result eligible, not guaranteed: it "enables a feature to be present, it does not guarantee that it will be present" (Google Search Central: General structured data guidelines).
- Star ratings in your own results usually won't show for your business. Google supports review markup for LocalBusiness and Organization only on sites that collect reviews about other businesses (Google Search Central: Review snippet structured data).
For which types a service business should use, see local business schema markup.
Which search features look different on a phone?
Some features show only on desktop, so test results on a phone, not just a laptop.
| Feature | Phone | Desktop |
|---|---|---|
| Breadcrumb trail in the visible URL | Not shown since January 23, 2025; domain only | Shown |
| Site name | Shown | Shown |
| Rich results from markup | Eligible, never guaranteed | Eligible, never guaranteed |
Google stopped showing breadcrumbs on mobile results worldwide because they got cut off on small screens; breadcrumb markup still works for desktop, and there is nothing to remove (Google Search Central Blog, Jan 23, 2025). Site names appear on both mobile and desktop (Google Search Central: Site names), so make sure Google shows the right one.
What should my server logs show for Googlebot?
Most Googlebot visits should come from the smartphone crawler. Google says the majority of crawl requests use the mobile crawler and a minority the desktop one (Google Search Central: Googlebot). A log full of desktop Googlebot is a warning: Google said in 2023 it keeps crawling sites that don't work on phones with its old desktop crawler.
How to check:
- Without server access: Search Console, Settings, Crawl stats. The "Googlebot type" table splits requests into Smartphone, Desktop, Image, Page resource load and more (Search Console Help: Crawl Stats report).
- With raw logs: search the user agent field. Google publishes both strings. The smartphone one contains "Android", "Mobile Safari" and "Googlebot/2.1"; the desktop one has "Googlebot/2.1" without "Mobile" (Google Search Central: Google's common crawlers).
- Confirm it's really Google. Anyone can fake a user agent. Google's method: run a reverse DNS lookup on the visiting IP address, check the name ends in googlebot.com, google.com or googleusercontent.com, then run a forward lookup and confirm it returns the same IP (Google Search Central: Verifying Googlebot). Or match the IP against Google's published range files, which moved to developers.google.com/crawling/ipranges/ in March 2026; Google said it would redirect the old addresses within six months (Google Search Central Blog, Mar 31, 2026).
- Look for gaps. Pages the smartphone crawler requests that return errors, and important pages it never requests.
One trap: robots.txt can't treat the two crawlers differently. Both obey the same "Googlebot" rule, so you can't block the desktop crawler and keep the mobile one (Google Search Central: Googlebot). On a separate mobile site, Google asks that robots.txt rules work as intended on both hosts. For AI bots in the same logs, see blocking AI crawlers.
Example
A plumber with a mobile theme that drops FAQs (US dollars)
The desktop service page has 600 words and 8 questions; the mobile theme shows 250 words and no questions. Google indexes the 250. Moving the questions into an accordion on mobile restores the content at no cost beyond an hour of theme work, about $100 from a freelancer.
A Vancouver clinic on an old m. site (Canadian dollars)
All 40 treatment pages on m. redirect to the mobile home page. Google's guide says those pages drop from the index. Fixing the redirects to point to matching mobile pages costs about C$800; moving to one responsive site removes the problem for good.
An accounting firm reading its logs
Of 1,000 Googlebot requests in a month, 900 claim Googlebot Smartphone, but 150 of those fail the reverse DNS check: a scraper. The real crawl mix is still mostly smartphone, which is what Google says to expect.
FAQ
Is content in tabs or accordions indexed on mobile?
Yes, if it's in the page on load. Google suggests them instead of removing content, but won't load content that appears only after a tap.
Do I need separate structured data for mobile?
No. Use the same markup on both versions. Responsive design covers both; on an m. site, point the markup's URLs to mobile addresses.
Can I block Googlebot Desktop in robots.txt?
No. Both crawlers follow the same Googlebot rule in robots.txt, so you can't target one of them.
Why don't my breadcrumbs show in phone results?
Google stopped showing them on mobile on January 23, 2025. Your markup still works on desktop results; keep it.
Different for you?
- Pages fall out of the index after a redesign: see traffic dropped after a redesign.
- Search Console says "Crawled, currently not indexed": see page not indexed.
- New to Search Console: see Search Console for a small business.
- Want someone to run these checks every month: see SEO.