Skip to content

Reference

Every check, and the fix for it.

13x runs 113 deterministic checks against a live product. Each one has a page here: what goes wrong, what it costs, how the rule decides, and the change to make. 76 of them are written separately for a specific framework, because a sitemap in Next.js and a sitemap in WordPress are not the same instruction.

Registry version 2026-07-30. The full rule registry is published with weights and scope, and is downloadable as JSON.

Discoverability

12

Whether a crawler can find, follow and index the site at all. These are the highest-severity checks in the set: a leftover noindex or a robots.txt that disallows everything makes every other finding irrelevant.

Why is my site not showing up in search →

Metadata

10

What a search result actually shows. Titles and descriptions are per page, and the failure mode is almost always one value set in a layout and never overridden per route.

Title tag and meta description problems →

AI visibility

13

Whether answer engines can reach your content, read it without JavaScript, and quote it once they have. This is the group no classic SEO tool covers, and the one where the fixes are cheapest relative to what they change.

How to be visible in AI search →

Social & sharing

9

What your link looks like when somebody shares it. Every failure here is silent — the card renders wrong on somebody else's screen and nobody tells you.

Open Graph and link preview problems →

Structured data

3

The markup that makes a result eligible for anything beyond a blue link, and increasingly how an answer engine decides what your product is.

Structured data and schema.org problems →

Legal & privacy

12

Presence and reachability of the legal pages, and whether tracking fires before consent. 13x detects; it does not give legal advice and does not generate legal text.

GDPR, Impressum and consent problems →

Accessibility

11

The defects that make a page unusable with a screen reader or a keyboard, plus the European Accessibility Act statement obligation that has applied since June 2025.

Web accessibility problems →

Security

11

Read from response headers and markup already fetched — never by probing. These are one-line changes with no downside, which is why their absence is usually an oversight rather than a decision.

Security header problems →

Performance

10

Causes rather than guessed metrics: what is blocking the render, what is uncompressed, what is shifting the layout. Every one is measured from the response, not estimated from a score.

Web performance problems →

Conversion

8

Whether a visitor who is convinced can act, and whether you would know if they were not. Advisory rather than scored hard — several of these are legitimate choices.

Landing page conversion problems →

Email deliverability

4

SPF, DKIM, DMARC and MX, read from DNS. The answers are definitive rather than heuristic: either the record is there or it is not. You launch, you send a welcome email, it lands in spam — and nothing tells you.

Email deliverability problems →

Basics

10

Transport and domain health. Nothing above matters if the certificate expired this morning or the registration lapses next month.

HTTPS, certificate and domain problems →

Run all of them against your own site

One URL, about 30 seconds, no account. You get every failing check with its evidence and the fix written for the framework we detected.

No signup. Results in 30 seconds.