Generating your AI visibility files is step one. For them to have any effect, they need to be accessible at your actual domain — yourdomain.com/llms.txt, yourdomain.com/robots.txt, and so on. AI crawlers look for these files at the root of the domain they are scanning. A file stored somewhere else will not be found.
One domain, one method
Every activation method below delivers the same 12 files, and files stay current automatically — your monthly refresh updates them no matter which method you chose. A domain only needs one method. The setup page (/deploy) shows a status banner for your domain: gray means “not live yet — pick one method”, orange means “live — setup is complete”. Methods your domain doesn't need are tagged Not needed.
Point DNS to Indexora — recommended, any registrar
The easiest option for most sites. Add one CNAME record at your existing DNS provider pointing your root domain to serve.indexora.app. Indexora serves your AI files from a global edge network and transparently forwards all other traffic to your existing website — your site and email are untouched.
- Works with GoDaddy, Namecheap, Squarespace, Route 53, Cloudflare, or any other registrar
- No Cloudflare account required on your side
- SSL is issued automatically — typically live 5–30 minutes after the record is added
- Some setups are asked for one extra TXT record to verify domain ownership — the setup page shows it when needed
You do: add one CNAME record (shown on the setup page), wait for validation. Done.
WordPress Plugin — no DNS changes
If your site runs WordPress (Hostinger, GoDaddy, SiteGround, WP Engine — any host), install the free Indexora plugin and paste your Hosting Token. Your files serve at your domain instantly, with zero DNS changes and no server access.
You do: install the plugin, paste one token. Live in under 2 minutes.
CF OAuth — one-click install into your own Cloudflare
If your domain's DNS is already managed by your own Cloudflare account, authorize Indexora once with OAuth and click Install. Indexora deploys a small worker into your account with routes for exactly the 12 file paths — nothing else on your site is touched. The consent screen shows the four scoped permissions requested, and you can revoke access anytime from your Cloudflare dashboard.
- No token copying — a standard authorization screen instead
- Files are sourced from Indexora and refreshed monthly, same as every other method
- Changed your mind? Click Uninstall on the setup page — it removes the routes and the worker
You do: click Connect → Authorize → Install. About one minute.
Your Cloudflare with a manual API token
The same result as CF OAuth, for users who prefer creating a scoped Cloudflare API token themselves and pasting it. OAuth replaces this for most people.
Server / manual — host the files yourself
For servers where you have SSH access, Indexora generates a personalised bash script that places each file in the correct location on your server. Supports Apache, Nginx, and any standard Linux web server. You can also download the ZIP and upload the files manually.
Which method to choose
| Method | Best for | You do | Setup time |
|---|---|---|---|
| Point DNS to Indexora | Anyone, any registrar | Add one CNAME record | 5–30 min (SSL) |
| WordPress Plugin | WordPress sites | Install plugin, paste token | ~2 min |
| CF OAuth | Domain on your own Cloudflare | Authorize, click Install | ~1 min |
| Manual API token | Same, without OAuth | Create + paste a token | ~3 min |
| Server / manual | SSH server access | Run the script or upload files | ~5 min |