ai.txt is an emerging plain-text file placed at your domain root that states your policy for how AI systems may use your content — for example whether training, summarization or republishing is allowed, who to contact, and your attribution preference. It is a human- and machine-readable declaration of intent that complements robots.txt and llms.txt.

robots.txt is an access-control file that tells crawlers which paths they may fetch. llms.txt curates and describes your best content for AI consumption. ai.txt sits between them as a policy statement about permitted uses — training, summarization, attribution — rather than crawl paths or content listings. Using all three gives crawlers access rules, content guidance, and usage permissions.

No single body has ratified it; ai.txt is an emerging, community-driven convention with a few competing proposals. Because it is not yet universally enforced, treat it as a clear public declaration of your wishes rather than a guaranteed control. Pair it with robots.txt rules, which more crawlers actively honor, for stronger effect.

Typically: a statement of whether AI training is permitted, whether summarization or quoting is allowed, your required attribution format, a contact email for licensing or removal requests, and optionally per-path or per-bot exceptions. This generator lets you set those fields with toggles and inputs, then writes a tidy, commented file.

Place it at the root of your domain so it resolves at https://yourdomain.com/ai.txt, the same location pattern as robots.txt. Make sure it returns a 200 status and plain-text content type. Some teams also link to it from their terms of service so the policy is discoverable by people as well as machines.

Adoption is early, so respect varies. A clear ai.txt strengthens your legal and ethical position and is increasingly checked by responsible AI developers, but it is not yet a technical enforcement mechanism. For uses you must prevent, combine ai.txt with robots.txt blocking of AI crawlers and, where needed, server-side restrictions.

No. ai.txt is a separate policy file and does not affect Googlebot or normal search indexing. It only communicates your AI-usage preferences. You can publish it safely without any impact on rankings, and it can even help by signaling clear, responsible content governance to partners and crawlers.