Skip to content
Plumb
Light theme onCheck a URL

DocsMobile SEO

Mobile-First Index Tool

Render a page as a desktop and a smartphone user agent and compare what each version carries: SEO signals, text, links, headings, image alt texts and structured data.
  • Rendered in Chromium
  • Separate m-dot URLs
  • Mobile usability
  • JSON API

What it Checks

Google indexes the mobile version of a page. Anything that exists only on the desktop version (a link, a heading, structured data) is not used. The tool renders the URL twice in Chromium, once at 1366px as a desktop user agent and once at 412px as a smartphone user agent, and lists what the mobile version is missing.

It compares the title, meta description, canonical, meta robots, hreflang and H1 of both versions (extra spaces ignored), measures how much of the visible text they have in common, and lists the text blocks, links, H2 headings, image alt texts and structured data types found on desktop but not on mobile. Text is compared by overlapping three-word sequences and block by block, so a date or a rotating banner doesn't count as missing content; links are compared without fragments, trailing slashes and tracking parameters (utm_*, ref…). The mobile rendering also gets the usability checks of the Mobile-Friendly Test.

When the desktop page announces a separate mobile URL with <link rel="alternate" media="…max-width…"> (an m-dot site), the mobile version is rendered from that URL instead.

Run a Test

  1. Paste the URL of the page.
  2. Pick the user-agent pair. Googlebot desktop and Googlebot Smartphone are the default.
  3. Press Compare. The verdict reads Mobile matches desktop., or names what is missing or different, for example Mobile is missing 12 links and 2 H2 headings. When a version answers an error status, the verdict says so: The mobile version answered HTTP 403.
Open the Mobile-First Index Tool

Options

  • User agents. Three pairs: Googlebot (desktop / phone), Chrome (Windows / Android) and SEO spider (Screaming Frog regular / mobile). A site that serves crawlers differently from browsers shows it when you switch between the Googlebot and Chrome pairs.
  • Export .json / Import .json. Save a result, screenshots included, and open it again later without running the test.

Reading the Result

  • Verdict: green when nothing is missing and the signals match; red when the canonical or meta robots differ, or when a version could not be rendered or answered an error status; amber for other differences.
  • Text: the share of text the versions have in common and their word counts. Text blocks count as missing on mobile only when less than 90% of the text is in common.
  • Content differences: text blocks, links, H2 headings, alt texts and structured data types present on desktop only, plus text and links found only on mobile (for information). Lists stop at 200 items (“200+”).
  • Desktop vs. mobile: the SEO signals of both versions side by side.
  • Mobile usability: viewport, content width, text size and tap target problems of the mobile rendering (not shown for an error page).
  • Renderings: a whole-page screenshot of each version side by side (up to 6,000px tall), each scrolling on its own, to see what the phone version shows, hides or moves.

Good to Know

  • Content is compared as rendered after JavaScript, once the page has loaded and the network is quiet (up to 6 seconds). Content loaded on scroll or on click is not seen.
  • Requests come from this server. A site that blocks requests claiming to be Googlebot from outside Google's network can answer with an error page; try the Chrome pair.
  • How canonicals work: the rel="canonical" guide.

API

POST /api/mobile-first-index

Send the URL and, optionally, the pair: googlebot (default), chrome or spider. Each snapshot also carries a base64 JPEG screenshot of the whole page (screenshotClipped when it is taller than 6,000px; pageHeight in CSS pixels) and the full signals object. diff.textSimilarity is 0 to 1.

Request
curl -X POST https://plumb.reacthive.dev/api/mobile-first-index \
  -H "content-type: application/json" \
  -d '{
    "url": "https://www.example.com/",
    "pair": "googlebot"
  }'
Response (Trimmed)
{
  "url": "https://www.example.com/",
  "separateMobileUrl": null,
  "agents": { "desktop": "Googlebot", "mobile": "Googlebot Smartphone" },
  "desktop": {
    "finalUrl": "https://www.example.com/",
    "status": 200,
    "signals": { "title": "Example", "canonical": "https://www.example.com/", "h1": ["Example"] },
    "screenshot": "data:image/jpeg;base64,/9j/4AAQ...",
    "screenshotClipped": false,
    "pageHeight": 3849,
    "timeMs": 4120
  },
  "mobile": {
    "finalUrl": "https://www.example.com/",
    "status": 200,
    "signals": { "title": "Example", "canonical": "https://www.example.com/", "h1": ["Example"] },
    "mobile": { "mobileFriendly": true, "issues": [], "legibleTextPercent": 97 },
    "timeMs": 3870
  },
  "diff": {
    "textSimilarity": 0.861,
    "wordsDesktop": 2087,
    "wordsMobile": 1946,
    "textMissingOnMobile": ["Careers at Example", "Join our team of 40 people in Lisbon and Berlin."],
    "textOnlyOnMobile": [],
    "linksMissingOnMobile": ["https://www.example.com/careers/"],
    "linksOnlyOnMobile": [],
    "altsMissingOnMobile": [],
    "structuredDataMissingOnMobile": ["BreadcrumbList"],
    "h2MissingOnMobile": []
  },
  "testedAt": "2026-10-22T09:14:03.000Z"
}