Prepare a compatible installation
Version 0.1.0 targets WordPress 6.4 or newer, PHP 7.4 or newer, and OpenSSL. WordPress must be installed at the website root on a domain matching the project. This adapter does not mirror subdomain publication mode. Test it on staging before enabling it in production: the theme, permalinks, cache and SEO extensions can affect the result. If another mechanism already serves /answers/, choose one approach first. Do not layer a second rewrite over the plugin without checking routes.
Who authorizes publication
The owner installs the ZIP and opens AURA GEO settings in WordPress. They enter the project identifier and a read key restricted to this website, then enable mirroring with a separate checkbox. The first authorized poll prepares section-verification files. The connection is then verified in AURA and publication permission enabled. The plugin receives only published snapshots, not drafts. Thus, the read key retrieves data, while the WordPress administrator separately grants the ability to create local entries; this must not be described as unnoticed publication through an ordinary MCP read.
How pages are updated
The agent prepares and publishes content in AURA, then WordPress retrieves the current snapshot. This version schedules polling approximately every fifteen minutes through WP-Cron. As the WordPress documentation explains, that scheduler depends on page loads, so exact timing is not guaranteed. A manual action in settings is available for testing. The adapter manages its own post type; unrelated articles must not be overwritten. If a managed entry was edited locally, the next version is skipped for manual review. AURA being unavailable is not a command to delete previously created content.
What to check separately
Open the created article and check its text, canonical and inclusion in your WordPress configuration's sitemap. This plugin does not yet install referral tracking or server-side bot collection. A signed wake-up endpoint is prepared, but automatic webhook sending from AURA is not connected yet; polling is the working mechanism here. An additional IndexNow response is retained in WordPress and does not automatically synchronize into the AURA workspace. When stopping a project, disable mirroring and revoke the key. That stops updates, but the fate of already published pages must be decided separately.
Conditions and limitations
- Subdomains and WordPress in a subdirectory are not supported by the adapter
- Automatic AURA webhook sending is not connected
- The tracker and server logs are installed separately