Skip to content
Back to search

seo

"Website SEO done as shipped, verified fixes: technical audits, indexing problems, Core Web Vitals, titles/meta, content refreshes, JSON-LD schema, local SEO (Google Business Profile, clinics, colleges, multi-location), internal linking, hreflang, migrations and redirects, robots.txt and AI-crawler policy, AI search visibility (ChatGPT, Perplexity, Google AI Overviews / GEO), compliant link earning, traffic-drop diagnosis and Search Console reporting. Bundles zero-dependency, tested scripts (crawler, page checker, robots tester, schema validator, CWV, redirect verifier) that run on free data. Use whenever the user mentions SEO, rankings, Google or Bing traffic, pages not indexed, Search Console, sitemaps, robots.txt, canonicals, schema, page speed for search, getting cited by AI assistants, or launching, migrating or redesigning a public site, even without saying 'SEO'. Not for paid ads, app-store optimization, YouTube growth, or in-app search engines."

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/boobal-official--claude-seo-skill/badge.svg)](/listings/boobal-official--claude-seo-skill)

HTML

<a href="/listings/boobal-official--claude-seo-skill"><img src="/api/listings/boobal-official--claude-seo-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code loads skills from `~/.claude/skills/` (all projects) or `.claude/skills/` (one project).

# macOS / Linux / Git Bash
git clone https://github.com/boobal-official/claude-seo-skill ~/.claude/skills/seo
# Windows PowerShell
git clone https://github.com/boobal-official/claude-seo-skill "$env:USERPROFILE\.claude\skills\seo"

