The Cloudflare auto-deploy is a one-click deployment that puts your AI visibility files at your actual domain without any manual file management. Everything is handled by Indexora's backend using your Cloudflare API token.
Prerequisites
- Your domain's DNS must be managed by Cloudflare (i.e. your nameservers point to Cloudflare)
- You need a Cloudflare account with access to that domain
- A completed Indexora scan for the domain (recommended — ensures your actual files are deployed)
If your domain is not on Cloudflare, use Point DNS to Indexora or the bash deploy script instead.
Recommended: one-click install with CF OAuth
The fastest path — no token copying. On indexora.app/deploy, select the CF OAuth card:
- Step 1 — Connect. Click Connect Cloudflare. Cloudflare shows a consent screen listing exactly what Indexora requests: Account Settings Read, Zone Read, Workers Scripts Edit, and Workers Routes Edit. Click Authorize.
- Step 2 — Confirm the domain. If you purchased hosting, your domain is already filled in — nothing to type.
- Step 3 — Install. Click Install automatically. Indexora deploys the worker and routes in about a minute.
The authorization is account-level and revocable anytime from your Cloudflare dashboard. To remove an installation later, click Uninstallnext to the “Previously installed” note on the setup page — it deletes the routes and the worker from your account. Your website itself is never affected either way: routes cover only the AI file paths.
Prefer not to use OAuth? Create an API token manually instead — steps below.
Alternative: create a Cloudflare API token manually
In your Cloudflare dashboard, go to My Profile → API Tokens → Create Token. Select the "Edit Cloudflare Workers" template. This template includes exactly the permissions needed:
- Workers Scripts: Edit
- Workers Routes: Edit
- Zone: Read (to find your zone ID)
Scope the token to your specific account and zone if you want to limit its access. Click "Create Token" and copy the token value — it is shown only once.
Step 2 — Deploy from the Indexora dashboard
Go to indexora.app/deploy and select the Cloudflare tab.
- Enter your domain (e.g.
yourdomain.com) - Paste your Cloudflare API token
- Enter the email address used for your Indexora scan (optional — links your generated files)
- Click Verify token →
- Once verified, click Deploy to Cloudflare →
The deployment takes about 5 seconds. Indexora will:
- Upload your files to R2 at permanent paths (
hosted/yourdomain.com/llms.txtetc.) - Deploy a Cloudflare Worker named
indexora-yourdomain-comto your account - Add a route for each of the 9 served file paths
What gets deployed
The following routes are created on your domain:
/llms.txt/robots.txt/sitemap.xml/ai-index.json/crawl-hints.txt/security.txt/faq-schema.json/faq-display.html/meta-tags.html/about-us.txt/agents.md/schema.json
Each route is handled by a Cloudflare Worker that fetches the file from R2 and serves it with the correct Content-Type header. If a file does not exist in R2 (e.g. no scan has been run for that domain), the Worker falls through to your origin server transparently.
Important: robots.txt
Deploying via Cloudflare will replace your existing robots.txt with the Indexora-generated version. If you have custom bot rules or crawl disallow directives that are not in the generated file, they will stop being served.
To restore your original robots.txt, remove the yourdomain.com/robots.txtWorker route from your Cloudflare dashboard under Workers & Pages → your worker → Triggers.
Verifying the deployment
After deployment, open a browser and visit:
https://yourdomain.com/llms.txt
https://yourdomain.com/ai-index.jsonYou should see the file content with an X-Served-By: Indexora response header. DNS propagation is instant for Cloudflare-proxied domains.
Troubleshooting
"Domain not found in your Cloudflare account" — Your domain's DNS is not managed by Cloudflare. The nameservers must point to Cloudflare's nameservers, not just using Cloudflare's proxy on individual records.
"Invalid or inactive API token" — The token may have expired or been revoked. Create a new one in your Cloudflare dashboard.
Worker deploys but files return 404 — No scan has been run for the domain yet, or the scan used a different email. Run a scan at indexora.app with your domain, then re-deploy.