seo-audit

Audits rendered HTML for metadata, canonicals, sitemap, robots, and structured data issues.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill seo-audit-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seo-audit
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/seo-audit
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill seo-audit-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical SEO issues like missing meta descriptions, broken canonical URLs, sitemap gaps, and invalid structured data silently hurt search visibility, and manually verifying every page's rendered HTML is tedious and error-prone. ## Core Features & Use Cases - Rendered-output verification: Builds the Next.js site, serves it in production mode, and inspects the actual HTML sent to crawlers rather than trusting source code. - Crawl graph cross-checks: Confirms every public route appears in the sitemap, sitemap URLs return 200, robots rules agree with the sitemap, and internal links resolve. - Safe fixes on a branch: Applies mechanical fixes on a local branch for approval, proposes judgment calls in a report, and never pushes, merges, or deploys. - Use Case: Run the audit before a site launch to catch a page accidentally marked noindex, a missing Open Graph image, and a case study absent from the sitemap, then review the fixes on the generated branch. ## Quick Start Ask the assistant to run the SEO audit on the website and report what it fixed, proposed, and verified clean.

Frequently Asked Questions about seo-audit

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

FAQPage Schema
How do I audit technical SEO on a Next.js website?

Build the site with npm run build, serve it in production mode, and fetch the rendered HTML of sampled pages to check titles, meta descriptions, canonicals, Open Graph tags, and structured data. Also fetch the sitemap, robots, and manifest routes directly to verify the crawl surface.

How to verify a sitemap matches actual site routes?

Cross-check that every public route appears in the sitemap and that every sitemap URL returns HTTP 200 from the running server. For registry-driven collections like components or case studies, fix derivation logic in sitemap.ts rather than hand-adding missing entries.

Does the SEO audit change visible page content or design?

No, the audit only touches behind-the-scenes surfaces: head metadata, crawl and index rules, link unfurl tags, structured data, and redirects. It never modifies layout, CSS, component structure, or visible copy.

Can the SEO audit push or deploy changes automatically?

No, all fixes are committed to a local branch named seo/YYYY-MM-DD-slug for review. Nothing is pushed, merged, or deployed; merging the branch approves the changes and deleting it rejects them.

What happens when the SEO audit finds nothing to fix?

A clean pass is a valid outcome and is reported as such, with no branch created and no invented changes. The report lists what was checked and verified clean, such as titles, canonicals, sitemap coverage, and structured data.