SEO, GEO & AEO

Agent Readiness Audit

Use when the user wants to know whether AI agents buying on a customer's behalf can find, evaluate and act on their product — machine-customer readiness, agentic commerce, or being included in AI-mediated comparisons. Also use when the user mentions AI agents buying, machine customers, agentic commerce, MCP, llms.txt, "can ChatGPT actually buy from us", or being left out of AI-generated shortlists. Scores five dimensions, names the blockers, and specifies the fixes in cost order.

AI Referral Share

Use when the user wants to know whether AI search is sending them visitors and customers - how much traffic and how many conversions come from ChatGPT, Perplexity, Gemini, Copilot, Claude and other AI assistants. Also use when the user mentions AI referral traffic, LLM traffic, ChatGPT traffic in GA4, utm_source=chatgpt.com, the GA4 AI Assistant channel, "is AI search sending us customers", or wants to prove AI visibility work paid off. Reads a GA4 traffic export, separates each assistant's sessions and key events, and says whether they really convert differently from the rest of the site.

Content Decay

Use when the user wants to find which pages are losing search traffic and which to refresh first - content decay, content refresh, "our blog traffic is flat", declining organic clicks, or a content audit from Search Console. Also use when the user mentions content decay, content refresh, update old posts, declining rankings, CTR optimisation, title tag tests, or wants to know where to spend the next content week. Takes a Search Console page export comparing two periods and sorts every page into decaying, demand drop, snippet loss, rising or stable, then ranks refresh candidates by the clicks they lost and finds page-one pages below the site's own CTR median.

GEO Citation Tracker

Use when the user wants to measure or monitor whether AI answer engines actually name and cite their brand over time — not whether a page is optimized, but what the engines are saying right now. Also use when the user mentions AI share of voice, LLM citation tracking, brand visibility in ChatGPT/Perplexity/Claude/AI Overviews, "are we showing up in AI answers", answer-engine monitoring, or wants to prove GEO work moved the needle. Designs the prompt set, scores the run, and says whether a change between runs is signal or noise.

GEO Content Optimization

Use when the user wants to optimize content so it gets cited by AI engines (ChatGPT, Perplexity, Claude, Google AI Overviews) and wins answer-engine snippets — i.e. GEO (generative engine optimization) and AEO (answer engine optimization). Also use when the user mentions AI citations, getting quoted by LLMs, llms.txt, answer-first content, featured snippets, or "make this content rank in AI answers." Rewrites/augments a page to maximize citation likelihood.

Programmatic SEO

Use when the user wants to generate many search-targeted pages from a template and a dataset — location pages, comparison pages, integration pages, calculator pages, "best X for Y" pages. Also use when the user mentions programmatic SEO, pSEO, scaled content, template pages, or "we have a database, can we turn it into pages". Models whether the build pays back before anything gets written, then specs the template and the quality bar.

Search Demand Reader

Use when the user wants to know what people search for in their category and where the demand is going unmet, using their own Search Console data rather than an estimated keyword tool - reading a Queries export by intent, grouping it into topics, finding the topics they already appear for on page two or worse, queries split across their own pages, the branded share of their traffic, and rival-brand searches they show up in. Also use when the user mentions keyword research, search demand, Search Console queries, keyword gaps, cannibalisation, branded vs non-branded, or "what should we write next". Never estimates a search volume it cannot see.

SEO / GEO / AEO Readiness Audit

Use when the user wants to audit a web page or site for SEO, GEO (generative- engine / AI citation readiness), and AEO (answer-engine / featured-snippet readiness). Also use when the user mentions SEO audit, AI search visibility, getting cited by ChatGPT/Perplexity/Claude, featured snippets, llms.txt, schema, crawlability, or "why don't we show up in AI answers." Produces a 0–100 score across 5 weighted categories, a grade, and prioritized fixes.

SEO Content Brief

Use when the user wants to plan or spec a piece of content before writing it — a content brief, an outline for a target keyword, or a blog post that needs to rank and get cited. Also use when the user mentions content brief, keyword targeting, search intent, SERP analysis, outlining an article, or "what should this post cover". Produces a writer-ready brief: intent classification, the answer block, heading structure, entities to cover, citation and internal-link targets, and the cannibalisation check.

Structured Data for AI Search

Use when the user wants to add, fix, or validate structured data (JSON-LD, schema.org) so search engines and AI answer engines read a page correctly: which types belong on which page, which properties Google requires, and whether the markup matches what the page shows. Also use when the user mentions schema markup, JSON-LD, structured data, rich results, SoftwareApplication, Organization schema, FAQPage, HowTo, Article or BreadcrumbList markup, meta tags, Open Graph tags, llms.txt, or "is our schema right". Produces a page-by-page type map, a sourced check of each page's JSON-LD and the exact fixes, or generates the JSON-LD, meta tags and llms.txt from the user's own facts and checks them.