Localized reading guide
seo-ai-visibilityPurpose, usage and source
Audits and fixes both halves of being found — classic search and AI answers. Search side: rankings, site structure, page speed, titles and descriptions, and content that answers what customers search for. AI side: whether assistant crawlers can reach the site, pages render without JavaScript, an llms.txt file, schema.org data, and presence in the directories assistants read. For online stores it also runs a bulk catalog cleanup, rewriting product titles, descriptions, alt text, and SEO fields in approved batches. Works on any public website with no connector. Use this whenever the owner talks about being found online, including "nobody finds us on Google," "how do I show up in ChatGPT," "make my website AI friendly," "SEO audit," "GEO," "AEO," "AI search visibility," "my competitor ranks above me," "fix my product listings," or "I asked an AI about my industry and we weren't in the answer."
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/seo-ai-visibility/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Audits and fixes both halves of being found — classic search and AI answers. Search side: rankings, site structure, page speed, titles and descriptions, and content that answers what customers search for. AI side: whether assistant crawlers can reach the site, pages render without JavaScript, an llms.txt file, schema.org data, and presence in the directories assistants read. For online stores it also runs a bulk catalog cleanup, rewriting product titles, descriptions, alt text, and SEO fields in approved batches. Works on any public website with no connector. Use this whenever the owner talks about being found online, including "nobody finds us on Google," "how do I show up in ChatGPT," "make my website AI friendly," "SEO audit," "GEO," "AEO," "AI search visibility," "my competitor ranks above me," "fix my product listings," or "I asked an AI about my industry and we weren't in the answer."
How the upstream workflow works
Step 1 — Crawl the site
No connector needed. This is the normal path. Fetch the site directly. Read reference/audit_checklist.md. Cover: Homepage, service and product pages, location pages, contact, about, blog robots.txt, sitemap.xml, llms.txt
Step 2 — Check the AI half
This is what owners are actually asking about and where most sites fail. Read reference/ai_visibility.md. Crawler access. Does robots.txt allow ClaudeBot, GPTBot, PerplexityBot, and the others? Many sites block them by accident through a blanket rule or a security plugin. This is the single highest-impact fix and it is usually a one-line change. Renderability. If the content only appears after JavaScript runs, most crawlers see an empty page. Check the raw HTML. llms.txt. A plain-language file at the site root describing what the business does, what it offers, where it operates, and how to reach it.
Step 3 — Test what an assistant actually sees
Ask the questions a customer would ask, in a few phrasings, and record what comes back. "Who does commercial HVAC service in Bergen County?" is the real test. Report exactly what happened — whether the business appeared, who did, and what sources were cited. Do not estimate a visibility score. Read reference/ai_visibility.md for how to run and record this honestly. These results vary run to run and are not a ranking. Say that plainly. A snapshot repeated monthly shows direction; a single run proves little.
Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- SEO and AI Visibility
- The positioning rule, and why it holds
- Step 1 — Crawl the site
- Step 2 — Check the AI half
- Step 3 — Test what an assistant actually sees
- Step 4 — Score and prioritize
- Step 5 — Write the fixes
- Step 6 — Catalog refresh, for stores
- Step 7 — Deliver and set the recheck
- Closing offer
- What not to do
- Reference files
- Using a tool that isn't listed
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
d6201648ed9e004da1d33c5e640ad2d34fd51a34d8cd06643021262d4e7dd72f