Indexing & Crawl

Mobile-first Indexing Gaps

Google’s mobile-first indexing means the mobile rendering of your pages is what Google crawls, evaluates and ranks. This report surfaces pages where that assumption breaks down: pages with explicit mobile usability errors, pages that are earning real clicks but are still being crawled as Desktop, and pages where the crawling agent is unknown. Left unresolved, these pages risk a ranking penalty or exclusion from the mobile-first index.

The four risk tiers

Mobile errors

Google’s URL Inspection API returned a non-passing mobile usability verdict (e.g. viewport not configured, content wider than screen, tap targets too close, text too small). Fix viewport, font-size and touch-target issues first — these are explicit quality signals.

Desktop-crawled (with traffic)

Googlebot last crawled this page as a Desktop agent even though it earns clicks in the selected window. Under mobile-first indexing Google indexes the mobile rendering — if it hasn’t crawled the mobile version, rankings may be based on stale or incomplete data.

Crawler unknown (with traffic)

The URL Inspection record has no crawling agent stored but the page earns real clicks. Re-run URL Inspection to confirm mobile-first status before assuming it is healthy.

Desktop-crawled (low traffic)

Still crawled as Desktop but earning fewer than 5 clicks. Lower priority, but signals an incomplete mobile-first migration. Monitor rather than fix urgently.

How we compute it

  1. We read the crawledAs field and the mobileUsabilityResult.verdict from the URL Inspection records we hold. Google allows only a small number of URL inspections a day, so Metricstab inspects the pages in your running SEO tests rather than sweeping the whole site. Pages outside a running test have no inspection record here.
  2. We join those records to the Search Console clicks and impressions for each URL.
  3. Each URL is assigned a tier using the logic above. Pages where Googlebot crawled as Smartphone and there are no mobile usability errors are excluded (healthy).
  4. Results are sorted by tier priority (Mobile errors first) then by clicks descending within each tier.

Summary tiles

  • Mobile errors — count of pages with an explicit mobile usability verdict failure.
  • Desktop-crawled with traffic — count of pages earning ≥5 clicks but last crawled as Desktop.
  • Clicks at risk — sum of clicks on all Mobile-error and Desktop-crawled-with-traffic pages. The economic exposure of the top two tiers.
  • Pages flagged — total pages across all four tiers.

Table columns

  • URL — links to the live page.
  • Risk tier — colour-coded badge.
  • Crawled as — the agent Googlebot last used: Smartphone, Desktop or unknown.
  • Mobile verdict — the URL Inspection mobile usability verdict: PASS, FAIL or blank.
  • Clicks / Impressions — Search Console totals for the selected window.
  • Recommended fix — a one-line action per tier.

What to do with it

  1. Fix Mobile errors first: open each URL in Google’s Mobile-Friendly Test to get the specific issues, then fix at the template level so all similar pages are corrected in one go.
  2. For Desktop-crawled with traffic: request a re-crawl via URL Inspection and verify the responsive rendering is correct. Check that there is no Vary header or user-agent-based redirect blocking Smartphone Googlebot.
  3. For Crawler unknown with traffic: submit via URL Inspection and re-check in 2–3 weeks.
  4. After fixes, re-run URL Inspection to confirm the verdict changes to PASS and crawledAs changes to Smartphone.

Related reports