How do I install the AI SEO skill?

Run npx skillmds@latest add automatelab-tech/ai-seo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is AI SEO safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with AI SEO?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is AI SEO free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published AI SEO?

AutomateLab-tech (@automatelab-tech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

AI SEO by automatelab-tech — Agent Skill

Name: AI SEO
Rating: 4.2 (5 reviews)
Author: AutomateLab-tech

AI SEO

Use when the user wants to audit a URL for AI citation eligibility, check why AI systems don't cite their pages, score AI Overview or citation worthiness, generate or validate an llms.txt file, rewrite content for AEO/GEO, extract named entities, or diff two page versions for SEO regressions. No API keys required.

File contents

ai-seo

Pairs with the @automatelab/ai-seo-mcp server (14 tools). Audits why AI systems do or do not cite a page — structured answer extraction, schema completeness, crawler access, llms.txt, canonical hygiene — and generates fixes.

When to use which tool

Start here: audit_page composes all 14 checks in one call and returns a ranked list of citation-blockers with specific fixes. Use it as the default entry point.

Drill into a specific dimension:

Tool	Use when
`audit_schema`	User asks about structured data, JSON-LD, or schema.org coverage
`audit_canonical`	Checking canonical URL, `og:url`, `hreflang`, or noindex traps
`check_robots`	Verifying GPTBot / ClaudeBot / PerplexityBot / OAI-SearchBot are allowed
`check_sitemap`	Checking `lastmod` freshness signals and sitemap coverage
`check_technical`	Core Web Vitals signals, crawl accessibility, redirect chains
`score_ai_overview_eligibility`	"Will this page appear in Google AI Overviews?"
`score_citation_worthiness`	Cross-engine citation probability score
`generate_llms_txt`	Create an `llms.txt` for the site
`validate_llms_txt`	Validate an existing `llms.txt` against the spec
`rewrite_for_aeo`	Rewrite a page section for Answer Engine Optimization
`rewrite_for_geo`	Rewrite a page section for Generative Engine Optimization
`extract_entities`	Check named entity density and `sameAs` coverage
`diff_pages`	Compare two versions of a page for SEO regressions

Default workflow

User: "Audit https://example.com/my-post"
→ audit_page(url)          # full citation-blocker report
→ Read findings, prioritize by severity
→ For fixable issues, call the specific tool (e.g. rewrite_for_aeo) or draft inline edits

Server setup

Add to your MCP config:

Claude Code (.claude/mcp.json):

{
  "mcpServers": {
    "ai-seo": {
      "command": "npx",
      "args": ["-y", "@automatelab/ai-seo-mcp"]
    }
  }
}

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "ai-seo": {
      "command": "npx",
      "args": ["-y", "@automatelab/ai-seo-mcp"]
    }
  }
}

Requires Node 20+. No API keys needed — all checks are read-only HTTP fetches against the target URL.

Developed by AutomateLab. Source: github.com/AutomateLab-tech/ai-seo-mcp.

---name: ai-seodescription: Use when the user wants to audit a URL for AI citation eligibility, check why AI systems don't cite their pages, score AI Overview or citation worthiness, generate or validate an llms.txt file, rewrite content for AEO/GEO, extract named entities, or diff two page versions for SEO regressions. No API keys required.license: MIT---# ai-seoPairs with the `@automatelab/ai-seo-mcp` server (14 tools). Audits why AI systems do or do not cite a page — structured answer extraction, schema completeness, crawler access, `llms.txt`, canonical hygiene — and generates fixes.## When to use which tool**Start here:** `audit_page` composes all 14 checks in one call and returns a ranked list of citation-blockers with specific fixes. Use it as the default entry point.**Drill into a specific dimension:**| Tool | Use when ||---|---|| `audit_schema` | User asks about structured data, JSON-LD, or schema.org coverage || `audit_canonical` | Checking canonical URL, `og:url`, `hreflang`, or noindex traps || `check_robots` | Verifying GPTBot / ClaudeBot / PerplexityBot / OAI-SearchBot are allowed || `check_sitemap` | Checking `lastmod` freshness signals and sitemap coverage || `check_technical` | Core Web Vitals signals, crawl accessibility, redirect chains || `score_ai_overview_eligibility` | "Will this page appear in Google AI Overviews?" || `score_citation_worthiness` | Cross-engine citation probability score || `generate_llms_txt` | Create an `llms.txt` for the site || `validate_llms_txt` | Validate an existing `llms.txt` against the spec || `rewrite_for_aeo` | Rewrite a page section for Answer Engine Optimization || `rewrite_for_geo` | Rewrite a page section for Generative Engine Optimization || `extract_entities` | Check named entity density and `sameAs` coverage || `diff_pages` | Compare two versions of a page for SEO regressions |## Default workflow```User: "Audit https://example.com/my-post"→ audit_page(url) # full citation-blocker report→ Read findings, prioritize by severity→ For fixable issues, call the specific tool (e.g. rewrite_for_aeo) or draft inline edits```## Server setupAdd to your MCP config:**Claude Code** (`.claude/mcp.json`):```json{ "mcpServers": { "ai-seo": { "command": "npx", "args": ["-y", "@automatelab/ai-seo-mcp"] } }}```**Claude Desktop** (`claude_desktop_config.json`):```json{ "mcpServers": { "ai-seo": { "command": "npx", "args": ["-y", "@automatelab/ai-seo-mcp"] } }}```Requires Node 20+. No API keys needed — all checks are read-only HTTP fetches against the target URL.---Developed by [AutomateLab](https://automatelab.tech). Source: [github.com/AutomateLab-tech/ai-seo-mcp](https://github.com/AutomateLab-tech/ai-seo-mcp).

Frequently asked questions