First a change, then a notification
Submit an address where a meaningful event has actually occurred. Before notifying search engines about a new article, check that it is published, opens at the final URL and contains the intended material. For deleted content, it should be clear which state the address now returns.
Under the protocol, the key verifies the right to submit URLs for the corresponding host. This is separate from checking whether content is public. The key file, URL list and declared host must agree. Verification of the main domain cannot be used as a universal right to notify search engines about arbitrary third-party websites.
How to interpret responses
The official documentation distinguishes successful receipt, pending key verification, format errors, key errors, URL ownership errors and rate limits. If an error occurs, fix its cause first. A blind series of identical requests may hit limits instead of speeding anything up.
Save the code, time and addresses. Notifications are passed to participating systems, but each independently decides whether to crawl and index. A protocol-side “accepted” status and a page’s absence from a particular search engine can therefore both be valid observations at the same time.
What to check after receiving a receipt
The next step is to read the URL’s search status and, where available, server observations. If access is blocked, the content is duplicated or the page is unsuitable for search, a receipt does not fix the problem. Likewise, a successful submission on Monday is no basis for promising a citation by Friday.
For a practical example, an agent publishes a guide, checks its live HTML and receives 202. A suitable report says “notification received; key verification pending.” The statement “indexed in every AI” does not match this evidence.
How AURA saves this step
AURA GEO provides submission of changed URLs within project permissions and stores real receipts. For managed pages, the notification is linked to publication and its checks.
Compare the addresses in the receipt with those you intended to submit. If a different deployment or subdomain changed, check its connection separately. The outcome of this task is a correct submission supported by evidence, not a guaranteed search position.
Conditions and limitations
- A receipt is not an index entry.
- The protocol applies to participating search engines, not every AI service.
Explore the details
A receipt is saved for the correct addresses and the next stage is clear.
View your website’s submissions