SEO Page Analyzer
Enter a public URL and our server fetches it once, exactly as a crawler would receive it. You get one report covering the response, indexing signals, tags, headings, links, images and structured data — each item marked pass, warning or issue.
How to use the SEO Page Analyzer
Enter the URL
Use the full address of the page you want to review, including https://. You can also paste HTML to review a staging page.
Let our server fetch it
The request follows up to 10 redirects and records the status, headers, response time and page size. If the fetch fails, you'll see why — never a guessed result.
Work through the checklist
Start with items marked as issues (indexing, status, title), then warnings. Each line links to a dedicated tool for a deeper look.
Fix, then re-run
Publish your changes and analyse the page again to confirm the new HTML is being served.
What it checks
- Response
- HTTP status of the final URL, number of redirects followed, total response time, HTML size, HTTPS and whether the fetch was truncated at 2 MB.
- Indexing signals
- Meta robots, X-Robots-Tag header, canonical tag(s) and whether the canonical points to this URL.
- Titles and snippets
- Title and meta description presence, length and approximate pixel width; duplicate title tags.
- Structure
- H1 count, heading level jumps, word count of visible text, html lang and viewport.
- Links and images
- Internal and external link counts, nofollow/sponsored/ugc usage, the most-used anchor texts, generic and empty anchors, and images without alt attributes.
- Readability
- An estimated Flesch reading ease score and average sentence length for the visible text (English only).
- Sharing and markup
- Open Graph and Twitter/X card basics, hreflang alternates, JSON-LD blocks and their @type values (with a parse check).
Interpreting the results
The report opens with a short summary — how many checks passed, how many produced warnings and how many look like real issues — followed by grouped details. There's deliberately no single “SEO score”: a number out of 100 would hide which problems matter. A missing meta description and an accidental noindex are not the same size of problem, so they're flagged differently.
- Issue (red) — something that commonly stops a page being indexed or understood: a 4xx/5xx response,
noindex, a canonical pointing elsewhere, no title. - Warning (amber) — worth fixing, but not blocking: long titles, several H1s, images without alt text, JSON-LD that doesn't parse.
- Pass (green) — the check found what it expected.
Response time is measured from our server to the site, once. It is not a Core Web Vitals measurement and will differ from what visitors experience.
Detected marks facts read directly from what you provided or what our server actually received. Guidance marks general recommendations based on those facts — rules of thumb, not guarantees or search engine requirements.
Practical guidance
Use this analyzer as a first pass before spending time — or money — on a page. If you're about to build links to a URL, the most expensive mistakes are the ones the “Response” and “Indexing” groups catch: a target that redirects, returns an error or tells search engines not to index it. Those items mirror the target-page checklist on our PBN backlinks page, and they apply just as much to guest posts or a backlink package.
When a group needs more detail, open the dedicated tool: the Heading Structure Analyzer for the full outline, the Canonical URL Checker for conflicting declarations, the Internal Link & Anchor Text Analyzer for every link, or the Schema Markup Validator for JSON-LD. A realistic example: a service page shows a pass for status and title, but an issue for “canonical points elsewhere” — a template setting copying the homepage canonical onto every page. Fixing one template line resolves it across the site.
For the bigger picture of how page quality and links interact, read Link building fundamentals.
Limitations
- It analyses the raw HTML the server returns. Content, tags or links added by JavaScript after the page loads aren't seen.
- One page per run. It doesn't crawl your site, discover other URLs or compare pages with each other.
- Some sites block requests from data centres or automated clients. When that happens you'll see the real response (for example 403) or a friendly error — use Paste HTML instead.
- It can't tell you whether a page is indexed or how it ranks. That information only exists in search engines' own tools, such as Google Search Console.
Frequently asked questions
Is this the same as a full site audit?
No. It reviews one URL in depth. Site-wide problems such as duplicate titles across pages or orphaned URLs need a crawler that visits many pages.
Why is there no overall score?
A single number hides what matters. We'd rather show that a page has one blocking issue and three minor warnings than turn that into, say, “72/100”.
Why does the page look different from what I see in my browser?
Your browser runs JavaScript and may be logged in or personalised. Our server sees the plain HTML response a crawler receives before any scripts run.
Which pages can it fetch?
Public http and https pages on standard ports. Local, private-network and reserved addresses are blocked for security, responses are capped at 2 MB and requests time out after 12 seconds.
Do you store the URL or page?
No. The page is fetched, passed to your browser for analysis and discarded. Nothing is logged against you.
Related tools
- Meta Tag Analyzer
List every meta and link tag in a page's head, with length checks and advice. - HTTP Status Code Checker
Live check of up to 10 URLs: status, full redirect chain, final URL and timing. - Heading Structure Analyzer
Map a page's H1–H6 outline and find missing H1s, skipped levels and empty headings. - Schema Markup Validator
Parse JSON-LD, find syntax errors and check common schema.org types for key properties.
More in On-Page SEO Tools · All 25 free SEO tools