Decide how AI accesses
your website.
See which AI agents reach the site. Decide what they can read and how it is delivered. Set commercial terms for how it is used.
Make selected stories available to approved agents while keeping other collections restricted.
/news/*/archive/*/explainers/*Let agents read product information while account and checkout pages stay closed.
/products/*/account/*/guides/*Open summaries to agents and keep full papers for approved use.
/abstracts/*/papers/*/courses/*Give agents accurate company information while internal resources stay private.
/about/*/partners/*/docs/*Choose what AI access does for the business.
Some content should be easier for agents to read. Some needs tighter limits, and some will carry commercial terms. All three can sit side by side on one website.
Make useful content available.
Agent Web serves approved pages to agents as clean, structured content on your own subdomain, with the original source attached.
Keep permissions specific.
Approving an agent for one collection does not open the whole site. Set rules for verified agents by property, section, asset or URL.
Make payment a choice. Coming soon
Retrieval & settlement will apply commercial terms where they fit: authorised crawls, retrievals or specific uses, without treating every AI visit as a paid one.
Understand the traffic. Then make the call.
You do not need a policy for every agent on day one. Start with the activity record, find the content that matters and decide where it needs a different approach.
Explore Citetab for AI companiesSee what is happening.
Review which AI agents reach the website, the pages they request and how that activity changes over time.
Choose a starting scope.
Begin with one property, a content section or a set of URLs, and decide which verified agents may access it.
Extend where it makes sense.
Serve structured content through Agent Web, and widen or tighten access rules as new agents appear.