How to fix what a website audit finds

A website audit tells you what is missing or misconfigured. These guides tell you how to put it right: where the setting lives, what the correct value looks like, and how to change it on the platforms most sites run on. Each one matches a check in WEBCHKR, and a failing check in your results links straight to its guide.

Start here

Walkthrough Website audit checklist: how to check your site’s technical fundamentals The manual method, group by group: HTTPS and redirects, crawling and indexing, on-page SEO, AI readiness, email authentication, security, analytics and performance, with the free tool for each step. Read the checklist

Fix them in this order

  1. Make the site reachable the right way. Every version of your address should land on one HTTPS page, and missing pages should return a real 404. HTTPS redirects, soft 404s.
  2. Let search engines in. One stray Disallow: / or noindex undoes everything else. robots.txt, noindex and sitemaps.
  3. Protect your email domain. SPF, then DKIM for every service that sends as you, then DMARC on top. SPF, DKIM, DMARC.
  4. Add security headers. A few lines of server or CDN configuration. Security headers.
  5. Decide how AI tools may use the site. Make your robots.txt say what you intend, and add an llms.txt if you want to. AI crawlers, llms.txt.

Guides

HTTPS & redirectsHow to redirect every version of your site to one HTTPS address Soft 404sHow to make missing pages return a real 404 robots.txt & sitemapHow to fix robots.txt, noindex and sitemap problems SPFHow to set up or fix your SPF record DKIMHow to set up DKIM for your domain DMARCHow to set up DMARC and move safely to enforcement Security headersHow to add security headers to your site AI crawlersHow to allow or block AI crawlers in robots.txt llms.txtHow to create an llms.txt file

Before you start

  • Find out where each setting lives. DNS records (SPF, DKIM, DMARC) are changed wherever your domain's nameservers point, which is often your registrar or Cloudflare rather than your web host. Redirects and headers live on your host or CDN. Tags live in your CMS or tag manager.
  • Change one thing at a time and re-check it before moving on, so you know which change fixed or broke what.
  • Keep a note of each change and the date. DNS changes take up to the record's TTL to appear everywhere, and it is easy to undo a fix that was simply still propagating.