Testing · Discoverability

Technical SEO testing

The technical half of SEO: the things that stop a page being indexed, shared or understood, all of which are invisible when you look at the page yourself.

What it checks

  • Indexability — the meta robots tag and the X-Robots-Tag response header. A noindex that escaped from staging is the single highest-value finding here, and the header version is the one people forget exists.
  • robots.txt — reachable, and not disallowing everything.
  • Sitemap — taken from the Sitemap: directive in robots.txt if one is declared, otherwise looked for at the conventional location.
  • Title and meta description — present, and within sensible length bands you can adjust.
  • Canonical URL and <base href>.
  • Open Graph and Twitter card tags — what a link to your page looks like when somebody shares it.
  • JSON-LD structured data — present, and actually valid JSON.
  • Document language and h1 count.
Title length
10–60 characters
Description length
50–160 characters
Reads
Server HTML only
Executes JavaScript
No

Duplicates are counted rather than overwritten. Two <title> tags or two canonical links is itself the defect, and a parser that keeps the last one it saw reports a clean bill of health on a genuinely broken page.

Not measurable is not the same as failing

This check reads the HTML your server sent and does not run JavaScript. On a client- rendered application, that HTML often contains an empty <head> and a root div.

When that happens the result says so. The page is reported as not measurable from static HTML, with a warning explaining why — not scored zero out of a hundred. A React app has not failed an SEO test; it has been asked a question this tool cannot answer, and telling you that is more useful than a confident wrong number.

It also happens to be the finding that matters. If your head is empty in the server response, that is roughly what a crawler saw too.

Findings, not a vanity score

Each run produces a list of findings with a severity, and a score derived from them. The score is there for tracking movement between runs; the findings are what you act on.

As with the other checks, the run only fails against a contract you set — a minimum score you chose. Left at the default it reports without failing, so adding it to a suite does not immediately turn everything red.

Pairs well with

PerformanceLighthouse scores and Core Web Vitals for mobile and desktop, with prioritised opportunities and the estimated saving from each one.Exposure scanFinds what should not be reachable: exposed .git and .env files, directory listings, public source maps and mixed content. Reachability only - it never attempts authentication.Broken linksFollows the links on a page and reports what is dead. Your own broken link fails the run; someone else's is reported without failing it.All testing checks

Test a page before you ship it

Scheduled monitoring is free on every plan, on unlimited websites. No credit card.