Short answer: A move to a new host, a new server or a new DNS provider changes things that nobody sees on the day: the SSL certificate, the redirect rules, the security headers, the compression settings and the DNS records for e-mail. Run Site AI Audit before the move to record your starting point and again after it, then compare the findings. New critical findings point to what was lost on the way, and a few of them, such as a missing certificate or a missing SPF record, are urgent.
Why moves break things that look fine
After a successful move, the home page opens and the pages look the same. That is the visible part. The rest of what makes a site work lives in settings that belong to the old server and are not copied with the files: the certificate that was bound to the domain, the rules that redirect http to https and www to the bare name, the headers that the server adds to each response, the compression, the caching and the version of PHP. If the DNS zone is moved too, every record in it must be recreated at the new provider, including the ones for e-mail.
These details fail quietly. A visitor does not see a missing header. A customer does not see a missing SPF record until a message goes to spam. A search engine does not complain; it just changes how it treats your pages. A structured check after the move is the way to catch them in the first days, not the first months. The article on website migration SEO covers the search side of a move in more detail.
Step 1: take a snapshot before the move
- Run a full audit of the website on the old host. Note the overall score, the four area scores and the number of findings. On a paid plan, download the PDF as a record, as described in the article on sharing the PDF report.
- Save the list of critical and warning findings. Some of them already exist, and you do not want to blame the new host for them.
- Write down your DNS records. Export the zone, or copy the records by hand: A, AAAA, CNAME, MX, TXT for SPF and DMARC, and the DKIM keys. The audit shows what it can see, but your own list is the safest backup.
- Lower the TTL of the main records a day before the change, so that the switch spreads quickly. The article on DNS propagation and TTL explains why.
Step 2: move, then wait for DNS
Do the move as planned. When the DNS records point to the new server, give them time to spread, from minutes to a few hours, depending on the TTL. Check the site from more than one network. When you can open the new site from a computer that did not see the old one and the certificate is valid, you are ready to check.
Step 3: run the audit again
Enter the same address and run a full audit. Compare the results with your snapshot. On a paid plan, the history page does the comparison and lists what is new, what is fixed and what has got worse, as explained in the article on comparing two audits. Otherwise, compare the two reports by hand. Then go through the areas in the order that matters.
What to look for, area by area
Security: certificate, redirects, headers
- “The website does not work over HTTPS”, a critical finding. The new server has no certificate for the domain yet. See the HTTPS finding.
- Certificate findings: expired, expiring, not trusted or issued for another name. A certificate installed on the new host may cover only the bare domain, or have an incomplete chain, as the article on SSL certificate findings explains.
- “http:// does not redirect to https://” and “The site opens on more than one address”. The redirect rules lived in the old server’s configuration. See redirect chains and address variants.
- Mixed content. If the new host serves some resources by http, browsers warn.
- Security header notices. HSTS, content type, frame and referrer headers were perhaps set on the old server and are gone, see security header findings.
- Exposed versions. A new host may show other server and PHP versions. A PHP version below 8.2 raises a warning, see exposed server, PHP and WordPress versions.
SEO: robots, indexing, missing pages
- “robots.txt blocks the whole site” or “The home page tells search engines not to index it”, both critical. Settings from a staging copy sometimes travel with the files. Check them first, because they can remove a site from search in days. See noindex findings.
- Broken internal links and missing pages that return 200 OK. Different rewrite rules on the new server can break pretty links or change how missing pages are handled. See broken internal links and soft 404 findings.
- Sitemap findings. The sitemap file may not have been moved, or the robots.txt line was lost.
- Redirect chains. Old rules plus new rules can double up.
Speed: the server itself
- “The server takes N s to respond”. A cold cache or a smaller plan can slow the first answer. See slow server findings.
- “Text files are sent without compression”. Compression is a server setting that must be switched on again. See compression and page weight.
- “The server uses the old HTTP/1.1 protocol”. A good new host usually offers HTTP/2 or better.
- The mobile speed score. Treat it as a guide only. A cache that is not warm yet can give an unfair result, so run the check again after a day.
E-mail: the records that live in DNS
If you changed the DNS provider as well as the host, check the e-mail area first. It is the one with the highest cost of a mistake:
- “The domain does not receive e-mail (no MX record)” means messages to you are not delivered. See the MX finding.
- No SPF record, or an SPF record that now fails. See SPF findings explained.
- “No DKIM key found” after a move can mean that the selector records were not copied. See the DKIM finding.
- “No DMARC record”. See how to fix a missing DMARC record.
Mail problems after a move often appear only when a customer says that a message was lost. On the Business plan, daily checks of the SPF and DMARC records alert you if one that was present disappears, as described in the article on the Business plan.
Step 4: fix, re-check, and keep the old host for a while
- Fix criticals first: certificate, indexing blocks, MX and SPF.
- Fix warnings next: redirects, broken pages, compression.
- Re-check and confirm that each finding has gone.
- Keep the old hosting for a short time so that you can fetch anything that was missed, and check that nothing still points to it.
- Re-run the audit a week later. Some problems, such as a certificate that fails to renew, appear only after a time.
Be fair to the new host
Compare the new report against your snapshot before you blame the new provider. Findings that were in the first report were not caused by the move. Findings that are new, and that match the list above, are the ones to take up with the host, with the finding text as your description of the problem. A request such as “your server answers without compression, please enable it” is much easier for a support team to act on than “the site feels slower”.
A worked example
A physiotherapy clinic moves its WordPress site from an old shared plan to a new VPS and changes the DNS provider on the same weekend. Before the move, the audit shows a score of 81 with one warning about missing compression. After the move, the score is 54. The report lists a critical finding, no HTTPS, because the certificate was not installed yet, a critical finding for no SPF record and a notice for no DKIM key, because the DNS records for e-mail were not copied, and a critical finding that the home page is set to noindex, copied from the staging settings. The agency installs the certificate, copies the e-mail records, removes the noindex and enables compression. The next audit shows 88, and no one has lost a message.
To record your starting point, run a Site AI Audit before you move. The first check needs a free account, and the plans unlock the full report and the history.
Related reading
- Shared Hosting vs VPS: Which Is Faster for Your Website?
- How to Redirect HTTP to HTTPS the Right Way (Without Loops)
- Run a Site AI Audit Before Launching a New Website
- Does Server Location Affect Website Speed? What to Know
The bottom line
A hosting or DNS change can silently remove the certificate, the redirects, the headers and the e-mail records. Audit before and after the move, fix criticals first and compare the reports to see exactly what changed.
BUJ
When should I run the second audit?
As soon as the DNS change has spread and the new site opens with a valid certificate. Run another one a week later.
Will the audit see problems with my e-mail after a move?
It checks the MX, SPF, DKIM and DMARC records of your domain, which are the usual victims of a DNS move.
Why is my score lower after the move?
Settings that belonged to the old server, such as compression, redirects and headers, may be missing. The findings tell you which ones.
Should I audit the new host before switching DNS?
Only if the new server is reachable on a public address with the standard ports. Otherwise audit after the switch.
Can I compare the two reports automatically?
On paid plans, the history page lists new, fixed and worsened findings between two checks.



