seo-llmo
Skill29 starsChanged 22 days agoApache-2.0View on GitHub
Use this skill whenever the user is building, reviewing, or launching a public website or web app; SEO, LLMO, and agent-readiness are baseline for every public site. Covers meta tags, Open Graph, JSON-LD, robots.txt for AI search and training crawlers (OAI-SearchBot, GPTBot, Claude-SearchBot, ClaudeBot, PerplexityBot, Google-Extended) with Content-Signal, sitemap.xml, llms.txt, Markdown content negotiation, Link headers, A2A Agent Card, MCP Server Card and AI Catalog discovery, Agent Skills index, pricing.md, and the "explicit absence beats silence" rule. Trigger for marketing sites, landing pages, blogs, docs, and stores; before any launch or go-live; when the user mentions isitagentready.com, ORA, agent-readiness, AI Overviews, or wants ChatGPT, Claude, Perplexity, or browser agents to find and use the site; and when scaffolding a public site even if SEO is not mentioned. Skip for internal tools, admin panels, or auth-gated dashboards with no public surface.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- aws-spa-deploySkill
- google-analytics-4Skill
- web-accessibilitySkill
- web-performanceSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Default: company/marketing site - drives which schema types to prioritize.
- Very specific: line 26
Default: if a framework config file (e.g.
- Distinctive: line 30
Default: worldwide, single language - skip hreflang unless multiple languages are confirmed.
- Distinctive: line 34
Default: all of the above - the baseline checklist covers Google + AI chat citation + agent-readiness in one pass.
- Distinctive: line 37
Default: no - but check for existing files before creating new ones, and merge rather than overwrite.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SEO & LLMO Implementation Guide
Applies to: Any website or web app | Updated: October 2026
A practical guide for implementing Search Engine Optimization (SEO), Large Language Model Optimization (LLMO), and agent-readiness - making your site discoverable and usable by search engines, AI chat tools, and autonomous agents.
Agents (ChatGPT deep research, Claude with web, Perplexity, Cloudflare Agents, browser agents) don't just index your page, they fetch and act on it. That raises the bar on three things beyond classic SEO: telling crawlers what they may do with your content (Content Signals), serving a clean Markdown version on demand, and advertising any programmatic entry points you expose. You can check your agent-readiness score at isitagentready.com.
Section 0: Before You Start
Answer these questions before generating any code. Each has a default - use it if the user hasn't said otherwise.
Q: What kind of site is this? (blog, online shop, company/marketing site, web app, documentation) Default: company/marketing site - drives which schema types to prioritize.
Q: How is the site built?
(plain HTML, React/Vue/Angular SPA, Next.js/Astro/Nuxt with server rendering, WordPress/CMS)
Default: if a framework config file (e.g. vite.config.*, next.config.*, astro.config.*) is visible in the project, detect from that; otherwise assume plain HTML.
Q: Where are your visitors? (one country, multiple countries/languages, worldwide) Default: worldwide, single language - skip hreflang unless multiple languages are confirmed.
Q: What's your main goal with SEO? (show up in Google search, get cited by AI chat tools like ChatGPT/Perplexity, be usable by autonomous agents, social sharing, all of the above) Default: all of the above - the baseline checklist covers Google + AI chat citation + agent-readiness in one pass.
Q: Do you already have a robots.txt, sitemap, or structured data set up? Default: no - but check for existing files before creating new ones, and merge rather than overwrite.
AI assistant: Read the user's answers (or use the defaults above) before generating any code. Skip sections that don't apply to their setup.
Contents
This guide is split into reference files. Use the Section 0 answers to decide which apply, then read only those; skip the rest.
- Structured Data (JSON-LD): Any site where you want Google rich results or AI citation.
- llms.txt and llms-full.txt: Goal includes AI tool visibility.
- robots.txt for AI and Search Crawlers: Any public-facing site.
- Sitemap: Site has more than one page and you want search engine indexing.
- Meta Tags and Social Sharing: Goal includes social sharing or Google click-through rates.
- Agent-Readiness: Goal includes being usable by autonomous agents (browser agents, deep research tools, agentic commerce), not just cited by AI chat.
- Core Web Vitals: Site targets Google search ranking, or is a SPA.
- SPA Considerations: Site is built with React, Vue, Angular, or another client-side-only framework.
- Static Hosting Notes: Deploying to AWS Amplify, CloudFront + S3, Netlify, or Vercel and you need SPA rewrites, headers, or content negotiation configured on that host.
- Validation: After deploying, to check structured data, social previews, crawl access, agent-readiness, cross-surface consistency, performance, and indexing.
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.