surfup

Compare source HTML, browser DOM, and Google URL Inspection

You will be able to identify what each method shows and which conclusions it supports.

Explanation

These methods answer different questions:

  • curl or “View Source” shows the HTTP response/source HTML returned for a particular request. Ordinary curl does not run JavaScript and does not represent Googlebot by itself.
  • The DOM in a browser after page load shows what the browser produced with JavaScript under those specific cookies, session, network, and actions. This DOM alone does not prove that Google received the same rendered page.
  • URL Inspection in Search Console can show the indexed version and, in a live test, information about Google’s current test. This is a check of a specific Google tool and URL, not of every crawler.
  • Use the Rich Results Test for structured data, and only for types it supports; it is not a general HTML or indexing tester.

Fictional example

In the source HTML for the training page /robots on staging/local, there is a heading while the text is fetched from an API. The lesson is visible in the browser after loading. This proves only that this browser received the content under these conditions. To check Google, the site owner runs URL Inspection for the page and reviews the available test rendering, resources, and errors. If URL Inspection is unavailable to the reviewer, Google rendering is marked “not checked.”

Practice

On your own staging/local mockup, save three separate records for the test page /robots: (1) source HTML and HTTP status from curl/View Source; (2) visible text and links in the browser DOM after loading; and (3) URL Inspection only if your staging URL is publicly accessible and added to a verified Search Console property. Do not submit synthetic learn.example.test to URL Inspection. Do not replace a missing check with a conclusion from another layer. If structured data needs checking, run the Rich Results Test separately, only for a suitable supported type on an accessible test URL.

Checklist

  • The method and response being recorded are identified.
  • Source HTML is not described as the rendered version.
  • Browser DOM is not presented as proof of Google rendering.
  • URL Inspection is for the exact URL; its live-test result is separate from indexed state.
  • The Rich Results Test is used only for a supported structured-data type.

Common mistake

Seeing text in the browser and concluding that Google sees it. Use a Google tool to check Google’s view; other crawlers require their own rules and checks.

Primary sources

Have a task? Share a few details — we’ll take it from there.

Latest materials

All materials

Practical articles and guides by SurfUp.

Guide · 10 min

“What is…” pages and AI answers: lost clicks or falling demand

A bank’s reference section lost 24% of visits as demand fell 13%. How to tell clicks lost to an AI block from falling demand and how to measure it.

Read
Guide · 8 min

Traffic dropped after a Google update

How to tell whether a traffic drop comes from a Google update, seasonality or a site fault. 2026 update timeline, a six-question check and a plan for the first 14 days.

Read
Guide · 9 min

Demand fell or the site lost: reconciling traffic with Wordstat

Demand for deposits fell 75%, traffic 37%; for cards demand −35%, traffic −63%. How to reconcile traffic with demand and not blame the site for the market.

Read