Hi All,
I am currently experiencing an issue with my Ghost website where changes made to published content are not consistently appearing on the live website immediately after the content has been updated. The editing process inside the Ghost Admin appears to work normally, and when I open the post or page in the editor, the latest version is clearly saved and published, but the public-facing version of the website sometimes continues displaying the previous content. The problem is not that the content fails to save inside Ghost; the main issue is that the live website does not always reflect the newest published version when I access the page normally. In some cases, if I perform a complete browser refresh, the updated content eventually appears, which makes me suspect that the website is serving an older version of the page somewhere in the request or rendering process. This is becoming difficult to troubleshoot because the behavior is intermittent rather than completely consistent. Some updates become visible immediately, while others appear to remain stuck on the previous version for a period of time before eventually updating. I am trying to understand whether this could be related to Ghost’s frontend rendering, caching behavior, theme implementation, or the way the site is serving published content to visitors.
The problem becomes more noticeable when I make several small changes to the same post or page during development. For example, I may update a paragraph, change an image, modify the title, publish the changes, and then open the public URL expecting to see the new version. Instead, the public page can sometimes show the older version even though the Ghost Admin confirms that the latest changes have already been published. If I return to the editor, the new content is still present, so I know the changes themselves have not disappeared. The confusing part is the difference between what Ghost appears to have stored and what the public website is actually returning to the browser. I have also noticed that opening the URL again after some time can eventually show the correct content without making another change in Ghost. Because of this, I do not want to assume that the problem is simply an unsuccessful publishing action. It seems more like the published content is being served inconsistently somewhere between Ghost and the visitor’s browser. I would like to know whether Ghost has any expected caching or content-refresh behavior that could explain why a newly published version is occasionally delayed on the frontend, particularly when the website is being accessed repeatedly during development.
I have tried basic troubleshooting by publishing the affected content again and checking the public URL in a fresh browser session instead of relying only on the existing browser tab. A full reload can sometimes make the newest version appear, but this does not happen reliably enough for me to consider it a real solution. I have also tried accessing the same page from different browsing sessions to determine whether the problem is specific to one browser session, but the behavior still seems inconsistent. The Ghost Admin side continues to show the correct published content, which makes me hesitant to start changing theme files or server settings without first understanding where the stale version could be coming from. My theme does include the normal Ghost templates for displaying posts and pages, so I am wondering whether something in the theme’s rendering process could be causing an older response or previously rendered content to remain visible after publication. At the same time, I do not want to assume that the theme is responsible because the same content eventually updates without me changing the template. I would therefore appreciate guidance on the correct way to determine whether Ghost itself is returning stale content or whether the problem is happening at the frontend/browser level after Ghost has already generated the correct response.
Another reason I am asking about this is that the issue can make content management difficult when I need to verify changes immediately after publishing. When working on the website, I need to be able to make an edit in Ghost, publish it, open the corresponding public page, and confirm that the live version matches what I just published. When the old version continues appearing, it becomes unclear whether the publication actually completed successfully or whether I am simply viewing an outdated response. I have considered adding cache-busting behavior to the website, but I would prefer not to introduce custom solutions until I know whether Ghost has a recommended mechanism for handling this situation. I am particularly interested in understanding how Ghost determines when a published post or page should be regenerated or served as a new version, and whether the normal publication process should invalidate whatever cached representation is being used by the frontend. If Ghost expects the theme or hosting environment to handle caching separately, I would also like to know what part of the request chain I should inspect first. My goal is not to force the website to reload everything on every visit, but rather to make sure that a newly published version becomes reliably available on the public URL without requiring visitors to manually refresh their browser.
I have been trying to keep the troubleshooting focused on this single content-refresh problem because the website otherwise loads and the affected pages remain accessible. The main reproduction pattern is that I make a legitimate change to an existing Ghost post or page, publish it, and then check the same public URL, where the previous version may still be displayed. After a full refresh or after waiting for some time, the updated version can appear, which makes the issue particularly difficult to reproduce consistently. I would like to know which logs, response headers, Ghost configuration settings, or theme files would be most useful for identifying where the old content is being retained. For example, if Ghost is already returning the newly published HTML but the browser is displaying an older response, that would point the investigation in a completely different direction than a situation where Ghost itself is still generating the previous version. Similarly, if Ghost’s frontend is correctly regenerating the page but an intermediate cache is serving an earlier response, I would want to identify that layer rather than modifying the post templates unnecessarily. Any recommended diagnostic sequence for separating these possibilities would be helpful, especially one that can be performed without making potentially disruptive changes to the production website.
Has anyone experienced a Ghost website where published content is saved and visible correctly inside Ghost Admin but the public page intermittently continues showing the previous version until a complete refresh or some amount of time has passed? I am mainly looking for the correct Ghost-specific way to diagnose why the live representation of a post or page is sometimes behind the version shown in the Admin editor. I would especially appreciate advice on whether Ghost normally handles this type of cache invalidation automatically, whether there are particular theme or frontend considerations that can interfere with the update process, and what evidence I should collect before changing anything on the server. If there is a recommended way to verify the exact HTML or response being returned immediately after publishing, that would also help me determine whether the stale content originates from Ghost itself or somewhere between Ghost and the browser. The important part is that the content is successfully updated and published from the Admin side, while the corresponding public URL does not always reflect that update immediately, so I would like to find the underlying reason for this inconsistent content refresh rather than relying on repeated manual browser refreshes as a workaround. Sorry for long post!
