Site health

Review HTTPS, error pages, and live site vitality signals.

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.

Health score

A domain-level vitality score from availability, HTTPS, errors, and related checks.

HTTPS mix

See whether pages and resources load over HTTPS or still pull insecure assets.

Error pages

Count 4xx and 5xx URLs from the latest crawl inventory with sample destinations.

Block-list and threat signals

Check popular filtering DNS resolvers and flagged sources that can hurt visibility.

What is site health?

Site health is whether the live origin is reachable, trusted, and clean.

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

Unhealthy origins lose crawl budget and user trust.

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.

Prove the site is reachable

A stable 200 on the canonical homepage is the first gate for SEO and assistant visibility.

Keep HTTPS consistent

Mixed content and leftover HTTP URLs trigger browser warnings and weaken trust signals.

Reduce error-page waste

Internal links to 404s spend crawl budget and frustrate users who follow them.

Catch reputation blockers

DNS block-list hits and unsafe flags can suppress traffic even when on-page SEO looks fine.

How it works

Live checks plus crawl inventory, summarized.

01

Probe availability

Review homepage reachability, response code, timing, and redirect chain.

02

Query block-list resolvers

Check popular filtering DNS resolvers for the monitored domain.

03

Collect quality signals

When available, console issues and HTTPS resource mix come from a quality check.

04

Compute error pages

4xx and 5xx URLs are counted from the latest crawl inventory with samples.

Health blocks

A compact vitality board for the selected domain.

Each block includes status, summary, and enough evidence to open a ticket.

Availability

Up status, HTTP code, response time, and redirect chain for the public origin.

Block lists

How many filtering DNS resolvers flag the domain, with server-level detail.

Console issues

Browser console errors tied to templates or third-party scripts when the quality check ran.

HTTPS

Page protocol mix, insecure resource count, and sample mixed URLs.

Error pages

Share of crawled URLs that returned client or server errors.

Quality scores

Category scores from the quality check when they are available.

What teams do next

Fix vitality issues before the next content sprint.

Resolve mixed content

Serve remaining HTTP assets over HTTPS or remove them from templates.

Repair internal links to errors

Update or remove links that still point at 404 and 410 URLs in the inventory.

Shorten homepage redirects

Land on one HTTPS canonical host with as few hops as possible.

FAQ

Site health questions.

Short answers for teams that want website health checks next to on-page SEO.

What does Crawlox site health include?

Site health covers availability, DNS block lists, console issues, HTTPS mix, crawl error pages, quality scores, and related threat flags for an authorized domain.

Is site health the same as on-page SEO analysis?

No. On-page analysis scores HTML on each URL. Site health looks at origin vitality: reachability, HTTPS, errors, and reputation signals.

Where do error pages come from?

Error pages are computed from HTTP status codes in the latest crawl inventory, with sample URLs you can open.

Does Crawlox run Lighthouse?

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.

Why do block lists matter for SEO?

If filtering DNS resolvers flag a domain, users and some crawlers may never reach the site even when pages are well optimized.

Who should use the Health view?

SEO leads, site reliability owners, and agencies that need a vitality check alongside crawl and on-page work.

Check site health

Keep the origin healthy enough to rank.

Crawl an authorized domain and review HTTPS mix, error pages, availability, and related vitality signals next to your SEO inventory.