AutomateIndex

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 so the dashboard can verify setup.

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. 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. 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

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.

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.