GoAiEzBot

You are probably here because you found this name in your server logs. This page says what it was doing there and how to stop it.

How to identify it

Every request sends this exact User-Agent header:

GoAiEzBot/1.0 (+https://goaiez.com/bot)

How to block it

Add this to your robots.txt. It takes effect within an hour, which is how long a copy of your robots.txt is kept before being fetched again.

User-agent: GoAiEzBot
Disallow: /

There is no setting anywhere in our product that overrides this for GoAiEzBot, for any customer, on any plan. The column that records whether a source honours robots.txt carries a database constraint pinning it true for every source GoAiEzBot fetches for, so the value cannot be changed to no by a support ticket or a configuration edit.

If we cannot read your robots.txt at all — it times out, returns an error, or is too large to parse — we treat that as a block and do not fetch. A robots.txt that returns 404 is treated as permission, which is what the standard says it means.

What it fetches, and why

GO AI EZ runs a free check of a local business's online presence. Part of that check reads the business's own public homepage to see whether the name, address and phone number shown there match the ones on their Google listing — a mismatch is one of the most common reasons a business is hard to find.

So a fetch of your site happens because somebody asked us to check that business. We do not crawl the open web, and we do not build an index.

What it does not do

• It does not follow links. One request fetches one page. There is no queue of discovered URLs, so a fetch of your homepage cannot become a fetch of anything else on your site.
• It does not run JavaScript. It is a plain HTTP GET. No headless browser, no rendering, no requests for your scripts, stylesheets, images or fonts.
• It does not log in, submit forms, or send anything. GET only. It never posts, and it carries no cookies from a previous request.
• It does not identify itself as a browser. The header above is the only one it ever sends. Serving us different content than you serve a person is something you are free to do, but you do not have to guess who we are to do it.

How politely

• Each of our checks has a request budget, shared by every site that check reads, and once it is spent no further request is made to any site until it refills.
• A request is abandoned after 10 seconds. We follow at most 3 redirects to a page and 5 to a robots.txt, as its standard asks, and read at most 2 MB.
• When a site refuses us, with a 403 or a 429 or a page that checks whether you are a person, the check that was refused waits 6 hours, then 24, then 72, before it asks any site again. We never retry a failed request on our own: it is reported as failed.