For sites built on JavaScript frameworks
See what your page says before its JavaScript runs
Read a page as your server sends it and as a browser renders it, and compare what each one contains.
The problem
Search engines can render JavaScript, but not always and not straight away, and many link-preview and AI crawlers do not render it at all. A product page whose description, price and links arrive by a client-side fetch can look complete in every browser and be close to empty for anything that only reads the HTML.
How domscout handles it
renderJs: false answers from one HTTP request, exactly as your server sent the page, without running any script. The same request without it renders the page in Chromium. Both return the same shape: the Markdown, the links, the title and description, metadata.wordCount and metadata.contentQuality. A page that drops from hundreds of words to a handful, or loses its links, without JavaScript depends on the browser for that content. The two requests cost the same, and the served one comes back faster.
Where it shows up
- An audit of templates that render their main content on the client.
- A CI check that key pages keep their content in the served HTML.
- A comparison after moving a page between server and client rendering.
The request
POST /scrape. Available on every plan, including the free Hobby plan. Each request costs 1 credit, with or without renderJs. contentQuality is ok, low_text, empty or likely_blocked.
Go further
More in SEO and site health: SEO regression checks · Link preview checks · Find every page on a site · Website migration checks · Page weight and load metrics · Backlink checks · JSON-LD structured data checks · hreflang checks · Website audits for prospects · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.