SEOLizeBot
SEOLizeBot fetches a page only when someone asks SEOLize to check it. It doesn’t crawl, follow links, or come back on its own.
How it identifies itself
Every request carries this User-Agent header:
SEOLizeBot/0.1.0 (+https://seolize.app/bot)It sends no cookies and no credentials.
What it fetches
For each check: the robots.txt of every host the request reaches, then the page itself and any redirects on the way. It doesn’t load images, scripts, stylesheets or linked pages.
Limits
These are read from the running service, so they’re always the ones in force.
- Ports
- 80 and 443 only, over HTTP or HTTPS
- Time
- 15 seconds for every request a check makes, robots.txt included; 3 seconds to connect
- Redirects
- At most 5, each one checked again before it’s followed
- Page size
- The first 5 MB; the rest isn’t read
- robots.txt size
- The first 500 KB; the rest is ignored
- Response headers
- Up to 200 headers and 64 KB in total
- At the same time
- 8 requests across the service, 1 per site and 2 per server address
- Per site
- 30 requests to any one site an hour
- Per server address
- 120 requests to any one server address an hour, whatever the site
- Per person
- 3 free checks a day
- Answer changes
- 60 answer changes an hour
How to block it
SEOLizeBot obeys robots.txt. To keep it off your whole site, add this group:
User-agent: SEOLizeBot
Disallow: /It reads robots.txt for every host before fetching a page from it, and matches its name the way RFC 9309 says. When the file answers with a server error (5xx), a 429, or nothing at all, it treats the whole site as off limits. Any other 4xx, such as a 404 for a missing file, means no restrictions.
Blocking SEOLizeBot doesn’t affect Googlebot or other search engines. To learn what SEOLize reads and why, see How it works.