Home › Knowledgebase › KB-1272

Why isn't my website updating after i made changes?

Summary

This guide helps you troubleshoot and resolve: Why isn't my website updating after i made changes?. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Why Your Website Isn't Updating After Changes

When you make changes to your website or its configuration, those updates do not always appear immediately. Depending on where the change was made, visitors may continue to see the old version of your site due to caching at various levels of the internet infrastructure, or because DNS records have not yet propagated across global servers.

This guide covers the most common reasons why website changes are not appearing, including DNS propagation, browser caching, CDN caching, server-side caching, and CMS-specific caching. It also provides steps to verify updates and clear caches where possible.

Common Causes and How to Fix Them

1. DNS Propagation Delays

If you have updated DNS records such as A, CNAME, MX, or TXT records, the changes must propagate across recursive resolvers worldwide. This delay occurs because internet service providers cache DNS records based on the Time to Live (TTL) value. During this period, some visitors may see the new website while others see the previous version.

Always back up your existing DNS records before making changes. Incorrect DNS configuration, particularly with MX records, can disrupt email delivery and take your website offline.

Preparing for DNS Changes

  1. Log in to your domain registrar or DNS hosting control panel.
  2. Export or screenshot your current DNS zone file as a backup.
  3. Lower the TTL value to 300 seconds (5 minutes) at least 24 hours before making changes. This reduces caching time and speeds up propagation.

Updating DNS Records in Common Control Panels

cPanel
  1. Log in to cPanel.
  2. Navigate to Domains > Zone Editor.
  3. Click Manage next to your domain.
  4. Locate the record you wish to edit, click Edit, update the value, and click Save Record.
Plesk
  1. Log in to Plesk.
  2. Go to Websites & Domains > DNS Settings.
  3. Select the record you want to change and click the edit icon.
  4. Update the record details and click OK, then click Update to publish the changes.

Verifying DNS Updates

  1. Visit a public DNS lookup tool such as Google Admin Toolbox Dig or MXToolbox.
  2. Enter your domain name.
  3. Select the record type you updated (for example, A, CNAME, or TXT).
  4. Compare the returned value with the new record you configured.
  5. Check multiple geographic locations if the tool allows, as propagation speeds vary worldwide.

If you lowered the TTL before making changes, return it to a standard value (such as 3600 or 86400 seconds) once propagation is complete to reduce unnecessary DNS queries.

2. Browser Caching

Web browsers store copies of web pages, images, stylesheets, and scripts to load pages faster on repeat visits. This means your browser may continue to display a cached version of your website even after you have published changes.

How to Check and Clear Browser Cache

3. CDN Caching

If your website uses a Content Delivery Network (CDN) such as Cloudflare, Akamai, or Amazon CloudFront, the CDN may cache static content at edge locations around the world. Changes to your origin server will not appear until the CDN cache expires or is manually purged.

Clearing CDN Cache

  1. Log in to your CDN provider's dashboard.
  2. Navigate to the caching or configuration section for your domain.
  3. Look for an option labelled Purge Cache, Purge All, or Purge Everything.
  4. Confirm the purge and wait for the edge caches to clear.
  5. If you are using Cloudflare, you can also use Development Mode temporarily to bypass the cache while testing changes.

Remember that DNS changes to point your domain to a new CDN or origin server are also subject to DNS propagation delays.

4. Server-Side Caching

Your web server or hosting environment may use caching mechanisms such as Varnish, Nginx FastCGI cache, Apache mod_cache, or opcode caching (such as OPcache). These store dynamic page output or compiled PHP code to improve performance, which can prevent recent changes from appearing.

Clearing Server-Side Cache

5. CMS Caching and Caching Plugins

If your website runs on a content management system such as WordPress, Joomla, or Drupal, caching plugins or built-in CMS caching may be serving old content to visitors. This is one of the most common reasons small business website changes do not appear immediately.

WordPress Caching Plugins

  1. Log in to your WordPress admin dashboard.
  2. Navigate to the caching plugin you are installed (common examples include WP Rocket, W3 Total Cache, WP Super Cache, or LiteSpeed Cache).
  3. Look for a button labelled Clear All Caches, Purge Cache, or Delete Cache.
  4. If you use a performance plugin with minification or file combination, also clear minified CSS and JavaScript caches.

Other CMS Platforms

If you have recently changed your website theme or updated content and it is not appearing, always check CMS caching first before assuming the change failed to save.

Troubleshooting Checklist

If you host with us, you don't need to manage DNS or caching changes yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket