2UA SEO Release Guard provides one administrative home for three monitoring modules:<\/p>\n\n
The plugin installs local module settings and an administrator-controlled connection to the 2UA cloud service. Activation alone does not contact 2UA or any other external service.<\/p>\n\n
Cloud monitoring requires an administrator to explicitly connect this plugin to the 2UA service. During connection, the plugin sends the public site URL, a random installation identifier, WordPress version, and plugin version. A short-lived verification token is then made publicly available at the plugin's WordPress REST API challenge route so 2UA can verify control of the public host.<\/p>\n\n
After connection, the plugin may send selected public page URLs, release event metadata, and the public run identifier and handoff purpose used to open a result on 2UA. It does not send page bodies, customer data, orders, form submissions, passwords, or WordPress user accounts. Requests are signed with a locally stored connection secret. The settings screen explains this transfer and requires explicit administrator consent before the first request.<\/p>\n\n
Published posts, pages, and WooCommerce products, theme switches, and completed plugin or theme updates can schedule an automatic release event. Repeated hooks are debounced for five minutes. The remote request runs through WordPress Cron after the publishing request finishes, and 2UA remains the authority for URL and automatic-run plan limits.<\/p>\n\n
The settings screen can also schedule a manual check. WordPress Cron polls the cloud run in the background and stores the latest status, verdict, counts, and complete finding list returned for that run in non-autoloaded local options. Account connection and optional result navigation open on 2UA through a short-lived one-time handoff. The plugin does not hide returned findings or embed checkout.<\/p>\n\n
The plugin is free to install. Anonymous cloud use is limited to one website, up to three public URLs per event, two manual runs per day, and the latest result. A connected free 2UA account increases this to five URLs, five manual runs per day, one automatic release run per day, seven days of cloud history, and critical email digests. Monitor Lite adds more inspected URLs, automatic release monitoring, daily monitoring, warning alerts, and 30 days of history. Higher 2UA plans provide their published website and monitoring limits. These limits govern processing performed by the external 2UA service; payment does not unlock or expand code or locally displayed findings inside the plugin.<\/p>\n\n
Inactive anonymous integration data expires after seven days. Connected monitoring history follows the active 2UA plan: seven days for Free and 30 days for Monitor Lite. Disconnect revokes the API credential immediately. Deleting the connected 2UA account removes its integration data and any stored diagnostic artifacts.<\/p>\n\n
2UA service information:<\/p>\n\n
2ua-seo-release-guard<\/code> directory to \/wp-content\/plugins\/<\/code> or install the ZIP through Plugins > Add New.<\/li>\n- Activate 2UA SEO Release Guard.<\/li>\n
- Open Settings > 2UA Release Guard.<\/li>\n
- Choose the monitoring modules you intend to use.<\/li>\n
- Review the public metadata disclosure, confirm consent, and select Connect to 2UA.<\/li>\n<\/ol>\n\n
Activation stores local configuration only. It does not make a remote request.<\/p>\n\n\n
\nDoes activation send my site data to 2UA?<\/h3><\/dt>\nNo. Activation creates local, non-autoloaded WordPress options only.<\/p><\/dd>\n
Who can configure the plugin?<\/h3><\/dt>\nOnly users with the manage_options<\/code> capability can configure the plugin or initiate checks.<\/p><\/dd>\nAre connection secrets shown on the settings page?<\/h3><\/dt>\nNo. Connection identifiers and HMAC secrets use separate non-autoloaded options and are never rendered by the settings screen.<\/p><\/dd>\n
Does the plugin contact 2UA while rendering my website?<\/h3><\/dt>\nNo. Pairing, rotation, and disconnect requests run only after protected administrator actions. Frontend page rendering does not call the 2UA API.<\/p><\/dd>\n
What happens if the connection response is interrupted?<\/h3><\/dt>\nConnect again from the settings page. 2UA verifies the same public host and safely replaces the unreachable secret without creating a duplicate installation.<\/p><\/dd>\n
Why can an automatic check start late?<\/h3><\/dt>\nAutomatic checks use WordPress Cron. On low-traffic sites, WordPress may not start a scheduled event until the next request reaches the site.<\/p><\/dd>\n
Does the plugin support WordPress multisite?<\/h3><\/dt>\nYes, with per-site activation. Network activation is rejected because every site needs its own public-host verification, connection secret, limits, and monitoring state.<\/p><\/dd>\n
What if WP-Cron is disabled?<\/h3><\/dt>\nConfigure the normal system cron request to wp-cron.php<\/code>. The settings screen shows a warning while DISABLE_WP_CRON<\/code> is enabled because checks and result polling cannot otherwise run.<\/p><\/dd>\nWhere can I see the check result?<\/h3><\/dt>\nThe settings screen shows the latest verdict, counts, and every finding returned for the latest check, with a device profile beside each URL. The optional result button opens the same run on 2UA through a short-lived one-time link.<\/p><\/dd>\n
Is the plugin free?<\/h3><\/dt>\nYes. Installation and all local WordPress functionality are free. Cloud checks have the clearly stated anonymous and connected-free service limits in the Description. Monitor Lite and larger 2UA plans add external processing capacity, history, alerts, or automatic monitoring. Payment never occurs inside WordPress and does not unlock code in this plugin.<\/p><\/dd>\n
Does 2UA modify my content, theme, sitemap, or schema?<\/h3><\/dt>\nNo. The plugin observes release events and asks 2UA to inspect selected public URLs. It does not edit posts, products, themes, plugins, sitemap files, robots.txt, or structured data.<\/p><\/dd>\n
How do I get support?<\/h3><\/dt>\nEmail support@2-ua.com with the plugin version, WordPress version, the visible error state, and the approximate time of the problem. Never send the HMAC secret, passwords, customer data, or a database export.<\/p><\/dd>\n
What should I do before deleting the plugin?<\/h3><\/dt>\nUse Disconnect from 2UA first so the remote credential is revoked. WordPress uninstall then removes all local 2UA options, credentials, cached capabilities, verification state, and scheduled events.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.1.1<\/h4>\n\n\n- Show every finding returned by the latest cloud check in WordPress without a client-side finding limit.<\/li>\n
- Clarify that paid plans affect external processing, history, and alerts rather than local plugin features.<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- Add the plugin bootstrap, autoloader, local lifecycle state, administrator capability guard, and module settings.<\/li>\n
- Add explicit cloud opt-in, public-host verification, signed WordPress HTTP API requests, bounded safe retries, secret rotation, disconnect, and interrupted-pairing recovery.<\/li>\n
- Add manual and debounced release event collection, same-host public URL resolution, WooCommerce product support, server-enforced run capabilities, and post-request WordPress Cron dispatch.<\/li>\n
- Add background result polling, native verdict and finding output, device profiles, protected account\/result\/upgrade handoffs, and distinct operational error states.<\/li>\n
- Add WordPress Privacy Policy Guide content, retention and disconnect guidance, a pre-connection tracking guard, and complete local option and cron cleanup on uninstall.<\/li>\n<\/ul>","raw_excerpt":"Monitor SEO-critical page, sitemap, indexability, and schema regressions after website changes.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/366022","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=366022"}],"author":[{"embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/twoua"}],"wp:attachment":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=366022"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=366022"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=366022"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=366022"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=366022"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=366022"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}