Tools

Browse by category or jump to the spotlight tools first.

Start here by goal: indexability triage (SEO Health Scorecard), routing cleanup (Redirect Chain Visualizer), crawl controls (Robots + Sitemap Auditor).

Next-step rule: after each tool result, pick exactly one fix, ship it, and re-run the same tool to confirm change.

Weekly fresh examples (Week of 2026-03-02 execution · refreshed Mar 2)

These are practical, repeatable checks operators can run this week to keep discoverability healthy.

Migration cleanup: run Redirect Chain Visualizer on 5 legacy URLs, then confirm host policy in WWW Canonical Checker.
Indexability sanity pass: validate Robots + Sitemap Auditor first, then score impact in Technical SEO Health Scorecard.
Post-release response audit: inspect 3 key templates in HTTP Header Inspector, then verify provider-routing assumptions in Hosting Fingerprint Checker before speed/canonical tuning.
DNS consistency check: run DNS Quick Check then confirm resolver convergence in DNS Propagation Spot Check.

Use this sequence to move from symptom to fix with minimal context switching.

Incident triage: /health + HTTP Header Inspector + FAQ triage playbook
Routing sanity: Redirect Chain Visualizer + WWW Canonical Checker
Indexability: SEO Health Scorecard + Robots + Sitemap Auditor
Infra baseline: DNS Quick Check + DNS Propagation Spot Check + Hosting Fingerprint Checker
SERP readiness: Meta Tag Inspector + Schema Markup Validator

Operator rule: after each stage, ship one fix and re-run only the same stage before moving forward.

Workflow hubs: FAQ triage scenarios · Indexability checks · Response/header QA · DNS baseline checks · External exposure triage · AI cost planning · Metadata validation · Schema QA · Routing triage.

Use these probes in uptime tools or runbooks to verify service and deployment freshness.

https://webboar.com/health — baseline status, build hash, uptime.
https://webboar.com/health?label=cron-daily — same payload with source label.
https://webboar.com/health?label=deploy-smoke&minTools=1&expectCatalog=1 — deployment smoke check with assertions.
https://webboar.com/health?label=latency-slo&maxLatencyMs=300 — fail when response latency breaches threshold.

Deploy confidence rule: confirm buildHash changed when code changed, and toolCount is non-zero.