What the request log shows
A server may observe the path, time and User-Agent. A name such as OAI-SearchBot helps initial classification, but a single string cannot authenticate the sender. AURA marks unverified reports separately, while supported provenance verification has its own source and method. Check precisely what the adapter verified, and do not replace missing verification with an attractive AI logo. Apply the same caution to your own technical test as to an ordinary request.
Bots perform different tasks
OpenAI distinguishes search-oriented OAI-SearchBot, training-oriented GPTBot and user-initiated ChatGPT-User fetches. A record saying ‘OpenAI visited the page’ therefore conceals different purposes. Access for one bot does not mean the information appeared in a user-facing answer. Do not change training rules merely for a promise of citation: first determine which product and stage you are checking. Verify roles and current verification methods against provider documentation, and limit the conclusion to the signal actually available.
Synthetic checks have their own value
When an audit sends a request with a similar User-Agent and receives HTTP 200, it tests the website's response from its own environment. The test may find an obvious block, a security error or missing HTML. It does not establish access from the provider's actual IPs and is not an independent visit by that provider's bot. The report may say ‘synthetic test passed,’ with the time and URL, but that result cannot be renamed completed indexing or a new AI link.
What AURA GEO shows
aura_get_bot_visits provides retained events and verification details, while aura_get_url_status separates a page's stages. One URL can simultaneously have verified publication, an accepted submission and unknown citation status. That is a normal process state rather than a counter error. Event source, retention period and verification method matter more than the total number of requests. Do not combine audits, bot requests and human browser loads into a single metric of potential customers or sales effectiveness.
Which step to take next
If requests are blocked, fix access and check the live page. If crawling exists but search status is unknown, read data from the connected search engine. If you need an AI recommendation, ask a neutral question in the relevant interface and save the answer with its links. Do not create repeated requests merely to increase a graph. Monitoring is valuable when a new signal changes the decision about content, access or the next check, rather than simply increasing event counts.
Conditions and limitations
- Connection, a technical check and a saved report do not guarantee an AI recommendation or a customer outcome.
Explore the details
A verifiable action plan and an explanation of the result with saved evidence and limitations.
View crawl evidence