Free SEO calculators
Choose a check, paste your evidence, and inspect the results below. Your inputs stay in this browser.
01 · PASTE, CHECK, DECIDE
SERP Snippet Audit
Measure an existing title and meta description for likely display fit, clarity and query placement.
What to paste: Your current title, meta description and target query.
Pixel fit is an estimate, not a Google rule or ranking prediction.
Ready when you are
Enter an existing title to see a transparent display-fit estimate and focused next steps.
How this check works · sources and limits
We measure text with Canvas using Arial (20px title, 14px description). The 580px/920px cutoffs are approximate desktop layout review heuristics, not Google limits. Google may rewrite either field. Characters and exact phrase occurrences are counts, not ranking factors.
Checked against published guidance on 21 September 2026. P0 = supplied input or indexing signal to inspect first; P1 = review; Note = context. No result guarantees rankings.
02 · PASTE, CHECK, DECIDE
Content + Heading Audit
Read your own page copy for scanability, heading sequence, topic placement and likely question coverage.
What to paste: Visible page copy or HTML, the main topic, and the questions your page should answer.
This flags visible patterns only. It never creates a keyword-density target.
See the structure, not a keyword score
Paste the existing page copy and the questions it should answer.
How this check works · sources and limits
Words are Unicode letter/number tokens. Scripts and styles are excluded. Heading skips mean an increase greater than one level. Question signals check exact words longer than three letters, excluding common question words; they cannot confirm semantic coverage. English reading ease estimates 206.835 − 1.015 × words/sentences − 84.6 × estimated syllables/words, clipped to 0–100. Syllables use vowel groups, so names and other languages reduce accuracy. There is no ideal word count or keyword density.
Checked against published guidance on 21 September 2026. P0 = supplied input or indexing signal to inspect first; P1 = review; Note = context. No result guarantees rankings.
03 · PASTE, CHECK, DECIDE
HTML SEO Health
Inspect source you paste for indexability signals, canonicals, headings, links, image context and metadata.
What to paste: Raw page HTML, intended URL, and whether the page should be indexable.
It cannot confirm headers, crawl status, rendering or index status unless you provide them.
Check the source you already have
This is a transparent page-source diagnostic, not an index-status or rank test.
How this check works · sources and limits
Checks inspect only pasted HTML: title, description, canonical count/URL, robots and Googlebot noindex/none, H1, viewport, document language, links and missing alt attributes. A canonical is a signal, and multiple H1s are not automatically a ranking defect. Missing tags are review points. HTTP headers, JavaScript rendering, live robots access and actual index status require separate verification.
Checked against published guidance on 21 September 2026. P0 = supplied input or indexing signal to inspect first; P1 = review; Note = context. No result guarantees rankings.
04 · PASTE, CHECK, DECIDE
Intent Collision Check
Compare two existing pages to see where their language and audience promise may overlap too much.
What to paste: Target topic plus the existing titles, headings and copy from both pages.
Editorial overlap is not proof of a Google cannibalisation issue.
Compare the promises, not just keywords
Use title, headings and copy from two pages that may be too similar.
How this check works · sources and limits
Phrase overlap = 100 × shared unique three-word phrases ÷ all unique three-word phrases (Jaccard similarity). Extracts shorter than three words use individual words. Opening-word overlap compares unique words in the first eight supplied lines; it does not inspect HTML structure. Topic signals count supplied topic terms present in each extract. Review levels of 35% and 60% are editorial triage choices, not industry ranking thresholds or proof of cannibalisation.
Checked against published guidance on 21 September 2026. P0 = supplied input or indexing signal to inspect first; P1 = review; Note = context. No result guarantees rankings.
05 · PASTE, CHECK, DECIDE
Sitemap + Robots Inspector
Check supplied robots.txt and sitemap XML for malformed URLs, duplicates, mixed hosts and obvious conflicts.
What to paste: Your current robots.txt and XML sitemap source.
This checks pasted files only; it does not fetch, crawl or validate a live server response.
Read the files before the crawler does
Use source from your existing robots.txt and sitemap XML.
How this check works · sources and limits
XML must parse with urlset or sitemapindex at its root. We count loc entries, exact duplicates, hosts and absolute HTTP(S) URLs. Mixed hosts prompt a review; cross-site submissions can be legitimate. Robots analysis selects Googlebot groups ahead of wildcard groups, merges equally specific groups, uses longest matching paths, and lets Allow win equal-length ties. Supports * and end-anchor $. This is a local approximation; percent-encoding, non-ASCII paths, live responses and server limits need verification. Sitemap index children are not fetched. A sitemap does not guarantee indexing.
Checked against published guidance on 21 September 2026. P0 = supplied input or indexing signal to inspect first; P1 = review; Note = context. No result guarantees rankings.
06 · PASTE, CHECK, DECIDE
Schema Markup Inspector
Parse pasted JSON-LD or page HTML for entity types, property review points and visible-content alignment.
What to paste: JSON-LD or full HTML, plus optional visible page text and URL.
Valid structured data does not guarantee a rich result.
Read the markup. Keep the claim honest.
Paste JSON-LD or source you own, then compare it with visible content.
How this check works · sources and limits
Parses JSON syntax, traverses nested entities and @graph, and recognises a context on the graph wrapper. Common property suggestions are not universal requirements. Repeated @id values can legitimately join the same entity. Visible-content checks use exact normalised text, so a mismatch only asks for human review. This is not a complete Schema.org vocabulary or rich-result validator.
Checked against published guidance on 21 September 2026. P0 = supplied input or indexing signal to inspect first; P1 = review; Note = context. No result guarantees rankings.
FOUND A CLUE?