Restart Claude Code (or start a new session). The skill triggers automatically on SEO requests (rankings, indexing, Search Console, robots.txt, schema, Core Web Vitals, migrations, AI-search visibility...). Requires Node.js 18+ for the scripts. Update with `git pull` in that folder.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 156 lines
  1. ---
  2. name: seo
  3. description: "Website SEO done as shipped, verified fixes: technical audits, indexing problems, Core Web Vitals, titles/meta, content refreshes, JSON-LD schema, local SEO (Google Business Profile, clinics, colleges, multi-location), internal linking, hreflang, migrations and redirects, robots.txt and AI-crawler policy, AI search visibility (ChatGPT, Perplexity, Google AI Overviews / GEO), compliant link earning, traffic-drop diagnosis and Search Console reporting. Bundles zero-dependency, tested scripts (crawler, page checker, robots tester, schema validator, CWV, redirect verifier) that run on free data. Use whenever the user mentions SEO, rankings, Google or Bing traffic, pages not indexed, Search Console, sitemaps, robots.txt, canonicals, schema, page speed for search, getting cited by AI assistants, or launching, migrating or redesigning a public site, even without saying 'SEO'. Not for paid ads, app-store optimization, YouTube growth, or in-app search engines."
  4. ---
  5. # SEO
  6. Make a website earn more search traffic that converts, from Google, Bing, and AI assistants:
  7. find what blocks it, fix it in the code or content, and prove each fix worked with before/after
  8. evidence. A report with no shipped change is not the deliverable; neither is a change with no proof.
  9. ## Principles (and why)
  10. - **Fix the blocker before the polish.** A perfect title on a page Bing cannot crawl earns
  11. nothing. Work in severity order on the pages that make money first.
  12. - **Evidence over memory.** Search engines change often (several 2025-2026 changes are recorded in
  13. `references/thresholds.md`). Measure the live site, read the repo, and re-check time-sensitive
  14. facts at the official URLs listed there. If you cannot verify something, say "not verified".
  15. - **Never invent facts.** No made-up statistics, prices, reviews, credentials, or quotes. Missing
  16. facts become `[NEEDS FACT: ...]` items for the owner.
  17. - **Free data first.** Everything works with the live site, the repo, Search Console/Bing exports,
  18. PageSpeed Insights, and web search. Paid SEO tools are optional if the user already has them; never recommend buying one.
  19. - **Stay inside search engine spam policies.** No link buying, cloaking, doorway pages, fake
  20. reviews, or scaled thin pages: they get sites penalised or ignored, and recovery is slow.
  21. - **Ask before irreversible, policy, or external actions** (list in Step 4).
  22. ## Step 1: Intake (short; infer what you can)
  23. 1. **Site URL** (or a local production build) and **goal**: audit, a specific problem, a page to rank, launch/migration, local, AI visibility, traffic drop.
  24. 2. **Money pages and conversion**: pricing, admissions, booking, product, contact. These get priority.
  25. 3. **Repo and stack**: `node <skill-dir>/scripts/repo-audit.mjs <repo>`.
  26. 4. **Data available**: GSC/Bing exports or access, analytics, a PSI API key, any paid SEO tool.
  27. If something is missing, proceed with what exists and note the gap once; do not block.
  28. `<skill-dir>` is this skill's base directory (shown when the skill loads). Scripts need only
  29. Node >= 18 and run from anywhere. Flags may come in any order; `--json` gives machine-readable
  30. output (always valid JSON, even on errors).
  31. ## Step 2: Route the task
  32. | Task | Read | Run |
  33. |---|---|---|
  34. | Full audit / "why don't we rank" | `references/technical-audit.md` | `repo-audit`, `robots-check`, `crawl-site`, `seo-check --deep`, `seo-check --bots` (separate run; ask first behind a WAF/CDN bot shield), `cwv` |
  35. | Traffic dropped | `measurement.md` (drop diagnosis) then `technical-audit.md` | `crawl-site`, `robots-check` |
  36. | Pages not indexed / GSC errors | `technical-audit.md`, `measurement.md` | `crawl-site`, `seo-check --deep` |
  37. | Page speed, Core Web Vitals | `core-web-vitals.md` | `cwv` |
  38. | Titles, meta, headings, intent, refresh a post | `on-page.md` | `seo-check`, `crawl-site` |
  39. | Content quality, E-E-A-T, AI writing cleanup, AI search / GEO | `content-and-ai-search.md` | `slop-check`, `seo-check --bots` (ask first behind a WAF/CDN bot shield) |
  40. | Schema / rich results | `structured-data.md` | `seo-check` |
  41. | Local, Google Business Profile, multi-location, clinics, colleges | `local-seo.md` + `structured-data.md` | `seo-check`, `crawl-site --money "^/locations/"` |
  42. | Internal links, orphans, site structure | `internal-linking.md` | `crawl-site --money ...` |
  43. | Multilingual / hreflang | `international.md` | `seo-check --deep` |
  44. | Domain move, rebrand, URL changes, replatform | `migrations.md` | `verify-redirects`, `crawl-site`, `robots-check` |
  45. | robots.txt, AI bots, blocking scrapers | `crawler-policy.md` | `robots-check`, `seo-check --bots` (ask first behind a WAF/CDN bot shield) |
  46. | Backlinks, PR, outreach, directories | `off-page.md` | - |
  47. | Keyword research, competitors, content plan | `research.md` | - |
  48. | Search Console, logs, reporting, IndexNow, Discover | `measurement.md` | `indexnow` (dry run first) |
  49. | Next.js / WordPress / Shopify / static / SPA specifics | `stacks.md` | `repo-audit` |
  50. Every threshold, limit, and time-sensitive policy fact lives in `references/thresholds.md` (the
  51. scripts read the same values from `scripts/thresholds.mjs`; the test suite fails if they drift).
  52. Workflow rules of thumb stay in the guide that uses them and are labelled as heuristics.
  53. ## Step 3: Prioritise
  54. Severity scale (defined in `thresholds.md`): FATAL, HIGH, MEDIUM, LOW, INFO. Order work by severity x page value:
  55. ```
  56. FATAL on any page that matters -> fix now
  57. HIGH on money / high-traffic pages -> fix now
  58. HIGH elsewhere, MEDIUM on money -> this change if under ~1 hour, else top of the roadmap
  59. MEDIUM elsewhere -> roadmap with owner
  60. LOW -> one batched line at the bottom; skip while FATAL/HIGH remain
  61. ```
  62. Script output is evidence, not a verdict. Confirm intent before "fixing": a `noindex` on a login
  63. page, a canonical on a true duplicate, or an owner-approved AI-bot block is correct.
  64. ## Step 4: Change and verify
  65. **Before** changing anything, run the check that found the issue and save its `--json` output
  66. under `seo/evidence/YYYY-MM-DD/` (the "before"). Make the change the way the repo already works (its routing, metadata helpers, CMS).
  67. Then re-run the same check (the "after"). Pass conditions:
  68. | Change | Proof (after) |
  69. |---|---|
  70. | robots.txt | `robots-check.mjs <origin>`: no FATAL; any remaining HIGH is a block the owner approved |
  71. | noindex / canonical / title / meta / schema | `seo-check.mjs <url> --deep` shows the new values and no issue code for it |
  72. | soft 404 | `crawl-site.mjs` no `soft-404`; `curl -s -o /dev/null -w "%{http_code}" <origin>/zzz-test` prints 404 |
  73. | redirects / http->https / host | `verify-redirects.mjs map.csv` "0 failed"; `crawl-site.mjs` no `http-not-redirected` / `host-duplicate` / `url-variant-duplicate` |
  74. | sitemap | `crawl-site.mjs` no `sitemap-*` codes |
  75. | hreflang | `seo-check.mjs <url> --deep` no `hreflang-*` codes on every language version |
  76. | bot access (WAF/UA rules) | `seo-check.mjs <url> --bots` status 200 for search + AI-search bots |
  77. | internal links | `crawl-site.mjs --money ...`: no `money-underlinked`/`orphan-pages`, or each remaining one explained |
  78. | rendering / content | `seo-check.mjs`: no `client-rendered`; the page's key facts (price, H1, main text) appear in the raw-HTML output |
  79. | structured data | `seo-check.mjs`: no `jsonld-parse-error`/`schema-missing-required`; the owner confirms in the Rich Results Test (no public API) |
  80. | CWV | `cwv.mjs` lab before vs after (field data lags; say so) |
  81. | copy cleanup | `slop-check.mjs` 0 hits, or each remaining hit justified |
  82. | NAP / local | `seo/local/nap-audit.md` shows every source matching; `seo-check.mjs` shows the same name/address/phone in JSON-LD and page text |
  83. | IndexNow | `indexnow.mjs ... --submit --json` returns `"ok": true` (after approval) |
  84. | AI-features opt-out | owner confirms Settings > Search generative AI shows Exclude on the right property; the Generative AI performance report trends to zero over the following days |
  85. Also run the repo's lint/typecheck/build. Not deployed yet: verify against the local production
  86. build and say that production still needs checking after deploy.
  87. **Ask the user first** before: noindexing, deleting, or redirecting pages that have traffic or
  88. backlinks; any robots.txt/WAF change that blocks a search engine, an AI search bot, or AI training
  89. bots (a policy decision); opting out of Google's AI features; dropping a locale; changing URLs at
  90. scale; submitting anything externally (IndexNow, sitemaps via APIs, directories, disavow files,
  91. Search Console Change of Address, Bing Site Move); running `seo-check --bots` against a production
  92. site behind a WAF/CDN bot shield (spoofed crawler user agents from the user's IP can get that IP
  93. rate-limited or banned). **Never**: send emails or messages, post to
  94. social or forums, create accounts, buy anything, or write reviews. Draft them for the owner.
  95. ## Step 5: Report (always this shape)
  96. ```markdown
  97. ## SEO: <site> (<date>)
  98. Verdict: <one plain sentence: the biggest thing holding the site back>
  99. ### Shipped (verified)
  100. | Change | File/URL | Before | After (proof command -> result) |
  101. ### Roadmap
  102. | # | Severity | Page(s) | Issue | Why it costs traffic/revenue | Fix | How the owner can verify (no skill needed) | Status |
  103. Every finding gets an owner-runnable check: a `curl` line, a Search Console/Bing report, or a
  104. browser view-source step, in addition to any script command.
  105. ### Needs from you
  106. - <max 3: access, facts marked NEEDS FACT, approvals>
  107. ### Not verified
  108. - <anything you could not measure, and what would verify it>
  109. ```
  110. Save it as `seo/reports/YYYY-MM-DD-<type>.md` in the repo when there is one. For ongoing work keep
  111. state in `seo/` (`measurement.md` lists the files) so the next run starts where this one stopped.
  112. ## Script reference
  113. | Script | Purpose |
  114. |---|---|
  115. | `scripts/repo-audit.mjs [dir]` | stack detection + source-level issues (env noindex, soft-404-prone routes, client-fetched content, missing metadata/sitemap/robots, SEO plugin conflicts) |
  116. | `scripts/robots-check.mjs <origin> [paths]` / `--file robots.txt [paths]` | RFC 9309 / Google-parser matching for search, AI-search, user-triggered and training bots (list in `scripts/robots.mjs`); render-asset blocks; sitemap lines; `--offline` skips sitemap fetches |
  117. | `scripts/crawl-site.mjs <origin> [--max N] [--max-sitemap N] [--concurrency N] [--sitemap URL] [--money REGEX] [--out f]` | link crawl + sitemaps: soft 404, broken links, chains, sitemap hygiene, duplicates, near-duplicates, depth, orphans, contextual in-links, URL variants, OG/favicon, production-host leaks, page issues rolled up |
  118. | `scripts/seo-check.mjs <url> [--deep] [--ua preset]` | one page as raw HTML: status, chain, robots directives, canonical, title/meta/H1, hreflang, JSON-LD validation, rendering, Googlebot HTML size limit (`thresholds.md`); `--deep` also fetches canonical/hreflang/og:image targets |
  119. | `scripts/seo-check.mjs <url> --bots` | separate mode: what a browser, Googlebot, Bingbot and AI bots each receive |
  120. | `scripts/cwv.mjs <url> [--strategy mobile\|desktop] [--local] [--from-json f]` | CWV field + lab via PageSpeed Insights; `--local` = Lighthouse on this machine (ask first) |
  121. | `scripts/verify-redirects.mjs map.csv [--http-max-hops N]` | 1-hop 301/308 to the mapped URL, final 200, http variants |
  122. | `scripts/slop-check.mjs <files>` | AI-writing tells in copy (skips code and frontmatter) |
  123. | `scripts/indexnow.mjs --host h --key k <urls> [--file f] [--submit]` | IndexNow ping (Bing and others); dry run unless `--submit` |
  124. | `scripts/tests/run-tests.mjs [--network]` | self-test against local fixture sites; run after editing any script |
  125. Exit codes (all scripts): 2 = FATAL found, 1 = HIGH found, 0 = otherwise, 3 = could not complete
  126. (network, quota, internal error: report "not measured", never guess), 64 = usage error.
  127. `cwv`: 2 = a field metric poor, 1 = needs improvement, 0 = good or no field data, 3 = not measured.
  128. Network safety: when the audited site is public, the scripts refuse requests to private, loopback
  129. and link-local addresses (e.g. cloud metadata endpoints) that a hostile site could point them at via
  130. sitemaps, og:image or redirects; `--allow-private` overrides. Output from pages is sanitised before printing.
  131. Residual risk: the check resolves hostnames before Node's fetch resolves them again, so a DNS-rebinding
  132. attacker could still switch addresses in between; run audits of untrusted sites from a machine without
  133. sensitive internal services if that matters.
  134. `verify-redirects`: 1 = a row failed. `slop-check`: 1 = hits remain. `indexnow`: 1 = key file or submission failed.
  135. With `--json` every script prints valid JSON, including on usage and internal errors; those carry
  136. severity INFO (a typo or an unreachable network is not a site defect) and the exit code (64 / 3) says what happened.
