How to Get Recommended by ChatGPT: A 10-Step Playbook for 2026

Part of the generative engine optimization guide and AEO Hub.

A founder messaged me in February after reading every “how to rank in ChatGPT” article he could find. ChatGPT still would not name his product. He did not want another theory of generative engines; he wanted a checklist he could work through on a Friday.

I wrote one, tested it on three of my own properties, and compared notes with two other operators. The version below is what survived: ten steps, each with an action, a way to measure it, a time estimate, and a realistic range of impact.

For the background, read how to rank in ChatGPT, why ChatGPT might not be recommending your product, and how AI engines choose sources. This guide starts with what to do on Monday morning.

The 10-step overview

Scan this table before you begin. The “expected lift” ranges assume you are starting with little or no ChatGPT visibility; established sites may move faster.

“Free” means doing the work yourself. Outsourcing the page updates in step 4 at USD 50-150 per hour changes the budget. The lift estimates also overlap, so they do not add neatly to 100%. For example, fixing robots.txt makes the other work discoverable, and a clearer page may also earn more third-party links.

Why this works in 2026 (the short version)

ChatGPT can recommend a source from what the model already learned, or retrieve it live during a search. Those paths work on different timelines and reward different signals. Most advice covers only one of them; this playbook covers both.

Steps 1-3 diagnose the problem, and steps 9-10 measure the result across both paths. Step 4 mainly improves live retrieval, while step 5 builds the third-party evidence that may enter future training data. Steps 6-7 help crawlers find the work. Step 8 helps the model understand that all your profiles and mentions refer to the same company.

The Princeton GEO paper [1] found that citations, statistics, and quotations increased generative-engine visibility by as much as 40%, while keyword stuffing had little effect. That finding is the basis for step 4. The relative weights also draw on measurements from roughly 40 properties and research from Ahrefs [2], Semrush [3], Backlinko [4], Profound [5], and Peec [6].

ChatGPT had roughly 400 million weekly active users in late 2025 [7]. AI Overviews also appeared in about one-fifth to one-quarter of the sampled Google results: 20.5% in Ahrefs' September 2025 crawl and 25.11% in Conductor's autumn sample [8]. AI discovery is already large enough to measure rather than treat as an experiment.

Step 1: Audit your current ChatGPT visibility

Start with a baseline. Before you change a page, run 20-30 prompts in ChatGPT, Claude, Gemini, and Perplexity. Record whether your domain appears, where it appears, and how the answer describes you. The next nine steps depend on this snapshot.

How to do it. Brainstorm 20 prompts for now; you will refine them in step 2. Use a clean browser session without a logged-in account when possible. For each answer, note whether your domain was cited, whether your brand appeared with or without a link, and which competitors were named. A spreadsheet with columns for engine, prompt, citation rank, brand mention, and notes is enough.

You can automate the scan with our AI visibility score, Profound [5], Peec [6], Otterly, or SEOcrawl. Still, doing the first pass by hand is worth an afternoon: reading the answers teaches you things a summary score will hide.

What success looks like. You leave with a clean baseline. Calculate the percentage of prompts that cite your domain and the percentage that mention your brand. Most properties I have audited begin between 0% and 15%. The number may be uncomfortable; that is why it is useful.

Time and cost. Three to six hours for the manual version. Free if you do it yourself; USD 0-99 per month for an automated tool depending on prompt count.

Expected impact. No immediate lift. This step gives you the evidence needed to choose and evaluate the work that follows.

Here is the spreadsheet shape I have used on every audit I have run, cleaned up for sharing. Steal it.

Run half the ChatGPT prompts with browsing and half without it. If you appear only with browsing on, the model can retrieve you but may not know you from training. If you appear in neither mode, both paths need work. The how AI engines choose sources guide explains this split in more detail.

Step 1 took me four hours on my own site. The result was uncomfortable: cited on three of twenty-eight prompts, all on Perplexity, none on ChatGPT. That number is the reason this article exists.

Step 2: Identify the 20-30 buyer prompts you actually need to win

Replace guesses with buyer language. A brainstormed prompt looks like a keyword: “Stripe attribution.” A real buyer asks, “How do I see which marketing channel my Stripe revenue came from?” The second version carries intent and is much closer to what ChatGPT receives.

