Hello Hugo Community,
I am currently facing one persistent issue with my Hugo website where the site builds successfully without reporting any errors, but some generated pages continue displaying older content after I make changes to the source files and rebuild the site. The core problem is that Hugo appears to process the updated Markdown and template files correctly during the build, and the generated output directory contains the changes I expect, but the version visitors receive from the deployed website sometimes remains an older version. For example, I can update the content of a page, run the Hugo build command, inspect the generated HTML, and confirm that the new text is present in the output. However, when I access the corresponding public URL, the browser can still display the previous version of that page. This is intermittent because some updated pages become visible immediately while other pages continue serving stale generated content even though the local build appears completely successful.
I have verified that the source content itself is being updated correctly and that Hugo is rebuilding the relevant pages. I am using Markdown content files together with Hugo templates, shortcodes, and static assets, and the build process completes normally without fatal errors. When I inspect the generated files locally after running the build, the expected changes are present, which tells me that Hugo is not simply ignoring the modified source file. The problem seems to occur after the generated output is produced and deployed. The public website can continue showing the previous version even though the newly generated HTML is definitely present in the deployment output. Because the Hugo build process itself reports success, I am trying to determine whether there is something in Hugo’s generated output, deployment process, or caching behaviour that could cause an older version of an otherwise correctly generated page to remain accessible.
I have also tried performing clean builds rather than relying on incremental changes, including removing the generated output directory before rebuilding the site. This produces the same expected HTML locally, so I do not believe the issue is simply caused by an obsolete file remaining in the local public directory. I have compared the timestamps and contents of the generated files and confirmed that the updated version is being produced. I have also checked the URL paths carefully because I want to make sure that the page I am editing corresponds exactly to the page being requested publicly. The affected URLs are correct, and there is no obvious duplicate content file that should be generating the older version. Despite these checks, the public page can still return content that no longer exists in the freshly generated output.
The problem becomes especially noticeable when I make several content updates and deploy them relatively close together. Sometimes the first deployment appears correctly, while a subsequent deployment seems to leave one or more pages displaying the previous version. Other pages from the same build become updated normally, which makes the issue difficult to reproduce consistently. I have tested the public URLs from different browsers and private browsing sessions, and in some cases the older content is still returned, suggesting that the issue may not be limited to the browser’s local cache. I am therefore trying to understand whether Hugo generates any particular caching headers or output structures that could influence how an external deployment platform, CDN, reverse proxy, or browser caches the generated pages. I want to establish whether the stale response is already present in the deployed files or whether an intermediary layer is returning an older copy.
I have also reviewed my Hugo configuration and deployment workflow to make sure that the build is using the expected content directory, layouts, themes, and output location. The same repository and configuration are used during the normal deployment process, and there have been no intentional changes to the URL structure or permalink configuration immediately before the problem occurs. I have considered whether Hugo’s page resources, render hooks, shortcodes, or template caching could be involved, but the fact that the freshly generated HTML contains the correct content makes me unsure where to focus the investigation. I would like to avoid making random changes to the configuration because the website is otherwise functioning correctly and I want to isolate the actual reason why the public site occasionally serves an older generated page.
I would appreciate guidance from the Hugo community on how to systematically diagnose this specific stale-content problem. In particular, I would like to know which Hugo commands, build options, debug output, or generated-file checks can help confirm that the correct page is being generated and that no unexpected duplicate output is being produced. I would also appreciate advice on whether Hugo itself can contribute to this kind of stale output behaviour or whether I should focus entirely on the deployment and caching layer once the public directory has been verified to contain the latest HTML. My goal is to make the deployment process reliable so that whenever Hugo successfully builds and publishes an updated page, visitors consistently receive that latest version at the public URL without needing repeated refreshes or waiting for an unpredictable period. Sorry for long post!