Free Raw vs Rendered HTML Checker
One of the free tools from KinetixSEO, an SEO and AI-citation (GEO) checker. It fetches your page, loads it again in a real browser, and shows you both — plus the specific links, images and headings that only exist once JavaScript has run.
What the Free Raw vs Rendered HTML Checker checks
- Title, canonical URL, robots meta tag and H1 compared between the raw response and the rendered DOM — JavaScript silently rewriting any of these is a ranking risk
- Word count, internal link count and JSON-LD block count in both versions
- Which specific internal links exist only after rendering, with their anchor text — links a non-rendering crawler cannot follow
- Which specific images exist only after rendering, with their alt text
- Whether the Largest Contentful Paint element — the biggest thing a visitor sees — is present in the raw HTML at all
- Interactive components (accordions, tabs, carousels, mega-menus) whose content only appears after hydration
- The raw and rendered HTML side by side, so you can read the difference yourself
Frequently asked questions
What is the difference between raw and rendered HTML?
Raw HTML is what your server sends in the HTTP response. Rendered HTML is the DOM after the browser has executed the page’s JavaScript. On a server-rendered site the two are nearly identical; on a JavaScript-heavy site the raw HTML can be an almost empty shell.
Why does the difference matter for SEO and AI search?
Google and Bing execute JavaScript, so they generally see the rendered version — eventually, and on their own schedule. Most AI crawlers do not: OAI-SearchBot, PerplexityBot and Claude-SearchBot read the raw HTML and nothing else. Anything that only exists after hydration is invisible to them, which is how a page ranks in Google and is never cited by ChatGPT.
What is the LCP element check?
The Largest Contentful Paint element is the biggest thing a visitor sees when the page loads — usually a hero image or headline. If it does not exist in the raw HTML, the single most prominent thing on your page is invisible to any crawler that does not render JavaScript, and it is also the element most likely to be hurting your loading performance.
The lists are cut off. Why?
Each list is capped at 50 entries, with the true total shown alongside it. A fully client-rendered page can have every one of its links and images missing from the raw HTML, and an uncapped list of thousands would not be more useful than the first fifty plus the number.
Is this the same as the render diff in the paid audit?
It is literally the same code. This tool runs the audit’s render-diff agent and shows you its output; the paid audit adds the rest of the pipeline around it — crawling the whole site, tracking changes over time, and turning findings into prioritised fixes.
Go deeper
This free check looks at one signal in isolation. KinetixSEO's paid report combines every signal below into one prioritised fix list and tracks it over time.
See the full paid report for this →