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.
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.
Why do AI-built sites disappear from search?
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.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 a fixed order. The first four rungs are the SEO fundamentals that earn ranking. The fifth adds AEO, so the same pages become eligible to be cited by AI answers. Diagnose top to bottom, fix bottom to top.
Reach
Can a crawler reach the URL and see its content in the served HTML?
Read
Is there real, readable content, correct metadata, and a good page experience?
Understand
Can engines identify the entities? (structured data)
Connect
Is the page wired into a coherent site? (internal links, canonicals)
Cite
Is it formatted to be cited by AI search? (AEO/GEO)
Rungs one to four are the SEO fundamentals that earn ranking. Rung five is the owned side of AEO: the formatting and trust signals that make a page eligible to be cited, with no promise that it will be. Ranking comes first; citation is the layer on top.
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 history16 skills, one method
The orchestrator routes broad requests; reach for a specialist when you already know the job. Technical foundations first, strategy and automation on top.
Start here
The five rungs
Technical specialists
Content & strategy
Automation & advanced
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 let it run the audit on your site.
Use the seo-for-ai-agents skill pack (https://github.com/manibharij/seo-for-ai-agents): audit my site with the Visibility Ladder, verify on the served HTML, fix the lowest failing rung first, and explain each change in plain English. Never fabricate authors, reviews, or trust signals.
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)
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.