The audience already moved
This is the channel your buyers are already using to evaluate products. Not a side bet - a primary inbound surface that did not exist three years ago.
When a buyer asks ChatGPT, Perplexity, Claude, Gemini, or Google AI Overviews a question your product answers, the cited source should be you. We audit, restructure, and monitor your site - schema, llms.txt, AI-crawler access, FAQ structure, entity links - so AI assistants treat your pages as the authoritative answer, not your competitors’.
Indicative timeline and starting price. Final scope, dates, and investment agreed after the intro call.
AI assistants are eating the top of the funnel. Showing up inside the answer - cited, named, linked - is the new page-one ranking. The numbers below are why we built a dedicated practice for it.
This is the channel your buyers are already using to evaluate products. Not a side bet - a primary inbound surface that did not exist three years ago.
For most informational queries, the AI answer is the first thing your buyer sees. Whether they keep scrolling depends on whether your page made it into that answer.
Even ranking #1, you lose roughly six out of ten clicks the moment an AI Overview shows up. Authoritas measured the drop on the top organic link at 79 percent in some verticals. Classic SEO alone no longer holds the floor.
Showing up inside the AI answer reverses the loss. The cited brand wins both the AI surface and the link below it - and the paid placements convert harder too.
Claude-referred traffic converts at 16.8 percent, ChatGPT at 15.9 percent, Perplexity at 10.5 percent - against 2.8 percent for Google organic. The visitor arrives late in the buying journey, having already used the AI to shortlist vendors.
Even if you treat the headline as scenario-modelling, the direction of travel is clear. The teams that ship AEO and GEO work this quarter will own the AI citations before competitors notice the channel exists.
One engagement covers the full AI-citation surface. Pick the modules that matter; descope what does not apply. Everything ships into your existing stack - CMS, repo, analytics - with no platform lock-in.
End-to-end audit of every page in scope across eight dimensions: schema completeness, technical hygiene, page structure, AI-crawler access, freshness, authority signals, entity density, and sitemap coverage. Each finding has a severity, a where-on-page, and a one-line fix. Powered by our open-source AI-SEO MCP.
JSON-LD designed for AI extraction: Article, FAQPage, HowTo, Organization, Service, Product, BreadcrumbList, and the sameAs entity links that tie your brand to Wikipedia, LinkedIn, Crunchbase, and GitHub. Built against current Schema.org rules - no deprecated patterns, no markup that gets ignored.
Per-bot robots.txt rules for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended, Bingbot, CCBot. We surface the GPTBot-blocked-but-OAI-SearchBot-allowed trap, then ship a hand-checked llms.txt and AGENTS.md so agents have a curated entry-point. Quick check via our free GPTBot access tool and llms.txt validator.
Page-level rewrites optimised for AEO and GEO: H2 headings phrased as the queries you want to win, the answer in the first 80 words, FAQ blocks at the bottom with FAQPage schema, comparison tables and step-by-step lists where the format calls for it. Generic AI-blog tone is what we are explicitly building against. See the patterns in our FAQPage schema audit.
One data set, hundreds of answer-shaped pages. Templates, data plumbing, and publish pipeline straight into your CMS, with internal-linking and schema baked in. Built for the long-tail queries AI assistants love and the hand-written backlog will never reach.
Track your brand’s appearance across ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews on a fixed query set. Citation share, position, sentiment, and the actual source URL the model cited. Weekly Slack digest plus a dashboard you can show your CMO.
The reason LLMs cite some brands and ignore others is the entity graph - whether they understand who you are, what you sell, and how you connect to the rest of the web. We wire sameAs links, fix the Wikipedia/Wikidata gap where it matters, and tune Organization and Person schema so models route citations to your canonical URLs.
Canonical link integrity, og:url consistency, trailing-slash hygiene, sitemap lastmod accuracy, IndexNow submission, Core Web Vitals, image alt coverage. The boring layer that decides whether the crawl succeeds at all.
Your team keeps everything: the repo, the schema templates, the rewritten pages, the monitoring dashboard, and our free AI-SEO MCP for re-running audits inside Claude, Cursor, or any MCP-capable agent. No license fee, no “managed” lock-in.
One working session with your content and SEO leads. We agree the query set, baseline your citation share across the five AI surfaces, and run the full audit on every page in scope. You see the per-page AI-SEO score and the ranked fix list by end of day three.
Per-crawler robots.txt rules, llms.txt, AGENTS.md, canonical and sitemap fixes, Core Web Vitals quick wins. The boring layer ships first because the crawl has to succeed before any content work matters.
JSON-LD rolled out across templates - Article, FAQPage, HowTo, Organization, Service, BreadcrumbList - plus sameAs entity links. Wikipedia and Wikidata gaps surfaced and patched where the project has authority to act.
Highest-payoff pages rewritten for answer extraction. If programmatic AEO is in scope, the template and first batch of pages publish here. Generic AI-blog tone explicitly avoided.
Brand-citation dashboard wired, weekly Slack digest live, the AI-SEO MCP installed in your team’s Claude/Cursor configs. Walk-through of the runbook, repo handed over. You leave week four with the practice running, not slideware.
Indicative timeline. Larger sites (10k+ URLs) or complex entity-graph work can stretch this; we confirm dates after the kickoff session.
We open-sourced the audit. Run it yourself before you talk to us - or use it to keep the gains running after handover. No signup, no API key, no rate-limited free tier.
Defined scope, agreed in writing before kickoff. No metered hours, no surprise add-ons, no scope creep mid-build. The first week sets the bar - we ship to it, and you see citation share moving by the end of week four.
You own the repo, the prompts, the templates, and the model relationship. The AI-SEO MCP is MIT-licensed and yours to run forever - no per-audit fee, no “managed” service tax. Production model usage during the build is on us; ongoing usage goes straight to your provider account.
Investment is sized to your URL count, content surface area, and CMS complexity after the intro call. We come back with one number, in writing.
Start a projectAI SEO is the umbrella term for getting your content surfaced by AI assistants. AEO (answer engine optimization) targets the structured answers shown inside ChatGPT, Perplexity, Claude, and Google AI Overviews. GEO (generative engine optimization) targets the way generative models compose multi-source answers and decide which sources to cite. The work overlaps with classic SEO but the ranking signals differ - schema completeness, FAQ structure, AI-crawler access, llms.txt, entity sameAs links, and brand authority weigh more than classic backlinks.
AI Overviews now appear on roughly 55 to 60 percent of US Google searches3, and ChatGPT alone serves over two billion daily queries1. When an AI answer shows up, the top organic result loses 58 to 79 percent of its clicks4 - but brands cited inside the AI answer pick up 35 percent more organic clicks. The traffic that does click through from AI assistants converts at four to five times the rate of Google organic5. Showing up inside AI answers has become the primary inbound channel, not a side bet.
Classic SEO optimises a page to rank on Google. AI SEO optimises a page to be extracted, summarised, and cited by an LLM. The technical surface is bigger: per-crawler robots.txt rules (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended), llms.txt, JSON-LD beyond Article (FAQPage, HowTo, Organization, sameAs entity links), and an answer-extractable page structure (H2 headings matching query phrasing, FAQ blocks, comparison tables, step-by-step lists). The content layer is also different - models cite the page that contains the clearest, most quotable answer near the top.
No. Everything we ship - structured data, FAQ structure, sitemap hygiene, canonical correctness, Core Web Vitals, entity links - also benefits classic Google ranking. The only AI-specific additions are llms.txt and per-crawler robots.txt allow rules, neither of which affects Googlebot. The work is additive, not a tradeoff.
Ahrefs’ March 2026 study7 found that adding schema to pages already getting AI citations did not move the needle. The honest read is that schema is necessary but not sufficient - it is the floor, not the ceiling. The bigger lifts come from page structure, entity links, llms.txt, and authority signals, which is why we treat schema as one of nine modules, not the headline. We ship it because it is required for FAQPage rich results and because Bing and Google both confirmed it helps their LLMs parse content, but we never bill it as the silver bullet.
Four numbers, baselined in week one and tracked monthly: (1) citation share across ChatGPT, Perplexity, Claude, Gemini, and AI Overviews on your target query set, (2) AI-Overview coverage rate for your branded and non-branded queries, (3) AI-referred traffic and its conversion rate vs Google organic, and (4) the per-page AI-SEO score from our audit MCP. Dashboard ships with the build.
Yes. The schema templates, the llms.txt, the robots.txt rules, the rewritten pages, the monitoring scripts, and the audit configuration are yours in a repo. We also hand over our open-source AI-SEO MCP so your team can re-run the audits in Claude, Cursor, or any MCP-capable agent forever. No license fee.
Crawler access and schema changes pick up within days to two weeks - AI Overviews and ChatGPT Search both refresh on roughly weekly cycles. Content rewrites and entity-graph work take four to eight weeks to show up in citation share. The build itself ships in three to four weeks of calendar time.
That is one of the first things we audit. Many sites unintentionally block GPTBot while leaving OAI-SearchBot allowed, or vice versa - meaning the model can answer about your page but not learn from it (or the opposite). We map per-crawler access for ten AI bots, surface the conflicts, and propose the right allow rules for your situation. The decision stays with you.
Tell us your top five queries and the AI surfaces you care about. We’ll come back within one business day with a baseline citation share and the next step.
Open the contact form