<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alex</title>
    <description>The latest articles on DEV Community by Alex (@413x).</description>
    <link>https://dev.to/413x</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4099599%2Fb5f7e9c0-f759-4920-9054-48d4c470aa6d.png</url>
      <title>DEV Community: Alex</title>
      <link>https://dev.to/413x</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/413x"/>
    <language>en</language>
    <item>
      <title>Google cites new pages in a day. ChatGPT takes weeks.</title>
      <dc:creator>Alex</dc:creator>
      <pubDate>Mon, 31 Aug 2026 15:46:53 +0000</pubDate>
      <link>https://dev.to/413x/google-cites-new-pages-in-a-day-chatgpt-takes-weeks-213f</link>
      <guid>https://dev.to/413x/google-cites-new-pages-in-a-day-chatgpt-takes-weeks-213f</guid>
      <description>&lt;p&gt;Every guide to generative engine optimization explains what to do. Almost none of them say when it pays off, which is the only question anyone actually asks before committing budget to it.&lt;/p&gt;

&lt;p&gt;That gap existed for a good reason. Answering it properly needs something nobody had bothered to build: a set of pages published at a known moment and then checked against several answer engines every single day afterwards. Without that, every claimed timeline was somebody's impression of their own client work, and impressions are exactly the wrong instrument for a system that regenerates its answers every couple of days.&lt;/p&gt;

&lt;p&gt;The measurement now exists. Eighty-one newly published pages on a single domain, queried daily for thirty days across Google's AI Mode and ChatGPT search. Here is what it found.&lt;/p&gt;

&lt;h2&gt;
  
  
  Google moves in days. ChatGPT moves in weeks.
&lt;/h2&gt;

&lt;p&gt;The gap at the start is larger than most people expect. Within 24 hours of publishing, 36% of the test pages were already being cited somewhere in Google AI Mode. ChatGPT search had picked up 10% in the same window, more than three times slower off the line. By day seven, Google was at 56% and ChatGPT at 17%.&lt;/p&gt;

&lt;p&gt;Then the curves change character, and this is the part that matters. Google's coverage fluctuated week to week, rising toward a peak of 59% and falling back from it repeatedly. ChatGPT's climbed steadily and did not give ground: 35% at two weeks, 42% at thirty days. Google is fast and noisy. ChatGPT is slow and cumulative.&lt;/p&gt;

&lt;p&gt;That has a direct consequence for how you report on this work, and it is where people get burned. A project reviewed at four weeks looks like a Google success and a ChatGPT failure, and both readings are artefacts of the review date rather than facts about the work. The correct checkpoint is somewhere past six weeks, and the correct framing is two separate curves rather than an average that describes neither.&lt;/p&gt;

&lt;p&gt;Perplexity sits outside the comparison for a structural reason. A significant share of its crawling is triggered by a user's question rather than by a schedule, so on a narrow, specific prompt it can be the fastest of the three, and on a broad one it can lag both.&lt;/p&gt;

&lt;h2&gt;
  
  
  The clock starts at crawl, not at publish
&lt;/h2&gt;

&lt;p&gt;The first week is not a content problem, and treating it as one wastes it. OpenAI runs three separate bots and the distinction matters: OAI-SearchBot surfaces sites in ChatGPT's search features, GPTBot crawls for model training, and both obey robots.txt, while ChatGPT-User fetches a page live because a person asked a question and is explicitly not bound by the same rules. Perplexity splits the same way, with PerplexityBot building the index under robots.txt and Perplexity-User fetching live during a question.&lt;/p&gt;

&lt;p&gt;Both operators quote roughly the same latency on the control side, about 24 hours from a robots.txt update for their systems to adjust. That is a small number with a sharp edge, because an accidental block costs a day to undo after somebody notices. And the most common cause is not robots.txt at all. It is a bot-protection rule in a CDN that nobody remembers switching on.&lt;/p&gt;

