ssr-page-audit

Audit server-side rendering coverage for public routes across SSR frameworks.

Updated May 6, 2026

Search Tags:#html #seo #ssr #crawlability #server-side-rendering #web-auditing

Ready to run

npx skills add https://github.com/Clvrwrk/Codex-Site-Maintenance-Repair-Technician --skill ssr-page-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ssr-page-audit
Source: https://github.com/Clvrwrk/Codex-Site-Maintenance-Repair-Technician/tree/main/skills/ssr-page-audit
Command: npx skills add https://github.com/Clvrwrk/Codex-Site-Maintenance-Repair-Technician --skill ssr-page-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Server-rendered HTML is essential for search engines, accessibility, and fast initial content. This skill verifies that each intended public page is rendered on the server and that critical content is present in the initial HTML, regardless of client-side execution.

Core Features & Use Cases

Validate SSR configuration across frameworks (e.g., Astro, Next.js, Nuxt) and deployment adapters to ensure server output.
Fetch and inspect the raw HTML of each intended route, verifying 200 status, presence of title, meta description, canonical, at least one meaningful H1, and visible body copy.
Detect client-side-only content or dynamic widgets that require JavaScript and assess their impact on crawlability and accessibility.
Generate reports summarizing SSR coverage across routes, including issues found and remediation steps.

Quick Start

Run the SSR Page Audit against your public routes to validate server-rendered HTML and identify any missing or problematic content.

Frequently Asked Questions about ssr-page-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify server-side rendering is working for all my public routes?▼

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.

How do I check if my Next.js or Nuxt site delivers crawlable HTML to search engines?▼

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.

Does server-side rendering audit work with dynamic routes and sitemap-derived paths?▼

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.

What is the best way to detect client-side-only content that impacts SEO crawlability?▼

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.

How do I validate SSR configuration across different frameworks and deployment adapters?▼

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.

Why does my server-rendered page return a 200 status but fail SEO audits for missing content?▼

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.