Website Builder site not publishing or changes not appearing after save.
Website Builder & ProductsVerified: Jul 14, 2026
Resolution Steps
- Confirm the customer is clicking "Publish" and not just "Save" — changes save locally but require publish to go live.
- Check the GoDaddy System Status page for any active Website Builder outages.
- Ask the customer to hard-refresh the published site (Ctrl+Shift+R / Cmd+Shift+R) to bypass browser cache.
- Verify the domain connected to the Website Builder is pointing to GoDaddy nameservers.
- Check if the site is connected to a custom domain or using the free subdomain — DNS propagation can delay updates.
- If using a custom domain, verify the A record or CNAME is correctly configured in DNS.
- Ask the customer to try publishing from a different browser or incognito mode.
- Check the site's publish history in the Website Builder dashboard for error messages.
- For Airo-built sites: confirm the site was exported and deployed, not just previewed in the builder.
- Clear the CDN cache from the hosting dashboard if changes are cached at the edge.
Say This
"Let's figure out why your changes aren't showing up. First question: after you made your changes, did you click the "Publish" button, or just "Save"? The reason I ask is that saving keeps your changes in the editor, but publishing is what sends them live to your website — it's a separate step. [if they only saved] That's the fix right there — go ahead and click Publish now, and your changes should appear within about 60 seconds. [if they did publish] Okay, so you did publish. Let's try a hard refresh on your site — hold Ctrl and press Shift+R at the same time (or Cmd+Shift+R on a Mac). This forces your browser to load the latest version instead of a cached copy. Can you try that now? [if still not showing] I'm going to check the publish history on your account to see if there's an error message. One moment..."
Quick Links
Escalate When...
- Website Builder is returning a persistent error on publish after multiple attempts — escalate to technical team.
- Customer's site data appears to have been lost or corrupted.
- Custom domain has been correctly configured but site is still unreachable after 48 hours.
- Customer is requesting a feature that is not available in their current plan — offer upgrade path.
- Airo-generated site has a billing or licensing issue preventing export.