Blocked our scanner? Here's how to let it in.
If you ran the free Creator Site Scan — or asked us for a Full Site Report — and got "blocked" instead of a score, nothing is wrong with your site. Your bot protection did exactly its job. This page is the fix: what our scanner is, why it got stopped, and the two-minute allowlist change that lets it through.
Meet the scanner
Our scanner is called HonedSignalBot, run by Honed Signal. It fetches public pages only — the same pages any visitor can open — and checks their technical health: page titles, canonical tags, broken links, and whether a sitemap exists. That is the whole list.
It identifies itself honestly, with this exact user-agent string on every visit:
HonedSignalBot/1.0 (+https://honedsignal.com/)
What it never does: log in, submit forms, create accounts, or bypass paywalls or bot checks. If a site stops it, the scan reports "blocked" and ends. It does not retry in disguise, rotate identities, or pretend to be a browser.
One name, everywhere: the free scan on this site and the Full Site Report use this same scanner and this same user-agent string. The allowlist steps below match on the word HonedSignal — one rule lets both in.
Why the scan came back "blocked"
Bot protection — Cloudflare's is the one we meet most — treats unknown bots as threats by default. That's the safe default, and it's the protection working as intended. Our scanner doesn't pretend to be a person's browser, so it gets the "Just a moment…" challenge page or a flat 403 instead of your site.
The fix is to tell the protection that one named guest is expected: an allowlist rule for our user agent. It takes about two minutes, and it can be undone in one click.
If your site is on Cloudflare
- Log in to your Cloudflare dashboard and select your site.
- Go to Security → WAF → Custom rules, then Create rule. (On the newer dashboard layout this lives under Security → Security rules → Create rule → Custom rules — same rule, new hallway.)
- Name it something like Allow Honed Signal scanner.
- Under When incoming requests match: set Field to User Agent, Operator to contains, and Value to HonedSignal. That one word is the scanner's name, so the rule matches its full user-agent string.
- Under Then take action: choose Skip, and tick the components your plan offers — Super Bot Fight Mode rules, WAF Managed Rules, Rate Limiting rules. If your plan doesn't offer Skip, choose Allow instead: that gets the scanner past the firewall rules, though it can't excuse it from Super Bot Fight Mode (see the notes below).
- Drag the rule to the top of your custom rules list — rules run in order, and a blocking rule above it wins — then click Deploy.
Free plan, Bot Fight Mode on? Cloudflare's free Bot Fight Mode can't be skipped by any custom rule — Cloudflare doesn't allow exceptions to it. If it's switched on and it's the thing stopping the scan, the choices are turning Bot Fight Mode off, or moving to a paid plan, where Super Bot Fight Mode does honor the Skip rule above.
Paid plan, Super Bot Fight Mode? It's configured under Security → Bots, but it has no per-bot guest list of its own. The Skip custom rule in the steps above is Cloudflare's own documented way to excuse one named tool — labels vary a little by plan and dashboard version, but the rule itself is the same.
Other setups: hosts, firewalls, and security plugins
Any system that filters visitors by user agent can make the same exception. Hand it this exact string:
HonedSignalBot/1.0 (+https://honedsignal.com/)
- WordPress security plugins (Wordfence and similar): look for an allowlist or whitelist for user agents or bot rules in the firewall settings, and add the string above. Matching just HonedSignal is enough — it's the name both the free scan and the Full Report use.
- Host firewalls and ModSecurity setups: the setting may be buried or support-only. Paste the string to your host's support team and ask them to allow that user agent through the firewall — it's a routine request, and they will know where it goes.
- Another CDN or firewall: same idea — an allowlist entry for the user agent, wherever that product keeps its bot rules.
A word about robots.txt
Our scanner does not read robots.txt. So editing yours won't let the scanner in — and robots.txt isn't what kept it out, either. robots.txt is a notice board for crawlers, not a lock. The lock is your firewall or bot protection, and the allowlist rule above is the key.
Done? Run the scan again
Once the rule is deployed, re-run the free scan — it should come back with a score instead of "blocked". If you've ordered a Full Site Report, email us and we'll re-run the full sweep; one free re-scan is already part of every report.
For the cautious
- It's reversible. The rule can be deleted in one click, any time. Nothing about it is permanent.
- It's visible. Every one of the scanner's visits appears in your logs under its real name — no disguises, so you can see exactly what it fetched and when.
- It's narrow. The rule matches one named user agent on public pages — not a network, not a company, not a back door.
- One honest caveat: a user-agent string is a name tag, not an ID card — anything can claim a name. That makes UA allowlists a good gate for a scanner that only reads public pages, and a bad lock for anything private. Don't use one to protect pages that need real security.