Website Health Snapshot
Analyze any URL for title, meta description, Open Graph, Twitter Cards, canonical, favicon, robots.txt, sitemap.xml, HTTPS, security headers and SEO recommendations.
How to use Website Health Snapshot
- 1Enter a URL
Type any public http or https address — the scheme is optional.
- 2Run the snapshot
Easutil fetches the page server-side and reads its HTML, headers, robots.txt and sitemap.xml.
- 3Review the checks
Core SEO tags, Open Graph, Twitter Cards, crawlability and security headers are each marked pass, warn or fail.
- 4Fix and export
Work through the prioritised recommendations, then copy or download the JSON report to share with your team.
Common use cases
- Pre-launch SEO checklist for a new site
- Debugging why a shared link shows no preview image
- Auditing a competitor's on-page setup
- Verifying robots.txt and sitemap.xml are live after a deploy
Website Health Snapshot FAQ
What does the Website Health Snapshot check?
Page title and length, meta description, canonical URL, H1 headings, viewport, html lang, favicon, image alt coverage, robots meta, Open Graph and Twitter Card tags, JSON-LD structured data types, robots.txt, sitemap.xml, HTTPS and six security headers.
How is the health score calculated?
Each failed check contributes one recommendation; the score is the share of the twenty tracked checks that passed, so a clean page scores 100%.
Can it scan a page behind a login or on localhost?
No. Only publicly reachable http and https URLs can be fetched; private, local and loopback addresses are blocked.
Why do security headers show as warnings?
Headers such as Content-Security-Policy and Strict-Transport-Security are strongly recommended but not required for a page to work, so a missing one is flagged as a warning rather than a hard failure.
Looking for something similar? Browse all developer tools on Easutil →