Title: AutomateIndex Author: automateindex Published: Nyakanga 5, 2026 Last modified: Nyakanga 17, 2026 --- Search plugins ![](https://ps.w.org/automateindex/assets/icon-256x256.png?rev=3596570) # AutomateIndex By [automateindex](https://profiles.wordpress.org/automateindex/) [Download](https://downloads.wordpress.org/plugin/automateindex.0.3.13.zip) * [Details](https://kin.wordpress.org/plugins/automateindex/#description) * [Reviews](https://kin.wordpress.org/plugins/automateindex/#reviews) * [Installation](https://kin.wordpress.org/plugins/automateindex/#installation) * [Development](https://kin.wordpress.org/plugins/automateindex/#developers) [Support](https://wordpress.org/support/plugin/automateindex/) ## Description AutomateIndex is AI visibility infrastructure for the open web. This connector links a WordPress site to owner-approved AutomateIndex setup so it can publish reviewed machine-readable guidance and verify that the connector is working from the AutomateIndex dashboard. The plugin is configured from an AutomateIndex account. After the site owner approves access, AutomateIndex can install the connector, save the site-specific settings, and run final Checks from the AutomateIndex dashboard. It is not a standalone generic file generator; it is the WordPress connector for an AutomateIndex site workflow. What the connector can do: * Serve owner-approved AutomateIndex visibility files such as `robots.txt`, `llms. txt`, and `ai-catalog.json`, plus related guidance files when enabled by the site owner. * Provide AutomateIndex-managed machine-readable responses for approved automated requests. * Send connector status and monitoring proof to AutomateIndex through a background WordPress cron event approximately every five minutes so the dashboard can verify setup without delaying public responses. What the connector does not do: * It does not promise or guarantee AI rankings, citations, traffic, indexing, or revenue. * It does not place visible public credits or links on the front end. * It does not block ordinary human visitors or normal search crawler access by default. #### External service This plugin connects to AutomateIndex at `https://app.automateindex.com` after the site owner configures the connector from an AutomateIndex account. The external service is used to deliver owner-approved guidance file content, verify connector health, and support dashboard checks. When configured, a background WordPress cron event sends connector heartbeat proof approximately every five minutes. Depending on the enabled options, the plugin may send the AutomateIndex site ID, integration ID, plugin version, AutomateIndex-managed request path, response status, content type, user agent, referer, and an HMAC-hashed IP value for likely automated requests. When optional AgentToll structured access is enabled, the plugin sends the requested public source URL to AutomateIndex. It may also forward incoming x402 V2 `PAYMENT- SIGNATURE`, x402 V1 `X-PAYMENT`, AutomateIndex payment-reference, and short-lived activation-probe headers so AutomateIndex can verify access and return the structured response. AgentToll payments, when enabled, settle directly to the publisher wallet; AutomateIndex does not custody, forward, or pay out those funds. The raw provider secret is stored in WordPress options and is sent only to authenticate AutomateIndex API requests. The plugin does not intentionally send raw IP addresses. AutomateIndex legal pages: * Terms: https://www.automateindex.com/terms * Privacy: https://www.automateindex.com/privacy ## Installation 1. In AutomateIndex, add or select your WordPress site. 2. Open the WordPress Wizard and choose the WordPress Application Password approval path. 3. Approve AutomateIndex on the native WordPress Application Password screen. 4. Return to AutomateIndex and click Install AutomateIndex. 5. Run final Checks in AutomateIndex. If a host login, security plugin, cache layer, or REST restriction blocks the automated install path, install and activate the plugin in WordPress, then paste the setup token from AutomateIndex in WordPress Admin > Settings > AutomateIndex. ## FAQ ### Does this plugin guarantee AI search visibility? No. AutomateIndex helps publish and verify machine-readable guidance. It does not guarantee rankings, citations, indexing, traffic, or revenue. ### Does this plugin change normal pages? No. The connector serves selected machine-readable paths for the configured site. Ordinary human pages and normal search access remain open by default. ### Does this plugin require an AutomateIndex account? Yes. The plugin needs site-specific settings from AutomateIndex before it can serve generated files or send monitoring proof. ### Where are settings stored? Settings are stored in WordPress options. The provider secret is never displayed back in the WordPress settings form after it is saved. ### What happens when I delete the plugin? Deleting the plugin clears the saved connector settings and transient health state. If AutomateIndex replaced an eligible physical `robots.txt`, it restores the byte- exact original; if AutomateIndex created the file, it removes it; and if the owner changed it later, the owner’s current file is preserved. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “AutomateIndex” is open source software. The following people have contributed to this plugin. Contributors * [ automateindex ](https://profiles.wordpress.org/automateindex/) [Translate “AutomateIndex” into your language.](https://translate.wordpress.org/projects/wp-plugins/automateindex) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/automateindex/), check out the [SVN repository](https://plugins.svn.wordpress.org/automateindex/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/automateindex/) by [RSS](https://plugins.trac.wordpress.org/log/automateindex/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.3.13 * Snapshot eligible pre-existing physical `robots.txt` content before AutomateIndex manages the file. * Restore the byte-exact original during approved deletion, remove only files AutomateIndex created, and preserve later owner edits. * Add an authenticated restore-preparation endpoint so the Wizard confirms cleanup before deactivating and deleting the exact plugin. #### 0.3.12 * Discover and bind the exact site-specific WordPress REST root instead of assuming a root `/wp-json` installation. * Support canonical subdirectory, custom-prefix, and query-form REST routes while keeping every unadvertised alias fail-closed. * Report the exact paid Markdown and JSON endpoints in setup, status, and heartbeat so AutomateIndex can bind generation, safety proof, and activation to one route contract. #### 0.3.11 * Move AgentToll Markdown and JSON serving to exact WordPress REST API routes that preserve the original HTTP method on managed hosts. * Register and reject HEAD, POST, PUT, PATCH, DELETE, OPTIONS diagnostics, and PROPFIND explicitly before payment headers or upstream work. * Hard-disable the legacy `/automateindex/markdown` and `/automateindex/json` pretty routes, including stale rewrite and public query-var aliases. * Flush the rewrite contract once after plugin updates so older paid-route rewrites cannot survive the safety cutover. #### 0.3.10 * Restrict generated-file method proof markers to the exact canonical `/llms.txt` path so query-var and trailing-slash aliases cannot mint diagnostic evidence. * Move connector heartbeat delivery to a verified five-minute WordPress cron event so cold public file and paid-route requests never wait on a heartbeat connection. * Keep synthetic installation and integrity checks out of crawler analytics so verification remains truthful and cannot wait on a background analytics connection. * Repair missing or stale heartbeat schedules automatically after upgrades, and clear the schedule on deactivation or uninstall. #### 0.3.9 * Run exact-route method diagnostics before every heartbeat, upstream request, or analytics write so managed-host latency cannot invalidate a safe proof. * Expose the current connector version on controlled structured-access responses. #### 0.3.8 * Make AgentToll routes strictly GET-only and isolate HEAD before any payment or upstream work. * Strengthen exact-route proof responses for per-method, cache-safe verification. #### 0.3.7 * Prove HTTP method isolation on both exact structured-access routes instead of using a generated-file path as a proxy. #### 0.3.6 * Forward short-lived AutomateIndex activation probes to structured routes so completed installs can activate Base mainnet access automatically without making a payment. #### 0.3.5 * Add a nonce-bound, same-path no-op proof for managed-host HTTP method behavior. * Keep dashboard verification traffic synthetic so Checks cannot inflate real crawler analytics. * Make structured HEAD challenge-only and never forward payment authorization without a response body. * Fail closed for unknown structured-route methods and keep disabled routes from advertising preflight support. #### 0.3.4 * Keep generated-file responses private and uncacheable on managed hosts. * Return explicit method-not-allowed responses when unsupported methods reach WordPress. * Prevent POST requests from being proxied into read-only structured-access fetches. #### 0.3.3 * Keep paid structured-access routes active after in-place upgrades even when WordPress rewrite rules are stale. * Prevent managed hosts from canonicalizing paid routes into ordinary page responses. #### 0.3.2 * Preserve the complete x402 requirements challenge in `WWW-Authenticate` for paid- route discovery crawlers. #### 0.3.1 * Preserve browser-agent CORS preflights on managed hosts that normalize `OPTIONS` to `GET` before WordPress receives the request. #### 0.3.0 * Support current x402 V2 and legacy V1 payment headers on structured-access routes. * Preserve complete payment challenges, authorizations, and settlement receipts without truncation. * Add browser-agent CORS preflight handling and expose the required payment response headers. #### 0.2.9 * Require exact managed-file hash proof before replacing an existing root `robots. txt` file. * Preserve custom physical and virtual `robots.txt` policies even when they mention AutomateIndex. * Merge WordPress core admin crawl rules into AutomateIndex-managed physical and virtual `robots.txt` output. #### 0.2.8 * Limit structured-access payment retry forwarding to the public x402 payment signature and AutomateIndex payment reference headers. * Keep internal AutomateIndex and development-only payment headers out of production structured-access retries. * Add a one-step setup token fallback for hosts that block the automated WordPress approval or setup request. #### 0.2.7 * Safely publish an AutomateIndex-managed root `robots.txt` on hosts that serve a physical root file before WordPress routes. * Avoid overwriting custom `robots.txt` policies and report a clear status when manual owner review is needed. * Remove the unchanged AutomateIndex-managed root `robots.txt` file when the plugin is deleted. #### 0.2.6 * Clarify the AutomateIndex connector workflow and public listing copy. * Refresh WordPress.org public listing copy and plugin icon assets. * Harden request handling and setup sanitization. * Preserve valid connector secrets while stripping unsafe control characters. #### 0.2.5 * Prepare WordPress.org submission package. * Rename public plugin identity to AutomateIndex. * Add WordPress.org readme metadata and GPL license declaration. * Avoid rendering the saved provider secret in the WordPress settings form. #### 0.2.4 * Add authenticated setup endpoint for the AutomateIndex WordPress Wizard. * Add setup redaction and heartbeat proof. ## Meta * Version **0.3.13** * Last updated **1 hour ago** * Active installations **Fewer than 10** * WordPress version ** 6.2 or higher ** * Tested up to **7.0.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/automateindex/) * Tags * [ai visibility](https://kin.wordpress.org/plugins/tags/ai-visibility/)[automation](https://kin.wordpress.org/plugins/tags/automation/) [monitoring](https://kin.wordpress.org/plugins/tags/monitoring/)[robots](https://kin.wordpress.org/plugins/tags/robots/) * [Advanced View](https://kin.wordpress.org/plugins/automateindex/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/automateindex/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/automateindex/reviews/) ## Contributors * [ automateindex ](https://profiles.wordpress.org/automateindex/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/automateindex/)