AlrebroBot

AlrebroBot is a small scanner run by Alrebro, an SEO and AI-visibility agency. It reads a public web page and reports on things like the title, headings, structured data, speed and whether AI search crawlers are allowed in.

It does not roam the web. A scan happens only when a person asks us to check a specific site — usually the site's owner, using the free audit on alrebro.com/audit, or a client scanning their own site from their dashboard.The free audit is limited to 3 scans per day from one connection and 1 scan per website per day.

It never hides. You'll see one of two user agents, and both point back to this site:

• AlrebroBot/1.0 (+https://alrebro.com/bot)— used when a page needs a real browser to load, for example when a plain request is met with a “verifying your browser” check.
• AlrebroSiteCheck/1.0 (+https://alrebro.com/audit) — used for ordinary page, robots.txt and sitemap requests.

We run on shared cloud infrastructure, so our requests don't come from a fixed IP range we can publish. The user agent is the identifier.

• The page that was requested (usually your home page), plus /robots.txt and your sitemap.
• A handful of your other public pages on deeper scans — never more than the scan's page limit, and fetched a few at a time, not in a flood.
• It only sends GET (or HEAD) requests. It does not log in, fill in or submit forms, add anything to a cart, or change anything on your site.

For any page beyond the one we were asked to scan, AlrebroBot follows your robots.txt. It obeys rules written for either AlrebroBot or AlrebroSiteCheck. The one exception is the exact page a person asked us to check: that single page is read even where robots.txt disallows it, because the person who asked is the one entitled to see how it looks to a scanner.

To keep us out of the rest of your site:

User-agent: AlrebroBot
Disallow: /

User-agent: AlrebroSiteCheck
Disallow: /

• Solve or bypass a CAPTCHA, Turnstile or other human-verification step. If a check needs a person, the scan stops and says so.
• Pretend to be Googlebot, GPTBot, ClaudeBot, PerplexityBot or any other crawler. It only uses the names above.
• Use stealth plugins, spoofed browser fingerprints, hidden automation flags or rotating proxies to look like a visitor.
• Keep retrying a site that said no. A blocked method is recorded as blocked, and the report tells the site owner what we could and couldn't verify.

Services like Cloudflare, Akamai or DataDome sometimes show AlrebroBot a challenge instead of your page. When that happens our report marks the affected checks as unverified — not failed — and it does not show a made-up score.

It's also worth knowing that the same rule that stops a scanner can stop AI search crawlers (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot), which generally can't pass a challenge either. If you want AI assistants to be able to read and cite your site, check your bot-protection logs for those crawlers being challenged.

To let AlrebroBot scan you, add an allow rule for requests whose user agent contains AlrebroBot or AlrebroSiteCheck— in Cloudflare, a WAF custom rule with the action “Skip” for those user agents. A user agent can be copied by anyone, so allow it only as far as you're comfortable with, and remove the rule when you're done.

Tell us through the contact pagewith your domain and we'll make sure it doesn't visit again.