SEO Auditor

How to use this SEO auditor

Paste any public URL.
Click "Analyze" to run a full on-page audit.
Review the score and each check to find what to fix.

How is the score calculated?

Ten on-page factors are checked, including title and meta description length, a single H1, HTTPS, a mobile viewport tag, Open Graph tags, image alt text coverage, canonical tag, word count and robots indexing rules. Each contributes a fixed weight toward the 100-point score.

Why does this need a server step?

Browsers can't fetch arbitrary third-party websites directly due to CORS restrictions, so this request is relayed through OmniDeck's own backend before being analyzed.

Does this store or share the URLs I analyze?

The URL is fetched server-side just to relay the page's HTML back to your browser for analysis — it isn't logged or stored beyond that single request.

Can I audit a page that isn't published yet?

No, the URL must be publicly accessible on the internet — pages behind a login or only on your local machine can't be fetched.

What this on-page checklist actually measures

This tool checks ten specific on-page technical factors — title length, meta description length, H1 presence, HTTPS, a mobile viewport tag, Open Graph tags, alt text coverage, a canonical tag, word count, and robots indexing rules — and combines them into a single weighted score. These are real, well-documented on-page SEO fundamentals, but they're a small, checkable subset of what actually determines search rankings, which involves hundreds of signals Google has never fully disclosed, many of which (like backlink quality, user engagement signals, and topical authority) simply can't be measured by fetching and parsing a single page's HTML.

On-page, off-page, and technical SEO are three different things

SEO work is usually grouped into three categories, and this tool covers exactly one of them well. On-page SEO is what's directly controllable within a page's own HTML — the checks this tool runs. Off-page SEO covers factors external to the page itself, primarily the quantity and quality of other sites linking back to it, which shapes a domain's perceived authority and can't be assessed by looking at the page alone. Technical SEO overlaps partly with on-page but extends further into site-wide infrastructure — page load speed, Core Web Vitals, crawl budget, site architecture — some of which this tool touches on (HTTPS, mobile viewport) and much of which it doesn't measure at all (actual load time, JavaScript rendering behavior, server response time).

Why title and meta description length rules are guidelines, not hard limits

Search engines don't actually enforce a fixed character count for titles and descriptions — what they truncate is based on pixel width in the search results display, which varies by device, font, and how many wide characters (like "W" or "M") versus narrow ones (like "i" or "l") a title happens to contain. The commonly cited "50-60 characters for titles, 150-160 for descriptions" guidelines are useful approximations based on average character width, not an exact technical rule, which is why two titles of the same character count can truncate differently in an actual search result. Staying safely under these approximate limits is still good practice — it's just worth knowing the underlying constraint is pixel width, not the character count itself.

A perfect score doesn't guarantee rankings

A 100/100 score here confirms a page has its on-page fundamentals in order, which removes some genuinely common obstacles to ranking well — but it's a compliance checklist, not a ranking predictor. Two pages can both score 100 on every on-page factor this tool checks and still rank completely differently, because actual search rankings weigh content quality and relevance to the specific query, backlink profile, domain trust built over time, user engagement signals, and dozens of other factors this on-page snapshot has no way to see. Treat a high score as "the easy, controllable fundamentals are handled," not as a prediction of search position.

Limitations of this tool

This tool analyzes a single URL as a one-time snapshot of its raw HTML, fetched server-side to work around browser CORS restrictions — it doesn't crawl an entire site, doesn't measure page load speed or Core Web Vitals, and doesn't check backlinks or domain authority, all of which are significant ranking factors outside what a single-page HTML check can capture. It also analyzes the HTML as initially delivered by the server, so content that's added or modified by client-side JavaScript after the page loads (common on heavily JavaScript-rendered sites) may not be reflected in the analysis, since this tool doesn't execute JavaScript the way a browser or Google's own renderer would.