RunTheTests
/

SEO tools

17 tools that run in your browser. Nothing to install, nothing uploaded.

On-page SEO checks that measure what search engines actually use. Title and description length are checked by estimated pixel width, not just character count, because that is what gets truncated in results — a line of narrow letters fits where wide ones do not. These are honest guides rather than promises: the pixel estimate is an approximation, and a meta description is a suggestion a search engine frequently overrides with its own snippet.

Titles and descriptions are cut by pixels, not characters

Every character-count rule for titles is an approximation of the real constraint, which is a pixel width in a proportional typeface. A title of sixty narrow characters fits comfortably where sixty wide ones are truncated, so the same count passes for one page and fails for another. The checks here estimate rendered width and show you where the cut falls, which changes what you do about it: you move the clause carrying the reason to click in front of the boundary rather than shaving characters off the end. The estimate is close, not exact — search engines render in their own fonts and adjust over time.

What you actually control, and what you only suggest

A title tag is usually respected. A meta description frequently is not — search engines rewrite it from page content whenever they judge their own snippet a better answer to the query, and that is normal rather than a fault to chase. Canonical tags are a hint that can be overruled by conflicting signals elsewhere on the site. Understanding which of these are instructions and which are suggestions saves a great deal of time: the productive work is making the page genuinely answer the query, and the metadata is how you frame an answer that is already there.

Structured data fails silently, which is why it needs checking

Invalid JSON-LD does not produce an error anywhere you would see it. Search engines parse the block, find a missing required property or a wrong type, discard it, and index the page as though the markup were never there — so the rich result simply never appears and nothing tells you why. The validator here checks the shape of the common types that actually produce rich results, and the generator emits markup that is valid to begin with. The other half of the rule is that structured data must describe what is genuinely on the page; markup that claims content a visitor cannot see is a manual-action risk, not a shortcut.

Headings and alt text are read by more than crawlers

A heading outline is the document structure a screen reader navigates by, which is why skipping from an h2 to an h4 matters even though nothing visibly breaks — the levels are a hierarchy, not a set of font sizes. Alt text has the same dual audience: it is what a blind reader gets instead of the image, and what a search engine uses to understand it. The checker flags the two failure modes that are equally common, an image with no alt attribute at all and one whose alt text says nothing useful, because "image1.jpg" and "photo" are technically present and practically empty.

Frequently asked questions

How long should a title tag be?

The real limit is pixel width in a proportional font, not a character count, which is why the usual "60 characters" rule works for some pages and truncates others. Roughly 580 pixels is the practical ceiling on desktop results. The useful response to a title that is too long is to move the words carrying the reason to click in front of the cut, rather than trimming characters off the end until a counter turns green.

Why did Google ignore my meta description?

Because a description is a suggestion, not an instruction, and search engines rewrite it whenever they judge their own snippet a better answer to the specific query. This is normal and happens for a large share of results, especially long-tail ones. It is not a fault to chase — writing a good description is still worthwhile for click-through when it is used, but a page ranks on whether it answers the query, not on the description you attached.

My structured data looks fine but I get no rich result. Why?

Invalid JSON-LD fails silently: the parser finds a missing required property or a wrong type, discards the block, and indexes the page as though it were never there. Nothing surfaces an error to you. Beyond validity, rich results are never guaranteed even for correct markup — it makes a page eligible, and the search engine still decides. Markup describing content that is not visible on the page is a manual-action risk rather than a shortcut.

Does skipping a heading level actually matter?

Yes, though not for the reason people assume. Heading levels are a document outline that screen reader users navigate by, so jumping from h2 to h4 leaves a gap in the structure they move through even when nothing looks wrong. Levels are a hierarchy, not font sizes — style a heading however you like with CSS and keep the sequence intact underneath.