How to do it. Pull questions from four places: sales calls, support tickets, Google's People Also Ask results, and autocomplete in ChatGPT or Perplexity. Collect 5-10 phrases from each source, remove duplicates, and keep the best 20-30.

What success looks like. Every prompt has a clear intent — informational, comparison, or transactional — and enough detail to prevent a generic answer. “Best CRM” is too broad. “Best CRM for solo founders selling productized services” gives the engine and the reader a useful constraint. Balance specificity with enough demand to matter.

Time and cost. Four to eight hours of focused work. Free.

Expected impact. Indirect but large. Every later step uses this list, so weak prompts send the entire project in the wrong direction. I have repeated this step three times because my first list was too generic.

Here is the breakdown I use for prompt-type balance.

Most teams skip problem-language prompts, even though buyers usually describe a symptom before they know the category name. A page that answers “my X is doing Y” in plain language can win citations that keyword-shaped pages miss. Our prompt tracking feature can monitor the final list, but choosing the questions still requires human judgment.

Run the 20-30 prompts once more and read each answer in two passes. First, note the cited sources. Then look at how ChatGPT frames the recommendations — phrases such as “best known for” or “commonly recommended.” Those phrases reveal the comparison slots your page needs to earn.

Step 3: Map prompts to existing pages (the gap analysis)

Match each prompt to a page. For every prompt, choose the page on your site that gives the best current answer. Then label the prompt: covered well, needs restructuring, fragmented across several pages, not covered, or dominated by a competitor you are unlikely to displace. This becomes the work queue for step 4.

How to do it. Add “current best page” and “gap state” columns to the audit spreadsheet. Pick one page per prompt. If several pages each answer only part of the question, mark the prompt as fragmented rather than absent. If none answers it, either create a page in step 4 or make a deliberate decision to skip it.

What success looks like. You have a prioritized list with rough effort estimates. In a typical 30-prompt audit, I expect 8-12 pages to need restructuring, 5-8 prompts to need new pages, and 3-5 prompts to need consolidation. The rest can stay as they are or be skipped.

Time and cost. Two to four hours. Free.

Expected impact. This step does not create visibility by itself. It prevents you from rewriting pages that already win while ignoring gaps you could realistically close.

Some competitor-dominated prompts are not worth chasing this quarter. A canonical Reddit thread, Wikipedia article, or strong first-party document may be too established to displace quickly. If ChatGPT consistently answers with Stripe's own documentation, choose a more winnable prompt.

For each "not covered" prompt, draft a one-line page brief: what the page needs to answer in its first 100 words, what supporting evidence it needs (statistics, citations, comparison tables), and which existing page (if any) it can be split off from. This is the bridge into step 4. Do not write the pages yet; just have the briefs ready.

Step 4: Restructure each target page for AI extractability

Make the answer easy to extract. Rework the pages marked “needs restructuring” and create the missing pages worth pursuing. This is the highest-impact part of the playbook, so plan to spend about 60% of your effort here.

How to do it. Give each page six things: a direct answer in the first 100-120 words; question-shaped H2s; at least one specific comparison table; 4-8 inline citations to primary sources; FAQPage and Article JSON-LD that match the visible questions; and a visible update date backed by a real quarterly refresh.

Each element helps in a different way. The direct answer provides a clean passage to quote. Question-shaped headings mirror the language people use. Tables organize comparisons. Primary citations support the claims. Structured data clarifies the page, and meaningful updates give crawlers a reason to return.

What success looks like. Watch for three signals over 4-8 weeks: the page begins appearing for its target prompts, its average citation position improves, and ChatGPT draws the answer from your direct-answer block. A citation that still paraphrases another source means the page has not become the preferred extract.

Time and cost. Roughly 3 hours per page once you have the briefs from step 3. Across 10-15 pages, budget 30-45 hours. Outsourced at USD 50-150/hour, that is USD 1,500-6,750. Do the first two or three yourself to internalize the pattern, then parallelize.

Expected impact. In my measurements, this step accounts for roughly 35-45% of the total visibility gain.

Here is the before-vs-after page structure I use, side by side, so you can audit your own pages quickly.

The direct-answer block is where most pages fail. Keep it to 60-120 self-contained words. If you pasted it into Slack, a colleague should understand the answer and know what to do next. The AI search optimization checklist includes more examples.

