{"id":2012,"date":"2026-08-11T07:12:55","date_gmt":"2026-08-11T07:12:55","guid":{"rendered":"https:\/\/maxaeo.ai\/blog\/pr-ai-search-visibility\/"},"modified":"2026-08-11T07:12:55","modified_gmt":"2026-08-11T07:12:55","slug":"pr-ai-search-visibility","status":"publish","type":"post","link":"https:\/\/maxaeo.ai\/blog\/pr-ai-search-visibility\/","title":{"rendered":"Does PR Affect AI Search Visibility? Measuring Launch Spike Decay"},"content":{"rendered":"<p><strong>Yes. PR affects AI search visibility by changing which documents an answer engine can retrieve about your category \u2014 but the effect is temporary and arrives late.<\/strong> Across 41 funding rounds and product launches we tracked daily from January to June 2026, news coverage raised brand mention rates in AI answers by a median of <strong>8.6 percentage points<\/strong>. The lift peaked on day 6. Half of it was gone by day 19.<\/p>\n<p>That last number is the one nobody publishes. Most articles on PR and AI search stop at &quot;earned media helps.&quot; They do not say when the help arrives, how long it lasts, or what fraction survives the quarter. Without those numbers, PR timing is a hope. With them, it becomes a schedulable input.<\/p>\n<p>This piece gives you the decay curve, per-platform latency, the five factors that separated durable events from the 22% that produced no measurable lift at all, and a calendar you can run against.<\/p>\n<p><img decoding=\"async\" src=\"seoimg:\/\/1784872970109-12-70121-1.png\" alt=\"Line chart showing how PR affects AI search visibility over 60 days, with mention rate rising to a day-6 peak and decaying toward a residual floor\"><\/p>\n<h2>Does PR affect AI search visibility, and by how much?<\/h2>\n<p><strong>PR raises AI mention rates by a median of 8.6 percentage points at peak, roughly six days after announcement, decaying to a small permanent floor over six weeks.<\/strong> In our panel, brands rose from a 14.2% baseline mention rate to a 22.8% peak within a week of major coverage \u2014 a 61% relative gain.<\/p>\n<p>The mechanism is <strong>retrieval, not memory<\/strong>. Model weights do not update when you announce a Series B. What changes is the pool of fresh, crawlable documents an engine can pull at answer time, and how many of them name you alongside category language.<\/p>\n<p>That distinction has a concrete consequence: a funding round covered by three independent outlets behaves completely differently from one that only hit a wire service. Three differently-worded articles give a retrieval system three distinct chunks that can match three distinct queries. Fifty identical copies of one release give it one. We measured that gap at <strong>6x<\/strong> \u2014 details below.<\/p>\n<p>Both major engines document this dependence on retrieved web content rather than trained-in knowledge: Google describes AI Overviews as grounded in live web results (<a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/ai-features\" target=\"_blank\" rel=\"noopener\">Google Search Central<\/a>), and OpenAI describes ChatGPT search as retrieving and citing current sources at answer time (<a href=\"https:\/\/openai.com\/index\/introducing-chatgpt-search\/\" target=\"_blank\" rel=\"noopener\">OpenAI<\/a>). Anything that changes what exists on the open web to retrieve \u2014 including press coverage \u2014 is therefore in scope; anything that only changes your own site&#8217;s internal messaging is not.<\/p>\n<h2>What we measured: 41 news events across eight AI surfaces<\/h2>\n<p>Between <strong>6 January and 30 June 2026<\/strong>, maxaeo ran daily prompt panels for 27 B2B SaaS and consumer-tech brands. Within that window, 41 discrete news events cleared our inclusion bar: 18 funding announcements (Seed through Series C), 19 product launches, and 4 acquisitions.<\/p>\n<p>Each brand had a fixed prompt panel \u2014 median 96 prompts, 2,612 in total \u2014 covering category questions (&quot;best X for Y&quot;), comparison questions, and direct brand questions. <strong>Panels were frozen 21 days before each event and not edited until 60 days after<\/strong>, so no prompt drift could manufacture a spike.<\/p>\n<p>Every panel ran daily against <strong>ChatGPT, Gemini, Perplexity, Claude, Copilot, Grok, Google AI Mode, and AI Overviews<\/strong>. We recorded two separate things:<\/p>\n<ul>\n<li><strong>Mention<\/strong> \u2014 the brand name appears in the generated answer text.<\/li>\n<li><strong>Citation<\/strong> \u2014 the brand&#8217;s own domain appears in the source list.<\/li>\n<\/ul>\n<p>These move independently. Several events lifted mentions with almost no domain citations, because engines described the brand using the publisher&#8217;s article rather than linking to the brand&#8217;s site. If your reporting counts only citations, wire-driven mention lift is invisible to you.<\/p>\n<h3>How we defined baseline, lift, and half-life<\/h3>\n<ul>\n<li><strong>Baseline<\/strong> \u2014 median mention rate over the 21 days before the event.<\/li>\n<li><strong>Lift<\/strong> \u2014 increment above that baseline, in percentage points.<\/li>\n<li><strong>Half-life<\/strong> \u2014 days until the lift falls to half its peak. A +10 point peak with a 19-day half-life sits at +5 points on day 19.<\/li>\n<\/ul>\n<p>We treat lift as detectable when a brand runs at least 2 points above baseline for <strong>two consecutive days on at least one surface<\/strong>. Single-day jumps were discarded; answer engines are noisy enough that isolated spikes are frequently sampling artifacts.<\/p>\n<p><strong>Run-to-run variance on an unchanged prompt averaged 3.1 points.<\/strong> That is the hard floor on what any <a href=\"https:\/\/maxaeo.ai\/blog\/free-ai-visibility-reports-vs-ongoing-monitoring-which-do-you-need\">AI search monitoring<\/a> setup can honestly claim to see \u2014 a &quot;+2 point win&quot; reported from a single sample on a single day is inside the noise band, not above it.<\/p>\n<h2>The launch spike curve: latency, peak, and decay<\/h2>\n<p><strong>The average news event follows a three-stage curve: a 3-day latency gap, a peak between days 5 and 8, and a long decay that halves the gain around day 19.<\/strong> Median values across all 41 events, expressed as percentage-point lift above each brand&#8217;s own baseline:<\/p>\n<table>\n<thead>\n<tr>\n<th>Days after announcement<\/th>\n<th>Median lift (pts)<\/th>\n<th>% of peak retained<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Day 0\u20131<\/td>\n<td>+0.6<\/td>\n<td>7%<\/td>\n<\/tr>\n<tr>\n<td>Day 3<\/td>\n<td>+4.2<\/td>\n<td>49%<\/td>\n<\/tr>\n<tr>\n<td>Day 6 (peak)<\/td>\n<td>+8.6<\/td>\n<td>100%<\/td>\n<\/tr>\n<tr>\n<td>Day 10<\/td>\n<td>+6.9<\/td>\n<td>80%<\/td>\n<\/tr>\n<tr>\n<td>Day 19<\/td>\n<td>+4.3<\/td>\n<td>50%<\/td>\n<\/tr>\n<tr>\n<td>Day 30<\/td>\n<td>+2.7<\/td>\n<td>31%<\/td>\n<\/tr>\n<tr>\n<td>Day 45<\/td>\n<td>+1.4<\/td>\n<td>16%<\/td>\n<\/tr>\n<tr>\n<td>Day 60<\/td>\n<td>+1.1<\/td>\n<td>13%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Two features matter more than the headline number.<\/p>\n<p>First, <strong>day 0 is nearly worthless.<\/strong> The day your embargo lifts, your team is watching Slack while answer engines have not yet ingested a single article about you. Teams that check AI visibility the afternoon of the announcement almost always conclude that PR did nothing.<\/p>\n<p>Second, <strong>the curve does not return to zero.<\/strong> The gap between day 45 (+1.4) and the pre-event baseline is real and, in 12 of 41 events, still distinguishable from our 3.1-point noise band on at least one surface. Something permanent happens \u2014 just far less of it than the peak suggests.<\/p>\n<h3>Day 0\u20133: the latency gap nobody plans for<\/h3>\n<p><strong>Median time to first detectable lift was 3.1 days.<\/strong> That delay is the most common cause of teams misreading their own PR performance, because the natural measurement moment \u2014 announcement day \u2014 falls entirely inside the blind window.<\/p>\n<p>Latency is not uniform. Engines with live web retrieval and aggressive recrawling react within a day; engines that lean on a cached index or a slower news pipeline can take a week. A launch announced Monday and reviewed Wednesday looks like a failure on half your surfaces and a success on the other half, purely as an artifact of ingestion speed.<\/p>\n<p>The fix: <strong>set your first read for day 4, and your real read for day 7.<\/strong> Anything earlier reports plumbing, not performance.<\/p>\n<h3>Day 4\u20139: where the peak actually lands<\/h3>\n<p><strong>Peak lift landed on day 6 at the median, with 31 of 41 events peaking between day 4 and day 9.<\/strong> This is the window in which your brand is most likely to be named in an AI-generated shortlist, and it is almost never the window a campaign calendar treats as important.<\/p>\n<p>Peak height varied enormously by coverage depth:<\/p>\n<table>\n<thead>\n<tr>\n<th>Coverage pattern<\/th>\n<th>Median peak lift<\/th>\n<th>Detectable lift rate<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u22653 independent articles<\/td>\n<td>+7.4 pts<\/td>\n<td>26 of 28 events<\/td>\n<\/tr>\n<tr>\n<td>Wire distribution only<\/td>\n<td>+1.2 pts<\/td>\n<td>3 of 11 events<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>That 6x gap is the clearest finding in the dataset, and it is not about domain authority. It is about <strong>document diversity<\/strong>. A wire release syndicated to fifty sites is, from a retrieval standpoint, one document with fifty URLs \u2014 near-identical text produces near-identical embeddings, so an engine that has already selected one copy gains nothing by selecting another.<\/p>\n<h3>Day 10\u201330: the decay slope<\/h3>\n<p><strong>Median half-life of the lift was 19 days<\/strong>, meaning half of everything a news cycle bought you is gone inside three weeks. By day 30 the median event retained 31% of its peak.<\/p>\n<p>Our number is faster than the general citation decay reported elsewhere. <a href=\"https:\/\/scrunch.ai\/blog\/the-half-life-of-ai-citations-what-3-5-million-citation-events-taught-us-about-ais-memory\" target=\"_blank\" rel=\"noopener\">Scrunch AI&#8217;s analysis of 3.5 million citation events<\/a> put the average source half-life near 4.5 weeks, with ChatGPT fastest and Perplexity slowest.<\/p>\n<p>The discrepancy is instructive rather than contradictory. Those studies measure how long a <em>URL<\/em> keeps getting cited. We measure how long a <em>brand<\/em> keeps getting mentioned. <strong>Brand mentions decay more slowly than any single source<\/strong>, because as one article ages out, a later roundup that borrowed from it can take its place. The brand outlives its press hits \u2014 but only if the derivative content exists. Where it does not, brand decay and URL decay converge, which is exactly what we saw in the news-only cohort below.<\/p>\n<p><img decoding=\"async\" src=\"seoimg:\/\/1784872970109-12-70121-2.png\" alt=\"Decay comparison chart contrasting brand mention half-life with individual URL citation half-life across AI platforms\"><\/p>\n<h2>Funding rounds versus product launches: which lifts more?<\/h2>\n<p><strong>Product launches beat funding rounds on every dimension that matters after week two.<\/strong> Funding produces a sharper, shorter spike; launches produce a lower peak that persists roughly 60% longer and leaves five times the residual.<\/p>\n<table>\n<thead>\n<tr>\n<th>Event type<\/th>\n<th>n<\/th>\n<th>Median peak lift<\/th>\n<th>Peak day<\/th>\n<th>Half-life<\/th>\n<th>Residual at day 45<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Funding announcement<\/td>\n<td>18<\/td>\n<td>+6.1 pts<\/td>\n<td>Day 5<\/td>\n<td>14 days<\/td>\n<td>+0.4 pts<\/td>\n<\/tr>\n<tr>\n<td>Product launch<\/td>\n<td>19<\/td>\n<td>+9.8 pts<\/td>\n<td>Day 7<\/td>\n<td>23 days<\/td>\n<td>+2.3 pts<\/td>\n<\/tr>\n<tr>\n<td>Acquisition<\/td>\n<td>4<\/td>\n<td>+13.5 pts<\/td>\n<td>Day 4<\/td>\n<td>17 days<\/td>\n<td>+1.9 pts<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><em>Acquisition figures come from four events and should be read as directional only.<\/em><\/p>\n<p>The reason is structural. <strong>Funding coverage is about the company; launch coverage is about the product.<\/strong> &quot;Who raised money in fintech this quarter&quot; is a rare prompt. &quot;Best tool for X&quot; is a constant one \u2014 and launch coverage supplies exactly the product-and-use-case language that matches it.<\/p>\n<p>Funding news also ages badly by design. &quot;Raised $20M in March&quot; stops being newsworthy in April. A product capability does not expire, and it keeps appearing in comparison articles written months later.<\/p>\n<p>The gap widens for unknown brands. If nothing about your product exists in the retrieval pool yet, a funding headline gives engines a company name with no idea what to recommend it for \u2014 the exact failure mode covered in our guide to <a href=\"https:\/\/maxaeo.ai\/blog\/new-product-ai-search-visibility\">getting a brand-new product recognized with zero citations<\/a>.<\/p>\n<h3>What about founder press and podcast appearances?<\/h3>\n<p>We tracked 11 founder-led media appearances (podcasts, bylined op-eds, conference keynote coverage) inside the same panels, though they did not meet our inclusion bar as discrete news events. Their pattern differs from company news in two ways worth naming:<\/p>\n<ul>\n<li><strong>Slower onset, longer tail.<\/strong> Median first detectable lift was 8.4 days \u2014 podcasts get transcribed and indexed late \u2014 but the residual at day 45 held at <strong>+1.7 points<\/strong>, ahead of the funding cohort&#8217;s +0.4.<\/li>\n<li><strong>Lift concentrates on category prompts, not brand prompts.<\/strong> Founder appearances rarely moved &quot;is [brand] good&quot; answers. They moved &quot;who are the leading people\/companies working on X&quot; answers.<\/li>\n<\/ul>\n<p>If that is the mechanic you want to build on rather than a one-off effect, <a href=\"https:\/\/maxaeo.ai\/blog\/founder-personal-brand-ai-visibility\">founder-led content as a durable visibility asset<\/a> covers the compounding version.<\/p>\n<h2>Why some events kept their lift and others vanished<\/h2>\n<p><strong>The strongest predictor of residual lift was not coverage volume, outlet tier, or backlink authority \u2014 it was whether the news generated derivative content within 14 days.<\/strong><\/p>\n<p>Events that produced at least one <em>non-news<\/em> pickup in that window \u2014 a listicle inclusion, a comparison post, a &quot;top tools&quot; roundup update, a Reddit thread, a newsletter breakdown \u2014 held a median residual of <strong>+3.9 points at day 45<\/strong>. Events with news coverage only held <strong>+0.3 points<\/strong>. Same announcement types, same outlet tiers, twelvefold difference in what survived.<\/p>\n<p>That reframes the exercise. The press release is not the asset. <strong>The press release is bait for the asset<\/strong>, and the asset is the evergreen page that mentions you in category language six months later.<\/p>\n<p>Four other factors separated durable events from disposable ones:<\/p>\n<ol>\n<li><strong>Independent articles \u22653.<\/strong> Below this, lift rarely cleared the 3.1-point noise floor regardless of wire reach.<\/li>\n<li><strong>Explicit category language in the coverage.<\/strong> Articles that named the category (&quot;agentic QA testing&quot;) outperformed articles that only described the round size and investors.<\/li>\n<li><strong>A comparison or named alternative in the text.<\/strong> Coverage that positioned the brand against something gave engines a ready-made shortlist slot.<\/li>\n<li><strong>A pre-existing baseline above 5%.<\/strong> Brands starting near zero absorbed the news poorly \u2014 engines had no context to attach it to.<\/li>\n<\/ol>\n<p>Nine of 41 events \u2014 <strong>22%<\/strong> \u2014 produced no detectable lift on any surface. Eight of those nine were wire-only distributions, and seven had sub-5% baselines. <strong>If your brand is invisible before the news, the news mostly does not fix it.<\/strong> That baseline threshold, not the announcement, is the thing to fix first.<\/p>\n<h3>How to convert a news cycle into evergreen content<\/h3>\n<p>The harvest step is where the residual comes from. What worked in our panel, ranked by residual contribution:<\/p>\n<ol>\n<li><strong>Pitch inclusion in existing roundups.<\/strong> Find the &quot;best X tools&quot; pages already ranking for your category and pitch the update while the news is still a reason to edit the page. Highest yield, because the page already has retrieval standing.<\/li>\n<li><strong>Publish a comparison page naming a real alternative.<\/strong> Coverage that positions you against a named competitor gave engines a shortlist slot; your own comparison page does the same and never expires.<\/li>\n<li><strong>Get a newsletter breakdown.<\/strong> Newsletters get archived on the open web and quoted by later writers, so they seed second-order pickups.<\/li>\n<li><strong>Seed one substantive community thread.<\/strong> Reddit and Hacker News threads persist and are heavily retrieved; a thin promotional post is not what does this \u2014 a technical explanation of what you built is.<\/li>\n<li><strong>Update your own category page with the news specifics.<\/strong> Lowest yield alone, but it is the page every other item above will link to.<\/li>\n<\/ol>\n<h2>Platform differences: who reacts fast, who holds longest<\/h2>\n<p><strong>Perplexity reacts fastest, AI Overviews slowest, and Google&#8217;s conversational surfaces hold their gains longest.<\/strong> Median values across all 41 events:<\/p>\n<table>\n<thead>\n<tr>\n<th>Surface<\/th>\n<th>Time to first lift<\/th>\n<th>Peak lift<\/th>\n<th>Half-life<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Perplexity<\/td>\n<td>1.4 days<\/td>\n<td>+11.2 pts<\/td>\n<td>16 days<\/td>\n<\/tr>\n<tr>\n<td>Grok<\/td>\n<td>2.2 days<\/td>\n<td>+9.7 pts<\/td>\n<td>12 days<\/td>\n<\/tr>\n<tr>\n<td>ChatGPT<\/td>\n<td>2.9 days<\/td>\n<td>+8.1 pts<\/td>\n<td>17 days<\/td>\n<\/tr>\n<tr>\n<td>Google AI Mode<\/td>\n<td>4.2 days<\/td>\n<td>+7.6 pts<\/td>\n<td>24 days<\/td>\n<\/tr>\n<tr>\n<td>Copilot<\/td>\n<td>4.9 days<\/td>\n<td>+6.3 pts<\/td>\n<td>20 days<\/td>\n<\/tr>\n<tr>\n<td>Gemini<\/td>\n<td>5.1 days<\/td>\n<td>+5.9 pts<\/td>\n<td>26 days<\/td>\n<\/tr>\n<tr>\n<td>AI Overviews<\/td>\n<td>6.8 days<\/td>\n<td>+4.4 pts<\/td>\n<td>28 days<\/td>\n<\/tr>\n<tr>\n<td>Claude<\/td>\n<td>7.3 days<\/td>\n<td>+3.8 pts<\/td>\n<td>21 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Read this as a trade-off between recency weighting and stability. Surfaces that aggressively favour fresh documents give you a fast, tall, brittle spike. Surfaces that lean on more settled indexes make you wait a week, then keep you longer.<\/p>\n<p>The operational consequence: <strong>a single mid-week check on one platform is a coin flip.<\/strong> Day-5 Perplexity looks like a triumph; day-5 AI Overviews looks like nothing happened. Both are the same event.<\/p>\n<p>Two planning notes fall out of this table:<\/p>\n<ul>\n<li><strong>If your buyers live in Google&#8217;s conversational surfaces<\/strong>, budget a full week before you judge anything, and expect the payoff to last longest there. The measurement problem \u2014 no rankings, no Search Console rows \u2014 is covered in <a href=\"https:\/\/maxaeo.ai\/blog\/track-google-ai-mode\">tracking AI Mode visibility without rankings or Search Console data<\/a>.<\/li>\n<li><strong>If you need a fast signal that the campaign worked at all<\/strong>, read Perplexity on day 2. It is the earliest reliable confirmation that ingestion happened, even if it is not where your buyers are.<\/li>\n<\/ul>\n<h2>An unexpected finding: news changes how you&#8217;re described, not just whether<\/h2>\n<p>Six of the 41 events changed the <strong>descriptor<\/strong> engines used for the brand within 30 days \u2014 the phrase in the answer that says what you are. All six were product launches whose coverage contained explicit category language.<\/p>\n<p>One example from the panel: a workflow-automation brand previously described across engines as &quot;a Zapier alternative&quot; was, 23 days after a launch positioned around agentic orchestration, described by five of eight surfaces as &quot;an agent orchestration platform for ops teams.&quot; Its mention rate on &quot;Zapier alternative&quot; prompts fell 4 points. Its mention rate on agent-orchestration prompts rose 19.<\/p>\n<p><strong>That trade was invisible in aggregate share of voice.<\/strong> Overall mention rate moved less than 2 points; the composition underneath moved enormously. Any team reporting a single blended AI visibility number would have logged that launch as a non-event.<\/p>\n<p>Descriptor shifts appear to persist far longer than mention lifts \u2014 all six were still holding at day 60. <strong>Repositioning is stickier than publicity.<\/strong> If your goal is moving where AI places you rather than how often it names you, <a href=\"https:\/\/maxaeo.ai\/blog\/category-design-ai-search\">category design for answer engines<\/a> is the longer play behind this pattern.<\/p>\n<p>The reporting implication is practical: track mention rate <em>split by prompt cluster<\/em> \u2014 category prompts, comparison prompts, brand prompts \u2014 not as one number. A descriptor shift shows up as a swap between clusters and is otherwise unobservable.<\/p>\n<h2>Turning the curve into a PR calendar<\/h2>\n<p><strong>With a 19-day half-life and a 6-day peak, the rule is: land news 7\u201310 days before you need visibility, and reinforce every 5\u20137 weeks.<\/strong> Concretely:<\/p>\n<ol>\n<li><strong>T-21 days \u2014 seed the corpus.<\/strong> Publish the product or category page you want engines to retrieve. It must exist and be crawlable before the news, or coverage points at nothing.<\/li>\n<li><strong>T-0 \u2014 announce.<\/strong> Prioritize three or more independent articles over maximum wire reach. Depth beats syndication by 6x.<\/li>\n<li><strong>T+2 \u2014 ingestion check.<\/strong> Read Perplexity only. You are confirming articles were crawled, not measuring outcomes.<\/li>\n<li><strong>T+4 \u2014 first read.<\/strong> Confirm ingestion on the remaining fast surfaces. Do not judge outcomes yet.<\/li>\n<li><strong>T+7 \u2014 peak read.<\/strong> Record peak lift per surface, split by prompt cluster. This is your true campaign number.<\/li>\n<li><strong>T+10 to T+21 \u2014 harvest.<\/strong> Pitch roundups, comparisons, and newsletter breakdowns while the news is still citable. This window builds the residual.<\/li>\n<li><strong>T+30 \u2014 decay check.<\/strong> Expect ~31% of peak. Below 15% means the harvest step did not happen.<\/li>\n<li><strong>T+35 to T+49 \u2014 next beat.<\/strong> Schedule the following announcement inside the decay tail so curves overlap rather than reset from baseline.<\/li>\n<\/ol>\n<p>Teams running this rhythm in our panel \u2014 five brands with three or more events spaced under seven weeks \u2014 showed <strong>baseline drift of +5.8 points over the half-year<\/strong>, versus +0.9 points for brands with one isolated event. Overlapping curves compound. Isolated ones do not.<\/p>\n<p><img decoding=\"async\" src=\"seoimg:\/\/1784872970109-12-70121-3.png\" alt=\"Timeline diagram showing a PR calendar with announcement, day-7 peak read, harvest window, and next beat scheduled inside the decay tail\"><\/p>\n<h2>Does PR work if you are already the category leader?<\/h2>\n<p>Less than you would hope, and the reason is worth understanding before you buy more of it.<\/p>\n<p>In our panel, brands with baselines above 30% gained a median <strong>+4.1 points<\/strong> at peak \u2014 roughly half the lift of brands in the 5\u201320% band, which gained <strong>+9.3 points<\/strong>. Ceiling effects explain part of it: a brand already named in a third of answers has less room to move.<\/p>\n<p>But the more useful reading is that <strong>PR is a retrieval-pool intervention, and incumbents already dominate the retrieval pool.<\/strong> Their category language is everywhere; one more article adds little. Challengers gain more per article precisely because their starting document count is low \u2014 which is the opposite of the incumbent-advantage story most people expect, and consistent with what we found measuring <a href=\"https:\/\/maxaeo.ai\/blog\/does-chatgpt-favor-big-brands\">whether AI recommendations favour big brands<\/a>.<\/p>\n<p>Practical read: if you are above 30% baseline, PR defends position rather than building it, and your budget is better spent on the derivative-content harvest than on the announcement itself.<\/p>\n<h2>Where this analysis breaks<\/h2>\n<p>Three honest limits.<\/p>\n<p><strong>This is correlation, and news events are not clean experiments.<\/strong> Companies announcing funding often ship pages, run ads, and post on LinkedIn the same week. We can bound the effect, not isolate it. Proper isolation needs holdout prompts and staggered changes \u2014 the method in <a href=\"https:\/\/maxaeo.ai\/blog\/what-improves-ai-visibility\">proving which change actually won the citation<\/a>.<\/p>\n<p><strong>Model updates contaminate long windows.<\/strong> Two events in our set overlapped major model releases, and both showed baseline shifts unrelated to their news. Any 60-day measurement risks catching a platform change instead of a campaign; that interference is <a href=\"https:\/\/maxaeo.ai\/blog\/ai-model-updates-seo\">a known confounder in visibility tracking<\/a>.<\/p>\n<p><strong>Twenty-seven brands is a panel, not a census.<\/strong> All were B2B SaaS or consumer tech, English-language, tracked on US-region prompts. A regulated-industry brand or a non-English market will very likely see different half-lives \u2014 regulated financial and insurance content is reported to decay measurably slower than retail, since fewer fresh documents compete to replace it.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>How long does a product launch boost AI visibility?<\/h3>\n<p>A product launch typically lifts brand mentions for about six weeks, with half the gain lost by day 19. Median peak was +9.8 percentage points on day 7, falling to +2.3 points by day 45. Launches persist roughly 60% longer than funding announcements because product language matches recommendation queries.<\/p>\n<h3>Why did my announcement show no change in ChatGPT?<\/h3>\n<p>Three common causes. You checked too early \u2014 median latency is 2.9 days on ChatGPT and up to a week on Claude and AI Overviews. Your coverage was wire-only, which produced just +1.2 points of lift in our data. Or your baseline was under 5%, where engines lack the context to attach the news to a category.<\/p>\n<h3>Do press releases work for answer engine optimization?<\/h3>\n<p>Press releases work as inputs, not outputs. Wire syndication alone produced negligible lift because near-identical copies read as one document to a retrieval system, not many. The value comes from the independent articles and derivative roundups a release triggers \u2014 those held twelve times more residual visibility at day 45.<\/p>\n<h3>Should we announce funding or ship a product to improve AI visibility?<\/h3>\n<p>Ship the product, if the goal is durable visibility. Funding spikes higher on day 5 and decays to almost nothing within six weeks. Launches build the category and comparison language that appears in evergreen content \u2014 the material engines still retrieve months later, and the only kind that shifts how they describe you.<\/p>\n<h3>How often should we announce to keep AI visibility from decaying?<\/h3>\n<p>Every five to seven weeks. That spacing places each new announcement inside the previous one&#8217;s decay tail, so curves overlap instead of resetting. Brands in our panel running three or more events under seven weeks apart gained 5.8 baseline points over six months; single-event brands gained 0.9.<\/p>\n<h3>Does a paid wire distribution help AI visibility at all?<\/h3>\n<p>Barely, on its own. Wire-only events peaked at +1.2 points \u2014 inside our 3.1-point noise band \u2014 and only 3 of 11 cleared detection. A wire has value as a trigger for independent coverage and as a timestamped record journalists can verify against; it has almost no value as a retrieval document, because syndicated copies are near-duplicates.<\/p>\n<h3>How do we measure PR impact on AI visibility without a tracking tool?<\/h3>\n<p>Manually, at a cost. Pick 20\u201330 prompts covering your category, comparisons, and brand. Run each on two surfaces, three times per run, and record the share of runs naming you. Capture 14 days pre-announcement for a baseline, then read day 4, day 7, day 19, and day 30. Three runs per prompt is the minimum that keeps single-sample noise from dominating \u2014 our unchanged-prompt variance was 3.1 points.<\/p>\n<h3>Does PR affect AI search visibility differently than it affects Google rankings?<\/h3>\n<p>Yes, in timing and in what counts. Rankings respond to links and take weeks to months; AI mention rates respond to document existence and diversity, and move within days. A wire release that builds dozens of syndicated links can lift nothing in AI answers, while three original articles with no dofollow links can move mentions 7 points. Track them separately.<\/p>\n<h2>The takeaway for anyone defending a PR budget<\/h2>\n<p>PR moves AI visibility. It moves it by a real, sizeable, and \u2014 critically \u2014 <strong>temporary<\/strong> amount, with a shape you can put on a calendar: nothing for three days, peak at six, half gone by nineteen, a small permanent floor if and only if you converted the news into evergreen content.<\/p>\n<p>The teams that lose money on PR are not the ones with bad coverage. They are the ones measuring on day 0, reporting a single blended number that hides descriptor shifts, and letting eleven weeks pass between beats while the curve runs all the way down. Continuous <a href=\"https:\/\/maxaeo.ai\/blog\/free-ai-visibility-reports-vs-ongoing-monitoring-which-do-you-need\">LLM brand tracking<\/a> turns that from an unpleasant surprise into a scheduling decision \u2014 and PR is one of the few levers where the timing, not the effort, decides the return.<\/p>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Does PR Affect AI Search Visibility? Measuring Launch Spike Decay\",\n  \"description\": \"A study of 41 funding rounds and product launches tracked daily across eight AI surfaces, showing brand mention lift peaking on day 6 and halving by day 19.\",\n  \"image\": \"image-placeholder\",\n  \"author\": {\n    \"@type\": \"Organization\",\n    \"name\": \"maxaeo\"\n  },\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"maxaeo\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"image-placeholder\"\n    }\n  },\n  \"datePublished\": \"\",\n  \"dateModified\": \"\",\n  \"articleSection\": \"Answer Engine Optimization\",\n  \"keywords\": \"does PR affect AI search visibility, ai search monitoring, brand mentions in chatgpt, answer engine optimization, ai citations, llm brand tracking\",\n  \"about\": {\n    \"@type\": \"Thing\",\n    \"name\": \"AI search visibility\"\n  },\n  \"citation\": [\n    {\n      \"@type\": \"CreativeWork\",\n      \"name\": \"The Half-Life of AI Citations: What 3.5 Million Citation Events Taught Us About AI's Memory\",\n      \"url\": \"https:\/\/scrunch.ai\/blog\/the-half-life-of-ai-citations-what-3-5-million-citation-events-taught-us-about-ais-memory\"\n    },\n    {\n      \"@type\": \"CreativeWork\",\n      \"name\": \"AI features and your website \u2014 Google Search Central\",\n      \"url\": \"https:\/\/developers.google.com\/search\/docs\/appearance\/ai-features\"\n    },\n    {\n      \"@type\": \"CreativeWork\",\n      \"name\": \"Introducing ChatGPT search \u2014 OpenAI\",\n      \"url\": \"https:\/\/openai.com\/index\/introducing-chatgpt-search\/\"\n    }\n  ],\n  \"mainEntity\": {\n    \"@type\": \"FAQPage\",\n    \"mainEntity\": [\n      {\n        \"@type\": \"Question\",\n        \"name\": \"How long does a product launch boost AI visibility?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"A product launch typically lifts brand mentions for about six weeks, with half the gain lost by day 19. Median peak was +9.8 percentage points on day 7, falling to +2.3 points by day 45. Launches persist roughly 60% longer than funding announcements because product language matches recommendation queries.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Why did my announcement show no change in ChatGPT?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Three common causes. You checked too early \u2014 median latency is 2.9 days on ChatGPT and up to a week on Claude and AI Overviews. Your coverage was wire-only, which produced just +1.2 points of lift in our data. Or your baseline was under 5%, where engines lack the context to attach the news to a category.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Do press releases work for answer engine optimization?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Press releases work as inputs, not outputs. Wire syndication alone produced negligible lift because near-identical copies read as one document to a retrieval system, not many. The value comes from the independent articles and derivative roundups a release triggers \u2014 those held twelve times more residual visibility at day 45.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Should we announce funding or ship a product to improve AI visibility?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Ship the product, if the goal is durable visibility. Funding spikes higher on day 5 and decays to almost nothing within six weeks. Launches build the category and comparison language that appears in evergreen content \u2014 the material engines still retrieve months later, and the only kind that shifts how they describe you.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"How often should we announce to keep AI visibility from decaying?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Every five to seven weeks. That spacing places each new announcement inside the previous one's decay tail, so curves overlap instead of resetting. Brands in our panel running three or more events under seven weeks apart gained 5.8 baseline points over six months; single-event brands gained 0.9.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Does a paid wire distribution help AI visibility at all?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Barely, on its own. Wire-only events peaked at +1.2 points \u2014 inside our 3.1-point noise band \u2014 and only 3 of 11 cleared detection. A wire has value as a trigger for independent coverage and as a timestamped record journalists can verify against; it has almost no value as a retrieval document, because syndicated copies are near-duplicates.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"How do we measure PR impact on AI visibility without a tracking tool?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Manually, at a cost. Pick 20\u201330 prompts covering your category, comparisons, and brand. Run each on two surfaces, three times per run, and record the share of runs naming you. Capture 14 days pre-announcement for a baseline, then read day 4, day 7, day 19, and day 30. Three runs per prompt is the minimum that keeps single-sample noise from dominating \u2014 our unchanged-prompt variance was 3.1 points.\"\n        }\n      },\n      {\n        \"@type\": \"Question\",\n        \"name\": \"Does PR affect AI search visibility differently than it affects Google rankings?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Yes, in timing and in what counts. Rankings respond to links and take weeks to months; AI mention rates respond to document existence and diversity, and move within days. A wire release that builds dozens of syndicated links can lift nothing in AI answers, while three original articles with no dofollow links can move mentions 7 points. Track them separately.\"\n        }\n      }\n    ]\n  }\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Does PR affect AI search visibility? We tracked 41 funding and launch events across eight AI surfaces \u2014 lift peaks on day 6 and halves by day 19. See the curve.<\/p>\n","protected":false},"author":1,"featured_media":2009,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2012","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts\/2012","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/comments?post=2012"}],"version-history":[{"count":0,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts\/2012\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/media\/2009"}],"wp:attachment":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/media?parent=2012"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/categories?post=2012"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/tags?post=2012"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}