Skip to content
AEO Toolkit AEO Toolkit

AEO Toolkit documentation

Answer Engine Optimization (AEO) is the practice of structuring content so AI assistants — ChatGPT, Claude, Perplexity, Gemini — cite your site when answering questions in your domain. Traditional SEO gets you ranked on the results page. AEO gets you quoted in the answer.

This toolkit automates auditing for that. It is Apache-2.0-licensed, TypeScript throughout, and runs entirely on your own infrastructure if you want it to.

Start here

If you want to…Read
Understand how the pieces fitArchitecture
See every tool and its routeTool reference
Use a package on its ownPackage reference
Run the whole thing yourselfSelf-hosting
Deploy it to VercelDeployment
Turn on auth and billingActivation runbook
Contribute codeConventions

What’s in the suite

Ten tools from two deployables. Five browser tools (technical audit, E-E-A-T scanner, llms.txt generator, GA4+GSC chat, 3D backlink graph), three MCP servers exposing 31 tools to Claude and other MCP clients, one scheduled content agent, and a Chrome extension. All of it is served from a single Next.js app plus the extension — see ADR-0003 for why.

Underneath sit 16 packages, of which six are published to npm. The keystone is @advance-labs/scoring: a weighted rule engine running 54 rules across technical SEO, AEO, and E-E-A-T, whose output four separate tool surfaces render.

Terminal window
git clone https://github.com/Advance-Labs/aeo-toolkit.git
cd aeo-toolkit
pnpm install && pnpm build
pnpm test              # 868 tests
docker compose up      # or run the whole console locally

Background

  • Visibility tracking — why an on-page audit is only half a retainer, and where the over-time citation tracking lives.
  • SEO + AEO plan — how the project’s own site dogfoods the product.
  • Decisions — the ADRs behind the monorepo, the clean-room TypeScript rebuild, and the single-deployment consolidation.

A note on the archive

archive/ holds superseded planning documents — the original nine-app build plan, the per-tool specs, and the managed-tier runbooks. They are kept for design history and are not published to this site. Every file there carries a banner saying so. If you are looking for how the repository works today, everything above is current; nothing in the archive is.