SEOCheckerBot

Why did SEOCheckerBot visit my site?

Someone pasted a URL from your site into the free checker at seoanalysischecker.com. SEOCheckerBot fetched that one page, plus a few standard site files, to generate an SEO report. It does not crawl your site, does not follow links recursively and does not revisit on a schedule.

How does it identify itself?

Mozilla/5.0 (compatible; SEOCheckerBot/1.0; +https://seoanalysischecker.com/bot)

Every request carries that string, including the probes below. If a hit in your logs claims to be SEOCheckerBot but behaves differently — crawling many pages, ignoring the request list, arriving in bursts — it is not us.

Which URLs does it request?

A single audit is a fixed, short list of requests. Written out in full, so you can match it against your access log:

• The exact URL that was submitted.
• /robots.txt — to report crawl rules and find the sitemap.
• The sitemap URL declared in robots.txt, if there is one.
• /llms.txt — for the AI-visibility part of the report.
• One URL that is meant to 404, of the form /__seoanalysischecker_404_probe_<timestamp>__. If you are wondering why a bot requested an obviously fake path, this is it: the report checks whether missing pages return a real 404 rather than a soft 200.
• The http:// version of the root, without following redirects, to test the HTTPS redirect.
• A HEAD request to the www or non-www variant of the host, to test host canonicalisation.

How much load does it put on a site?

• One page per user request — no recursive crawling, no scheduled revisits.
• At most seven requests per audit, inside a 20-second total budget.
• Repeat checks of the same URL within 24 hours are served from cache, not re-fetched.
• Only ports 80 and 443.

Does SEOCheckerBot obey robots.txt?

It reads your robots.txt on every audit and the report states whether the submitted URL is allowed for its user-agent. But a check is a single fetch that a person explicitly asked for, and it is not currently withheld when robots.txt disallows it. We would rather say that plainly than imply a block that does not happen.

How do I block it?

Block the user-agent at your server, WAF or CDN — that stops the fetch outright. For example, in nginx:

if ($http_user_agent ~* "SEOCheckerBot") { return 403; }

You can also state the preference in robots.txt, which we report but do not currently enforce:

User-agent: SEOCheckerBot
Disallow: /

Blocking only prevents people from running SEO reports on your pages with this tool. It has no effect on how search engines or AI crawlers see your site. Questions or a removal request? See the contact section.