seo-audit
SEO auditing tool for checking site metadata and structure.
Install
mkdir -p .claude/skills/seo-audit-zioalex && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12348" && unzip -o skill.zip -d .claude/skills/seo-audit-zioalex && rm skill.zipInstalls to .claude/skills/seo-audit-zioalex
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run a repeatable SEO audit of the Vox Quieta frontend (Next.js App Router + next-intl) and the deployed voxquieta.org site. Use when the user asks to audit SEO, check meta tags / titles / descriptions, verify sitemap / robots / canonical / hreflang, find missing alt text, or check for broken links and 4XX pages. Produces a prioritized report separating real issues from boilerplate.Key capabilities
- →Perform static codebase scans for SEO issues
- →Run live checks on deployed sites for HTTP status and meta tags
- →Verify `robots.txt` and `sitemap.xml` contents
- →Assess `hreflang` correctness and crawlability
- →Generate a prioritized SEO audit report with evidence
How it works
The skill executes static checks on the codebase and live checks on the deployed site to identify SEO best practice violations, then compiles these findings into a prioritized report.
Inputs & outputs
When to use seo-audit
- →Audit site SEO
- →Verify meta tags
- →Check for broken links
About this skill
SEO Audit (Vox Quieta)
Audit the site's discoverability and produce a prioritized, evidence-backed
report. The frontend is Next.js 16 App Router + next-intl, locale-prefixed
(localePrefix: "always"), 11 locales, deployed at https://voxquieta.org.
This skill is read-only — it inspects and reports; it never edits the site.
Steps
-
Static codebase scan (always). Run:
bash scripts/seo-static-check.shIt prints PASS/FAIL/WARN for metadataBase, Open Graph / Twitter, sitemap, robots, favicon,
title.template, homepage title length, per-locale metadata coverage (all 11frontend/messages/*.json), image alt-text exposure, and manual-review reminders (hreflang on sub-pages, client-rendered homepage). Exit code is non-zero if any FAIL — note which checks fail. -
Live check (if the domain is reachable). Try:
bash scripts/seo-live-check.shIt reports HTTP status for key routes (including an un-prefixed
/privacyand a bogus path to confirm 404 behaviour), the rendered<head>meta of the homepage + a sub-page, robots.txt/sitemap.xml contents, and a server-rendered word-count gauge. The Claude Code web sandbox usually blocks this (403 host_not_allowed). If it fails, ask the user to run the script on a networked machine and paste the output, or to provide the "live-site data needed" list (see the audit plan / README of this skill). -
Manual judgement passes (the scripts can't decide these):
- hreflang correctness —
frontend/src/app/[locale]/layout.tsxalternates.languagespoint to locale roots (/en,/it, …); inherited by sub-pages, so/en/privacymislabels its alternates. Confirm. - Crawlability —
frontend/src/app/[locale]/page.tsxis"use client";generateMetadatastill emits title/description server-side, but body text is client-rendered. Check how much indexable content the homepage exposes. - Links — internal links use
@/i18n/navigationLink(locale-safe). Spot-check external links, esp.https://disciplestoday.org(ChurchFinderModal.tsx), for liveness.
- hreflang correctness —
-
Write the report. Use this structure:
- A verdict table mapping each reported claim (broken links, 4XX, missing
alt, missing descriptions, duplicate/missing meta, long/unoptimized titles)
to real here? yes / partly / no with one-line evidence (
file:line). Call out boilerplate that doesn't apply (this site has no images, so "missing alt text" usually doesn't apply). - Findings grouped: metadata infra, titles, crawl/index files, routing/4XX,
links — each with
file:lineevidence. - Prioritized roadmap (P0/P1/P2), reusing the existing per-locale
generateMetadata+messages/*.jsonpattern. Do not propose fixes outside SEO scope.
- A verdict table mapping each reported claim (broken links, 4XX, missing
alt, missing descriptions, duplicate/missing meta, long/unoptimized titles)
to real here? yes / partly / no with one-line evidence (
Notes
- Keep findings grounded in
file:lineevidence or script/live output — no floating claims. - For deeper or delegated runs, the
seo-auditorsubagent (.claude/agents/seo-auditor.md) contains the same checklist and can run autonomously inside a larger task. - Reference doc with the full current-state findings:
the SEO audit plan written under
~/.claude/plans/(if present).
When not to use it
- →When editing the site based on audit findings
- →When the deployed domain is unreachable for live checks
- →When the user wants to ignore boilerplate findings
Limitations
- →It is read-only and never edits the site
- →Live checks may be blocked by web sandbox environments
- →It requires manual judgment for `hreflang` and crawlability
How it compares
This skill combines static codebase analysis with live site checks for a specific Next.js/next-intl application, providing a tailored and evidence-backed SEO audit report unlike generic SEO tools.
Compared to similar skills
seo-audit side by side with the closest alternatives in the catalog.
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
seo-audit
davila7
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
seo
ThanhTrunggDEV
Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.
seo
manusco
SEO and GEO audit: structured data, canonical, schema, AI-citation optimization.
seo-audit
openzigs
Perform a comprehensive technical SEO audit on a website using the openzigs SEO Suite.
indexing-issue-auditor
ranbot-ai
High-level technical SEO and site architecture auditor. Invoke to scan local or live environments for indexing, crawl budget, and structural errors.
seo-flow
hschne
Run the full SEO workflow as a guided, interview-first sequence — discover requirements, then keyword research, on-page, technical, performance, and audit. Use when the user wants to improve a site's SEO end to end, be walked through the whole SEO process, start SEO from scratch, or mentions "seo fl