Overview
Screenshot
HTTP status & redirects
Crawl stage: plain HTTP requests from the URL you entered, with no browser HSTS memory and no JavaScript – what Googlebot gets before rendering. Render-stage hops (JavaScript / meta refresh) are appended and marked.
Raw vs rendered SEO signals
Highlighted rows changed after JavaScript ran. If the rendered value is what you want indexed, Google has to successfully render the page to see it.
| Signal | Raw HTML (before JS) | Rendered DOM (after JS) |
|---|
Hreflang
| hreflang | Raw HTML (before JS) | Rendered DOM (after JS) |
|---|
Rendering differences – raw HTML (before JS) vs rendered DOM (after JS)
red present in the raw HTML but removed by JavaScript · green added to the rendered DOM by JavaScript · both sides are extracted with the same code (raw side loaded with JavaScript disabled) so counts are directly comparable.
Images
Every <img> in the rendered page with the signals Google Images uses to understand it: alt text, caption, nearest heading and surrounding text. Images that only exist after JavaScript, or with no alt or no dimensions, are flagged.
| Image | URL & attributes | Alt text | Context (caption · nearest heading · surrounding text) | Flags |
|---|
Internal links
Crawlable links to this site – <a> elements with an href that resolves to an http(s) URL on the same domain (subdomains included) – in the rendered page, with anchor text and where on the page they sit. External links are counted but listed only in the Rendering differences › Links tab. Link-like elements Googlebot cannot follow are listed separately below.
Elements that behave as links for users but that Googlebot cannot follow: only <a> elements with an href that resolves to a URL are crawled. Anything here that points at an important page needs a real <a href>.
| Text | Type | Apparent destination | Location | Why it is not crawlable |
|---|
Internal resources
| # | URL | Type | robots.txt | Status | URL Fingerprinting | Cache Headers | Note |
|---|
URL Fingerprinting is about the URL only: does the filename change when the content changes (e.g. main.2bb85551.js)? Cache Headers is what the server sent (Cache-Control / Expires). Per web.dev's HTTP caching guide: fingerprinted URLs should be cached for a year (max-age=31536000); unversioned URLs should use no-cache with an ETag/Last-Modified (revalidate every time) or no-store. Red rows break that (long-cached without a fingerprint, or no headers at all so the browser guesses a lifetime). Amber rows are acceptable for browsers but WRS, which may ignore headers, would still be safer with a fingerprint. Green rows are fingerprinted but under-cached – free performance.
External resources
Third-party domains. The same filters as the internal table apply.
| # | URL | Type | robots.txt | Status | URL Fingerprinting | Cache Headers | Note |
|---|
Critical resources
Re-renders the page once per resource with only that resource blocked and measures what disappears from the rendered DOM. One extra render per resource, so a heavy page takes a few minutes.
| Impact | Resource blocked | Type | Visible text | Links | Images | JSON-LD | Tags changed | Also lost |
|---|
Critical: blocking it changes the title, H1, canonical or meta robots, removes JSON-LD, or cuts visible text or links by 25%+. Contributes: a smaller change (5%+), or a change to meta description, hreflang or images. None: the rendered DOM is unchanged without it. "Also lost" is the number of other requests that no longer happen when this one is blocked (its dependents).
robots.txt files consulted
| Origin | Status | Bytes | Note |
|---|
WRS emulation applied
Console errors & warnings
HTML
Audit checklist – opportunities to improve this page
Every check that can be answered for a single page from this fetch, worded to match the Technical SEO Checklist workbook (tab › section › check) so findings can be pasted straight into it. Checks needing Search Console, a full crawl, backlinks or analytics are left to the workbook.