Step 4 took me about 3 hours per page across my first eight pages. The impact showed up in week 5 on Perplexity, week 7 on ChatGPT search, and the unprompted browse-off mentions did not arrive until late month three. That lag is consistent across every operator I have compared notes with.

Step 5: Earn citations on third-party sources

Build credible mentions elsewhere. Focus on sources ChatGPT already uses: Reddit, Wikipedia, G2, Capterra, Hacker News, industry newsletters, Stack Overflow for technical brands, and respected category roundups. The goal is a useful, verifiable mention — not a paid backlink.

How to do it. Work through these five channels, roughly in order of impact for most categories:

1. Reddit. Identify the 5-10 subreddits where your category buyers hang out. Build a posting history of genuinely helpful answers (not promotional). When relevant, name your product. Do not spam; the moderators are sharp. Reddit's content is licensed to Google for AI training reportedly around USD 60M per year [9], which means a genuine helpful mention compounds for a long time.
2. Wikipedia and Wikidata. Wikipedia has notability rules that block most SMB SaaS, but Wikidata is permissive. Create a Wikidata entity for your company with founder, founding date, headquarters, category, and official site properties. Then ensure any Wikipedia article in your category (if one exists) has an accurate, neutral mention of your product with a primary-source citation.
3. G2 and Capterra. Claim your profiles, fill them completely, request reviews from happy customers, and respond to every review professionally. AI engines lean on these for B2B SaaS comparison queries because the review platforms are heavily crawled.
4. Listicles and category roundups. For each of your top 10 prompts, identify the 5-15 listicles that already rank. Reach out to the authors with a genuinely useful pitch (data, a specific perspective, a comparison angle they missed). Aim for 2-5 placements per quarter.
5. Hacker News, podcasts, and newsletters. Lower-volume but high-trust sources. A single thoughtful HN comment thread or podcast appearance can move the corpus needle disproportionately.

What success looks like. Track monthly third-party mentions, placements in the roundups you targeted, and citation changes for prompts that usually draw from Reddit or G2. Those prompts should move first as the engines recrawl the sources.

Time and cost. Plan for 3-6 hours a week. Doing it yourself costs time; a community or outreach specialist may cost USD 500-2,000 a month. The work is slow, but a credible history of mentions can compound over 12-24 months.

Expected impact. Roughly 25-35% of total visibility lift in my measurements. Step 4 usually moves faster; this step builds the longer-term advantage.

Here is the source matrix I use to plan the third-party citation work. The "AI weight" column is my own subjective estimate based on observation, not a published number.

A Reddit warning: a banned account is worse than no account. Contribute useful answers before mentioning your product, never lead with a pitch, and be honest about competing options. A balanced answer can remain useful for months. A new account posting “check out my tool” will usually disappear in minutes.

The Reddit and Wikipedia thesis is so important I wrote a dedicated piece on the r/SaaS and r/SEO mention compounding effect for the deep version. For the playbook, just know that step 5 is the slow but durable moat, and ignoring it caps your ceiling on every other step.

Step 6: Publish llms.txt and llms-full.txt

Publish two crawler-friendly files. Add /llms.txt, a short map of your most useful pages, and /llms-full.txt, a longer collection of canonical content. Follow the llmstxt.org specification [10]. Adoption was still low in Q1 2026, so treat this as a small, inexpensive bet rather than a core ranking tactic.

How to do it. Write llms.txt in Markdown with your site name, a one-line description, links to the best documentation and articles, and an optional “Other” section. Keep it under 5,000 words. Build llms-full.txt from the complete Markdown of those canonical pages. Serve both with HTTP 200 and a text/plain or text/markdown content type.

What success looks like. Confirm both files return HTTP 200, then check your logs for AI crawlers requesting /llms.txt within 7-14 days. Stop after a few hours; this is a small optimization, not a weeklong project.

Time and cost. 1-2 hours. Free.

Expected impact. About 3-7% of total visibility lift by my estimate. Ship it because it is cheap and may become more useful as adoption grows, not because it is a shortcut.

Here is the minimum-viable llms.txt template I use, with placeholders. Save 20 minutes by adapting this directly.

