Enter a public page URL
Paste the complete URL, including https://, for a page you are authorized to test. Pages behind a login or firewall may not be accessible to the checker.
SSR & CSR Checker
Compare a page's initial HTML with its JavaScript-rendered HTML. Find metadata, content, heading, link and structured-data differences that deserve a closer SEO review.
Analyze a webpage
Enter a publicly accessible URL. The checker fetches the original response and renders the page in a browser, then compares the SEO signals it finds.
SCAN REPORT
Analysis complete
Rendering & SEO comparison
Initial text words0Extracted from original HTML
Rendered text words0Extracted after JavaScript
Word count change0%Relative to initial HTML
SEO differences0Signals requiring review
SEO signal comparison
| Signal | Initial HTML | Rendered HTML | Assessment |
|---|
Interpret results carefully. A difference between initial and rendered HTML is not automatically an SEO problem. Search engines can render JavaScript. This report identifies observable differences, not a guarantee of what a search engine indexed. Verify important findings with URL Inspection and a real browser.
How to use the SSR & CSR Checker
Run the comparison
Select Analyze page. The checker requests the original HTML and a browser-rendered version, then compares the SEO signals it can extract.
Review and validate findings
Compare word counts, titles, descriptions, canonical URLs, headings, links and JSON-LD. Confirm meaningful differences in a browser and Google Search Console URL Inspection.
What is server-side rendering (SSR)?
Server-side rendering generates HTML on the server and sends that HTML to the browser. Depending on the implementation, the initial response can already contain the main content, headings and metadata before client-side JavaScript runs.
What is client-side rendering (CSR)?
Client-side rendering uses JavaScript in the browser to create or update page content. Some CSR pages initially send a minimal HTML shell, with important text or interface elements added after scripts execute.
What should SEO teams compare?
- Page title, meta description, canonical and robots directives.
- Main headings and visible text content.
- Internal and external links.
- Structured data such as JSON-LD.
- Differences that may point to blocked scripts or delayed rendering.
Do differences automatically mean an SEO issue?
No. Differences can be expected on dynamic websites, and search engines can render JavaScript. Investigate important missing or inconsistent content, then verify the actual page and its index status with suitable testing tools.
Frequently asked questions
What does an SSR & CSR Checker do?
It compares selected SEO signals in the initial HTML response with the page after JavaScript has rendered. This can help identify differences in metadata, headings, links, text content and structured data.
What is the difference between SSR and CSR?
SSR generates HTML on the server before sending it to the browser. CSR relies on browser-side JavaScript to build or update some or most of the page. Many modern websites use a combination of both.
Is SSR always better for SEO than CSR?
No. Both approaches can support SEO when implemented correctly. SSR can make key content available in the initial HTML, while CSR requires important content and links to render reliably and be accessible to crawlers.
How do I use this checker?
Enter a public URL, select Analyze page, wait for the scan to finish, and review the comparison table and issue notes. Validate important findings with browser testing and Google Search Console URL Inspection.
Why is my page missing content in the initial HTML?
The page may rely on JavaScript to add content after the initial response. Check whether scripts and resources load successfully and whether the main content renders reliably. Depending on the site, server-side rendering, static generation or prerendering may be options.
Why might a scan fail or show incomplete results?
A site may block automated requests, rate-limit access, require authentication, or load content after the browser's wait period. A failed or incomplete scan does not by itself prove that the page has an SEO problem.
Can this checker tell me whether Google indexed my page?
No. It compares the HTML versions it can access and does not confirm Google's indexing decision. Use Google Search Console URL Inspection to review Google's reported index status and available rendered-page information.
What should I do if the canonical URL differs after rendering?
Inspect the canonical tags in both versions and confirm that the intended indexable URL is consistent. Check for duplicate canonical tags, JavaScript changes, redirects and conflicting signals before deploying a fix.