🔍 Understanding the NoSuchBucket Error
If your Website Studio site shows a NoSuchBucket XML error on your custom domain, the platform is sending the request to a Google Cloud Storage bucket that does not exist. This is a platform routing problem, not a problem with your domain registration or DNS. Contact Search Atlas support and include the domain and the full error. Reloading the page, republishing, or changing DNS will not fix it.
📋 Common Causes
Before making changes, check for these common causes:
- DNS pointing mismatch: A subdomain should use the CNAME target shown in Website Studio, and a root domain should use the A record IP shown there. Those targets point to Search Atlas, not to a storage bucket. Wrong DNS usually stops domain verification or shows a different site or certificate error; it does not cause NoSuchBucket.
- Domain Name Typo: The domain mapped in your platform settings does not exactly match your active domain name.
- Unverified custom domain: If verification has not finished, the domain is not yet connected and will not serve the published Website Studio site. Finish the DNS record shown in Website Studio and click Verify. That is a separate setup step and does not repair a NoSuchBucket error.
- SSL or routing delay: After DNS is verified, Search Atlas provisions the certificate and connects the domain. Until that finishes, you may see a certificate warning or the site may not load. This is not a NoSuchBucket error, and it does not provision a new storage bucket.
🚀 Step-by-Step Fixes
Follow these steps to restore your site:
- Check the domain in Website Studio: Open the project, go to its Domains area, and confirm the connected domain is exactly the one you are visiting, including www or the root domain. If it is already connected and verified, changing the spelling will not fix NoSuchBucket. Contact support.
- Check DNS only if the domain is not verified: In your DNS provider, such as Cloudflare, GoDaddy, or Namecheap, use the record shown in Website Studio. Use a CNAME for a subdomain or an A record for a root domain. This confirms the domain reaches Search Atlas; it does not repair a NoSuchBucket error on an already connected domain.
- Do not remove and re-add the domain to fix NoSuchBucket. Removing it only disconnects the domain and deletes its routing and certificate; adding it again starts DNS verification again and does not create a new bucket. Contact Search Atlas support so the platform routing can be corrected, then reopen the domain.
- Clear Local Cache: Clear your browser cache or open the website in an incognito window to verify if DNS propagation has completed. DNS updates can take anywhere from a few minutes up to 24 hours to take effect globally.
💬 Contact Search Atlas Support
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.