GEO Content Auditor
Audit 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.
Give this skill one page and it checks the eight prose properties that let an answer engine quote it correctly: answer-first lead, question-shaped headings, one fact per sentence, dated and sourced figures, standalone definitions, consistent entity names, a visible FAQ, and a visible date. It returns a scorecard with quoted evidence and a rewrite plan.
Install to ~/.claude/skills/geo-content-auditor/SKILL.md
npx agentscamp add skills/geo-content-auditorGenerative engine optimization and answer engine optimization come down to a plain question: if a model had thirty seconds with this page, could it lift a correct, attributable answer? This skill audits one page for that. It reads the rendered text, checks eight properties of the prose that make a passage quotable (not the markup, not the crawl plumbing), scores each pass or fix with the sentence that earned the verdict, and returns a rewrite plan ordered by effect. It never promises a citation; nobody can. It makes the page easy to quote correctly.
When to use this skill
- A page ranks but does not appear in AI Overviews or assistant answers for the question it targets.
- You are refreshing an article and want the structural edits before the content edits.
- A draft written from a seo-content-brief-writer brief is finished and you want the lead, headings, and FAQ checked before the content-editor agent does the claims pass.
- A definition page or glossary entry should become the sentence a model repeats.
When NOT to use this skill
- Titles, canonicals, sitemaps, redirects: the seo-technical-auditor skill.
- Writing or validating JSON-LD for a visible FAQ: the schema-markup-generator skill. This skill tells you whether the FAQ exists and reads well; that one marks it up.
- Fact-checking claims or fixing voice: the content-editor agent and the /brand-check command.
- A whole site: run this per page, or ask the seo-specialist agent, which samples pages and applies this skill to each.
Instructions
- Get the text as a reader sees it. For a URL,
curl -sLand reduce to the main content; for a Markdown file, read the body plus any frontmattersummary,description, andfaqfields that the site renders visibly. Write down the primary question the page answers and its main entity (a product, a concept, a person) in one line each. If you cannot, that is the first finding. - Answer-first lead. Take the first paragraph after the H1, or the visible summary. Can it stand alone as the answer to the primary question in roughly 40 to 60 words, naming the entity? Quote it. A lead that opens with scene-setting or with a promise ("In this guide you will learn") is a fix.
- Question-shaped headings. List every H2 and H3. Is each one a question people type, or a noun phrase a model would match to one ("How X differs from Y", "X pricing", "X vs Y")? Does the first sentence under it answer it? Mark headings that are clever rather than literal, and sections whose answer arrives in the third paragraph.
- One fact per sentence. Sample the key paragraphs: the lead, the first paragraph under each H2, the conclusion. Flag sentences carrying two claims joined by "and" or "while", and sentences that borrow their subject from the previous one ("It also supports…"). A quoted sentence loses its neighbours; each must survive alone.
- Dated and sourced figures. Find the numbers, for example
rg -n '[0-9][0-9,.]*\s?(%|percent|million|billion|ms|x\b)' page.md, and read each hit. A figure needs a date (a year, an "as of", or a dated source) and a source (a link or a named publication) in the same sentence or the next. Flag the undated and the unsourced; a model that quotes them attaches your name to a stale or unverifiable number. - Liftable definitions. For the main entity and each term the page introduces, look for a sentence shaped "X is a that ", with the term, not a pronoun, as the subject. A definition that is absent, split across sentences, or buried in a parenthesis is a fix; write the replacement.
- Entity naming. The first mention in each major section uses the full name (product with vendor, person with role, acronym expanded once). Flag long stretches of "the tool", "the platform", and "it", and any inconsistent spelling or casing of the entity.
- FAQ block and freshness. Is there a visible section of questions phrased the way people ask them ("How much does X cost?", not "Pricing?"), each answered in 40 to 60 words with the entity named in the answer? If frontmatter
faqentries exist but do not render, say so: hidden FAQ is a markup problem, not an answer. Note whether the page shows a publication or updated date. - Write the plan. Order the fixes: lead first, then definitions, then headings, then figures, then FAQ, then sentence-level edits. For the top three, write the replacement text. Keep every fact exactly as it was; this skill restructures, it does not invent.
WARNING
Never manufacture an FAQ, a statistic, or a date to satisfy a check. An invented "as of" date is worse than none, because a model that cites it spreads the error under your name. When a figure has no source, the fix is to find one or cut the figure.
NOTE
Passing all eight checks does not guarantee a citation; engines choose sources for reasons nobody outside them can see. The checks remove the reasons a page gets skipped or misquoted.
Output
A scorecard table with one row per check (Check, Verdict, Evidence quoted from the page), the ordered rewrite plan, replacement text for the top three items, and a list of figures that need a date or a source. For a page that passes, say so briefly; a short plan is a legitimate result.
Filed under
claude · seo · geo · aeo · ai-search · marketers
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.
- 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".
- 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 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.
- SEO CheckRun 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 Content Brief WriterWrite an SEO content brief from a target keyword plus the SERP notes and competitor outlines you paste in: search intent with evidence, an angle the ranking pages under-serve, an H2/H3 outline, the entities and questions to cover, internal-link placeholders, a length-checked meta title and description, and a word-count target explained by the SERP rather than a rule of thumb. Use when a writer or a coding agent needs a brief before drafting an article and you do not want search volumes, difficulty scores, or rankings invented.
- Does AI-Written Content Rank in 2026? What Google Actually SaysWhat Google's own documentation says about AI-generated content in 2026: what it rewards, what scaled content abuse is, how AI features cite, and a checklist.
- Content EditorUse this agent to edit marketing and editorial drafts (blog posts, landing pages, emails, social copy, newsletters) for clarity and brand voice while marking every unsourced claim, statistic, and superlative with a [CITATION NEEDED] or [VERIFY] tag and a one-line reason, never inventing a source, and returning the edited draft with a change log. Examples — 'edit this post before it goes to the client', 'tighten this launch email and tell me which numbers I need to back up', 'check this page copy against brand-voice.md and mark anything we cannot prove'.