For llms-full.txt, the pattern is to concatenate the full markdown of every page in your "## Docs" and "## Blog" sections, separated by clear headers. This file can be 50,000+ words. Some teams generate it dynamically from their CMS; for most static sites a build-step script suffices.

The llms.txt revenue impact post walks the measurement nuances if you want to verify a lift in your specific case. For 90 percent of sites, ship the file, log the crawler hits, move on. Do not let llms.txt become a weeklong project.

Step 7: Open up to AI crawlers (robots.txt)

Check who can crawl the site. Review robots.txt for blocks on GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and OAI-SearchBot. Many sites added broad blocks in 2023-2024 and never revisited them. A 15-minute audit can reveal that the rest of the work is not crawlable.

How to do it. Look for a crawler name followed by Disallow: /. If you want that engine to use the public site, remove the blanket block or replace it with Allow: /. Keep sensitive paths such as /admin/ blocked separately. A legal or licensing requirement may justify a broader block; make that choice deliberately.

What success looks like. Fetch the public robots.txt and confirm the intended rules. Then search server logs for the listed user agents. No activity after 14 days may mean a rule, firewall, or DNS layer is still blocking them.

Time and cost. 15-30 minutes. Free.

Expected impact. This is an unblocker, not a lift. If you were blocking, removing the block makes every other step possible. If you were not blocking, this step costs you nothing and changes nothing.

Here is the actual robots.txt block I run on my own site, scrubbed for sharing. Lift it directly if you want.

One important nuance: blocking GPTBot affects future crawls; it does not remove content already present in a trained model. If your team added a block in 2023, revisit the original reason and weigh it against the value of future recommendations.

For technical-brand sites, the AI crawler tracking guide walks the server-log side of this in detail, including how to verify the bots you are seeing are the real bots (the impersonators are real and increasingly clever).

Step 8: Build entity disambiguation

Make your company easy to identify. Your site and trusted profiles should agree on what the brand does, who founded it, and when and where it began. If those details conflict, an AI engine may confuse you with another entity or leave you out of an answer.

How to do it. Keep these six profiles complete and consistent:

1. Wikidata entity. Create a Q-item for your company. Include: instance of (business), industry, founder, founding date, headquarters location, official website, social media handles. Wikidata is the most-quoted entity graph by every major LLM.
2. Crunchbase profile. Complete with founders, funding (if any), category, description, official URLs.
3. LinkedIn Company page. Complete with about, industry, headquarters, size, founded year.
4. Your homepage Organization JSON-LD. Include a sameAs array pointing to every other profile above (Wikidata, Crunchbase, LinkedIn, X/Twitter, GitHub, G2, Capterra).
5. Google Business profile (if you have a physical address). Or skip if purely online.
6. GitHub Organization (if you ship code). Public repos add corpus weight.

What success looks like. Ask ChatGPT without browsing, “Tell me about [Brand].” An accurate description of your category, founder, and basic history is a good sign. Confusion or omission means the identity signals still disagree. A Google Knowledge Panel is another useful signal, though not a guarantee of how ChatGPT will respond.

Time and cost. 6-12 hours total across the six profiles. Free (some platforms charge for verification badges, optional).

Expected impact. 8-15 percent of total visibility lift. The impact compounds with step 5 (third-party citations), because every citation source verifies your entity against the sameAs graph you built.

Here is the property checklist for your Wikidata entity. Fill all of these; partial entries do less work.

The Wikidata documentation [14] walks the editor flow if you are new. Plan for an hour for the initial entity creation, and revisit quarterly to add properties as your company grows.

Your homepage Organization JSON-LD should look approximately like this shape (paraphrased to avoid MDX issues; see the full spec at schema.org/Organization):

The sameAs array connects those profiles to one entity. Without it, a crawler has to infer that the records all describe the same company.

Step 9: Monitor weekly with prompt tracking

Track the same prompts on a schedule. Re-run the 20-30 prompts from step 2 and record which ones gained or lost citations. This tells you whether the work is moving and where to focus next.

How to do it. Manually run each prompt in ChatGPT, Perplexity, Claude, and Gemini, or use a tracker that sends you the changes. The manual version is slow but informative. Our prompt tracking feature, Profound [5], Peec [6], and Otterly automate the scan.

What success looks like. Track three metrics:

