A new product is invisible to AI models on day one and stays that way unless you seed retrieval. ChatGPT's August 2025 training cutoff means any launch after that date is unknown to the base model until the next release. The fastest path to citation is retrieval: a category-fit landing page, three to five independent press articles, a G2 or Capterra listing with at least ten reviews, and one Reddit or community thread that uses your product name in a buyer question. Expect Perplexity within days, Google AI Overviews within two to four weeks, and ChatGPT browsing within four to eight weeks. The base model lags by quarters.
Launch week is when your AI visibility curve gets shaped for the next year. Most teams treat AI search as an SEO problem they will get to after the press cycle ends. By then the citation graph has already formed around competitors, and your product is the unfamiliar option an AI model declines to recommend because nothing in its retrieval set vouches for you.
This playbook covers what to publish, where to seed citations, and how to measure whether AI models actually picked your product up. It is written for a team launching one product, not a brand running a sustained content program. The principles still apply if you are launching a feature, a category extension, or a rebrand, but the timelines compress.
Parse tracks AI visibility across ChatGPT, Google AI Overviews, and Perplexity, which is how we know how slowly new entrants typically register and which signals correlate with early lift.
Why a new product is invisible by default
AI models pick the brands they recommend from two pools: their training data and a real-time retrieval set. A product launched today appears in neither. Training cutoffs lag the calendar: ChatGPT 5.4 has a cutoff of August 2025 with a release date of March 2026, Claude 4.6 Opus is August 2025, and Gemini 3 is January 2025, according to Otterly's tracker. A product that did not exist before those dates simply is not in the base model.
Retrieval is the only path until the next training round. ChatGPT browses through Bing. Google AI Overviews retrieve from the Google index. Perplexity uses its own Sonar crawl. Each has different freshness, different signals, and different blind spots. Your launch needs to be visible in all three retrieval systems within the first month, or AI answers about your category will continue to default to whoever was there before you.
The two paths AI models use to find a new product
Every AI answer about a brand is built from one of two retrieval modes. Understanding which mode applies tells you where to seed.
The first mode is base model recall. The model "knows" a brand exists because that brand was mentioned thousands of times across the training set: press, reviews, Wikipedia, community discussion. New products have zero base model presence. You inherit this only over months or years of accumulated coverage.
The second mode is augmented retrieval. The model issues sub-queries at runtime, retrieves a small set of fresh pages, and uses them as evidence. This is how a brand with limited historical presence still gets mentioned: by having strong, authoritative pages live when the query fires. Perplexity, ChatGPT browsing, and Google AI Overviews all work this way for current questions. Sonar's index processes tens of thousands of update requests per second, per Perplexity's own description, which is why a new page can show up in answers within days.
Your launch strategy targets retrieval, not training. You cannot influence the next model checkpoint. You can influence what AI models see when they search this week.
Realistic timeline: when each platform catches up
The platforms catch up on different clocks. Set internal expectations against this table, not against the SEO ranking timelines your team is used to.
A short setup before the numbers: these ranges assume a brand with no pre-existing AI visibility, a clean launch page live by day one, and at least three independent press hits in the first two weeks. Brands with stronger PR amplification compress these windows.
| Platform | First citations possible | Typical reliable inclusion | Base model recognition |
|---|---|---|---|
| Perplexity | 1 to 5 days | 2 to 3 weeks | N/A (always retrieval) |
| Google AI Overviews | 2 to 4 weeks | 4 to 8 weeks | N/A (always retrieval) |
| ChatGPT browsing | 1 to 4 weeks | 4 to 8 weeks | Quarters |
| ChatGPT base model | Not applicable | Not applicable | 6 to 18 months |
| Claude with web | 1 to 4 weeks | 4 to 8 weeks | Quarters |
| Gemini | 2 to 4 weeks | 4 to 8 weeks | Quarters |
The 2 to 4 week range for Google AI Overviews matches the broader pattern: meaningful AI Overview impact from new pages typically shows within two to four weeks of indexing, per ecosystem reporting on freshness signals. The slower base-model timeline reflects the historical 6 to 18 month gap between training cutoff and release date that OpenAI, Anthropic, and Google have all run on. The lesson: do not plan a launch around the expectation that ChatGPT "just knows" about you. Plan around what retrieval can see.
Before launch: prep work that earns early citations
The four weeks before launch decide whether retrieval works on day one. The goal is to have a category-fit corpus already indexed when AI models start fanning out on your launch-day queries.
Five things must exist before you announce:
- A product page with a clear category claim in the first 150 words ("X is a [category] for [audience] that does [job]"). The category line is what AI extracts when answering "what is the best [category] for [audience]" queries.
- A comparison page that names your product against the two or three incumbents readers will reach for. Comparison content is disproportionately cited because AI is often answering comparative sub-queries.
- A product-docs page with at least one FAQ block. Product documentation outranks marketing pages for evidentiary AI citations, which is why the help-center playbook treats docs as a citation surface, not a support deliverable.
- A review-platform listing on G2 or Capterra, even if reviews come later. The category page is what AI retrieves, not the individual product profile.
- Schema markup on the product, comparison, and docs pages: Product, FAQ, Organization. AI Overviews lean on structured data when picking which page to cite.
If any of these is missing on launch day, you start the citation curve a week behind.
Launch week: the five citation surfaces to prioritize
Launch week is not for novelty content. It is for putting your product into the retrieval slots competitors already occupy.
Earned media. Three to five independent articles from outlets your category readers actually read. Not a wire-service press release: AI models discount syndication and Wikipedia rejects press releases as primary sources, per Wikipedia's notability guidance for organizations. Independent coverage is what builds notability and what AI uses as a quality signal.
Review platforms. Get to ten G2 reviews in launch week. The G2 citation research shows tools with at least 10 reviews and category-page presence get citation lift; under that threshold AI treats the tool as insufficiently validated to recommend with confidence. Twenty-five reviews moves you onto the category ranking page that AI actually cites.
Community presence. One genuine Reddit or community thread where your product is discussed by name in a buyer question. Reddit citation share in AI answers has grown 73% across categories from October 2025 to January 2026, per the AI platform citation source index 2026. Google AI Overviews now display direct Reddit quotes as community perspectives, which means the thread itself can become the citation.
Comparison content on third-party sites. A category roundup that includes you ("best [category] tools in 2026") on a domain AI already cites in your space. You earn this through outreach, not advertorial.
Owned hub content. Two to three deep pieces on your domain that answer the high-fan-out sub-queries an AI would issue for your category. Examples: a how-to, a buyer's guide, a real customer case. These are the retrieval anchors you control.
If you want to see which sources shape AI answers about your brand, run a free brand check — it takes a minute.
What to publish on your own domain
Your owned content has one job in launch week: be the canonical answer to the sub-queries AI fans out to. A reader who asks ChatGPT "what is the best [category] for [audience]" causes the model to issue three to five atomic sub-queries. Your domain needs to be the strongest result for at least one of them.
The mistake most launches make is publishing one omnibus "introducing [product]" post and expecting it to do six jobs. AI fan-out rewards posts that answer one atomic question completely, not posts that bundle definitions, features, comparisons, and quotes into a single page.
Map the fan-out before you write. List the user query you want to win, then list the atomic sub-queries an AI would decompose it into. Each sub-query needs a dedicated page or section, structured so a retrieval pass can extract a clean passage. The answer capsule technique covers the structural pattern: a 40 to 80 word direct answer in the first 150 words of every page, written as a self-contained passage an AI can lift verbatim.
Sections should run 120 to 200 words. Tables earn 2.5× more AI citations than prose-only blocks, per ecosystem research compiled in content structure for AI citation. Use them where comparison is the point.
Week 1 to 4: seed retrieval where AI is already looking
The next four weeks are about putting your product into retrieval sets across the domains AI actually cites for your category. Use Parse or a similar tool to inspect which domains are cited most for your category prompts, then prioritize that list.
Some categories rely heavily on review aggregators (B2B SaaS). Some rely on community (developer tools, consumer apps). Some rely on industry trade press (regulated industries, enterprise). The mix differs, but the principle is the same: AI cites a small number of domains repeatedly. Your job is to get on those domains, by name, with a buyer-relevant claim.
Tactics that move citation faster:
- Reach out to category roundups. Search for "best [category] 2026" results and offer the author a structured pitch with proof points. The roundup becomes a citation feeder.
- Publish a comparison page that names competitors. Do not hedge. AI extracts head-to-head claims and reuses them in answers.
- Pitch one independent analyst piece. Trade publications and analyst notes carry disproportionate weight in regulated and enterprise categories.
- Recruit five customer case studies. Even short ones. Named, dated, with a specific outcome. These are the retrieval evidence for "is X any good" sub-queries.
Track every new article that mentions your product against AI citation prompts. If a piece is mentioned in an AI answer within ten days of going live, that domain is in the retrieval set. Invest more there.
Measurement: signals that the launch worked
Three signals tell you whether AI visibility for the launch is on track. None is a "ranking" in the SEO sense. AI visibility is a portfolio, not a position.
The first signal is citation share on a tracked prompt set. Build a list of 20 to 30 prompts a buyer in your category would actually issue. Re-run them weekly across ChatGPT, Perplexity, and Google AI Overviews. Track how often your product appears, in what position, with which citation. Tools like Parse run this automatically; the prompt set construction guide covers how to pick the right prompts.
The second signal is citation source breadth. A new product cited by Perplexity but not by ChatGPT browsing means your retrieval signal is too narrow. AI models cite different domains for the same query, by design. The which-domains-cited-most breakdown, backed by Parse's data on the most-cited source domains in AI answers, is the baseline you are pushing against.
The third signal is referral traffic from AI sources. Set up a custom channel in GA4 to identify AI referrals (chatgpt.com, perplexity.ai, gemini.google.com, claude.ai, copilot.microsoft.com). Traffic is sparse but high-intent. The setup steps are in our GA4 AI traffic guide.
If you see Perplexity citations within two weeks, Google AI Overview citations within four weeks, and AI referral traffic by week six, the launch worked. If two of the three are flat by week eight, retrieval seeding is the problem.
What not to do at launch
A short list of patterns that look productive but reliably underperform.
- Mass wire-service press release distribution
- One omnibus "introducing [product]" post on the blog
- Pay-to-play category awards
- AI-generated comparison pages targeting every adjacent keyword
- Heavy investment in the product page meta description
- Buying placements on listicles that read like ad inventory
- Three independent journalist relationships and pitched stories
- Five focused pages, each answering one atomic sub-query
- Customer-written G2 reviews with use-case detail
- Two or three deeply structured comparison pages naming real competitors
- FAQ schema on docs and comparison pages
- One genuine Reddit thread where buyers ask and your team is named
Manufactured signals get filtered. AI retrieval increasingly discounts content that looks coordinated: identical phrasing across many domains, syndication patterns, and review burst patterns. The reason brands with steady, varied, named-source coverage outperform brands with bigger PR budgets is that retrieval treats the second as noise.
How to defend a strong launch
A strong launch decays without follow-up. Citation freshness data shows pages updated within 30 days are cited at 3.2× the rate of older content. What used to decay over 12 to 18 months now declines in 3 to 6 months for competitive topics, per content freshness research. Parse's data on how long an AI citation lasts quantifies that churn.
Three defensive moves in the 30 to 90 day window after launch:
- Refresh the canonical launch page monthly. Add a "what is new in [month]" section. Re-date when content materially changes (not when it cosmetically changes; AI evaluates substance).
- Pitch a follow-up story to the journalists who covered the launch. A 90-day update with numbers is easier to place than a launch announcement.
- Convert the launch into a recurring data asset. Publish a quarterly category benchmark, a usage snapshot, or an industry survey under your name. Brands with proprietary recurring data anchor AI citations in a way one-time launches cannot.
For teams running a launch alongside an existing AI visibility program, see the first 90 days operating plan for how launch-week tactics roll into a steady-state monitoring cadence.
FAQ
How long does it take for ChatGPT to know about a new product?
ChatGPT's base model knows about products that were in its training data, which currently lags the calendar by 6 to 18 months. A product launched after the August 2025 cutoff is unknown to the base model until the next training round. ChatGPT browsing (web search) can surface a new product within 1 to 4 weeks if independent coverage is live, which is the only practical path until the next checkpoint.
Which AI platform is fastest to cite a new product?
Perplexity is consistently fastest. Sonar's index processes tens of thousands of update requests per second, and Perplexity's freshness signals reward newly published authoritative pages. A new product with a category-fit landing page and three independent press articles can earn Perplexity citations within 1 to 5 days. Google AI Overviews typically follows within 2 to 4 weeks. ChatGPT browsing is similar.
Do press releases help AI cite my product?
Indirectly. Wire-service press releases themselves are discounted by both AI retrieval and Wikipedia notability rules, which treat them as primary, non-independent sources. What helps is the independent coverage a press release can generate. Three independent articles in outlets your category readers know are worth more than 100 syndicated wire pickups for AI citation purposes.
How many G2 reviews do I need before AI cites my product?
A working minimum is 10 reviews on G2 (and 5 on Capterra) for AI to treat the product as validated enough to recommend. The bigger lift comes at 25 reviews, where the G2 category ranking page starts reliably including the product. The ranking page is the AI citation surface, not the individual profile page. Review velocity also matters: 80 well-phrased recent reviews can outperform 400 generic older ones.
Should I optimize for one AI platform or all of them at launch?
Optimize for retrieval signals that apply across all major platforms: a clear category-fit landing page, schema markup, independent press, review platforms, and one community thread. Platform-specific optimization (Bing for ChatGPT, the Google index for AI Overviews, Sonar for Perplexity) helps at the margin, but the same 5 to 8 fundamentals carry across all of them. Spend most of launch week on signals that compound.