Why did gen3-aivisibility-audit visit my website?

A customer of AI Visibility by Gen3 Marketing declared your domain as their own and asked for a site audit of it, attesting by name and role that they had the authority to do so. The agent never crawls the open web and never discovers sites on its own.

Does the agent obey robots.txt?

Yes. It reads your robots.txt before fetching anything, follows the group addressed to gen3-aivisibility-audit or the wildcard group, and honors Crawl-delay. Only a written authorization from the site owner, recorded in their own report, lets it proceed past a disallow rule.

Add a robots.txt group for the user agent gen3-aivisibility-audit with Disallow: /. The agent honors it on its next visit. You can also email aiv_expert@gen3marketing.com and we will stop future runs against your domain.

What does it store, and for how long?

Copies of the pages, headers, robots.txt and sitemap files it fetched, used only to evaluate that site against published AI platform requirements and to evidence the findings. They are never used to train models, never shown to another customer, and never republished, and they are kept for no longer than 90 days from capture, sooner on request.

About the AI Visibility site audit agent

gen3-aivisibility-audit is the web agent behind the site audit feature of AI Visibility by Gen3 Marketing. If you found this page from your server logs, a request carrying that token came from us. This page explains why it was there, how it behaves, what it keeps, and how to stop it.

Why it visited your site

The agent fetches pages from a website only when a customer of AI Visibility has declared that domain as their own and attested, by name and role, that they have the authority to have it audited. There is no open crawl of the web, no discovery of new sites, and no schedule that runs on its own. Every audit is a request by a person, recorded against the domain, and the customer can withdraw that permission at any time.

If your domain was audited and you did not ask for it, someone with an AI Visibility account declared it as theirs. Contact us at the address below and we will tell you who authorized the run, stop future runs, and remove the copies we hold.

How it identifies itself

Every request carries this user agent:

gen3-aivisibility-audit/1.0 (+https://aivisibility.gen3marketing.com/audit-bot)

For a small number of comparison checks the agent may also present a browser-shaped or smartphone-shaped user agent string. Those strings still end with the same token and this URL, so every request is attributable to us. The agent never sends another operator's crawler token, and it never claims to be a search engine or an AI assistant's fetcher.

Requests originate from Microsoft Azure infrastructure. We do not publish a fixed IP range, so the token and this URL are the way to recognize the agent.

How it behaves

It obeys robots.txt. It reads your robots.txt before fetching anything, follows the group addressed to gen3-aivisibility-audit or the wildcard group, and honors Crawl-delay. In the rare case a site owner asks us in writing to audit paths their own robots.txt disallows, that authorization is recorded and their report says so.
It is polite by default. At most two requests at a time to any one host, a floor of 250 milliseconds between requests, and a budget of at most 300 pages per audit. It stops early if your server starts refusing or erroring.
It stays on the domain it was asked about. Pages on other hosts are noted in the report but not fetched unless the customer's declaration covers them.
It runs once per request. An audit is a single visit, not a recurring crawl.

What it keeps, and for how long

The agent stores copies of what it fetched: page HTML, response headers, robots.txt and sitemap files, and the headers of a few images. Those copies exist for one purpose: to evaluate the customer's own site against what AI platforms publicly ask publishers to do, and to show the evidence behind each finding. They are never used to train models, never shown to another customer, and never republished. They are kept for no longer than 90 days from capture, and sooner on request.

How to block it

Add this group to your robots.txt:

User-agent: gen3-aivisibility-audit
Disallow: /

The agent honors it on its next visit, and the customer who requested the audit sees the block in their report rather than a result.

Contact

Questions, concerns, or a request to stop: email aiv_expert@gen3marketing.com. Include the domain and, if you have it, the date and time of the request from your logs.

Frequently asked questions

Why did gen3-aivisibility-audit visit my website?: A customer of AI Visibility by Gen3 Marketing declared your domain as their own and asked for a site audit of it, attesting by name and role that they had the authority to do so. The agent never crawls the open web and never discovers sites on its own.
Does the agent obey robots.txt?: Yes. It reads your robots.txt before fetching anything, follows the group addressed to gen3-aivisibility-audit or the wildcard group, and honors Crawl-delay. Only a written authorization from the site owner, recorded in their own report, lets it proceed past a disallow rule.
How do I block it?: Add a robots.txt group for the user agent gen3-aivisibility-audit with Disallow: /. The agent honors it on its next visit. You can also email aiv_expert@gen3marketing.com and we will stop future runs against your domain.
What does it store, and for how long?: Copies of the pages, headers, robots.txt and sitemap files it fetched, used only to evaluate that site against published AI platform requirements and to evidence the findings. They are never used to train models, never shown to another customer, and never republished, and they are kept for no longer than 90 days from capture, sooner on request.