1. Citation count. How many of your 20-30 prompts cited your domain across all four engines combined.
2. Share of voice. Of all the sources cited across your prompts, what percentage were yours (versus competitors and third-party sources).
3. Brand mention count. How often your brand name appeared in answer text without a link (corpus-pathway signal).

Review the trend over 8-12 weeks rather than reacting to one run. If the numbers remain flat, revisit the page work in step 4 and the third-party evidence in step 5.

Time and cost. 1-2 hours per week manual; USD 99-499 per month for an automated tool depending on prompt count and engines covered. The Attrifast version starts at $9.99/month on Starter (10 prompts, auto-scan every 30 days) and moves to auto-scans every 10 days across 30 prompts on Pro at $49/month.

Expected impact. Monitoring does not create visibility. It shortens the time between doing the work and learning whether it helped.

Here is the weekly tracking template I run on my own properties. Copy it.

Do not ignore the “top-losing prompt” column. A lost citation may mean a competitor improved its page, the engine changed retrieval, or your content went stale. Each cause needs a different response.

Step 10: Measure traffic and conversion (the revenue close)

Connect the work to revenue. Use first-party attribution to detect AI sources from referrers and behavioral signals, then join the session to a Stripe payment through a webhook. This lets you see which engines produced customers and how much each visit was worth.

How to do it. ChatGPT, Claude, and Perplexity often remove the referrer, so GA4 puts many of their visits in Direct or (none) [15]. The fix has three parts:

1. Server-side referer capture. When a visitor lands on your site, capture the Referer header server-side (before any JavaScript runs) and store it on the session. AI clients that leak even a partial referer are detected here.
2. AI source detection. Maintain a lookup of known AI user-agents (ChatGPT-User, ClaudeBot, etc.) and behavioral patterns (no JavaScript, no cookies, fetch-only). Flag visits that match.
3. Stripe webhook join. When a Stripe payment_intent.succeeded or checkout.session.completed event fires, join the customer email or customer ID back to the original session by stored attribution key, and record AI source as the first-touch (or last-touch, depending on your model).

The implementation is documented in track ChatGPT traffic, AI citation tracking, and the ChatGPT referral analytics guide. A team with a Node or Python backend can build it in 1-2 weeks. Attrifast packages the same workflow as a $9.99/month product with a short installation.

How you measure success. The output you want is a table that looks like this, refreshed weekly.

The last row is the problem. In this example, much of “Direct” is AI traffic that GA4 could not label. If you cannot separate it, the finance team sees no AI revenue line and cannot evaluate the work fairly.

Time and cost. 1 hour setup. $9.99/month for the Attrifast version. Free if you build it yourself (1-2 engineer weeks).

Expected impact. This step does not improve visibility. It turns visibility work into a measurable business result.

What's actually realistic timeline-wise

Ignore promises of “ChatGPT recommendations in seven days.” Across roughly 40 properties I have instrumented, and in comparisons with other operators, the sequence usually looks like this:

Three reality checks:

1. Weekly results are noisy. A citation may appear in week 4, disappear in week 6, and return in week 9. Judge the trend, not one scan.

2. Perplexity usually moves first, followed by ChatGPT search. Recommendations without browsing may not change until a new model includes your newer third-party mentions. That can take 6-12 months.

3. The work compounds. Restructured pages can move in the first year; a history of credible mentions and consistent entity data takes longer. Plan for an ongoing program, not a one-quarter campaign.

The pessimistic column is what happens when step 4 was rushed, step 5 was skipped, or the category is dominated by Reddit-and-Wikipedia incumbents. The optimistic column is mostly an empty category. Most teams executing the playbook honestly land in the realistic column.

Common failure modes (and how to spot them)

These are the failure modes I see most often. They are much cheaper to prevent than to repair after a quarter.

Failure mode 1: skipping the baseline. Teams rewrite pages and discover three months later that they cannot prove anything changed. Spend the four hours before you edit.

Failure mode 2: tracking prompts nobody asks. “Attribution software” sounds like a keyword. “How do I see which channel drove this Stripe payment?” sounds like a buyer. Rebuild the list from sales calls and support tickets.

Failure mode 3: ignoring third-party evidence. Page edits feel productive immediately; credible mentions take longer. Set a quarterly goal for 5-10 worthwhile placements and protect the time.

