ai-seo

ai-seo

Team Pick
SEO & AEO
Corey Haines
Answer engine work that starts with a baseline check across ChatGPT, Perplexity and AI Overviews before it recommends a single content change.
REPO
coreyhaines31/marketingskills
INSTALL
npx skills add
NEEDS
Your key queries
Last updated
August 4, 2026

Preview

ai-seo

What it is.

It starts by making you check your priority queries in ChatGPT, Perplexity and Google AI Overviews and record who gets named. Everything after that is planned against the baseline you just took.

It separates two goals people conflate, being cited as a source and appearing inside an AI Overview for a query, because those need different work. Content types, existing search strength and structured data all feed the plan, and llms.txt is covered with the argument for it.

What you get.

  • A baseline check across the assistants for your priority queries
  • The two goals separated: citation as a source, and AI Overview presence
  • Content-type guidance, since docs and comparison pages behave differently
  • Structured data recommendations tied to the citation goal
  • llms.txt and Open Knowledge Format guidance, with the argument for each
HOW TO USE IT

How to set it up.

1

Install with npx skills add coreyhaines31/marketingskills --skill ai-seo -a claude-code.

2

List the queries that matter commercially before anything else. This is the measurement set you will keep re-checking.

3

Run those queries manually through ChatGPT, Perplexity and AI Overviews and record who gets named. That is the baseline.

4

Say which goal you want. Getting cited as a source and appearing in AI Overviews for a query need different work.

5

Bring your content types into it. Comparison pages and documentation get cited on different query shapes than blog posts.

6

Check your structured data next, because it is one of the levers the skill treats as concrete.

Pricing Plans

Free. MIT license.

Checked against the repo in July 2026.

Use cases

Taking the first baseline

Leadership asks how you show up in AI answers and nobody knows. List the queries that matter commercially, run them through the assistants by hand, and record who gets named; that record is what every later change gets measured against.

Splitting the two goals

The team says AEO and means two different things. State whether you want to be cited as a source or to appear inside an AI Overview; the plan comes back different because the work behind each is.

Fitting AEO to strong SEO

Your traditional rankings are already good. Bring that search strength into the run along with your content types; the recommendations narrow to what's worth adding, including whether llms.txt earns a place.

The monthly re-check

One check tells you what a single assistant said on one day. Re-run the same query set each month; movement against that first record is the signal you report.

Best for

The AEO question with no baseline

It makes you measure before you act, which stops a quarter of content work aimed at a problem you never confirmed.

Deciding between citation and Overview presence

These are different goals with different work behind them, and the skill separates them explicitly.

A team with strong traditional SEO

It asks for your existing search strength, because that changes what AI-search work is worth doing.

Read the source

Published by Corey Haines. Opens in a new tab.
Open the Tool

Questions about ai-seo

How do I know if AI answers name me?
Is being cited the same as appearing in AI Overviews?
Should I publish llms.txt?
Can it measure AI traffic?

Questions about SEO & AEO

Where do you start with AI search visibility?
Is AI search worth the effort at low volume?
Strengths
  • Demands a baseline measurement before it recommends anything.
  • Separates being cited from appearing in an Overview, which most advice blurs.
  • Names attribution as a known blind spot and hands that off to the attribution skill.
  • Version 2.2.0, and one of the more actively updated skills in the library.
Limitations
  • The baseline is a manual check unless you add a tracker such as ai-citations-report.
  • It gives strategy, and llms.txt is contested. Claude SEO's seo-geo cites Google's position against it, which is worth reading alongside this.
  • No measurement of AI-referred traffic, which the library treats as an attribution problem.
Skip this if
  • Skip it if you already have a baseline for how assistants answer your category.

The team behind these plays.

We build inbound GTM engines for B2B software teams, and these are the plays we build from. Tell us the pipeline target and we'll show the plan under it.