Free tool · AI search
CSR vs SSR Checker: Is Your Content in the Raw HTML?
Most AI crawlers don't run JavaScript. This checker shows what's in the HTML your server sends, so you can see whether search engines and AI tools can read your content without rendering.
By Ajay Padhy · Updated · Free, no sign-up
Disclaimer
This checks the HTML your server returns without running JavaScript. It's a strong indicator, not a full render. Results can differ by URL, device, location, logged-in state and bot protection. Confirm what Googlebot sees with URL Inspection in Google Search Console (View crawled page).
Privacy: URLs you check are fetched once to produce the result and aren't stored.
SSR vs CSR in plain English
- Server-side rendering (SSR): the server sends finished HTML with your text, links and metadata already in it. Static site generation (SSG) and incremental static regeneration (ISR) work the same way from a crawler's point of view.
- Client-side rendering (CSR): the server sends a nearly empty page plus JavaScript, and the browser builds the content. Single-page apps built with React, Vue or Angular often work this way unless configured otherwise.
- Hybrid: part of the page is in the HTML and the rest loads with JavaScript (for example, reviews, prices or tabs).
Why it matters for SEO and AI search
| Who's reading | Runs JavaScript? | What happens with a CSR page |
|---|---|---|
| Googlebot | Yes, in a later rendering step | Usually indexed, but rendering can be delayed and errors can hide content |
| Bingbot | Yes, with limits | Similar to Google, generally less forgiving |
| Most AI crawlers (e.g. OpenAI's and Anthropic's) | Generally no | They see the empty shell, so your content may never reach their index |
| Social previews (LinkedIn, X, WhatsApp) | No | Previews use only the raw HTML meta tags |
In 2024, Vercel and MERJ analysed AI crawler traffic and found the major AI crawlers fetched JavaScript files but didn't execute them. If you care about being cited by AI assistants, your important content needs to be in the HTML.
How the checker decides
It fetches the page as a normal browser would (without running scripts) and measures:
- visible words in the HTML, the H1, and the number of internal links
- title, meta description, canonical and structured data
- signs of client-side apps, such as an empty
<div id="root">or an "enable JavaScript" message - the framework in use where it can tell (Next.js, Nuxt, Angular, WordPress and others)
Add a sentence you can see on the page in the optional box, and it checks whether that exact text is in the raw HTML. That's the most reliable single test.
How to check manually
- Right-click the page and choose View page source (not Inspect). That's the raw HTML.
- Search it for a sentence from the middle of the page. If it isn't there, it's added by JavaScript.
- In Chrome DevTools, disable JavaScript and reload. What you still see is what non-rendering crawlers get.
How to fix client-side rendering
- Use your framework's server rendering or static generation (Next.js, Nuxt, SvelteKit, Angular SSR).
- For an existing single-page app, prerender key routes at build time.
- Keep navigation as real
<a href>links in the HTML, not click handlers. - Put title, meta description, canonical and JSON-LD in the server response, not injected later.
If a rebuild is on the table, my website development work starts with exactly this.
FAQ
CSR vs SSR Checker: common questions
Short answers to what people ask most about this tool and topic.
Not automatically for Google, which renders JavaScript, but it adds risk: rendering can be delayed, errors can hide content, and links built by JavaScript may not be discovered. For AI crawlers that don't run JavaScript, content that only exists after rendering is effectively invisible.
It can use server rendering, static generation or client rendering per page or component. Pages built with the App Router render on the server by default, but components marked "use client" that fetch their data in the browser can still leave gaps. Test key pages rather than assuming.
Some content is in the HTML but key signals are thin, such as few internal links, no H1 or your test phrase missing. Look at the individual checks to see which part loads with JavaScript.
Yes. In Google Search Console, use URL Inspection, then View crawled page or Test live URL. It shows the rendered HTML and a screenshot.
Built by
SEO and AI search (GEO) consultant with 14+ years in digital growth. I build these tools for the checks I run on client sites every week. Need more than a quick check? See my SEO-friendly website development or get in touch.
Found this useful? Link to it
If you mention the csr vs ssr checker in a guide, checklist or resource list, you can copy this link:
<a href="https://ajaypadhy.com/tools/ssr-checker">CSR vs SSR Checker</a>
More free tools
Have a growth problem worth solving?
Tell me where you're stuck. On a 30-minute intro call I'll tell you where I think the constraint is and what I'd look at first — whether or not we end up working together.