Prove the site is reachable
A stable 200 on the canonical homepage is the first gate for SEO and assistant visibility.
Site health
Crawlox health checks go beyond on-page tags: availability, DNS block lists, console issues, HTTPS mix, crawl error pages, and quality scores for the authorized domain.
A domain-level vitality score from availability, HTTPS, errors, and related checks.
See whether pages and resources load over HTTPS or still pull insecure assets.
Count 4xx and 5xx URLs from the latest crawl inventory with sample destinations.
Check popular filtering DNS resolvers and flagged sources that can hurt visibility.
What is site health?
Ranking depends on more than titles. If the homepage is slow or looping redirects, if HTTP resources mix into HTTPS pages, or if crawlers hit error URLs, SEO work on copy will not stick. Crawlox groups those vitality signals next to the crawl inventory.
Why it matters
Search systems and AI crawlers start from the same public fetch path. Availability failures, mixed content, and error pages reduce how often your URLs are fetched, indexed, and cited.
A stable 200 on the canonical homepage is the first gate for SEO and assistant visibility.
Mixed content and leftover HTTP URLs trigger browser warnings and weaken trust signals.
Internal links to 404s spend crawl budget and frustrate users who follow them.
DNS block-list hits and unsafe flags can suppress traffic even when on-page SEO looks fine.
How it works
Review homepage reachability, response code, timing, and redirect chain.
Check popular filtering DNS resolvers for the monitored domain.
When available, console issues and HTTPS resource mix come from a quality check.
4xx and 5xx URLs are counted from the latest crawl inventory with samples.
Health blocks
Each block includes status, summary, and enough evidence to open a ticket.
Up status, HTTP code, response time, and redirect chain for the public origin.
How many filtering DNS resolvers flag the domain, with server-level detail.
Browser console errors tied to templates or third-party scripts when the quality check ran.
Page protocol mix, insecure resource count, and sample mixed URLs.
Share of crawled URLs that returned client or server errors.
Category scores from the quality check when they are available.
What teams do next
Serve remaining HTTP assets over HTTPS or remove them from templates.
Update or remove links that still point at 404 and 410 URLs in the inventory.
Land on one HTTPS canonical host with as few hops as possible.
FAQ
Short answers for teams that want website health checks next to on-page SEO.
Site health covers availability, DNS block lists, console issues, HTTPS mix, crawl error pages, quality scores, and related threat flags for an authorized domain.
No. On-page analysis scores HTML on each URL. Site health looks at origin vitality: reachability, HTTPS, errors, and reputation signals.
Error pages are computed from HTTP status codes in the latest crawl inventory, with sample URLs you can open.
Console and HTTPS resource signals come from a quality check when it is available. Treat those blocks as supporting evidence, not a full lab report replacement.
If filtering DNS resolvers flag a domain, users and some crawlers may never reach the site even when pages are well optimized.
SEO leads, site reliability owners, and agencies that need a vitality check alongside crawl and on-page work.
Check site health
Crawl an authorized domain and review HTTPS mix, error pages, availability, and related vitality signals next to your SEO inventory.