seo-audit

Audit SEO health, indexation, metadata, and Core Web Vitals for the Quiver web application.

1|Updated Oct 20, 2024
One-click install
npx skills add https://github.com/SteveChandler/quiver --skill seo-audit-stevechandler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seo-audit
Source: https://github.com/SteveChandler/quiver/tree/main/.agents/skills/seo-audit
Command: npx skills add https://github.com/SteveChandler/quiver --skill seo-audit-stevechandler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Diagnosing SEO issues across a large Next.js codebase requires checking routes, metadata, sitemaps, robots rules, and search performance data scattered across many files and exports. This Skill produces an evidence-backed, review-only SEO audit without publishing content, mutating production data, or running unnecessary commands. ## Core Features & Use Cases - Scoped SEO Audits: Audit technical SEO, indexation, on-page metadata, internal links, content quality, Core Web Vitals, or AEO citation readiness for a named route or query. - Deterministic Diagnostics: Runs the smallest appropriate command such as yarn seo:technical-audit, yarn seo:gsc-refresh, or yarn seo:recommend instead of broad crawls. - Protected Page Guardrails: Checks lib/seo/gsc-performance-protection.ts before recommending changes to pages with proven search performance. - Use Case: Ask for an audit of why a beach forecast page dropped in rankings, and receive prioritized findings with file-level evidence, impact, the smallest safe fix, and a verification check. ## Quick Start Audit the SEO health of the Quiver beach detail pages and report the highest-impact indexation and metadata findings with evidence.

Frequently Asked Questions about seo-audit

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

FAQPage Schema
How do I run an SEO audit on a Next.js app?▼

Define the audit surface first, such as technical SEO, indexation, or a specific route, then run the smallest deterministic command like `yarn seo:technical-audit`. Verify findings against current route, metadata, sitemap, and robots files rather than historical reports.

How do I diagnose why a page dropped in search rankings?▼

Start with a current Google Search Console export as the indexing and query source of truth, then check the route's metadata, canonical, and robots rules in code. Vercel and PostHog data describe traffic and behavior but do not prove ranking causality.

Does this audit change my site content or configuration?▼

No, the audit is review-only. It does not publish content, mutate production data, apply migrations, commit, or push unless you explicitly request that as a separate action.

Can I audit Core Web Vitals and AEO citation readiness?▼

Yes, the audit scope covers Core Web Vitals and AEO citation readiness alongside technical SEO, on-page metadata, internal links, and content quality. Scope the request to the specific surface you need investigated.

When should I not use this SEO audit workflow?▼

Use the narrower repository scripts instead for routine scheduled reporting. The audit avoids paid APIs, broad crawls, and external model calls unless they materially improve the requested investigation.