Custom checks
The checks only your site needs
Your analytics snippet, your consent banner, the staging domain that must never ship: four kinds of rule, checked on every page.
- kinds of rule
- 4kinds of rule
- of every crawl
- Every pageof every crawl
- effect on the health score
- 0effect on the health score
- rules belong to one site
- Per siterules belong to one site
Four kinds
Contains- the page must contain this text
The analytics snippet, the consent banner, the schema block your legal team asked for.
Absent- the page must not contain this text
A staging domain, a placeholder like “lorem ipsum”, an old tracking script you thought was removed.
Meta tag required- this meta or Open Graph tag must be present
The one your CMS drops on templated pages, and which nothing else notices until a link is shared.
Pattern- a regular expression, screened before it is accepted
For the cases the first three cannot express. Capped in length and refused if it has the shapes that blow up.
Why they do not touch the score
A score that anything can move is a score that means nothing. Yours is comparable to your own history and to a competitor audited with the same checks - and a rule about your analytics snippet is comparable to neither.
So a custom finding behaves like every other finding except in the arithmetic: it is in the list, on the page it was found on, markable as done or ignored, and in the report. It simply does not move the number at the top.
What people actually write
The tag that keeps disappearing
A canonical, an Open Graph image, a hreflang - the one your CMS drops on a template nobody reviews.
The thing that must never ship
A staging hostname, a debug flag, placeholder copy. Cheap to check on every page, expensive to find in production.
The snippet that must be everywhere
Analytics, consent, a conversion pixel. 'It is on all the pages' is a claim; this is the check.
The house rule
Whatever your team agreed and nobody enforces. A rule makes it visible on the next scan instead of at the next argument.
Written once, checked on every page, for as long as it matters
A rule is part of the site, not part of a scan: it runs on every crawl until you switch it off, and it appears in reports beside the findings everyone else’s crawler would have found.
Questions
- No, and that is deliberate. The score is a versioned, comparable number - comparable to your own history and to a competitor's site. A rule like 'every page must carry our analytics snippet' is a real thing to check and not an SEO fact, so it appears in the findings list, can be marked done or ignored, and is excluded from scoring.
- No. A rule is evaluated while the page's HTML is in memory during a crawl, and we do not store the HTML afterwards - so a new rule takes effect on the next scan rather than pretending to know what an old page contained.
- It is bounded rather than impossible. A rule reads at most the first 200 KB of a response, patterns are capped at 200 characters, and the shapes that cause catastrophic backtracking - nested quantifiers, backreferences - are refused at the form with a message. A rule that spends too long on one page is dropped for the rest of that crawl and says so on the rule.
- Your choice, per rule. Off by default, because most of what people check for is markup they do not control the casing of.
Start free
One site and 100 credits - up to 200 pages a scan, about 5 scans, and the whole report. No card. Paid plans add more sites, bigger crawls and the AI rewrites.