ssr-page-audit

To verify server-side rendering across public routes, fetch and inspect the raw HTML of each page to confirm critical content loads without client-side JavaScript. This checks for HTTP 200 status, valid titles, meta descriptions, canonical tags, and meaningful H1 tags.

You can check crawlable HTML by auditing the server output of your Next.js or Nuxt site to ensure meaningful body copy and required JSON-LD are present in the initial HTML response. This validates that dynamic routes and sitemap-derived paths return proper server-rendered content.

Yes, server-side rendering audits account for dynamic routes and sitemap-derived paths by validating intended public routes across local builds or deployed sites. This ensures every dynamic page returns HTTP 200 with valid meta tags and visible body copy.

The best way to detect client-side-only content is to analyze the initial server-rendered HTML and identify dynamic widgets requiring JavaScript. This assesses their impact on crawlability and accessibility by checking if essential content is missing without client-side execution.

To validate SSR configuration, audit frameworks like Astro, Next.js, and Nuxt alongside their deployment adapters to ensure proper server output. This verifies that each intended public route returns a 200 status with essential meta tags and visible body copy.

A server-rendered page might return a 200 status but fail SEO audits if critical content like titles, meta descriptions, canonicals, or meaningful H1 tags are missing from the initial HTML. This requires verifying that content is not dependent on client-side JavaScript execution.