SEO Check
Run a single-page SEO and AEO check on a file or URL (title and meta lengths, one H1, heading order, answer-first lead, FAQ, structured data, canonical, internal links, alt text) and return a pass-or-fix table.
/seo-check<file path or URL>A read-only slash command that checks one page, from a Markdown or HTML file or a fetched URL, against ten rules: title and meta length, one H1, heading order, canonical, internal links, alt text, an answer-first lead, a visible FAQ, and structured data backed by visible content. It returns a pass-or-fix table with evidence and the skill for each fix.
Install to ~/.claude/commands/seo-check.md
npx agentscamp add commands/seo-checkCheck one page before it ships, or after it stops performing. This command reads a Markdown or HTML file, or fetches a URL, and runs ten checks that cover classic on-page SEO and answer-engine readiness together, returning a pass-or-fix table with the evidence behind each verdict. It reads only and changes nothing. For a whole site, use the seo-technical-auditor skill; for a ranked plan across pages, the seo-specialist agent.
Scope
Interpret $ARGUMENTS in this order:
- A URL (
http://orhttps://): fetch it withcurl -sL, record the final URL and status code, and keep the response headers forX-Robots-TagandLink: rel=canonical. - A path ending in
.html:Readit as the rendered page. - A path ending in
.mdor.mdx:Readthe frontmatter and body. Take the title fromseoTitleortitle, the meta description fromseoDescriptionordescription, the FAQ fromfaq, and treat the body's first paragraph (or asummaryfield the site renders) as the lead. Say in the report that rendered output was inferred from source. - A path to a page component (
.tsx,.astro,.vue): read themetadataexport or the<head>, mark the check partial, and recommend running it again on the built HTML. - Several arguments: one report per page, in the order given.
- Empty: ask "Which file or URL should I check?" and stop. Do not pick a page yourself.
NOTE
This command needs a target query to judge intent. Use one if the frontmatter or the user supplies it; otherwise use the H1 as the stand-in and say so. It does not check facts, sources, or voice; the content-editor agent and /brand-check do those.
Step 1 — Extract the fields
List what you pulled before judging it: title, meta description, canonical, robots directive, H1 text and count, the heading sequence (level and text), the first paragraph, the visible FAQ section, every application/ld+json block and its @type, internal links (count and targets), and images without alt. If a field is absent, write "absent"; absence is a finding, not a gap in the report.
Step 2 — Apply the ten checks
| Check | Rule |
|---|---|
| Title | 50 to 60 characters; contains the target query |
| Meta description | 120 to 155 characters; one or two sentences; not a copy of the title |
| H1 | exactly one; makes the same promise as the title |
| Heading order | no level skipped; H2s read as questions or searchable noun phrases |
| Answer-first lead | the first paragraph answers the title's question in 60 words or fewer and names the entity |
| FAQ | a visible section of at least three questions phrased the way people ask them; faq frontmatter that does not render is a FIX |
| Structured data | at least one JSON-LD block that parses, whose @type matches the page kind, and whose dates, author, and FAQ values appear on the page |
| Canonical | present, absolute, on the production host, self-referencing |
| Internal links | at least three to pages on the same site, each resolving |
| Images | every img has an alt attribute |
A verdict is PASS or FIX; there is no "warn". Attach one line of evidence to every row: the measured length, the quoted lead, the @type found, the count.
Step 3 — Verify the links
For a URL, check up to ten internal links with curl -s -o /dev/null -w '%{http_code}' <link> and list any that are not 200. For a file, Glob for the matching route or content file (for example /guides/x/y to src/content/guides/x/y.md or app/guides/x/y/page.*) and list any that do not exist. Stay read-only throughout.
Step 4 — Report
## /seo-check: <title or path>
Source: <URL (final status 200) | file path (inferred from source)>
Target query: <query | H1 used as stand-in>
| Check | Verdict | Evidence |
| ----------------- | ------- | ------------------------------------------------- |
| Title | PASS | 54 chars; contains "session replay" |
| Meta description | FIX | 171 chars; will truncate |
| H1 | PASS | 1 found; matches title |
| Heading order | FIX | H2 "Setup" followed by H4 |
| Answer-first lead | FIX | opens with "In today's…"; no answer in 60 words |
| FAQ | FIX | 3 entries in frontmatter, none rendered |
| Structured data | PASS | Article + BreadcrumbList; dates match byline |
| Canonical | PASS | self-referencing, https |
| Internal links | PASS | 7 links; all resolve |
| Images | FIX | 2 of 5 images lack alt |
Score: 5 of 10 pass.
Next: fix the lead and the FAQ first (geo-content-auditor), then the meta description.Step 5 — Route each FIX
End with one line per FIX naming what executes it: lead, headings, and FAQ wording go to the geo-content-auditor skill; JSON-LD that is missing, mistyped, or not backed by visible content goes to the schema-markup-generator skill; canonical, robots, and link problems that recur across pages go to the seo-technical-auditor skill; a site with no /llms.txt goes to the llms-txt-generator skill. The per-article loop this command sits in is described in the SEO content workflow with Claude Code.
Filed under
Related
- 9 Best Claude Skills for SEO (and AI Search)Compare Claude skills, commands, and agents for technical SEO audits, structured data, answer-engine readiness, llms.txt, content briefs, landing pages, Core Web Vitals, and brand voice.
- GEO Content AuditorAudit one published page or draft for answer-engine and LLM-citation readiness: an answer-first lead, question-shaped headings each answered in their first sentence, one fact per sentence, figures with a date and a source beside them, definitions that can be quoted whole, consistent entity names, and a visible FAQ block, then return a pass-or-fix scorecard and an ordered rewrite plan with replacement text. Use when you want to know why a page is not being quoted by AI Overviews or chat assistants and what to change in the prose, not in the markup or the crawl setup.
- Schema Markup GeneratorWrite JSON-LD structured data (Article or TechArticle, FAQPage, HowTo, SoftwareApplication, Product, BreadcrumbList, Organization) from the content that is actually visible on a page, fill the required and recommended properties from Google's structured-data documentation, link the nodes in one @graph, and validate the result with the Schema.org validator and the Rich Results Test before it ships. Use when a page needs structured data written, or an existing block checked property by property.
- SEO SpecialistUse this agent to review a site or a set of pages for search and answer-engine performance and get one prioritized plan: it checks technical hygiene with the seo-technical-auditor skill, the match between each page's title, H1, and lead and the query it targets, title and meta wording, internal linking, answer-first structure with the geo-content-auditor skill, and structured data with the schema-markup-generator skill, then ranks the fixes by effect and effort. Read-only; it never edits a page or invents a search volume. Examples: "review our docs site for SEO and tell me what to fix first", "why does this guide rank but never get cited by AI Overviews", "audit the ten pages in this folder and give me a plan".
- SEO Technical AuditorAudit a website's source or built output (Next.js, Astro, or static HTML) for technical on-page and crawl hygiene: title and meta description length and uniqueness, self-referencing canonicals, one H1 and an unbroken heading hierarchy, presence of JSON-LD, sitemap and robots.txt, redirect chains, internal-link click depth, and image alt text, then return one findings table ordered by severity with the file or route to fix. Use when you want the crawl and markup plumbing checked across a whole site, not the quality of the writing or the correctness of the structured data.
- llms.txt GeneratorGenerate or refresh a site's llms.txt (and, on request, llms-full.txt) from its sitemap, route tree, docs navigation, or content directory, following the llmstxt.org conventions: an H1 with the site name, a blockquote summary, H2 sections of links each with a one-line description taken from the page's own metadata, and an Optional section for secondary pages. Use when a site or docs repository needs the file created, or an existing one checked against the pages that actually exist today.
- An SEO Content Workflow in Claude Code: Brief, Draft, On-Page CheckA repeatable SEO content workflow in Claude Code: a content repo with CLAUDE.md, SERP research over Exa and Firecrawl MCP, a brief, a draft, and on-page checks.
- Brand CheckScore a draft file against the project's brand voice guide (brand-voice.md or a brand-voice skill) and list every violation with a rewrite, without editing it.