SEO Tools

Audit any URL for on-page problems, then generate what it needs: meta and Open Graph tags, JSON-LD schema, a robots.txt, and keyword frequency for your copy.

5 tools in this category.

SEO Analyzer
Audit any page for on-page SEO issues in seconds — titles, meta tags, headings, canonicals, images, structured data and indexability, scored out of 100.
Meta Tag Generator
Generate a complete set of head tags — description, canonical, Open Graph and Twitter Card — from a handful of fields.
robots.txt Generator
Build a valid robots.txt from a list of paths, with a sitemap declaration and a warning before you block anything important.
Schema Markup Generator
Generate valid JSON-LD structured data for the six schema types that actually earn rich results.
Keyword Density Checker
Count word and phrase frequency in any text, with stop words removed and n-grams up to three words.

About SEO Tools

Five tools that follow the order the work actually happens in: audit first, then fix. The SEO Analyzer fetches a URL and reports what is wrong with it — title and description length against what Google renders, heading structure, canonical and robots directives, image alt text, structured data. The other four generate the things it tends to find missing: the Meta Tag Generator for title, description and Open Graph, the Schema Markup Generator for JSON-LD, the robots.txt Generator, and the Keyword Density Checker for copy that has drifted into repetition.

The analyser is the one tool on this site that is not purely client-side, and the reason is the same-origin policy: a browser cannot fetch a page from another domain, so the request is made from our server. Everything else in this category runs locally.

Two findings are worth understanding before you act on any report. Title and description length are measured in rendered pixels rather than characters, because that is what Google truncates on — roughly 580 pixels for a title, and a description limit that varies with device. Counting characters is a rough proxy that misclassifies both wide titles full of capitals and narrow ones full of thin letters. And a noindex directive, a 4xx status or a missing title caps the score no matter what else is right, because each of those stops a page ranking outright, so a high score beside one would be misleading.

Frequently asked questions

Why does the analyser need a server when everything else here runs in my browser?

Because the same-origin policy forbids a browser from fetching a page on another domain, which is exactly what auditing a URL requires. The request therefore comes from our server. Every other tool in this category — meta tags, schema, robots.txt, keyword density — runs entirely in your browser, since those transform text you supply rather than fetching anything.

Why measure titles in pixels instead of characters?

Because Google truncates on rendered width, not character count. A title in capitals or full of wide letters is cut off well before one made of narrow characters at the same length, so a character limit misjudges both directions. Measuring the pixel width of the actual string against roughly 580 pixels predicts what will really appear in the results page.

Is keyword density still a ranking factor?

Not in any direct sense, and it has not been for many years — search engines model topics and synonyms rather than counting repetitions. The checker is useful as a diagnostic rather than a target: unusually high density is a reliable signal that copy reads badly, and unusually low density for the term a page is meant to be about often means the page never quite says what it is about. Write for readers and use it to catch drift.

The generated JSON-LD is valid but no rich result appears. Why?

Valid markup makes a page eligible for a rich result; it does not entitle it to one. Google decides case by case, and eligibility also depends on the content type, whether the markup describes what is genuinely visible on the page, and site-level quality signals. Confirm the markup parses in the Rich Results Test, make sure every field it declares is actually present on the page, then expect a delay while the page is recrawled.

Other categories