Site Analysis
Check one page in detail or sample a site crawl, prioritize failures, and reopen saved runs.
Site Health
Find the technical issues holding your website back
Check page and site foundations, measure speed and Core Web Vitals, inspect links, and turn the most useful findings into work your team can verify.
Works with any public website No WordPress required
Three connected diagnostics
See whether the site is clear, fast, and reliably connected
Site Health combines foundation checks, Page Speed testing, and Link Analysis so technical problems remain tied to the affected URL, available evidence, and a practical next step.
How it works
A clear path from uncertainty to evidence
- 1
Choose a page or site scope
Run a detailed single-page check or a capped same-domain crawl, depending on the question you need to answer.
- 2
Inspect the technical foundation
Review titles, descriptions, headings, structured data, HTTPS, canonical, indexability, sitemap, and crawler-discovery signals.
- 3
Measure speed and links
Test a page and device for lab performance and Core Web Vitals status, or map links and inspect destinations, redirects, and anchor quality.
- 4
Fix and compare
Send supported findings to Fix Center, rerun the relevant check, and compare saved results without inventing improvement where evidence is missing.
What you can inspect
Evidence you can open and understand
Page Speed
Review plain-language performance results and Core Web Vitals status by tested page, device, lab, and available city.
Link Analysis
Inspect internal and external links, destination status, redirects, anchors, filters, comparisons, and CSV export.
Discovery and indexing
Check canonical, robots, sitemap, indexability, llms.txt, AI crawler access, and supported submission guidance.
Evidence boundary
What a Site Health result can—and cannot—show
- A page check represents the tested URL; a site crawl represents the capped pages retrieved during that run.
- Page Speed lab results are controlled measurements and may differ from field performance experienced by real visitors.
- A passing technical check does not guarantee AI visibility, search ranking, traffic, leads, or sales.
- Blocked, timed-out, or unavailable pages should produce a clear coverage limitation instead of placeholder metrics.
Practical guide
Use Site Health without chasing every warning
Technical work is most useful when it starts with a real page, prioritizes material failures, and ends with a comparable rerun.
Match the tool to the problem
Use Site Analysis for foundations, Page Speed for loading and responsiveness, and Link Analysis for paths, destinations, and anchors.
Start with failures that block retrieval or use
Broken responses, noindex directives, missing canonical signals, dead links, and severe performance issues deserve attention before cosmetic advice.
Preserve the tested context
Keep the URL, device, location or lab, crawl scope, and run time attached to the result so later comparisons remain meaningful.
Rerun the same check
After publishing a change, repeat the relevant test under comparable conditions before calling the issue resolved.
Common questions
Clear answers before you start
What is Site Health?
Site Health is BoostGeo’s technical measurement area for Site Analysis, Page Speed, Link Analysis, and discovery and indexing checks.
Is Site Health the same as Website Readiness?
No. Site Health measures technical foundations such as metadata, speed, links, crawl signals, and indexing configuration. Website Readiness evaluates how clearly representative page evidence communicates the business and supports AI interpretation.
Does Site Health crawl my entire website?
You can run a detailed page check or a capped same-domain site sample. The result identifies its tested scope and should not be interpreted as unseen pages.
Does a high Site Health score guarantee better rankings?
No. Technical health can remove important barriers, but it does not guarantee search rankings, AI mentions, citations, traffic, or business outcomes.
Site Health