How SeoraBot crawls, identifies itself, and how to opt out.
Seora audits read publicly served pages. This page explains how our crawler behaves on sites our users don't own, how to recognize it in your access logs, and how to reach us about abuse.
SeoraBot identifies itself with a User-Agent that links to this page.
Crawls of sites the account doesn't own honour robots.txt rules and the Crawl-delay directive.
Crawls are small and read-only: a bounded number of public pages, no forms, no logins.
Site owners can block SeoraBot in robots.txt or contact us to report abuse.
robots.txt
Disallow rules are honoured on every crawl; Crawl-delay is additionally honoured when the account has not verified ownership of the site.
Read-only
SeoraBot only sends GET and HEAD requests to publicly served pages. It never submits forms, attempts logins, or posts content.
Bounded
Every audit crawls a capped number of pages at a throttled rate under a hard time budget, so a crawl stays a light touch.
How to recognize SeoraBot
When a signed-in Seora user audits a site they have not verified ownership of, the crawl identifies itself with a User-Agent that links back to this policy page. Audits of a site the account has verified (the owner's own site) use our standard audit agent instead.
Every crawl is triggered by a logged-in, accountable Seora user who requested an SEO audit of that URL — SeoraBot does not roam the web on its own.
What SeoraBot respects
The crawler is built to be a good citizen on sites our users don't own. It reads your robots.txt before fetching anything and keeps its footprint small and predictable.
robots.txt Disallow rules are honoured on every crawl, third-party or not.
The Crawl-delay directive is honoured on third-party crawls (capped at a sane maximum so an audit can still finish).
Page caps, a politeness delay between fetches, and a hard wall-clock budget bound every crawl.
Only public web pages are fetched — requests to private networks and internal addresses are blocked outright.
How to block SeoraBot or report abuse
If you don't want Seora auditing your site, one robots.txt rule is enough — SeoraBot honours it on the next crawl. If you believe a crawl misbehaved, tell us and we will investigate.
Block all crawls: add "User-agent: SeoraBot" followed by "Disallow: /" to your robots.txt.
Report abuse: email abuse@seora-ai.com with your domain, the time window, and what you observed in your logs.
We investigate every report and can exclude your domain from future third-party crawls.
Found SeoraBot in your logs?
Send us the domain, the time window, and what you saw at abuse@seora-ai.com — we investigate every report and can exclude your site from future third-party crawls.