Changes in Content Not Reflecting on My Hugo Website After Deployment

support
1

Hi everyone,

I’m using Hugo to build my website, and I’ve recently encountered an issue where changes I make to my content or templates are not reflecting after deployment. The site builds without any errors, but the updated content doesn’t appear on the live website.

What I’ve observed:

  1. When I run hugo server locally, all changes appear as expected.
  2. After committing and pushing to my GitHub repository, the Netlify deployment completes successfully, but the live site still shows the old version.
  3. Clearing the browser cache doesn’t help, and even after purging the Netlify cache, the changes don’t show.

What I’ve tried so far:

  1. Verified that the updated files are present in the GitHub repository.
  2. Checked the Netlify build logs, which don’t show any errors or warnings.
  3. Ensured the public/ folder is not committed to the repository, as Netlify builds it during deployment.
  4. Updated the baseURL in config.toml to match the live site.

Questions I have:

  1. Could this be an issue with Hugo’s caching or the way the public/ directory is generated?
  2. Are there specific settings in the config.toml file that might cause this issue?
  3. Should I manually clean the resources/ directory or any other cached files before deploying?

Any guidance or troubleshooting tips would be greatly appreciated. Thanks in advance!

2

Is there a chance that you are viewing a locally cached version of the page instead of what was last published?

You could try visiting the site in a new private/incognito window, or use a different browser.

3

Thank you for the suggestion!

I’ve already tried clearing the browser cache and even purged the cache on Netlify, but unfortunately, the issue persists. I also tested viewing the site in incognito mode and on a different browser, but I’m still seeing the old version of the site.

It seems like the deployment process on Netlify completes successfully, and the logs don’t show any errors, which makes me think the problem might be related to Hugo’s build process or caching on the server side. Do you think manually cleaning the resources/ directory before pushing changes could help? Or is there any way to confirm that the updated files are actually being used during the deployment? Thanks again for your help! By the way, this reminds me of working with CapCut for video edits—it’s similar in that sometimes clearing cached previews helps resolve issues with outdated renderings. If you’re interested in trying out a modded version of CapCut or capcut mod apk for enhanced features, you can click here. Perhaps there’s a parallel here, where clearing out all build artifacts and starting fresh might be the solution. Thanks again for your help!

4

No.

How do you know this? Can you share the build log?

Is the problem only with updated files, or with new and deleted files as well? If you don’t know, test it.