Failure mode 4: corpus latency frustration. New companies blame the playbook when browse-off ChatGPT does not recommend them. The fix is patience plus measurement of the surfaces you can move (Perplexity, ChatGPT search). The browse-off surface follows the model retrain cycle, not your roadmap.

Failure mode 5: measuring presence but not revenue. A citation count cannot answer the finance team's obvious question. Set up step 10 in the first week, even if the content work takes months.

Failure mode 6: chasing every new engine. Teams scatter effort across seven engines and win none. The fix is concentration: ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, in that order. Master the first three before adding anything else.

The Hacker News thread on this topic from late 2025 [16] is worth reading for the operator commentary, especially the section on Reddit moderation, which catches more brands than any other failure mode. The r/SEO subreddit recurring thread on "ChatGPT recommendations" [17] is the live pulse of what is actually working at the small-team level; bookmark it.

What the data says (and where it gets uncertain)

Some claims below come from published research; others are estimates from my own sample. This table separates the two so you can decide how much confidence to place in each number.

Two uncertainties matter. First, the balance between page restructuring and third-party mentions may reverse after the first year as those mentions compound. Second, the sample is heavily US English. Reports from German, Japanese, and Spanish markets may not follow the same pattern.

A few additional pieces worth reading to triangulate this playbook: the Backlinko AI Overviews citation guide [4], the Profound blog [5], the Peec.ai blog [6] for European measurement, the Common Crawl statistics [18], the Search Engine Land AI search library [21], the Anthropic crawler docs [12], the OpenAI bot docs [11], and the which brands does ChatGPT recommend in 2026 measurement piece for category-level benchmarks.

FAQ

How long does it actually take to get ChatGPT to recommend my product?

Honestly, eight to twelve weeks of consistent work, and that is for the live-retrieval surface (ChatGPT search and browse). The deeper training-corpus surface, where ChatGPT recommends you without browsing turned on, runs on OpenAI's retrain cycle and takes one to three quarters. In my own measurement across roughly 40 properties, the first Perplexity citations land in week 3-5, the first ChatGPT search citations in week 5-8, and the unprompted browse-off mentions on a refreshed model can take six months or more. Anybody promising overnight results is selling you something.

Do I need to pay for an AI visibility tool to do this?

Not for step 1. You can audit your current ChatGPT visibility by manually running 20-30 prompts in ChatGPT, Perplexity, Claude, and Gemini and logging the results in a spreadsheet. It is tedious but free. Paid tools like Profound, Peec, Otterly, and Attrifast's prompt tracking automate the weekly run and the diffing. The honest break point: under 30 prompts and a quarterly cadence, do it manually; above that, the labor cost exceeds the tool cost.

What is the single highest-impact step in this playbook?

Step 4 — restructuring your top revenue pages for AI extractability. Across the operator data I have collected, that one move accounts for roughly 35-45 percent of the total visibility lift, because it touches both the live-retrieval re-ranker (better extraction of your passages) and the training-corpus pathway (cleaner ingestion when the next crawl happens). The next-highest impact step is step 5, earning citations on third-party sources like Reddit and trusted listicles, which compounds slowly but durably.

Should I block GPTBot to protect my content from being trained on?

Only if you have a specific legal or licensing reason. For the vast majority of SMB SaaS, ecommerce, and content sites in 2026, blocking GPTBot removes you from future training corpora and slowly erodes the chance ChatGPT recommends you without browsing turned on. The companies that block it are mostly large publishers with content licensing deals. If you want to be recommended, allow GPTBot, ClaudeBot, PerplexityBot, and Google-Extended in your robots.txt and treat their crawls as free brand-building.

How many prompts should I track per week?

Between 20 and 40 for a focused SaaS. Pick five to ten high-intent buyer prompts (the ones that read like "best tool for X" or "how do I solve Y"), five to ten comparison prompts ("A vs B"), five to ten problem-language prompts ("my X is doing Y, what should I use"), and five general category prompts. Run each across ChatGPT, Perplexity, Claude, and Gemini weekly. Less than that misses real movement, more than that becomes a tracking job nobody maintains.

Will llms.txt actually move the needle?

