Our audit server
If you found seoscoreapi.com/bot in your logs: a customer of SEO Score API
asked us to check a page on your site for SEO, accessibility or AI-readability problems, and our
server fetched it. Each audit is a page that a person or their software asked for. We do not
crawl the web on our own.
Where requests come from
Every request comes from one fixed address:
32.190.161.153
Our server sends no requests from any other address, and never through proxies.
How we identify ourselves
| What | User agent | What it fetches |
|---|---|---|
| Single-page audits (SEO, AI readability, GEO, conversion) | SEOScoreAPI-Bot/1.0 (+https://seoscoreapi.com/bot) | The page, plus a few small files such as robots.txt, the sitemap and llms.txt. |
| Site crawls (POST /crawl) | SEOScoreAPI-Crawler/1.0 (+https://seoscoreapi.com) | Follows links on the same site, up to the customer's page cap, 4 requests at a time. |
| Pages that need JavaScript, and accessibility audits | A standard Chrome identity | Loads the page in a headless browser, as a visitor would, to run the checks. |
To let us in
If your firewall or bot protection refuses us, a customer sees an error instead of a report.
To allow us, add 32.190.161.153 to your allowlist (in Cloudflare: Security, WAF,
Tools, IP Access Rules, Allow).
To keep us out
- Site crawls obey robots.txt for the token
SEOScoreAPI-Crawler:User-agent: SEOScoreAPI-Crawler Disallow: /
- A single-page audit is one fetch a person asked for, like opening the page in a browser, so it
does not consult robots.txt. To refuse those, block
32.190.161.153. When you do, the customer is told your site refused us. We do not retry from elsewhere or try to get around it. - Or email info@seoscoreapi.com with your domain and we will stop auditing it.