SEO for AI AgentsOpen-source · MIT · 18 skills
A drop-in skill pack for AI coding agents.
Build sites that search engines rank and AI answer engines cite.
$ claude "audit my site's SEO"
Analyzing built output from /dist...
✓ Rung 1: Reach (HTML serves content)
✓ Rung 2: Read (Metadata & Core Vitals)
✗ Rung 3: Understand (Missing JSON-LD)
Fixing Rung 3...
↳ Injected SoftwareApplication schema into index.html
↳ Added Organization schema to /about
Ready for review. Run `git diff` to see changes.
Sound familiar?
You vibe-coded a new app over a weekend. It looks great, the design is clean, the demo works. You ship it, and weeks later: nothing. No search traffic, no AI tools mentioning it.
The build is quietly full of SEO problems you can't see in a browser: an empty HTML shell that crawlers receive, missing titles and metadata, no structured data, pages wired to nothing. The site exists for a human with a browser, and barely exists for a search engine. That's the gap this closes.
Built for developers shipping real sites
Whether you're starting fresh, improving a site you built, or pointing an agent at an existing codebase, the audit is the same. Only the emphasis changes.
Starting a new site
Build it SEO-correct from the first commit, instead of fixing it after launch.
Improving a site you built
Audit what's live and raise it, without regressing pages that already rank.
An existing codebase + agent
Point your coding agent at the repo and have it diagnose and fix the SEO.
What's going wrong → what the pack does
My AI-built site isn't showing up in Google
Finds why crawlers can't see it, and fixes it
I edited the code but search didn't change
Verifies on the served HTML, not the source
I want to rank, not just look good
Works the SEO fundamentals in order, up to Rank
My site is slow or clunky on mobile
Diagnoses Core Web Vitals and mobile, fixes the causes
Engines don't understand my pages
Adds valid, honest structured data they can read
I can't risk breaking what already ranks
Audits safely, preserving URLs, canonicals and what works
Fixes keep silently breaking on deploys
Re-audits and catches regressions, even in CI
I'd also like AI answers to cite me
Adds the AEO layer, once the page can rank
Tuned to your site
What are you building?
The method is the same for every site; where sites fail is not. Pick your kind of site to see the failures the audit hunts first. Each has a full guide, and a profile in the pack that tunes the audit automatically.
SaaS & product marketing
The classic failure: The marketing site is an SPA that serves crawlers an empty shell.
- Marketing pages client-rendered, invisible in the served HTML
- Vague 'platform that empowers teams' copy matching no real query
- Pricing hidden inside a JavaScript-only widget
- Thin 'alternatives' pages that add no real value
Priority tilt
Check Reach first and hard, then Read (intent-matched clarity) and the AEO layer (comparison and answer formatting).
Or browse all seven use-case guides.
Why doesn't it rank?
AI-built sites often look perfect in a browser but are nearly invisible to crawlers. Coding agents frequently edit JSX and declare "meta tags added" without verifying what's actually served in the built HTML. If a crawler receives a blank <div id="root">, your site can't rank, because to a search engine it isn't there.
Ranking in search is the goal, and it still starts with the fundamentals: a site that's crawlable, readable, well structured, and trustworthy. Get those right and the same foundations also make your pages eligible to be surfaced by AI answer engines like AI Overviews, ChatGPT and Perplexity. That's a layer on top, after the basics, not a replacement for them.
Most AI-built sites fail at the very bottom of the ladder. This skill pack fixes that, from the ground up.
See it on the served HTML
A site built as a single-page app looks perfect in your browser, and serves crawlers an empty shell. The pack checks what's actually served, and fixes it.
<body>
<div id="root"></div>
<script src="/app.js"></script>
</body>
# curl returns an empty shell.
# No headings, no copy. Invisible.<main>
<h1>Web design that converts</h1>
<p>Award-winning studio in Leeds…</p>
</main>
# curl now returns real content.
# Crawlable. Indexable. Citable.<head>
<meta charset="utf-8">
<meta name="viewport" ...>
</head>
# No title, no description.
# Nothing to show in the results.<head>
<title>Web design that converts | Studio</title>
<meta name="description" content="…">
<link rel="canonical" href="…">
</head>
# A real title and snippet.
# A reason to click.<!-- nothing here -->
# Engines can't identify what
# this page actually is.<script type="application/ld+json">
{ "@type": "Product",
"name": "…", "offers": {…} }
</script>
# A real entity, honestly marked up.
# Eligible for rich results.Verified by re-fetching the page, not by trusting that a source edit worked.
The Visibility Ladder
Begin with the foundation
Search visibility is built in order. The first four rungs make a page eligible; the fifth, Rank, is whether it deserves to win. Diagnose top to bottom, fix bottom to top. AEO (being cited by AI answers) is the layer on top, applied alongside ranking, never instead of it. Click any rung to see what it checks.
Authority
Beside the ladderBacklinks, brand and reputation are a major ranking factor, but you earn them off-site over time, not in code. The pack audits and strategises them, strictly white-hat. It never fakes them.
The first four rungs make a page eligible to compete. Rung five, Rank, is whether it deserves to win, and because ranking is earned it has two halves: what you build (intent, depth, on-page authority) and what you earn (links and reputation, beside the ladder). AEO, being cited in AI answers, is a layer on top, applied alongside ranking, never a replacement for it.
It's an audit that remembers
Not a one-shot fix. The pack writes a .seo/ folder into your project, so every run builds on the last, and catches regressions before they cost you.
First run
Audits all five rungs, fixes the safe wins, and records a baseline, a readable report, an issue tracker, and a history.
Every re-run
Re-verifies past fixes on the served HTML, catches regressions (a fix that quietly broke in a deploy), finds what's new, and advances.
In CI, automatically
Wire it into a deploy/PR check so a change that makes your site uncrawlable fails the build, not weeks later in lost traffic.
.seo/
├── audit.md # readable scorecard
├── state.json # every issue + status
└── log.md # dated run historyA skill for every part of SEO
The orchestrator routes broad requests; reach for a specialist when you already know the job. Technical foundations first, strategy and automation on top. Hover any skill for the technical detail.
Start here
The five rungs
On top of the ladder (AEO)
Technical specialists
Content & strategy
Automation & advanced
Use it well
Powerful, and only as good as your judgement
The agent verifies, executes and remembers; you decide, review and own. The guide is the honest manual: why human judgement always wins, the six habits that make this pack compound, and the short list of things you should never let an agent do.
How do I install SEO for AI Agents?
Fastest start, paste this into your agent
No setup. Drop this prompt into Claude Code, Cursor, or any AI coding agent and it audits your site and reports back. It won't change anything until you ask it to.
Use the seo-for-ai-agents skill pack (https://github.com/manibharij/seo-for-ai-agents): audit my site against the Visibility Ladder, checking on the served HTML. Do not change any code or files yet. Report the lowest failing rung first, then a prioritised list of issues with the recommended fix for each in plain English. Never fabricate authors, reviews, or trust signals.
More prompts you can paste straight away
Once the pack is installed, reach for the right job. Each one is read-only: it analyses and reports, so nothing changes until you decide. Swap the bracketed parts for your own details.
Using seo-for-ai-agents, analyse why [paste URL] isn't ranking. Work top-to-bottom through the Visibility Ladder on the served HTML, identify the lowest failing rung, and explain the root cause. Report your findings only, don't change any code or files.
Using seo-for-ai-agents, run a read-only SEO audit of my site. Diagnose each rung on the served HTML and give me a prioritised list of issues with the recommended fix and the risk of each. Don't edit any files, just report.
Using seo-for-ai-agents, review the structured data on my pages. Check what's present in the served HTML, flag anything missing, invalid, or not matching the page, and recommend honest schema to add. Report only, don't change anything.
Using seo-for-ai-agents, I'm about to change my URLs / redesign / move domains. Inventory the current URLs and give me a recommended 1:1 301 redirect map plus a pre-launch checklist. Just produce the plan, don't apply any changes.
Using seo-for-ai-agents, analyse my Core Web Vitals and mobile experience on the served pages. Identify the build-time causes (images, fonts, JavaScript, layout shift) and tell me which to address first. Diagnosis only, don't change code yet.
Using seo-for-ai-agents, assess whether my pages are eligible to be cited by AI answer engines. Review only, don't change anything: check answer formatting, entities and attribution on the served HTML, and tell me what to improve once a page can rank.
Install into your agent
Drop the skills folder into your agent's config directory or copy-paste a mini. No complex setup.
Ask it to audit your site
Tell your agent: 'Audit my SEO'. It detects your stack, finds the lowest failing rung, and dispatches fixes.
Review and approve
The agent explains every change in plain English. You decide what to publish. All fixes are reversible.
Supported Environments
Claude Code
~/.claude/skills/
Cursor
.cursor/rules/
AGENTS.md
For Codex, Zed, Gemini CLI
Copy-paste Minis
Zero config needed
Is SEO for AI Agents right for you?
For
- Developers and marketers who vibe-code with AI agents
- Anyone building a new site with Claude Code, Cursor, or Codex
- Developers whose AI-built site isn't showing up in Google
- Agencies and consultants who audit client sites
- Existing sites that need SEO health maintained over time
Not For
- Anyone expecting guaranteed rankings or citations
- People without an AI coding agent
- Those wanting live rank-tracking or backlink tools
- Black-hat or spam SEO
What doesn't SEO for AI Agents do?
Key distinctions
- Fixes owned-media SEO only (not link-building, not rank-tracking)
- Verifies on served HTML, not just source code edits
- Strictly white-hat, never fabricates authors, E-E-A-T signals, or reviews
- Works for existing sites too (protects URLs and canonicals that already rank)
The honest question
Can AI agents replace SEO professionals?
No, and anyone promising otherwise is overselling. Strategy, judgement and hard-won experience don't come in a skill pack. But that was never the point. This puts a rigorous, white-hat SEO method in your agent's hands and runs it like continuous testing: a tireless audit that checks the fundamentals on every build, shows you what's wrong, and waits for you to decide. A force-multiplier for an SEO professional, and a safety net for everyone building without one.
It assists, it doesn't replace
The method is rigorous, but it has no taste, no strategy and no accountability. A human still owns the calls that matter. Treat its output as a well-argued draft from a fast junior, not a verdict, and keep evaluating it as the professional you are (or hire one).
A considered bet on where this is heading
Using it now is a wager that coding agents keep getting better at SEO, and that the people who learn to direct them well compound an edge. It is built to grow more capable as the models do, so you are testing and learning early, not late.
It changes nothing unless you say so
By design it audits and reports first, and makes no edits to your code until you have reviewed the findings and told it to proceed. Continuous testing on your terms, with nothing touched behind your back.
It is at its best on new or recent builds that aren't ranking yet, laying clean foundations from the start, and as a constant second pair of eyes for an SEO professional on an established site. It cannot guarantee rankings or citations; those depend on factors no tool controls. Built on a fifteen-year, white-hat SEO mindset, to do the right things well and leave the decisions to you.
Frequently asked questions
Does it guarantee rankings or AI citations?
No, and anything that promises guaranteed rankings is misleading. It fixes build-time, owned-media SEO and improves your eligibility to rank and be cited. Whether a search engine ranks you, or an AI engine cites you, depends on competition, demand, and authority outside any tool's control.
Does it work on existing sites, or only new ones?
Both. On an existing site it audits without regressing what already ranks: it preserves URLs (adding redirects if any must change), respects intentional canonicals and noindex rules, and flags bigger changes for you to approve first.
What about WordPress, Shopify, or Webflow?
The diagnosis works on any site, because it reads the served HTML. On hosted platforms the fixes often live in the platform's settings or theme rather than code, so the agent tells you exactly what to change, rather than editing code it doesn't control.
Is it free? Do I need paid data tools or API keys?
It's free and open-source (MIT), and needs no paid data to work. You can optionally connect your own Search Console, DataForSEO, or Ahrefs keys to sharpen the audit, but nothing is paywalled or required.
Will it change my code without asking?
It applies safe, clearly-correct fixes and explains each one in plain English. Risky changes like restructuring URLs, removing content, or authorship and trust decisions are flagged for you to approve. You review before publishing, and everything stays in version control.
Which AI coding agents does it work with?
Claude Code, Cursor, and AGENTS.md hosts (Codex, Gemini CLI, Zed) via the skills, or a copy-paste mini in any chat. It's a skill pack the agent reads, not a separate app to run.
Does it work for my kind of site: a shop, a blog, a SaaS, a local business?
Yes. The pack ships site-type profiles that tune the audit: e-commerce, SaaS marketing, local business, blogs and content sites, documentation, news publishers, and international sites. The orchestrator detects your site type itself and applies the right profile, weighting the checks that matter most for it.