seo-audit

Verify technical and content SEO readiness of public pages before deployment.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill seo-audit-vtrka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seo-audit
Source: https://github.com/vTRKA/supervibe/tree/main/skills/seo-audit
Command: npx skills add https://github.com/vTRKA/supervibe --skill seo-audit-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seo-audit prevents pages from going live with broken indexing signals by turning an SEO request into a scoped, evidence-backed checklist that verifies technical SEO and content SEO.

Core Features & Use Cases

  • Technical SEO + metadata verification: checks crawlability (robots/sitemap/canonical/status codes), titles/descriptions, open graph/Twitter cards, and structured data (Schema.org) to reduce indexing risk.
  • Content and internationalization checks: validates headings, internal linking quality, duplicate/thin content risks, and hreflang/canonical per locale to protect ranking eligibility across markets.
  • Performance and validation with safe gating: runs Lighthouse and Core Web Vitals impact checks when a runnable preview exists, otherwise blocks or marks items unavailable to avoid overstated claims; outputs a structured PASS/FAIL/PARTIAL/BLOCKED decision packet with evidence.

Quick Start

Tell your AI tool: "Run an SEO audit for these pages and verify crawlability, metadata, schema, sitemap/robots, and Core Web Vitals using current 2026 best-practice research, then return an evidence-backed audit packet."

Frequently Asked Questions about seo-audit

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

FAQPage Schema
How do I verify technical SEO and metadata before a page goes live?

Technical SEO verification requires checking crawlability, titles, descriptions, open graph cards, and structured data to prevent broken indexing signals. You must gather evidence-based proof through static or browser checks to confirm metadata and schema are correctly configured.

What is the best way to audit hreflang and canonical tags for multi-locale pages?

Auditing hreflang and canonical tags for multi-locale pages involves validating each locale's configuration to protect ranking eligibility across markets. You must verify canonical URLs and hreflang annotations per locale to ensure international targeting signals are properly resolved.

How do I run a Lighthouse audit for Core Web Vitals on JS-heavy routes?

Running Lighthouse audits for Core Web Vitals on JS-heavy routes requires a runnable preview to execute performance checks. If no preview exists, the audit must mark items unavailable or block them to avoid overstating performance claims without evidence.

Can I check Schema.org structured data without a fully deployed page?

Schema.org structured data validation uses static or browser checks to assess structured data on landing pages or articles. The audit verifies schema correctness and outputs a structured PASS, FAIL, PARTIAL, or BLOCKED decision packet based on the available evidence.

What should an SEO readiness checklist include for crawlability risks?

An SEO readiness checklist for crawlability risks must include robots directives, sitemap validation, canonical tags, and HTTP status code checks. It should also assess internal linking quality and duplicate or thin content risks to protect ranking eligibility.

Why does my SEO audit return a BLOCKED or PARTIAL status on some checks?

An SEO audit returns BLOCKED or PARTIAL status when evidence is missing, such as lacking a runnable preview for Lighthouse checks. This gating mechanism prevents overstated claims by ensuring every PASS or FAIL decision is backed by verifiable proof.