Google renders, but not instantly
Googlebot crawls the raw HTML first, then queues the page for rendering. Content that only appears after JavaScript can be indexed late, or missed if rendering fails. Seeing both views shows the gap.
Technical SEO Tool
Pre-rendering (Fetch & Render)
Render a page with a real headless browser to see what a JavaScript-executing crawler sees: the post-render HTML and a screenshot, plus what changed versus the raw server HTML.
Render a page
We load the URL in headless Chromium with the user-agent you pick, then compare it to the raw HTML.
Rendering is not set up yet
This tool needs Cloudflare Browser Rendering, which is not enabled on this deployment. To turn it on:
- In the Cloudflare dashboard, enable Browser Rendering for the account.
- Create an API token with the Browser Rendering permission, scoped to that account.
- Add it to this Pages project as the
BROWSER_TOKENsecret (plus the account id asBROWSER_ACCOUNT_ID), then redeploy.
Until then, the other tools in the hub all work normally.
Why rendered HTML matters
Many crawlers do not render at all
Plenty of bots, including some AI crawlers and social previewers, read only the raw HTML. If your links, copy, or metadata are injected by JavaScript, those crawlers never see them.
Check the important elements
Compare the <title>, headings, body copy, and internal links between raw and rendered. Anything that appears only after render is content you are relying on Google to execute.
Fix it at the source
Server-side rendering or static pre-rendering puts the important content in the raw HTML for every crawler. StudioHawk helps teams choose and ship the right rendering strategy.
Is JavaScript hiding your content from crawlers?
Rendering problems are one of the most common, most invisible technical SEO issues. StudioHawk's specialists find them and fix them.