AI Terms / publish
Put your AI Terms file on your site
Your file goes at /.well-known/ai-terms: a folder whose name starts with a dot, and a file with no ending. Those two details are where most people get stuck, so here are the exact steps for each kind of host.
Three things that are true everywhere
- The address is exactly
https://your-site/.well-known/ai-terms. Notai-terms.json, and not in a subfolder. - Serve it as
application/jsonif your host lets you. If it doesn't, publish anyway: readers read the contents whatever the type says. - Add one line to your robots.txt so crawlers find it:
AI-Terms: https://your-site/.well-known/ai-terms
Pick your host
Nginx · Apache · Caddy · Next.js · Vercel (static site) · Netlify or Cloudflare Pages · GitHub Pages · Hugo · Jekyll · Eleventy (11ty) · Astro · WordPress
Nginx
Put the file at .well-known/ai-terms inside your site's root folder, add this inside your server { } block, and reload Nginx.
Code4 lines
location = /.well-known/ai-terms {
default_type application/json;
add_header Access-Control-Allow-Origin *;
}Many Nginx configs block every folder that starts with a dot. This exact-match block still wins, so the file is served.
Apache
Put the file at .well-known/ai-terms inside your site's root folder. In that same .well-known folder, create a file named .htaccess with these lines.
Code4 lines
<Files "ai-terms">
ForceType application/json
Header set Access-Control-Allow-Origin "*"
</Files>Needs mod_headers for the second line (on by default on most hosts). Without the .htaccess the file is still served and still readable; it just has no type.
Caddy
Put the file at .well-known/ai-terms inside your site's root folder, add these lines to your site block above file_server, and reload Caddy.
Code3 lines
@aiterms path /.well-known/ai-terms
header @aiterms Content-Type application/json
header @aiterms Access-Control-Allow-Origin *Next.js
Create app/.well-known/ai-terms/route.js (the folder name starts with a dot) and paste your file's contents where marked.
Code6 lines
// app/.well-known/ai-terms/route.js
const terms = PASTE_YOUR_FILE_HERE;
export const dynamic = "force-static";
export function GET() {
return Response.json(terms, { headers: { "Access-Control-Allow-Origin": "*", "Cache-Control": "public, max-age=900" } });
}On the pages router, put the file at public/.well-known/ai-terms instead and set the type in next.config.js headers().
Vercel (static site)
Put the file at public/.well-known/ai-terms (or .well-known/ai-terms in the folder you deploy) and add this to vercel.json.
Code11 lines
{
"headers": [
{
"source": "/.well-known/ai-terms",
"headers": [
{ "key": "Content-Type", "value": "application/json" },
{ "key": "Access-Control-Allow-Origin", "value": "*" }
]
}
]
}Netlify or Cloudflare Pages
Put the file at .well-known/ai-terms in the folder you publish, and add these lines to a file named _headers in that same folder.
Code3 lines
/.well-known/ai-terms
Content-Type: application/json
Access-Control-Allow-Origin: *GitHub Pages
Put the file at .well-known/ai-terms in your site's source. GitHub Pages skips folders that start with a dot unless you tell it not to: add an empty file named .nojekyll at the top of the site, or add the line below to _config.yml.
include: [".well-known"]GitHub Pages can't set a file's type, so yours is served without the JSON type. That is fine: readers of AI Terms read the contents whatever the type says, and the checker will pass it with a note.
Hugo
Put the file at static/.well-known/ai-terms (Hugo copies everything under static/ to your site as it is, dot folders included). Rebuild and deploy as usual.
Where your Hugo site is hosted decides its type: on Netlify or Cloudflare Pages add the _headers lines from that section; on GitHub Pages see that section.
Jekyll
Put the file at .well-known/ai-terms in your site's source, and add this line to _config.yml: Jekyll leaves out folders that start with a dot unless you list them.
include: [".well-known"]Eleventy (11ty)
Put the file at .well-known/ai-terms in your project, and tell Eleventy to copy it as it is: add this line inside the function in eleventy.config.js (or .eleventy.js).
eleventyConfig.addPassthroughCopy(".well-known");Astro
Put the file at public/.well-known/ai-terms. Astro copies public/ to your site as it is, dot folders included.
For the JSON type, use the _headers lines (Netlify, Cloudflare Pages) or vercel.json (Vercel) from those sections, depending on where it's hosted.
WordPress
With your host's file manager or FTP, open the folder that holds wp-config.php, create a folder named .well-known in it (if it isn't there already) and upload the file into it, named ai-terms with no ending. On Apache hosts, also add the Apache .htaccess above.
File managers often hide names that start with a dot; turn on "show hidden files". If you use AIPayGen pay-per-crawl, skip all this: the plugin serves the file for you.
Check it, and get listed
Enter your site's address in the checker. It reads the file from your site and tells you what, if anything, is wrong, including the common hosting slips: a missing dot-folder, a blocked folder, or a host answering with your home page. A site whose file passes is added to the list of sites that publish AI Terms.
What we tested
We ran these ourselves and saw the file served as JSON: Nginx 1.30, Apache 2.4, Caddy 2.11, Next.js 16.4. The steps for Vercel (static site), Netlify or Cloudflare Pages, GitHub Pages, Hugo, Jekyll, Eleventy (11ty), Astro, WordPress follow each host's own documentation; we have not run them. If one is wrong for your setup, tell us and we will fix it.
AI Terms is a file a website publishes at /.well-known/ai-terms that says, for each use of its content by AI (search, answer, training, agent), whether that use is allowed, allowed for a price, or not allowed. More.