&lt;p&gt;Google is a different case entirely, and simpler. Its own documentation states there are no additional requirements to appear in AI Overviews or AI Mode and no special markup necessary, but that to be used as a supporting link a page must be indexed and eligible to be shown in Google Search with a snippet. The AI clock and the classic indexing clock are the same clock. There is no separate AI index to get into, and if the page is not indexed, no amount of GEO work reaches it.&lt;/p&gt;

&lt;p&gt;So before blaming your content, check whether the crawlers are in your server logs at all, whether a firewall rule is turning them away, whether the page is indexed, and whether it renders anything useful without JavaScript. A crawler that receives an empty shell has technically fetched you and learned nothing. Those four cover most cases of "we are not being cited anywhere".&lt;/p&gt;

&lt;h2&gt;
  
  
  The ceiling nobody quotes
&lt;/h2&gt;

&lt;p&gt;The number worth carrying out of this is not a speed, it is a limit. Over a full month, Google AI Mode peaked at 59% of the test pages and ChatGPT search reached 42%. That was on a domain with strong established authority publishing squarely inside its own subject area. Even under those conditions, roughly half of everything published was never cited anywhere.&lt;/p&gt;

&lt;p&gt;This is the honest correction to how GEO is usually sold. The pitch implies that structuring content correctly makes it citable. The data says structuring content correctly makes it eligible, and selection is a separate, competitive step you do not control.&lt;/p&gt;

&lt;p&gt;Plan on that basis and the economics stay sane. A page that fails to get cited is not a failed page, it is the expected outcome for about half of them, and the ones that do get cited tend to keep the citation. The practical consequence is that publishing a small number of genuinely specific answer pages beats publishing many broad ones, because the ceiling is per-page and broad pages lose to bigger entities every time.&lt;/p&gt;

&lt;h2&gt;
  
  
  A single check tells you almost nothing
&lt;/h2&gt;

&lt;p&gt;This is the least intuitive finding in the area and it should change how you measure. Ahrefs tracked more than 43,000 keywords with at least sixteen recorded AI Overviews each and found an average persistence of 2.15 days, meaning an AI Overview has roughly a 70% chance of being different from one observation to the next. More usefully, only 54.5% of the cited URLs overlap between consecutive runs of the same query. Close to half the source list is replaced every time.&lt;/p&gt;

&lt;p&gt;What does not change is the meaning. The same query re-run produces answers with an average cosine similarity of 0.95, and 54% of the named entities stay put. The system is confident about what it thinks and casual about who it credits, which means a citation appearing or disappearing on any given day carries far less signal than it feels like it does.&lt;/p&gt;

&lt;p&gt;The rule follows immediately. Never measure AI visibility with a single check. Run a fixed prompt list at least ten times across several days and report the share of runs in which you appear, and freeze that list early, because changing it mid-measurement destroys the comparison and is how most in-house tracking quietly dies. A binary "are we cited" screenshot is roughly a coin flip, and I have watched more than one agency relationship turn on one taken at the wrong moment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ranking still helps, but a lot less than it did
&lt;/h2&gt;

&lt;p&gt;For most of the AI-search era the reassuring answer to "how do we get cited" was "rank well, the rest follows". In July 2025 that held up, when Ahrefs analysed 1.9 million citations from a million AI Overviews and found 76.1% of cited pages ranked in Google's top 10.&lt;/p&gt;

&lt;p&gt;By March 2026 the same analysis over 863,000 SERPs and four million AI Overview URLs put the top-10 share at 37.9%, with 31.0% coming from pages beyond the first hundred results entirely. Ahrefs attribute the shift to Google changing the model behind AI Overviews in January 2026 and expanding its query fan-out more aggressively, pulling sources from related searches rather than only the one the user typed.&lt;/p&gt;

&lt;p&gt;Two things follow, and they pull in opposite directions on purpose. Ranking is no longer a reliable route to citation, so a strong SEO position is not the guarantee it was. But not ranking is no longer disqualifying either, and roughly a third of citations now coming from pages nobody would find in a normal search is the first genuinely new opportunity this field has produced for smaller sites.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do while you wait
&lt;/h2&gt;

