It ranges from a few days to several months. ChatGPT refreshes through web browsing, its training data, and third-party sources at different speeds. Pages that are crawlable, well-sourced, and echoed on high-trust sites get picked up far faster than isolated updates on a slow-to-crawl page.
The honest answer on timing
There is no single number, and anyone who gives you one is guessing. ChatGPT learns about your brand through two very different pipes: its underlying training data, which updates on long cycles measured in months, and live web browsing, which can surface a new page within days. When you ask ChatGPT about a company, it often blends both. So the same brand can feel current in one answer and stale in another.
What you control is how quickly the fast pipe finds and trusts your pages. That is where the real work sits.
Why the two pipes matter
The model's baseline knowledge is frozen at a training cutoff. Anything after that only reaches ChatGPT through browsing or connected sources. This is the same idea we cover in where AI gets its facts: the engine is only as current as the sources it can reach at answer time.
For most brands, browsing is the lever. If your updated page is crawlable, loads cleanly, and states the new fact plainly, a browsing query can reflect it quickly. If the fact only lives in a PDF, a login wall, or a JavaScript blob, the fast pipe never sees it.
What decides which pages get picked up first
Freshness plus trust. Engines prioritize pages that are easy to fetch and corroborated elsewhere. A few things move you up the queue:
- Crawlability — server-rendered HTML, no bot blocks, a clean sitemap.
- Corroboration — the same fact stated on other reputable pages, not just yours.
- Structure — a clear heading and a direct sentence the model can lift.
- Authority — the domain is already referenced by trusted sources.
Miss these and you wait. Fix them and the likelihood of a quick refresh climbs.
The corroboration effect
A single edit on your own site is the weakest possible signal. Engines are cautious about acting on one unverified source. When the same updated fact appears across your site, your profiles, and independent write-ups, the model treats it as settled and reflects it sooner.
This is why a rebrand or new pricing can lag for months if you only changed your homepage. If you are not seeing your update reflected, the first thing to check is why, which we break down in speed to index.
How to speed it up
Publish the change in plain, quotable language on a crawlable page, then get it echoed. Practically:
- State the new fact in one clear sentence near the top of the page.
- Update every profile and directory that repeats the old fact.
- Earn a mention on a source the engine already trusts.
- Submit the page for indexing and confirm it renders without JavaScript.
These same fundamentals are what earn citations in the first place, which is the focus of how to get cited by ChatGPT.
Set expectations, then verify
Plan for a range, not a date. Simple, well-corroborated facts on a crawlable page can appear in browsing answers within days. Changes to the model's baseline knowledge take much longer and are outside your control. Verify by asking ChatGPT directly, with and without browsing, and watching what it returns over a few weeks. If the old fact persists, the problem is almost always corroboration or crawlability, not patience.
What a typical refresh looks like
In practice, updates arrive unevenly rather than all at once. A browsing query might reflect your new page within days, while a plain question that leans on training knowledge still returns the old answer for months. You will often see the change appear, disappear, and settle as different sources are weighed on different runs. That inconsistency is normal and not a sign you did something wrong. It reflects the engine pulling from several sources of varying freshness on each answer. The steadier your corroboration, the sooner those runs converge on the current fact and stop flickering between old and new.
Common reasons updates stall
When an update refuses to land, the cause is almost always mechanical, not mysterious. The usual suspects are worth ruling out one by one:
- The page renders only with JavaScript, so crawlers see an empty shell.
- The old fact still lives on profiles and directories you forgot.
- No trusted third party repeats the new fact, so it stays unverified.
- The page is blocked in robots or buried with no internal links.
Clear these and you remove the friction that keeps the engine anchored to stale information. None of it requires waiting on a training cycle you cannot influence.
Questions people ask
Not through its base model, but its browsing feature can reach new pages within days. When ChatGPT answers, it may combine frozen training knowledge with a live fetch. So a fact can show up quickly in a browsing answer while the model's underlying knowledge stays behind until a much later training cycle you cannot influence.
Usually because the new fact is not crawlable or not corroborated. If it only lives on one page, sits behind JavaScript, or is not repeated on trusted sources, the engine has weak reason to trust it. Update every profile that repeats the old fact and earn one independent mention, then recheck over a few weeks.
State the change in one plain sentence on a crawlable page, update all your profiles and directories, and earn a mention on a source ChatGPT already trusts. Confirm the page renders without JavaScript and submit it for indexing. Corroboration across several sources moves the update far faster than editing your homepage alone.
Want this done for you?
Want to know if AI is recommending you or your competitor? Get an AI visibility audit from Acromatico.
Get a free AI Visibility Audit →