SEO Checker
Audit a public webpage’s technical SEO with verifiable evidence and clear limitations.
Check what the returned HTML actually says
Objective technical checks with evidence. No ranking predictions or content-quality claims. JavaScript is not rendered and linked pages are not crawled.
Source-HTML snapshot only. No JavaScript rendering, full-site crawl, backlink analysis, Core Web Vitals, broken-link crawl or Google rich-result validation. Results do not guarantee indexing or rankings. Save as PDF uses your browser’s print dialog.
What is an SEO checker?
An SEO checker inspects a webpage for technical signals that search engines and browsers can read. isMust fetches public source HTML, robots.txt and limited sitemap resources and reports the evidence. It does not predict rankings or confirm Google indexing.
What this audit checks
Checks cover HTTP status, redirects, indexing directives, canonical, title, meta description, headings, language, viewport, charset, Googlebot robots rules, sitemap discovery, JSON-LD syntax/types, social tags, links and image alt attributes. Optional signals do not lower the score.
What this audit does not check
V1 does not render JavaScript, crawl an entire site or sitemap, check all link destinations, measure Core Web Vitals, analyze backlinks or judge content quality. Source HTML can differ from a browser-rendered page. Challenge pages and suspected incomplete shells receive limited confidence with no score.
Technical SEO vs content SEO
Technical checks describe accessibility and machine-readable signals. They cannot establish whether content is accurate, original, helpful or competitive. A high technical score is not a guarantee of traffic, rankings or indexing.
Why canonical tags matter
A canonical tag identifies a preferred URL for duplicate or similar content. It is a hint, not a directive. A canonical different from the fetched URL may be intentional; verify the destination rather than blindly changing it.
Why robots.txt matters
robots.txt controls crawler access. It does not itself prevent a URL from appearing in search results. A noindex directive must be accessible to the crawler to be processed. This checker evaluates Googlebot rules for the final URL but cannot verify a search engine’s actual crawl.
Titles, headings and descriptions
Titles and main headings describe a page’s topic. A description can inform a search snippet, but search engines may rewrite it. Length measurements are informational rather than fixed pass/fail thresholds. Empty alt can be correct for decorative images.
Score and privacy
The visible weighted checks total 100 points before exclusions: HTTP 20, indexing directives 20, canonical 10, title 10, H1 10, Googlebot access 10, HTTPS 10, description 4, viewport 3, language 2 and heading hierarchy 1. N/A checks are excluded from the denominator. Submitted URLs go to the isMust server; no intentional URL history is saved. Hosting providers may process request metadata/logs. Analytics does not receive inspected URLs, hostnames or page content. Avoid URLs containing sensitive tokens.
Resource limits
Only public HTTP(S) pages on standard ports are supported. The shared safe fetcher validates DNS and pins connections at every redirect. Limits include four redirects, eight seconds per resource chain, 25 seconds overall and 2 MiB of decoded HTML. Robots and sitemap resources have smaller caps. No remote scripts or image resources are executed or fetched.
How to use
- Enter a public webpage URL and select Check SEO.
- Review confidence first, then the technical score, evidence and recommended actions.
- Use Print report or Save as PDF to open your browser’s print dialog. Reset clears the current report.
Frequently asked questions
Does this check guarantee Google rankings?
No. It reports a bounded source-HTML snapshot and technical signals, not rankings, content quality or confirmed index inclusion.
Why is my report marked limited confidence?
Bot challenges, blocked responses, tiny HTML and JavaScript shells may not represent the page visitors see. The checker withholds the score and marks content-related checks N/A rather than treating missing content as a normal failure.
Is JSON-LD reported as Google-valid?
No. Syntax and detected types are inspected, not complete schema conformance or Google rich-result eligibility.
Are audited URLs sent to analytics?
No. Custom events allow only severity counts, a broad score bucket and confidence. The server fetches the submitted URL temporarily; hosting infrastructure may process request metadata/logs.
Does Save as PDF create a PDF on the server?
No. It opens your browser’s print dialog; choose Save as PDF where supported. The report stays on the current page until reset or navigation.