Technical website checks
Technical website checks inspect response statuses, resource failures, redirects and signals identifying a preferred URL. A successful response can still carry an error message, reference missing assets or disagree with its declared canonical. Read response evidence alongside the rendered result. Differences between crawler requests and normal visits can reveal an infrastructure rule rather than a content defect.
Test valid pages, an unknown address and each supported hostname and protocol. Confirm that redirects reach the intended destination without unnecessary steps and missing resources return an appropriate status. Review deployment configuration before editing templates, particularly when a proxy supplies headers or rewrites paths. Repeat production checks because local responses cannot establish CDN behaviour.
The check pages below describe the exact observable condition, why it matters, practical fixes and the limits of the detector. Open the affected URL and inspect its evidence before making a change. After correction, repeat the scan and verify the result in a browser. The related guide connects these individual checks into a review workflow. Keep deliberate exceptions documented so that a passing automated result is never mistaken for a complete manual assessment.
Checks and fixes
Crawled pages returning a 4xx or 5xx status
Review crawled HTTP errors. Separate expected removal from server failure, repair references, investigate excluded responses, and test the exact public route.
Failed to Load Resource Errors: Separate Network Failures from HTTP Errors
Diagnose resources failing before an HTTP response. Inspect network evidence, preserve security controls, and separate request failures from status errors.
Favicon Missing: Declare and Verify a Real Site Icon
Fix a missing favicon declaration. Link a real appropriate icon from the homepage, verify retrieval and supported formats, and understand search-display limits.
JavaScript Errors in Console: Diagnose the Message and Real Impact
Investigate console errors without hiding them. Separate logged messages from uncaught exceptions, inspect network and policy failures, and test actual tasks.
Meta Charset Missing: Declare the Encoding That Matches the Bytes
Fix missing character-encoding declarations. Match UTF-8 bytes and headers, place metadata early, and verify real decoding rather than a presence-only pass.
Missing Doctype HTML: Select No-Quirks Rendering Deliberately
Fix missing HTML doctypes. Use the modern short form, inspect actual rendering mode, and distinguish raw-prefix checks from browser parsing behaviour.