A website can look complete in your browser while its first HTML response contains little of the page. To check server-side rendering, compare three things: the server response, the visible page without JavaScript and the page after scripts run. A framework name or an HTTP 200 response alone does not answer the question.
Start with a specific page and its important content
Choose a public landing page, article or product page. Write down what should be available: its main heading, description, product information and links to related pages. Check the published URL, not a development preview, and record whether a login or location setting changes the result.
Run the Milten SEO audit to inspect SEO, metadata and SSR results for up to five pages of the same website. Open the relevant page in the report. A result from one template does not establish the state of every route or language.
Read the response, then check what is actually visible
In the browser's Network panel, select the document request and read its response. Look for the heading and important links as HTML elements. Text inside a JSON payload, script or serialized component data is not the same as visible page content.
Next, disable JavaScript and reload in a clean browser context. Does the heading appear? Can you read the main description and follow the links? Hidden streaming containers can contain the right words while still needing a script to move them into the visible page. Searching the response for a phrase will miss that distinction.
Re-enable JavaScript and reload. Compare the same content after data requests and rendering finish. Record which section depends on scripts rather than relying on a single text-volume score.
Understand a small client-rendered example
This teaching fragment inserts the product information with JavaScript. It is not a customer measurement.
<main id="product"><p>Loading product information...</p></main>
<script>
document.getElementById('product').innerHTML =
'<h1>Trail backpack</h1><p>A 25-litre day pack.</p>';
</script>
With JavaScript enabled, the heading appears. With JavaScript disabled, the visitor receives a loading message. A server-rendered version would include the meaningful heading and description in the returned markup; interactive features can still be added afterwards.
Do not treat every difference as a defect. An account menu, live stock indicator or personalized price may intentionally be dynamic. Identify the content the public page needs before changing its rendering strategy.
Separate an SSR finding from an indexing decision
Google can render JavaScript. Missing content in the first response is therefore a diagnostic finding, not proof that the URL cannot be indexed. Check the current URL in Search Console and inspect its crawl date, indexing state and selected canonical. Google's JavaScript SEO documentation explains how crawling and rendering fit into indexing.
Also check HTTP status, robots directives, canonical and internal links. A complete server-rendered page can still intentionally carry noindex or point to another canonical URL. The technical SEO checklist covers those separate checks.
Verify the change on the published version
After changing the template, repeat the same three comparisons on the published URL. Check another page using that template and each affected language. Confirm that the heading, useful text and crawlable links remain available, and that scripts do not replace the canonical with a different URL.
Keep the before-and-after observations with the deployment date. Then check when Google next crawls the page. A successful browser check confirms the delivered content; a later Search Console result confirms what Google processed. Check your website's SEO and SSR and verify indexing separately.
