Update to AEOTester

{
  "description": "AI SEO audit of a website - the AEOTester checklist for answer engine optimization (AEO) and generative engine optimization (GEO), 26 checks and 133 points - with a scored report in aeotester-report.md. Audits the site code in the current repo, or a live site when given a URL. Use when the user asks to audit a site or URL for AI search visibility, AI SEO, AEO, GEO, llms.txt, schema markup, AI crawler access or agent readiness.",
  "included_files": [
    {
      "relative_path": "references/README.md",
      "size_in_bytes": 563
    },
    {
      "relative_path": "references/ai-bots.json",
      "size_in_bytes": 19808
    },
    {
      "relative_path": "references/rubric.json",
      "size_in_bytes": 234297
    },
    {
      "relative_path": "references/rubric.schema.json",
      "size_in_bytes": 2199
    },
    {
      "relative_path": "scripts/audit.mjs",
      "size_in_bytes": 2992
    },
    {
      "relative_path": "scripts/checks/agent-readiness/controls.mjs",
      "size_in_bytes": 7882
    },
    {
      "relative_path": "scripts/checks/agent-readiness/markdown.mjs",
      "size_in_bytes": 13795
    },
    {
      "relative_path": "scripts/checks/agent-readiness/protocols.mjs",
      "size_in_bytes": 11065
    },
    {
      "relative_path": "scripts/checks/agent-readiness/server-rendered.mjs",
      "size_in_bytes": 5302
    },
    {
      "relative_path": "scripts/checks/ai-access/bot-crawlability.mjs",
      "size_in_bytes": 7282
    },
    {
      "relative_path": "scripts/checks/ai-access/content-signals.mjs",
      "size_in_bytes": 6786
    },
    {
      "relative_path": "scripts/checks/ai-access/llms-txt.mjs",
      "size_in_bytes": 6067
    },
    {
      "relative_path": "scripts/checks/content/accessibility.mjs",
      "size_in_bytes": 4632
    },
    {
      "relative_path": "scripts/checks/content/author.mjs",
      "size_in_bytes": 19340
    },
    {
      "relative_path": "scripts/checks/content/freshness.mjs",
      "size_in_bytes": 4202
    },
    {
      "relative_path": "scripts/checks/content/headings.mjs",
      "size_in_bytes": 3202
    },
    {
      "relative_path": "scripts/checks/content/image-alt.mjs",
      "size_in_bytes": 2369
    },
    {
      "relative_path": "scripts/checks/content/internal-links.mjs",
      "size_in_bytes": 4239
    },
    {
      "relative_path": "scripts/checks/content/quality.mjs",
      "size_in_bytes": 7391
    },
    {
      "relative_path": "scripts/checks/crawlability/http-behavior.mjs",
      "size_in_bytes": 13952
    },
    {
      "relative_path": "scripts/checks/crawlability/https.mjs",
      "size_in_bytes": 9244
    },
    {
      "relative_path": "scripts/checks/crawlability/indexability.mjs",
      "size_in_bytes": 9616
    },
    {
      "relative_path": "scripts/checks/crawlability/sitemap.mjs",
      "size_in_bytes": 6961
    },
    {
      "relative_path": "scripts/checks/meta/description.mjs",
      "size_in_bytes": 3679
    },
    {
      "relative_path": "scripts/checks/meta/language.mjs",
      "size_in_bytes": 4954
    },
    {
      "relative_path": "scripts/checks/meta/open-graph.mjs",
      "size_in_bytes": 4144
    },
    {
      "relative_path": "scripts/checks/meta/title.mjs",
      "size_in_bytes": 2418
    },
    {
      "relative_path": "scripts/checks/meta/twitter-cards.mjs",
      "size_in_bytes": 3778
    },
    {
      "relative_path": "scripts/checks/meta/viewport.mjs",
      "size_in_bytes": 3287
    },
    {
      "relative_path": "scripts/checks/structured-data/present.mjs",
      "size_in_bytes": 9313
    },
    {
      "relative_path": "scripts/checks/structured-data/valid.mjs",
      "size_in_bytes": 6288
    },
    {
      "relative_path": "scripts/lib/engine.mjs",
      "size_in_bytes": 11094
    },
    {
      "relative_path": "scripts/lib/html.mjs",
      "size_in_bytes": 19160
    },
    {
      "relative_path": "scripts/lib/jsonld.mjs",
      "size_in_bytes": 3952
    },
    {
      "relative_path": "scripts/lib/noindex.mjs",
      "size_in_bytes": 6280
    },
    {
      "relative_path": "scripts/lib/remote.mjs",
      "size_in_bytes": 21233
    },
    {
      "relative_path": "scripts/lib/report.mjs",
      "size_in_bytes": 9817
    },
    {
      "relative_path": "scripts/lib/robots.mjs",
      "size_in_bytes": 3512
    },
    {
      "relative_path": "scripts/lib/schema-validator.mjs",
      "size_in_bytes": 14798
    },
    {
      "relative_path": "scripts/lib/site.mjs",
      "size_in_bytes": 15547
    },
    {
      "relative_path": "scripts/lib/sources.mjs",
      "size_in_bytes": 8426
    }
  ],
  "name": "audit",
  "skill_md_contents": "---\nname: audit\ndescription: AI SEO audit of a website - the AEOTester checklist for answer engine optimization (AEO) and generative engine optimization (GEO), 26 checks and 133 points - with a scored report in aeotester-report.md. Audits the site code in the current repo, or a live site when given a URL. Use when the user asks to audit a site or URL for AI search visibility, AI SEO, AEO, GEO, llms.txt, schema markup, AI crawler access or agent readiness.\nargument-hint: \"[site-folder | https://site.com[/page]] [--pages N] [--all]\"\nallowed-tools: Read, Glob, Grep, Bash(node --version), Bash(node ${CLAUDE_PLUGIN_ROOT}/skills/audit/scripts/audit.mjs:*)\n---\n\n# AEOTester audit\n\nAudits a site against the AEOTester rubric and writes `aeotester-report.md` in the current directory (for a folder: in that folder).\n\nTwo ways to run it:\n\n- **Repo mode** (no argument, or a folder): reads the site's files in this repo. No network requests.\n- **URL mode** (an `http://` or `https://` URL): fetches the live site, the way an AI crawler sees it.\n  - A page URL (`https://site.com/blog/post`) audits that one page, plus the site-wide files (robots.txt, llms.txt, sitemap, `/.well-known/`).\n  - The homepage (`https://site.com`) audits a sample: the homepage, the pages linked from the header, nav and footer, and a listing page plus one item from each section (blog, docs, products...), about 25 pages at most. One page per template finds nearly every issue without crawling the whole site.\n  - `--pages N` changes the sample size. `--all` audits every page found (up to 500, or `--pages N`).\n  - Requests go to that site only, are polite (a few at a time, with timeouts) and skip pages that robots.txt disallows. The README lists exactly what is fetched.\n\n## Other hosts (Codex, ChatGPT)\n\nThe commands below start with Claude Code's plugin-root variable. A host that does not substitute it (Codex, ChatGPT) leaves it as literal text: replace that prefix with the absolute path of the plugin root, which is the folder two levels above the folder that contains this SKILL.md (it holds `skills/`). Do the same for the skill-folder variable, which is the folder that contains this SKILL.md. Write the resolved path into the command; never run it with the variable unexpanded. Slash commands such as `/aeotester:audit` are Claude Code syntax: elsewhere the user asks for this skill by name or mention, and `$ARGUMENTS` means whatever folder, URL or flags their request names (leave it out if there are none). The scripts need Node 18+ and a shell, so the skill only works in a host that can run them.\n\n## Rules\n\n- Read-only. The only file written is the report, and the script writes it. Never edit site files here; fixes belong to `/aeotester:fix`.\n- Repo mode stays inside the current repo and makes no network requests.\n- URL mode only fetches the site the user named. Use it only when the user gave a URL or asked for the live site.\n\n## Steps\n\n1. **Check Node.** Run `node --version`. The scripts need Node 18 or newer. If Node is missing, tell the user the audit needs Node 18+ and stop.\n\n2. **Run the audit.** Pass the user's arguments through (`$ARGUMENTS`, default `.`):\n\n   ```bash\n   node ${CLAUDE_PLUGIN_ROOT}/skills/audit/scripts/audit.mjs $ARGUMENTS\n   ```\n\n   It prints a short summary and writes `aeotester-report.md`.\n\n3. **Handle the mode the summary reports:**\n   - **\"No build output found\"** (Astro, Next.js, Hugo, Eleventy, Vite): the audit reads built HTML because that is what crawlers and agents receive. Ask the user whether to run the build command it names. Only run it if they say yes, then run the audit again. If they say no, offer URL mode on the deployed site instead.\n   - **Report-only** (WordPress or another database-backed CMS): page content lives in the database, so the repo cannot be scored. Say so plainly and offer to audit the live site with `/aeotester:audit https://their-site.com`. Do not try to edit anything.\n   - **No pages found**: in repo mode, ask where the site's HTML lives; in URL mode, say the site could not be fetched and show the status from the summary (it may block automated requests).\n\n4. **Summarize in chat** in a few lines, not the whole report:\n   - the score, percentage and grade, and in URL mode how many pages were audited,\n   - the three to five issues that lose the most points (see \"Writing each issue\" below),\n   - pages left out of the score and advice (see \"Not scored and advice\" below),\n   - checks marked \"predicted from config\" or \"inconclusive\" that the user should confirm (see \"Live checks\" below),\n   - the next step: in repo mode, `/aeotester:fix` applies the auto-fixable items, always with a diff and a confirmation first; in URL mode, open the site's code and run `/aeotester:fix` there.\n\n   Link the report file. Do not paste it.\n\n   **Writing each issue.** Write for someone who has never seen the rubric:\n   - Say what the check looks for and why it matters to AI search or agents, in one plain sentence, before the finding.\n   - Show a short concrete example of what is missing or what the fix adds, such as the exact tag or line. For Content Signals, for example: \"`robots.txt` sets rules for GPTBot and ClaudeBot, but has no `Content-Signal:` line. That line tells AI companies whether they may use your pages for search results, as answer input, or for training, for example `Content-Signal: search=yes, ai-input=yes, ai-train=no`.\"\n   - Never show bare rubric labels such as \"auto-fix\", \"assisted\" or \"inconclusive\". Say what they mean instead: \"`/aeotester:fix` can change this for you\" (auto-fix; after a URL audit, add \"in the site's code\"), \"needs your input, such as dates or copy, so the fix will guide you\" (assisted), \"can't be confirmed from the files, check the live site\" (inconclusive or predicted from config in repo mode), \"the site blocked or did not answer this request, so it was not scored down\" (inconclusive in URL mode).\n   - Name the affected pages as Markdown links to the page on the live site: the page's canonical URL if it has one, otherwise the base URL plus the served path. Without a known base URL, link the file path instead. List up to 10 pages inline, then say \"and N other pages\". Get the full list from `--json`, because the printed report shortens it.\n\n   **Not scored and advice.** Neither of these costs points, so never present them as issues or count them as points lost:\n   - `excludedPages` in `--json` lists pages kept out of search on purpose (noindex, not the homepage, not in the sitemap). Say in one line that they were not scored and why, linking them like other pages, for example \"[privacy](https://site.com/privacy) and [terms](https://site.com/terms) are kept out of search on purpose, so they were not scored\". A noindex page the sitemap lists is a real issue and appears under Indexability instead.\n   - Checks with `advice` (and the advisory Content Signals check, status `advice`) go in a short \"Worth considering\" list after the issues, each with the same plain explanation and example as an issue, and a note that it may be deliberate. For example: Content Signals (no line in robots.txt, which leaves AI use unrestricted), answering `Accept: text/markdown` when a Markdown copy is already linked, or a \"last updated\" date on a privacy page.\n\n   **Live checks.** In repo mode, checks marked \"predicted from config\" or \"inconclusive\" can be measured on the deployed site. First offer a URL audit: `/aeotester:audit https://their-site.com` (or the single page URL). For one quick check, the user can also run a command themselves: give it with the `!` prefix (for example `! curl -sI -H \"Accept: text/markdown\" https://example.com/`) so the output lands in the conversation, say what a pass looks like (here, `Content-Type: text/markdown` in the response headers), and once they run it, read the output and tell them the result. In URL mode these checks were already measured; only \"inconclusive\" ones (the site blocked or timed out) are worth retrying later.\n\n## Reference\n\n- `references/rubric.json` holds every check: weight, scoring rules, how it is detected, and where results from source can differ from a live page (`parity`). Look up a single check by `id` when the user asks why something scored the way it did; do not load the whole file into the conversation.\n- `audit.mjs ... --json -` prints the full machine-readable result, which is useful for answering detailed questions.\n- Repo mode: `--base-url https://site.com` sets the production URL when the repo does not reveal it (used to tell internal from external links and to check canonical URLs).\n- URL mode: `--ignore-robots` also audits pages that robots.txt disallows. Only use it when the user owns the site and asks for it.\n"
}