README.md · README · 135 lines
  1. # SEO skill for Claude Code
  2. An agent skill that does website SEO the way a senior technical SEO would: find what blocks
  3. traffic, fix it in the code or content, and **prove each fix worked** with before/after evidence.
  4. It runs on free data (your live site, your repo, Search Console/Bing exports, PageSpeed Insights)
  5. and ships with zero-dependency, tested Node.js scripts.
  6. ```
  7. "Audit https://example.com and tell me why we get no traffic from Bing and ChatGPT"
  8. "Fix the SEO problems in this Next.js repo before launch"
  9. "Our admissions pages aren't indexed. Find out why."
  10. "We're moving blog.example.com to example.com/blog. Plan the redirects and verify them."
  11. ```
  12. ## Why this skill
  13. | | |
  14. |---|---|
  15. | **Ships changes, not PDFs** | Every workflow ends in edited files plus a proof command (and a check the site owner can run without the skill: `curl`, Search Console, view-source). |
  16. | **Current to 2026** | Facts that changed recently are recorded with official links to re-check: FAQ rich results retired (May 2026), Googlebot's 2 MB HTML limit, the Search Console AI Overviews / AI Mode control, ChatGPT-User and robots.txt, Next.js streaming metadata, AIPREF status. |
  17. | **One source of truth** | Every threshold and policy fact lives in `references/thresholds.md`; the scripts read the same values from `scripts/thresholds.mjs`, and the test suite fails if they drift. |
  18. | **Free data first** | No paid SEO tool required, none recommended, no affiliate links. If you already have Ahrefs/Semrush/DataForSEO, it can use them. |
  19. | **Safe by default** | Asks before noindexing, redirecting, blocking any crawler, or submitting anything externally. Never sends emails, buys links, or writes reviews. No cloaking, no prompt-injection tricks. Stays inside Google's spam policies. |
  20. | **Tested tooling** | 285 automated tests against local fixture sites with planted defects, a clean site that must stay clean, and edge cases from four rounds of adversarial code review. CI runs them on Windows, macOS and Linux with Node 18, 20 and 22. |
  21. | **Safe to point at untrusted sites** | SSRF protection (no requests to private/loopback/cloud-metadata addresses, incl. IPv4-mapped IPv6 forms, when auditing a public site; DNS rebinding documented as a residual risk), gzip-bomb and size caps, linear-time parsing, and terminal-escape sanitising of page content. |
  22. ## Install
  23. Claude Code loads skills from `~/.claude/skills/` (all projects) or `.claude/skills/` (one project).
  24. ```bash
  25. # macOS / Linux / Git Bash
  26. git clone https://github.com/boobal-official/claude-seo-skill ~/.claude/skills/seo
  27. ```
  28. ```powershell
  29. # Windows PowerShell
  30. git clone https://github.com/boobal-official/claude-seo-skill "$env:USERPROFILE\.claude\skills\seo"
  31. ```
  32. Restart Claude Code (or start a new session). The skill triggers automatically on SEO requests
  33. (rankings, indexing, Search Console, robots.txt, schema, Core Web Vitals, migrations, AI-search
  34. visibility...). Requires Node.js 18+ for the scripts. Update with `git pull` in that folder.
  35. ## What's inside
  36. ```
  37. SKILL.md router: intake -> route -> prioritise -> change + verify -> report
  38. references/
  39. thresholds.md every number, limit and time-sensitive policy fact (+ official links)
  40. technical-audit.md crawl, index, render, canonicals, soft 404s, programmatic pages
  41. core-web-vitals.md LCP / INP / CLS diagnosis and stack fixes
  42. on-page.md intent, titles, meta, headings, content refresh
  43. content-and-ai-search.md helpful content, E-E-A-T/YMYL, answer-first structure, AI visibility
  44. structured-data.md JSON-LD templates (Organization, LocalBusiness, Product/merchant, Article...)
  45. local-seo.md Google Business Profile, NAP, location pages, clinics, colleges
  46. internal-linking.md architecture, click depth, orphans, contextual links
  47. international.md hreflang and locale strategy
  48. migrations.md domain moves, redirect maps, cutover, monitoring
  49. off-page.md link earning inside spam policies, outreach drafts
  50. crawler-policy.md search vs AI-search vs training bots, robots.txt templates, bot verification
  51. measurement.md Search Console, Bing, traffic-drop diagnosis, logs, reporting
  52. stacks.md Next.js (App/Pages Router, 15/16), WordPress, Shopify, static, SPA
  53. research.md free keyword and competitor research
  54. scripts/ Node.js >= 18, no npm install
  55. crawl-site.mjs link crawl + sitemaps: soft 404, broken links, chains, sitemap hygiene,
  56. duplicates, near-duplicates, depth, orphans, contextual in-links
  57. seo-check.mjs one page as raw HTML (what non-JS crawlers see); --deep, --bots
  58. robots-check.mjs RFC 9309 / Google-parser matching for search, AI-search and training bots
  59. repo-audit.mjs source-level issues before deploy (Next.js, WordPress, SPA)
  60. cwv.mjs Core Web Vitals via PageSpeed Insights (field + lab)
  61. verify-redirects.mjs 1-hop 301/308 verification for migrations
  62. slop-check.mjs AI-writing tells in copy
  63. indexnow.mjs IndexNow ping (dry run unless --submit)
  64. tests/run-tests.mjs self-test suite
  65. ```
  66. Use the scripts directly too:
  67. ```bash
  68. node scripts/robots-check.mjs https://example.com /pricing
  69. node scripts/crawl-site.mjs https://example.com --max 300 --money "^/(pricing|admissions)" --out seo/crawl.json
  70. node scripts/seo-check.mjs https://example.com/pricing --deep
  71. node scripts/repo-audit.mjs ./my-next-app
  72. ```
  73. Exit codes: `2` FATAL found, `1` HIGH found, `0` otherwise, `3` could not complete (network/quota),
  74. `64` usage error. Add `--json` for machine-readable output.
  75. ## How it was evaluated
  76. The skill was built and improved over five review rounds against a fixed rubric
  77. ([docs/RUBRIC.md](docs/RUBRIC.md)), scored by independent reviewer agents that had not seen the
  78. author's reasoning. One reviewer checked every factual claim against official documentation; a
  79. second hunted for script bugs by running crafted inputs. Each round's findings were fixed and
  80. re-verified. Details: [docs/EVALUATION.md](docs/EVALUATION.md).
  81. | Dimension | v1 | final |
  82. |---|---|---|
  83. | Accuracy (current to Nov 2026) | 5 | 10 |
  84. | Ships verified changes | 8 | 10 |
  85. | Works with zero paid tools | 9 | 10 |
  86. | Coverage | 7 | 10 |
  87. | Safety & neutrality | 8 | 10 |
  88. | Tooling quality | 5 | 10 |
  89. | Skill design | 6 | 10* |
  90. | Internal consistency | 7 | 10 |
  91. \*The last review scored skill design 9 for one duplicated constant; it was fixed and is now
  92. guarded by a test, but that final change was verified by the test suite rather than another review round.
  93. **With vs without the skill** (same model, same tasks, blind grading against objective checks):
  94. on a 110-page site audit and a "review my developer's SEO advice" task, runs with the skill
  95. scored **24/24 (100%)** against **19/24 (79%)** without it. The baseline's misses were factual
  96. (e.g. saying Applebot was blocked when it falls back to Googlebot's rules, quoting an outdated
  97. "safe" Next.js version).
  98. Honest limits: search engines change constantly, so `thresholds.md` records when each fact was
  99. checked and tells the agent to re-verify; Core Web Vitals needs a free PageSpeed API key once the
  100. shared quota runs out; spoofed-UA bot tests run from your IP and can differ from real crawlers.
  101. ## Run the tests
  102. ```bash
  103. node scripts/tests/run-tests.mjs # offline, local fixture sites on random ports
  104. node scripts/tests/run-tests.mjs --network # also a live fetch + PageSpeed check
  105. ```
  106. ## Contributing
  107. Issues and pull requests are welcome, especially corrections with an official source link.
  108. If you change a number, change it in both `references/thresholds.md` and `scripts/thresholds.mjs`
  109. (the tests will tell you if you forget), and run the test suite.
  110. ## License
  111. MIT, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.