Modestly. llms.txt is not a ranking signal. It is a curated map of your most LLM-relevant pages that some AI crawlers read when they encounter it. Adoption is still low (~7-10 percent of public SaaS sites in Q1 2026), so the upside is real and the downside is zero. I treat it as a 30-minute investment with a small-but-positive expected value, not as a centerpiece. Step 4 (page restructure) and step 5 (third-party citations) outweigh it by an order of magnitude.

How do Reddit and Wikipedia fit into this playbook?

They sit in step 5 and they are arguably the highest-leverage third-party citation sources, because both are heavily weighted in LLM training corpora. Reddit's content was licensed to Google for AI training (Reuters reported around USD 60M per year), and Wikipedia underpins the entity disambiguation graph every major model uses. A genuine, helpful presence in r/SaaS, r/SEO, r/marketing, plus a clean Wikidata entry, can move your ChatGPT recommendation odds more than ten paid backlinks.

What if my product launched after the model's training cutoff?

Then ChatGPT literally does not know you exist in browse-off mode, and steps 1-9 of this playbook will not change that in the short term. You have two options: lean entirely on the live-retrieval surface (ChatGPT search, Perplexity, Google AI Overviews) by nailing steps 4-7, and wait one to three quarters for the next model retrain to ingest your earned third-party citations and Wikidata entry. The waiting is brutal, but the work in the meantime is exactly what gets you into the next training pass.

How do I disambiguate my brand entity?

Step 8 covers this in detail. Short version: claim and complete profiles on Wikidata, Crunchbase, LinkedIn Company, GitHub Organization (for technical brands), G2 and Capterra (for B2B SaaS), then make sure your homepage Organization JSON-LD lists every one of those URLs as sameAs entries. The goal is that when ChatGPT encounters your brand name, the surrounding context across 5-7 authoritative sources agrees on what you do, who founded you, and what category you sit in. Without that, the model defaults to confusion or omission.

What is the cheapest version of this playbook that still works?

Manual prompt tracking in a spreadsheet (step 1, 2, 9), a free Wikidata edit (step 8), free robots.txt and llms.txt edits (steps 6, 7), and roughly 40 hours of content restructure across your top 10 pages (step 4). That gets you 60-70 percent of the impact at near-zero cash cost. The paid layer (prompt tracking tools, AI visibility platforms, Attrifast for revenue attribution) shaves time and adds the measurement loop, but it does not replace the work.

How do I measure whether any of this actually drove revenue?

Step 10 is the whole reason this article exists. ChatGPT and the other AI engines strip the referer header, and GA4 buckets AI-attributed sessions as Direct or (none). To see whether your GEO work shipped revenue you need server-side first-party attribution that detects AI-engine sources by referrer, behavioral pattern, and known AI user-agents, then joins the session to your Stripe payment via webhook. That is exactly the part Attrifast was built for. Without that join, you are optimizing a metric you cannot prove paid for itself.

Can I skip steps in this playbook?

Steps 1, 2, 3, and 10 are non-skippable, because they are diagnostic and measurement, not execution. You can defer step 6 (llms.txt) and step 8 (entity disambiguation) if you are bandwidth-constrained, but you will pay for it in slower compounding. Steps 4 and 5 are the load-bearing execution steps. Step 9 (weekly monitoring) is what keeps the whole thing honest. The fastest realistic version is steps 1, 2, 3, 4, 5, 9, 10 with a promise to revisit 6, 7, 8 in month two.

Does this work for ecommerce, or only for SaaS?

It works for both, with a different emphasis. SaaS benefits more from step 5 (third-party citations on G2, Capterra, Reddit comparison threads) because category language matters. Ecommerce benefits more from step 4 (page restructure with PriceSpec and Product schema) and step 7 (allowing OAI-SearchBot to crawl product pages) because ChatGPT shopping and similar surfaces lean on classic product-feed signals. The 10 steps are the same; the relative weights shift by category.

What is Attrifast's role in this playbook?

Attrifast is the Stripe-native AI revenue attribution tool: it detects AI traffic from ChatGPT, Claude, Gemini, Perplexity, Copilot, and Google AI Overviews, measures your AI search visibility across prompts, and joins those sessions to Stripe payments so you can see which AI recommendations actually drove revenue. Step 1 (audit) and step 9 (monitoring) live in our AI visibility score and prompt tracking features. Step 10 (revenue measurement) is the wedge — nobody else closes the cited-clicked-paid loop because GA4 cannot see AI sources at all.