Crawler information

SEOLZ-Bot

SEOLZ-Bot is the web crawler for SEOLZ. When you — or the SEO/agency team looking after your site — run a SEOLZ audit, this crawler reads your pages to check your search, AI-visibility, accessibility and security health. It obeys robots.txt, crawls at a polite rate, and never tries to evade a bot challenge.

SEOLZ-Bot is operated by SEOLZ.com (Sparta, Michigan) and is not affiliated with any other crawler that has a similar name.

How to identify SEOLZ-Bot

User-agent
SEOLZ-Bot/1.0 (+https://seolz.com/bot)
From these IPs
3.12.80.1318.190.136.247All SEOLZ traffic comes from these addresses. The second one is our accessibility renderer, a headless Chrome browser that identifies itself as SEOLZ-ADA.
Other SEOLZ user-agents
  • Mozilla/5.0 (compatible; SEOLZ-ADA/1.0; +https://seolz.com/bot) …Accessibility checks and rendered accessibility scans
  • Mozilla/5.0 (compatible; SEOLZ-FlowWatch/1.0; +https://seolz.com/bot) …Opt-in cart/checkout monitoring (never submits)
  • Mozilla/5.0 (compatible; SEOLZ-SecurityWatch/1.0; +https://seolz.com/bot) …Security monitoring
  • Mozilla/5.0 (compatible; SEOLZ-Verify/1.0; +https://seolz.com/bot)Checking pages cited in AI answers
  • Mozilla/5.0 (compatible; SEOLZ-CompetitiveGap/1.0; +https://seolz.com/bot)Profiling pages AI engines cite (obeys robots.txt)
robots.txt token
SEOLZ-Bot
Behavior
The crawler obeys robots.txt · polite rate (at most 8 concurrent requests per site, slowing down when your server does) · read-only, never submits forms or places orders. Exceptions: accessibility checks also load a few standard pages directly — cart, checkout, search, login — even if robots.txt disallows them, because those pages are part of accessibility conformance, without submitting anything; opt-in checkout monitoring does the same. Only when the account holder opts in and provides test details do our accessibility checks sign in with those test credentials, or add one item to the cart so the checkout page can be tested. We never place an order.

Verify it's really us

Check the source IP. Genuine SEOLZ requests come only from the IP addresses above. Anything claiming to be SEOLZ-Bot from any other IP is not us — you can safely block it. We don't currently publish reverse-DNS hostnames, so the IP list is the way to verify.

Blocked us by mistake? Allowlist SEOLZ-Bot

If your firewall, CDN or security plugin is blocking us, your SEOLZ audit will come back empty. Add one allow rule below — an IP rule is the cleanest — and we'll be able to read your site. After you save it, click Re-test access on your site in SEOLZ.

Cloudflare

A Skip/Allow custom rule overrides Bot Fight Mode — this is the reliable fix for a bot-managed site.

  1. Dashboard → your domain → Security → WAF → Custom rules → Create rule.
  2. Match: IP Source Address is in 3.12.80.13, 18.190.136.247 (or: User Agent contains SEOLZ-Bot).
  3. Action: choose "Skip", then tick "All remaining custom rules".
  4. Under "More components to skip" enable Super Bot Fight Mode (and Bot Fight Mode).
  5. Deploy. If you use Super Bot Fight Mode, also set Definitely/Likely automated to not Block our IP.

AWS WAF

  1. Create an IP set with 3.12.80.13/32, 18.190.136.247/32.
  2. In your Web ACL add a rule that Allows requests from that IP set.
  3. Place it ABOVE any Bot Control, rate-based, or managed blocking rules so it evaluates first.

Akamai

  1. Add 3.12.80.13, 18.190.136.247 to your firewall / Bot Manager IP allowlist (whitelist).
  2. Or classify the SEOLZ-Bot user-agent as a known transparent/good bot so it isn't challenged.

Sucuri

  1. Firewall dashboard → Settings → Access Control → Whitelist IP Addresses.
  2. Add 3.12.80.13, 18.190.136.247 and save.

Wordfence

  1. Wordfence → All Options → Allowlisted IP addresses → add 3.12.80.13, 18.190.136.247.
  2. Wordfence → Rate Limiting: allow known crawlers, or raise the limit so a full crawl isn't throttled.
  3. Check Wordfence → Blocking that the SEOLZ-Bot user-agent isn't blocked.

robots.txt (all sites)

We always obey robots.txt. Even with a WAF rule, a Disallow will stop us.

  1. Make sure robots.txt doesn't disallow us. To be explicit, add:
  2. User-agent: SEOLZ-Bot
  3. Allow: /

Still stuck after allowlisting us? Contact us and we'll help.

Frequently asked questions

How do I identify SEOLZ-Bot?+

The SEOLZ-Bot crawler uses the user-agent SEOLZ-Bot/1.0 (+https://seolz.com/bot) and the robots.txt token "SEOLZ-Bot". Our specialized checks use user-agents that also contain "SEOLZ" and a link to seolz.com/bot. All SEOLZ traffic comes from the IP addresses listed on this page. The crawler obeys robots.txt, crawls at a polite rate (at most 8 concurrent requests per site, slowing down when your server does), and never submits forms. Accessibility checks also load a few standard pages (cart, checkout, search, login) directly, without submitting anything.

How do I verify a request is really from SEOLZ-Bot?+

Check the source IP. Genuine SEOLZ requests come only from the IP addresses listed on this page. Anything claiming to be SEOLZ-Bot from any other IP is not us, and you can safely block it. We don't currently publish reverse-DNS hostnames, so the IP list is the way to verify.

SEOLZ-Bot was blocked by mistake — how do I allowlist it?+

If your firewall, CDN or security plugin is blocking SEOLZ-Bot, your SEOLZ audit will come back empty. Add one allow rule using the recipe for your WAF or CDN — an IP allow rule is the cleanest — then click Re-test access on your site in SEOLZ.