The AI search toolkit · 2.0Technical · Tool 09
Free JavaScript Rendering Checker
Compare raw response HTML with an optional rendered snapshot. Inspect text, titles, headings, canonical hints and JSON-LD tags to see which important signals are present before and after your page’s scripts run.
Compare supplied HTML
Processed in your browserExample data is loaded. These are fictional demonstration inputs, not a DigiMSM or client performance result. Use Clear to start your own analysis; editing example values keeps the run labelled as an example.
The interactive tool requires JavaScript. If the form does not appear, check that your WordPress setup allows this fragment’s inline script. The methods and FAQs below remain readable.
Inputs changed. Run the tool again to refresh the result and enable exports.
Your evidence comes first.
Compare supplied raw and rendered HTML without executing untrusted page code. Enter your information or load the labelled example to see the workflow.
No score, scan or platform result is invented while you wait.
A practical workflow
From input to a useful next step.
Capture raw response HTML
Use View Source or a saved response body for the page. Avoid substituting the browser’s post-render Elements view when collecting the raw version.
Add the rendered snapshot
Optionally copy the post-render document HTML from the same URL and state. This lets the checker compare what the two supplied snapshots contain.
Review important differences
Inspect the title, first H1, text tokens, canonical hint and other extracted signals. Verify findings in a real browser or platform inspection tool before changing the rendering architecture.
Know what you are measuring
The method behind the result.
Compare supplied raw and rendered HTML without executing untrusted page code. The scope and limitations below help you interpret the output and decide what to verify next.
No script execution
Pasted HTML is processed as text with a bounded lexical parser. It is never mounted into the document, and the checker does not fetch images, iframes or scripts from your input.
Content clues, not a crawler simulation
Text counts include page chrome and do not prove visual availability. Hidden content, CSS effects and browser state are outside this comparison. The tool does not claim to reproduce a particular AI crawler.
Compare like with like
A consent screen, logged-in state or different locale can change the rendered snapshot independently of server rendering. Keep the capture conditions aligned so the differences are meaningful.
Clear answers
Before you act on the result.
Understand the inputs, what the output can establish and how to use it in a broader audit.
Does this tool render my website?
No. It compares HTML text that you provide. Paste a raw response and, optionally, a rendered snapshot captured elsewhere. It does not launch a browser or execute page scripts.
What is the difference between View Source and Inspect?
View Source generally shows the response HTML. The Elements panel shows the current document after browser parsing and script changes. Use the appropriate version for each input field.
Can a low raw word count prove a site is invisible to AI?
No. It is a review signal. Important content, bot behaviour, response status, rendering support and the actual request context need separate verification.
Is the vocabulary overlap a content-completeness score?
No. It measures how many unique rendered text tokens also appear in the raw text. Shared navigation can inflate overlap, and word presence does not establish meaning or visual accessibility.
Does the JSON-LD count validate my schema?
No. It counts recognized JSON-LD script tags. Use a schema validator to inspect the JSON syntax, types, properties and correspondence with the visible content.
When should I consider server rendering?
Review it when commercially important content is missing from the initial response and your delivery requirements call for reliable HTML access. The right change depends on your platform, performance budget and actual inspection evidence.
Continue your investigation
The next check is one click away.
AI Crawler Checker
Test robots.txt rules by path for OpenAI, Perplexity, Claude and search bots.
Open this tool ↗Schema Markup Generator
Create type-specific JSON-LD with validation and a safe code preview.
Open this tool ↗Core Web Vitals Analyzer
Read PageSpeed, Lighthouse and CrUX reports with lab and field data separated.
Open this tool ↗DigiMSM · Server-rendered content implementation
Deliver important content in the right form.
DigiMSM can inspect your page delivery and implement server-rendered or pre-rendered content where the evidence supports it.
Built for DigiMSM · Methods reviewed 14 September 2026 · Free tool; service work is scoped separately.