Free tools / Crawler vs browser view
Crawler vs browser view: what your raw HTML leaves out
Our crawler vs browser view reads the raw HTML of one page, which is what a crawler that does not run scripts receives, and lists what is missing from it: title, description, headings, main text, links and JSON-LD, compared with what the page itself declares. We do not run a browser, and we say plainly what that leaves unseen.
We read robots.txt before anything else and follow it, then read your page within eight seconds: up to three redirects, each checked again and each to a public HTTPS address, and at most 1.5 MB. HTTPS websites are supported; other addresses are refused.
No email is needed; runs are limited per network and per day, and by the site's daily allowance.
We do not save your website, company name, page content or result. We keep daily totals and hashed network counters to enforce limits. A shared result stays in its link, not on our server.
What we check and why
Title and description
A crawler reads them before the body text. When the sharing tags (og:title, og:description) carry them and the page elements do not, a script may be filling in the rest.
Headings
An H1 and section headings tell a crawler what the page and each part are about. If structured data names a headline that no heading carries, the two disagree.
Main text
We count words of main text in the HTML and in embedded script data such as __NEXT_DATA__. More words inside script data than on the page means a browser builds the text after load.
Links
A crawler follows links that carry an address. Link elements with no address, # or javascript: work when scripts run.
JSON-LD
Structured data in the raw HTML is read without running scripts. Structured data that a tag manager inserts is not.
What we do not do
We do not run a browser or scripts. We compare parts of the raw HTML with each other, so a page that loads its content from an API with no trace in the HTML shows as thin, and we cannot show what it would contain.
Questions
Do AI crawlers run JavaScript?
Not all of them. When the main text, title and links are in the raw HTML, the page works for crawlers that run scripts and for those that do not.
Your site uses React or Next.js. Is that a problem?
Not if the server sends the content. Server rendering or static generation puts the text in the raw HTML; a page that renders everything in the browser does not. This check shows which one your page does.
Why not render the page in a browser?
Rendering shows what a person sees, not what a crawler that skips scripts gets. We read the HTML as those crawlers do, with no scripts, cookies or styles, so the result is repeatable.
Want the fix made for you?
Answer Repair completes one agreed source-backed page or fix. Choose Live or Handoff before payment. Due 48 elapsed hours after Ready. Full refund on request within 30 days of delivery.
When you want us to do the work, every offer and its published price is on our offers page. More free checks: the ChatGPT Business Hub readiness check, the raw HTML readability checker, the page token count and the AI access checker, or see all free tools. Read next: How do you write a page an AI engine can quote?