&lt;p&gt;The waiting period is not idle time, and the work that pays during it is unglamorous. Fix what the crawlers see: server-rendered content, clean headings, a direct answer near the top of each section rather than three paragraphs in, and structured data that states plainly who you are and what you sell. None of that is AI-specific. It is the same technical foundation classic search rewards, which is why the two disciplines are additive rather than alternatives.&lt;/p&gt;

&lt;p&gt;Then work on the half you cannot edit. Answer engines cross-reference sources rather than trusting one, so the same facts about your business appearing consistently across directories, profiles and comparisons does more for attribution than another rewrite of your homepage. A business described three different ways in three places gets attributed less confidently than one described identically everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  The caveats, stated plainly
&lt;/h2&gt;

&lt;p&gt;The day-by-day figures come from one controlled test on one domain with strong existing authority. Treat them as a best case rather than an average, because a newer or weaker site should expect the same shape stretched over a longer axis and a lower ceiling.&lt;/p&gt;

&lt;p&gt;There is also no submission form, no priority queue and no paid inclusion route anywhere across these engines. The only levers are being crawlable by the right agents, being indexed where indexing is the gate, and being a page worth selecting over the alternatives. Anyone offering to fast-track you is selling something that does not exist.&lt;/p&gt;

&lt;p&gt;And the honest one: Google changed the model behind AI Overviews in January 2026 and the ranking-to-citation relationship roughly halved within months. Any timeline in this field, including this one, describes a moving system rather than a law. What has stayed stable across every change so far is only the shape. Google is fast and volatile, ChatGPT is slow and cumulative, and about half of what you publish is never cited at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the full version
&lt;/h2&gt;

&lt;p&gt;This is the condensed version. The full article walks the first six months week by week, covers what each engine specifically needs before it can cite you, and answers the parts I skipped here, including whether you should be blocking AI crawlers at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://levelui.com/resources/how-long-until-ai-cites-you?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=ai-citation-timeline" rel="noopener noreferrer"&gt;How long until ChatGPT and Perplexity actually cite you?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;p&gt;The citation timings come from Semrush's &lt;a href="https://www.semrush.com/blog/how-fast-do-ai-search-platforms-cite-new-content/" rel="noopener noreferrer"&gt;controlled test of 81 newly published pages&lt;/a&gt;. The volatility figures are from Ahrefs on &lt;a href="https://ahrefs.com/blog/ai-overview-change/" rel="noopener noreferrer"&gt;how often AI Overviews change&lt;/a&gt;, and the ranking comparison from their &lt;a href="https://ahrefs.com/blog/search-rankings-ai-citations/" rel="noopener noreferrer"&gt;July 2025 analysis&lt;/a&gt; and its &lt;a href="https://ahrefs.com/blog/ai-overview-citations-top-10/" rel="noopener noreferrer"&gt;March 2026 re-run&lt;/a&gt;. Crawler behaviour is documented by &lt;a href="https://developers.openai.com/api/docs/bots" rel="noopener noreferrer"&gt;OpenAI&lt;/a&gt;, &lt;a href="https://docs.perplexity.ai/docs/resources/perplexity-crawlers" rel="noopener noreferrer"&gt;Perplexity&lt;/a&gt; and &lt;a href="https://developers.google.com/search/docs/appearance/ai-features" rel="noopener noreferrer"&gt;Google&lt;/a&gt; directly. The measurement advice and the read on what all this means for a smaller site are mine.&lt;/p&gt;

&lt;p&gt;If you have been tracking your own citation timings I would genuinely like to hear how they compare, particularly from anyone on a newer domain, since that is exactly the case the published study does not cover.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>analytics</category>
      <category>google</category>
      <category>seo</category>
    </item>
  </channel>
</rss>
