🔍 Overview
After migrating your website to a new host, you may notice that Site Audits inside Search Atlas repeatedly fail. This article explains why this happens and what to have ready when contacting our team so the issue can be resolved as quickly as possible.
⚠️ Why This Happens
A hosting migration changes several technical details about your site — including its IP address, DNS records, SSL certificate, and server response behaviour. These changes can prevent Search Atlas's audit pipeline from completing successfully, resulting in postprocessing failures and, in some cases, quota consumption without a completed report being produced.
✅ What to Check Before Escalating
- Confirm your site is publicly reachable. Open a browser in a private/incognito window and navigate to your domain. If the site does not load, the issue is with your hosting setup — resolve DNS propagation or SSL errors with your hosting provider before contacting us, as Search Atlas cannot audit a site that is not publicly accessible.
- Check for redirects on your root URL. After a migration, root domains sometimes temporarily redirect to a staging URL or return a non-200 status code. Verify that your homepage is loading correctly for external visitors before re-running any audit.
- Do not repeatedly re-trigger audits while the issue persists. Running multiple audits in quick succession while the underlying connectivity problem is unresolved may result in additional quota consumption without producing output. Wait until your site is confirmed publicly reachable before attempting another audit run.
📋 What to Have Ready When You Contact Support
Because this type of failure requires a backend investigation by our engineering team, please gather the following information before reaching out:
- The exact project name and domain affected
- The approximate date and time the migration took place
- The approximate date and time the failed audit was triggered
- Any error messages or status indicators you can see within the platform
- Confirmation of whether your site is now publicly reachable (and when it became reachable, if it was temporarily down)
Having this information ready will allow our team to investigate the backend failure and, where applicable, review any quota consumed during the failed audit.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.