Advocate MCP Structured Data

FAQ

Where can I get help?

Use the contact form at https://app.advocatemcp.com/contact or email
support@advocatemcp.com.

I already use Yoast or Rank Math. Should I use both?

Probably not both for the same business. Two descriptions of one business on one
page can confuse crawlers. The settings page warns you when it detects another
SEO plugin — ask Advocate which one to keep.

How quickly does a profile edit reach my site?

The plugin checks for updates about once an hour. Choose Refresh now to check
sooner. Cached pages may need to be cleared before they show the update.

Automatic checks run through WordPress scheduled tasks (WP-Cron), which only
run when your site is visited or when your host triggers them, so there is no
fixed delivery deadline. “Refresh now” checks immediately; a successful check
updates this plugin’s own copy of the profile, not caches in front of your site.

What happens if Advocate is down?

The saved profile can appear on newly generated pages for up to 24 hours after
its last validated download. Failed retries do not extend that time. After
that, publishing pauses until a valid download succeeds. The settings page
shows the pause and offers Refresh now. This uses the WordPress server clock;
keep it synchronized. It does not guarantee a deadline across clock changes.

Page/CDN caches may still contain older HTML and must be cleared separately.
This is an outage-age limit, not an authenticated remote withdrawal signal.
Updating the downloadable ZIP does not update existing installed copies;
replace the installed plugin through your normal WordPress update procedure.

Does this support WordPress multisite?

Activate and configure Advocate separately on each site. New network activation
is refused, and one business is never configured for all sites. Public website
path and nondefault port must match as well as hostname. Deactivation clears
that site’s refresh tasks and cached profile while preserving its settings;
reactivation needs a fresh download. Uninstall removes plugin settings too.
When two copies of the plugin are installed (see the 2.5.0 changelog), the
notice appears on each site’s own Plugins screen, not on the network Plugins
screen. A network-wide delete of the earlier copy restores settings only when
this copy is loaded in that Network Admin request, that is, active on the main
site; if it is active only on sub-sites, nothing is saved anywhere.

Legacy network deactivation cleans the current network, while uninstall checks
all networks because plugin files are shared. Automatic cleanup is limited to
100 sites. A larger scope is refused before any site is changed. A database or
cache failure stops cleanup with an error; resolve it and retry. Completed
sites may already be cleaned. Neither operation purges existing page/CDN HTML.

How does an administrator remove Advocate from more than 100 sites?

Use a maintenance window and a verified backup. Stop incoming PHP/cron work and
drain existing workers first; older plugin code does not honor the new inactive
marker. Inventory every site across every network. Use WP-CLI with
–skip-plugins=advocatemcp-structured-data to deactivate the plugin on every network and
any separately active site without loading its bounded automatic hooks. Keep
the plugin files in place until every site’s cleanup is verified.

For each site URL in that inventory, run the following with the current source
installed (a copy installed before 2.5.0 uses the advocate-agent folder and
main file name in both places). Replace the example URL. This reuses the plugin’s per-site cleanup,
then removes settings only after that cleanup succeeds. Stop on any error:

wp --url='https://example.com/site/' --skip-plugins=advocatemcp-structured-data eval '
require WP_PLUGIN_DIR . "/advocatemcp-structured-data/advocatemcp-structured-data.php";
advocate_deactivate_site();
$missing = new stdClass();
foreach ( [ "advocate_agent_settings", "advocate_setup_import", "advocate_setup_notice", "advocate_connect_attempt", "advocate_lifecycle" ] as $key ) {
    delete_option( $key );
    if ( get_option( $key, $missing ) !== $missing ) {
        WP_CLI::error( "Cleanup failed for " . $key . "; resolve storage errors and retry." );
    }
}
WP_CLI::success( "Advocate data and refresh tasks cleared for this site." );'

Retain a successful receipt for every site and verify that no Advocate refresh
task or plugin data remains. Only then remove the shared plugin directory and
clear page/CDN caches. A site-level Delete button does not bypass the global
100-site uninstall preflight. This operator procedure still requires a staging
rehearsal for your WordPress/WP-CLI and cache configuration.