Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Marketing & sales

seo-agent-readiness

Make a site readable by AI crawlers and usable by browser agents and assistive technology. Covers the owner's three choices about AI search answers, model training, and on-request reading in robots.txt, an llms.txt file with an honest label, accessible names and ARIA for every control, and the agent reference scans. Use while a site is built, before it goes live, or when the owner asks about blocking AI crawlers, GPTBot, llms.txt, or whether agents can use the site. For whether AI answers name the site, use seo-ai-visibility.

rankmyseo · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add rankmyseo/skills --skill seo-agent-readiness

About this skill


name: seo-agent-readiness description: Make a site readable by AI crawlers and usable by browser agents and assistive technology. Covers the owner's three choices about AI search answers, model training, and on-request reading in robots.txt, an llms.txt file with an honest label, accessible names and ARIA for every control, and the agent reference scans. Use while a site is built, before it goes live, or when the owner asks about blocking AI crawlers, GPTBot, llms.txt, or whether agents can use the site. For whether AI answers name the site, use seo-ai-visibility.

SEO agent readiness

Read seo first if you have not read it in this session. Its rules for account writes, guest keys, and reading results apply here.

Goal: AI crawlers read the pages the owner wants them to read, and a browser agent or a screen reader can find and use every control.

Acceptance: robots.txt matches the owner's three answers, every button, link, and field on the key pages has a name, and the owner knows what llms.txt does and does not do.

Do this after the basics in seo-site-setup. Main text in the first HTML response (its section 2) matters most here too, because several AI crawlers do not run JavaScript.

1. AI crawler choices in robots.txt

The base robots.txt rules are in seo-site-setup, section 6. Add the AI rules only after the owner answers.

Ask the owner these three questions before you write AI rules. Do not guess the answers:

  1. Do you want your pages to appear in AI search answers, where an assistant searches the web and cites sources? Blocking those crawlers removes you from those answers.
  2. Do you allow AI companies to train their models on your content? Blocking training crawlers does not affect whether your pages appear in AI search answers.
  3. Do you allow AI tools to read a page when a person asks about it?

Each vendor uses separate names for search, training, and reading on a person's request. Block only the names that match the owner's answer:

VendorAI search answers (question 1)Model training (question 2)Read on a person's request (question 3)
OpenAIOAI-SearchBotGPTBotChatGPT-User. OpenAI says robots.txt rules may not apply to it
AnthropicClaude-SearchBotClaudeBotClaude-User
PerplexityPerplexityBotPerplexity says its crawler is not used for trainingPerplexity-User. Perplexity says it generally ignores robots.txt
GoogleGooglebot. AI Overviews and AI Mode come from the normal Search indexGoogle-Extended, which also covers Gemini groundingNot controlled by robots.txt
AppleApplebot (Siri, Spotlight, Safari)Applebot-ExtendedNot listed

Other facts that matter for the answers:

  • Blocking a training name leaves the search name allowed. A site can block GPTBot and still appear in ChatGPT search answers through OAI-SearchBot.
  • Never block Googlebot to stop AI use. That removes the site from Google Search, including AI Overviews.
  • Google-Extended does not affect Google Search. Blocking it does affect Gemini answers grounded in your content.
  • If robots.txt has no rule for Applebot but has one for Googlebot, Applebot follows the Googlebot rule.
  • A rule for one person-request name does not cover the others, and some of them ignore robots.txt. If the owner says no to question 3, say that robots.txt cannot fully enforce it.
  • Changes can take about a day to apply, per OpenAI and Perplexity.
  • Record the owner's answers as Content Signals in robots.txt when the owner wants that (ai-train, search, ai-input).
  • Vendors add and rename crawlers. Before writing the rules, open each vendor's crawler page and confirm the names in this table are current.

2. llms.txt (optional, with an honest label)

  • Put a file named llms.txt at the site root. Include a short summary of what the site is, who it serves, and links to the key pages, including pricing.
  • Be precise about what it does. It is valid for some uses: developer tools and coding agents that read it when pointed at it, and Lighthouse's experimental agent audit that checks for it. Google Search does not use it, and Google's guide says it is not needed for Google's AI features. No major AI vendor has documented reading other sites' llms.txt files.
  • Add it when the owner wants agent discovery, and say that is the reason. Do not promise rankings or AI citations from it.
  • If the reference scan in section 4 marks it as missing, explain that it is an agent-discovery check, not a Google check.

3. Accessible names and ARIA (WCAG, and what agents read)

Why this matters for search and AI: WCAG requires every control to have a programmatic name and role. Browser agents read the page's accessibility tree, which holds those names and roles, to find buttons, links, and fields. A control with no name is invisible to both assistive technology and agents.

  • Use native HTML first. A button already has keyboard support, a role, and states. A div with role="button" needs all of that rebuilt by hand. The first rule of ARIA is to use a native element when one fits.
  • Button with visible text: the text is the name. Nothing else is needed.
  • Icon-only button: add aria-label that names the function ("Close", "Add to cart"). Set the icon's SVG to aria-hidden="true".
  • Link: the link text says where it goes. Avoid "read more" and "click here". An icon-only link gets an aria-label.
  • Form input: a label element linked with for and id. Placeholder text is not a label.
  • Image: informative images get alt text that describes them. Decorative images get empty alt.
  • Match visible text: when a control shows visible text, its accessible name must contain that text, with the visible words first (WCAG 2.5.3, Label in Name). A visible "Search" button named "Find products" fails for voice users who say "Search".
  • Name the function, not the look. Name an X
Read the complete source ↗