seo-technical
Skill1 starsChanged 29 days agoMITView on GitHub
Audits and fixes technical search visibility: robots.txt, indexing, canonicals, redirects, JavaScript rendering, structured data, Core Web Vitals, sitemaps and IndexNow, hreflang, migrations and traffic-loss triage, deploy-drift gates, live-site inspection, Search Console and CrUX APIs. Use for "not indexed", "wrong canonical", "add schema", "fix hreflang", "traffic dropped". Not for what content to write (seo-content).
38 other projects use a version of this.
Adopted by
Most recently taken up by
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- brainbytes-dev/everything-claude-marketingtheir own version, first seen Nov 1, 2026
- zhtyyx/codex-seotheir own version, first seen Nov 1, 2026
- Maudeunfledged834/startup-founder-skillstheir own version, first seen Oct 25, 2026
- joaoguirunas/team-ostheir own version, first seen Oct 21, 2026
- DoddleHQ/doddle-seo-geo-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use seo-agentic, seo-maps and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AgriciDanielSkillseo-agentic
Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).
Also in 5 projects that use this
timruebenachSkillseo-maps
Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".
Also in 17 projects that use this
megastepSkillseo-sitemap
Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".
Also in 29 projects that use this
- timruebenachSkill
seo-ecommerce
E-commerce SEO analysis: Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps. Combines on-page product SEO with marketplace data from DataForSEO Merchant API. Use when user says "ecommerce SEO", "product SEO", "Google Shopping", "marketplace SEO", "product schema", "Amazon SEO", "product listings", "shopping ads", or "merchant SEO".
Also in 17 projects that use this
- megastepSkill
seo-images
Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, and CLS prevention. Use when user says "image optimization", "alt text", "image SEO", "image size", or "image audit".
Also in 25 projects that use this
mangollcSkillseo-backlinks
Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.
Also in 18 projects that use this
- +3 more from timruebenach
- +3 more from megastep
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- AgriciDaniel/claude-seo★ 20ksame name
- shawnpang/startup-founder-skills★ 331same name
- zhtyyx/codex-seo★ 152same name
- ronaldships/foundvia-discovery★ 29same name
- Thibaultbm/claude-seo-geo★ 18same name
- coopersimson96/ai-content-system★ 17same name
- ZachArticulateV/designer-pro-and-seo★ 10same name
- brainbytes-dev/everything-claude-marketing★ 9same name
- Maudeunfledged834/startup-founder-skills★ 8same name
- YepAPI/skills★ 8same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- seo-ai-searchSkill
- seo-authoritySkill
- seo-contentSkill
- seo-engine-policiesSkill
- seo-evidenceSkill
- seo-optimizerSkill
- seo-strategySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Never forecast a published number onto a client site.
- Very specific: line 15
No rollout without a pre-declared revert rule (applicability, holdout, what stays fixed, metric + window, trigger).
- Very specific: line 51
Never Disallow a URL you want noindexed — the crawler must fetch it to read the tag.
- Distinctive: line 54
Every redirect, canonical or template change ships with a revert rule and a re-crawl check.
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
seo-technical
Can every engine fetch, render, index and correctly attribute the page — and does it stay that way after each deploy?
<!-- grammar-excerpt -->Label every tactic with one of the 9 marks: [documented: <URL>, <date>] · [documented-secondary: …] · [unverified: …] · [measured: MARK, n=S, c=C] · [practitioner: anonymised sources · …] · [hypothesis] · [vendor] · [memory] · [unvalidated house heuristic].
Numbers keep their denominator; marks are counts, not verdicts; bundles support direction, not size.
Never forecast a published number onto a client site; only the client's own GSC demand and funnel forecast.
No rollout without a pre-declared revert rule (applicability, holdout, what stays fixed, metric + window, trigger).
Repetition never proves; full grammar: skill seo-optimizer § Evidence marks.
<!-- /grammar-excerpt -->Load rule
Open one reference per load-when row the question touches (a "by H2" row: only the part holding that H2); never a file "to be thorough". A pointer into another seo- skill's file is a citation: quote it, or first load that skill's SKILL.md and open the file through its own load-when row. Engine pages, ledger and practitioner parts and the crawler registry are lookup-only.
Load when
| ID | Question shape | Open |
| TE1 | crawl, index, robots.txt, canonicals, redirects | crawl-and-index.md |
| TE2 | JS rendering, sitemaps, IndexNow, bot/user parity | by H2: part 2 (sitemaps, IndexNow, JS rendering, audit checklist) or part 1 (JSON-LD, CWV bar, hreflang tags) |
| TE3 | structured data | schema-reference.md |
| TE4 | Core Web Vitals diagnosis | cwv-field-lab-diagnosis.md |
| TE5 | LCP subparts, images, sitemap extensions | by H2: part 1 (LCP, images) or part 2 (sitemap extensions, agent-friendly pages) |
| TE6 | traffic loss, incident classification | incident-triage.md; then skill seo-engine-policies › google-updates-timeline-2 (core/spam rollout dates) and, to rule decay in or out, skill seo-content › content-and-intent-2 (decay triage) |
| TE7 | migrations, URL changes, consolidation, rollback | migrations-and-recovery.md |
| TE8 | hreflang, locales | by H2: part 1 (MT and scaled content, geo signals, formats) or part 2 (scale, frameworks, Bing/Yandex, locale release gates) |
| TE9 | deploy drift, CI gates | seo-drift-monitoring.md |
| TE10 | Search Console / CrUX APIs, quotas | by H2: part 1 (query shapes, URL Inspection, Indexing, GA4, Consent Mode, CrUX) or part 2 (quota table, Keyword Planner, auth) |
| TE11 | live-site inspection | site-inspection-method.md |
Not mine
| Question | Skill |
| is a tactic allowed by an engine | seo-engine-policies |
| does schema or a title change work | seo-evidence |
| AI crawler access as a citation strategy | seo-ai-search |
| what pages to build | seo-content |
Rules
- Index status comes from Search Console URL Inspection, never from
site:. - Never
Disallowa URL you want noindexed — the crawler must fetch it to read the tag. - Classify an incident (deploy, core update, manual action, demand, tracking) before treating it.
- Server HTML must carry everything that must rank or be cited.
- Every redirect, canonical or template change ships with a revert rule and a re-crawl check.
- A schema request that also promises AI citations or a ranking tactic stays here (TE3) plus skill
seo-evidence› works-vs-doesnt for the claim; it does not needseo-ai-search.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.