THE PRACTICAL GUIDE

Turn a website inspection report into a repair plan

Follow a page from DNS to its final HTML, separate availability from indexing, and prioritize fixes using the evidence behind each check.

Inspect the page a visitor actually opens

Start with a public URL, including the path of the page you want to check. A successful homepage response does not establish that a product, article, or campaign landing page works. Record the submitted address, the final address after redirects, and the report time so you can repeat the same check after a change.

ADEMN requests the page from its server without your browser’s login cookies and does not execute the page’s JavaScript. Use a URL without private tokens or credentials. If your browser shows content but the report sees a login screen, a challenge, or an empty application shell, compare the actual responses before changing the page’s metadata.

Resolve connection problems before editing page content

Read the request in dependency order: public DNS, the connection and certificate, redirects, then the final response. A failure early in that sequence can prevent later checks from collecting evidence. A missing title in an error response is a symptom; adding a title to your normal template will not make that response reachable.

For an illustrative landing page, an HTTP address might redirect to HTTPS and then return 404 at its final path. The redirect can be correct while the destination is missing. Confirm the published path and its deployment first. Repeat the check for the same path rather than testing only the homepage and assuming the issue is resolved.

Choose the next investigation from the observed failure
Observed resultFirst investigationFocused tool
Public name does not resolveCompare DNS answers with the hosting configurationDNS Lookup
Certificate hostname or trust check failsCheck the certificate served for this hostnameSSL Checker
Redirect repeats or reaches the wrong pathRead each Location value and final URLRedirect Checker
Final response is 404 or 500Check the route, published content, and server logsWebsite Inspector after the repair

Check returned HTML against the intended page

Website Inspector reads the title, meta description, canonical link, and robots meta value from the returned HTML. Compare those fields with the intended page and final URL. A nonempty canonical can still point at a different page; a description can exist while describing the wrong product. The presence checks do not judge that meaning.

The example below shows a page that responds successfully but explicitly requests exclusion from indexing. The inspector’s score gives points for a successful response and present metadata; it does not subtract points for this robots value. Read the individual fields even when the score looks favorable. For a page intended for search, investigate why noindex was set before changing it.

Illustrative response with an indexing directive
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8

<title>Packaging sizes | Sample shop</title>
<meta name="description" content="Compare the dimensions of our three packaging sizes.">
<link rel="canonical" href="https://example.com/packaging">
<meta name="robots" content="noindex, follow">

Open discovery files and inspect their contents

The report checks the conventional /robots.txt and /sitemap.xml addresses on the final origin. Availability means the response resembles the requested file; it does not establish that every rule or listed URL is correct. A site can also publish a sitemap at another address. Inspect the file and its declared locations when the conventional check fails.

A reachable robots.txt can disallow an important path. A sitemap can list removed pages or omit a newly published guide. Google distinguishes crawling controls in robots.txt from indexing controls such as noindex; blocking a page from crawling can prevent its indexing directive from being read. Check those decisions separately and use Search Console to investigate Google’s view of a particular URL.

Use the score to organize evidence and retest

ADEMN’s score adds the weights of passing checks. The security-header check contributes 15 points when at least three of six selected headers are present. An illustrative report with all other checks passing but only two detected headers therefore scores 85/100. This arithmetic describes the checklist, not a measured probability of safety or a search ranking.

Read each header’s actual value and decide whether it fits your application before editing it. Then make one coherent repair, repeat the original URL check, and confirm the page in a browser. Keep your own before-and-after notes if needed: ADEMN does not save diagnostic reports. A repaired status code, expected final URL, and correct page content provide more useful evidence than a score alone.

A small repair record you can reproduce
Before: /packaging → HTTPS → 404
Repair: publish /packaging in the production deployment
Retest: same submitted URL → expected HTTPS URL → 200
Verify: correct page title, body, canonical, and intended indexing directives

Methods and references

Put it into practice