WordPress or checkout is failing
Collect a manual report from your site or import a sanitized error log. Review measured failures, affected components and the evidence still needed.
Display settings
These choices, favorites and recent tools stay in this browser. Private diagnostic jobs store encrypted inputs and reports for up to 24 hours. Data and retention details
Webmaster tools - Check, fix and verify!
83 free tools for DNS, email, SSL, redirects, SEO and WordPress. Each check shows what it found, whether it matters and what to change.
No account needed. Queued diagnostic reports expire within 24 hours.
Each check runs from our server. Results appear here as they return.
Full reportThe six setup checks covered redirects, DNS, HTTPS, headers, page tags and crawler access. If your store still fails to take an order, troubleshoot checkout. If you are moving this site, compare the new server before changing DNS.
Download evidence to keep a copy. Saving a Website Project in My websites is a separate action.
Start from the problem
Choose the symptom. Each card lists checks in a useful order, so you can rule causes out and repeat the same measurement after a fix.
Collect a manual report from your site or import a sanitized error log. Review measured failures, affected components and the evidence still needed.
Compare saved DNS inventories to find changed records and TTLs, or follow the aliases returned for a public hostname.
Compare robots rules for specific paths, review sitemap changes or inspect the indexing signals on selected pagination pages.
Start with the website setup report. If your public site and origin disagree, compare both endpoints using your server IP. Origin checks require domain verification.
Measure a public page with one screen size and inspect its requests and rendering. If you already have a HAR capture, analyze it locally instead.
Compare the current site with the proposed server before changing DNS. Supply the new public server IP, verify the domain and state the responses you expect.
Save a checklist in a verified website project, run it manually and compare with an approved baseline. For a single report, use the visual comparison or journey tool.
Check the site from our server, then look at what your own connection can reach.
Record failed scripts, browser errors and visible content on a verified project page. Compare completed evidence after changing the deployment.
How checks run
Website owners who see our requests in their logs can read how our checker behaves.
Good places to start
See which DNS records a resolver returns when a site move or mail change has yet to reach visitors.
Check a certificate's expiry, covered names, chain and supported TLS versions.
Follow a URL through every redirect and spot loops, HTTP downgrades and long chains.
Compare the current site with a proposed server before changing DNS.
Repeat a browser measurement and inspect timing, requests and rendering evidence.
Compare two rendered pages and inspect screenshots and their pixel differences.
My websites
Website projects are free and need no account. Verify your hostname to save checks in this browser. Each project keeps up to 100 history entries for up to 30 days.
Guides