WordPress Plugin

The Indexora AI Files plugin connects your WordPress site to your Hosted Files subscription and serves your AI visibility files directly at your domain — yourdomain.com/llms.txt, yourdomain.com/robots.txt, and the rest. Because WordPress itself answers those URLs, there are no DNS records to add and nothing to configure at your host.

Requirements

• An active Hosted Files subscription
• WordPress 5.9 or newer, PHP 7.4 or newer
• Permission to install plugins on your site (Administrator role)

Step 1 — Download the plugin

Get the latest version from indexora.app/deploy → select WordPress Plugin → Download plugin, or download it directly: indexora.app/api/wp-plugin/download.

Step 2 — Install and activate

In your WordPress admin:

Plugins → Add New Plugin → Upload Plugin
→ choose indexora-ai-files.zip → Install Now → Activate

Step 3 — Paste your Hosting Token

Your Hosting Token identifies your subscription. Find it on indexora.app/deploy in the WordPress Plugin section (you need to be signed in). Then, in WordPress:

Settings → Indexora AI Files → paste token → Save Token

Saving the token fetches your files immediately. The settings page shows a status panel with your connected domain, plan tier, and a table of every file path with its current state.

What gets served

The plugin answers up to 12 paths at your domain, depending on what your scans have generated:

/llms.txt          /robots.txt        /sitemap.xml
/ai-index.json     /crawl-hints.txt   /security.txt
/faq-schema.json   /faq-display.html  /about-us.txt
/meta-tags.html    /agents.md         /schema.json

Paths marked Not generated yetin the settings table simply haven't been produced for your domain — run a scan at indexora.app/generate and refresh. WordPress installs in a subdirectory (e.g. example.com/blog) are supported; files are served relative to your WordPress address.

Keeping files current

Files refresh three ways — you don't need to do anything for the first two:

• Automatically after every rescan — Indexora pings your site the moment new files are generated.
• Daily background refresh — a scheduled task pulls the latest files once a day, which covers sites Indexora can't reach directly (password-protected staging, strict firewalls).
• Manually — the Refresh Files Now button on the settings page.

Plugin updates

The plugin updates itself like any wordpress.org plugin (v1.2.0 and later): it checks indexora.app for new versions automatically, and when one is available it appears in Dashboard → Updates and on the Plugins screen with the usual update nowlink — one click and you're on the latest version. Your Hosting Token, fetched files and settings are stored in your WordPress database and are never touched by an update, so everything continues exactly as you set it up — no reconnection, no re-entering the token.

Reinstalling or moving hosts? Update in place rather than removing the plugin: download the latest zip, then in wp-admin go to Plugins → Add New → Upload Plugin, choose the zip and click Replace current with uploaded. Your token and settings are preserved (do not delete the plugin first — deleting erases its saved data).

About robots.txt

While the plugin is active, Indexora's robots.txtreplaces the one WordPress generates. It includes everything WordPress would normally output, plus AI crawler directives. Deactivating the plugin instantly reverts to WordPress's own robots.txt and sitemap.xml; the other AI file paths return 404 until reactivated.

Troubleshooting

• "Refresh failed" after saving the token— check the token was copied exactly, your subscription is active, and you've run at least one scan for the domain at indexora.app/generate. The settings page shows the exact API error under Last error.
• Files show old content — a caching plugin or host-level page cache may be caching the file URLs. Exclude the AI file paths from caching, or purge the cache after a refresh. The plugin itself serves with a 1-hour cache header.
• /robots.txt ignores the plugin — if a physical robots.txtfile exists in your site's web root, the server serves it before WordPress loads. Delete or rename the physical file so requests reach WordPress.
• Uninstalling — deleting the plugin removes all of its data (token, cached files, scheduled tasks) automatically.
• Still stuck — email [email protected] with your domain and a screenshot of the plugin settings page.

Prefer not to use a plugin?

The CNAME setupserves the same files from Indexora's edge network with one DNS record — a good fit if you keep WordPress lean or your host restricts plugins.