Originally published on Medium ↗
You changed the price. You fixed the wrong date. The editor shows the new version, the page loads fine, and you moved on.
Three days later someone quotes the old number back at you.
If that number is your price, your availability, or the terms of your service, you now have a customer conversation to deal with. The answer they found does not match what you offer.
The instinct is to blame the cache. But which cache? Your website, a visitor’s browser, a search engine, and an AI service can each be working from different information.
Publishing the correction is the part you control. Finding out where the old version is still appearing takes investigation.
What Actually Happens When You Hit Publish
Publishing makes the new version live in your publishing system. What happens beyond that depends on the platform.
Other systems may already have requested, indexed, or stored the page. Updating your website does not necessarily notify them, and a notification does not guarantee an immediate refresh.
Start with two questions: does the public page contain the correction, and where is the old information appearing?
Someone seeing an old price on your website has a different problem from someone seeing it in a Google result or receiving it in an AI answer. Those deserve different checks.
Why Cloudflare Might Not Be Holding Your Old Page
Cloudflare does not cache HTML or JSON by default. Its default caching behaviour is based on file extensions, including common images, stylesheets, scripts, and PDFs.
On that default configuration, an HTML request goes through Cloudflare to your origin without a Cloudflare cache lookup.
That does not prove the response is fresh. Your hosting platform, application, or another service behind Cloudflare may have its own cache.
It also does not mean your whole page updates together. The HTML may contain the correction while a stylesheet, script, or image remains cached. That can leave the words correct and the presentation wrong.
If you have explicitly enabled HTML caching, Cloudflare may hold the page too. The relevant questions then become how long it stays fresh and what happens to that cached copy when you publish.
HTML caching can be useful. It needs an update process that matches the content you are publishing.
What the Response Headers Can Tell You
This command requests the response headers:
curl -sI https://yoursite.com/your-page/
Run it against the page, then against a stylesheet or image used on that page. The results may differ.
For a response passing through Cloudflare, CF-Cache-Status helps establish whether Cloudflare used its cache:
- HIT: Cloudflare found the resource in its cache.
- MISS: The resource was eligible for caching but was not present in that cache when requested.
- DYNAMIC: Cloudflare decided the request was not eligible for caching and made no cache lookup.
- BYPASS: The request was eligible, but the origin response or related conditions prevented caching.
One naming detail causes unnecessary confusion: a Cloudflare rule configured to bypass caching produces DYNAMIC, rather than BYPASS. These distinctions are explained in Cloudflare’s cache response documentation.
The Age header can help too, but it needs context. Cloudflare sets it on certain cached responses, and an origin can also supply an Age value that Cloudflare passes through. It does not prove a Cloudflare cache hit on its own.
These headers describe the response to your request. They do not reconstruct what another visitor received yesterday or tell you what an AI service has stored.
And headers are only part of the check. Request the content itself and confirm that the corrected price, date, or sentence is actually present.
Why Purging Cloudflare Does Not Clear a Visitor’s Browser
Cloudflare’s cache TTL documentation states:
Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser.
A purge reaches Cloudflare’s cache. It does not reach into someone’s browser and remove a copy already stored there.
Opening the page in a private window is a useful comparison. If the correction appears there but not in your normal window, browser storage becomes a suspect. It is not conclusive, because cookies, login state, and other differences can also change what a page displays.
After a purge, check the response and the content again. The useful result is seeing the corrected version delivered, not simply receiving a successful response from the purge request.
Why Google Can Still Show the Old Information
Google says recrawling can take from a few days to a few weeks. Requesting a recrawl does not guarantee immediate inclusion in search results, and submitting the same URL repeatedly does not make it faster.
For a property you manage, Search Console’s URL Inspection tool provides evidence about Google’s last crawl and indexed version. A live test helps check the page’s current accessibility, but it does not mean the indexed version has already changed.
Keep those observations separate:
- The correction is present on the public page.
- Google has crawled the page since the correction.
- The search result you checked reflects the correction.
Each answers a different question.
Google’s old public cached-page feature is gone, which also limits what you can inspect without access to the property’s Search Console.
When an AI Answer Still Uses the Old Price
An AI answer introduces another uncertainty: the wrong number alone does not tell you where it came from.
It might have been retrieved from an older copy of your page. It might still appear on another page, in a PDF, or on a third-party website. The answer might also contain a claim that its cited source does not support.
A citation gives you somewhere to investigate. It does not prove the service fetched the current page when it produced the answer.
An August 2026 report in Search Engine Land, describing research by Olivier de Segonzac of RESONEO, reported behaviour consistent with ChatGPT retaining and reusing fetched page content, including older copies.
That is outside observation of one service. It should not be presented as a confirmed description of every AI system, or used to diagnose every outdated answer as a cache problem.
For a specific incorrect answer, record the question, the answer, any cited URLs, and the date. Check whether the old information remains at those sources. If you repeat the test later, record that result separately.
A corrected answer is useful evidence about that test. It is not proof that the correction has reached every user.
How We Would Investigate It
If an old price keeps appearing, we would start with the exact page, the wrong number, and where someone encountered it.
First, check the public page and its underlying content. Does the visible price agree with the metadata and structured data? Does the old price remain elsewhere on the site, including downloadable documents?
Next, inspect the delivery path. What do the response headers show? With the appropriate access, what can the hosting configuration, publishing system, and Search Console tell us?
If the problem involves an AI answer, inspect the cited sources and record what can actually be reproduced.
The output should be specific: affected URLs, supporting evidence, recommended actions, and an order of work. If the evidence does not establish the cause, the report should say so.
That is the approach we take to scoping an investigation at AI Visibility Studio. The findings give your team something to act on. Fixes and follow-up checks can then be agreed around the problem.
What to Do When a Correction Matters
Start where you have control, then check the places where the old information was reported.
- Verify the public page. Confirm that the correction appears in the delivered content, not just in the editor.
- Look for conflicting copies. Check relevant pages, metadata, structured data, and downloadable files.
- Investigate caching where the evidence points to it. Purge the relevant cache if needed, then verify the delivered content.
- Request a search update where supported. Use Search Console for Google. IndexNow can notify participating search engines, but should not be treated as a universal refresh mechanism.
- Record external observations. Save the search result or AI answer, its sources, and the date.
- Check again and report the limits. State what changed in the checks you performed and what remains unverified.
That last distinction matters. “The website is corrected” and “the old information no longer appears in the answers we tested” are different findings.
FAQ
Why is my website not showing my changes after I publish?
The cause could be browser storage, a hosting or application cache, a CDN cache, or an incomplete publishing update. Compare the public page with the editor, try a private window, and inspect the delivered content and response headers before choosing a fix.
Does Cloudflare cache HTML pages by default?
No. HTML and JSON are not cached by default. Explicit cache rules or other platform configurations can change that behaviour.
Does purging my CDN clear visitors’ browser caches?
No. A CDN purge does not remove copies already stored in visitors’ browsers. Browser behaviour depends on the response headers and how the resource is requested.
How long does Google take to show a correction?
Google says recrawling can take from a few days to a few weeks. A recrawl request does not guarantee an immediate update to search results.
Does an old AI answer prove that my page is cached?
No. The answer could use another source or contain an unsupported claim. Check the cited pages and record what you can reproduce before attributing the problem to caching.
Can an audit guarantee that AI answers will update?
No. An audit can establish what your website publishes, identify inconsistencies and access problems, and document observed search and AI results. It cannot guarantee how an external service will answer future questions.
Most people treat a correction as a publishing action. It is also a propagation problem, and many of the systems holding an older copy belong to someone else.
The useful work is establishing what is correct now, finding inconsistencies you can fix, and recording what still needs checking.
At AI Visibility Studio, our audits connect website problems to the pages and evidence behind them, with a clear order of work. You can take those findings to your own team or ask us to scope the fixes.