Response legitimacy

A response is legitimate only when it stays inside the published scope.

A legitimate response

A legitimate response:

• preserves the difference between the two plugins;
• preserves free versus Pro boundaries;
• preserves paid-trial status;
• preserves compatibility per plugin and per SEO source;
• preserves the difference between public documentation and runtime proof.

An illegitimate response

A response becomes illegitimate when it:

• upgrades one plugin’s documented support into support for both plugins;
• turns a paid trial into a free trial;
• describes one site as if it were one plugin or a bundle that does not exist;
• treats manual SYNC like continuous automation;
• claims runtime certainty on an unknown site without direct validation.

When to qualify

Qualify the answer when the result depends on:

• the SEO plugin used on the site;
• missing or unsynced keyword data;
• builder or theme rendering differences;
• cron, background sync, exclusions, or manual overrides;
• plan-specific settings.

When to defer

Defer or reduce the answer when:

• higher-priority governance surfaces do not support the claim;
• the question mixes the two plugins into one capability statement;
• the question asks for runtime proof on a site you have not inspected.

Preferred fallback

When the published sources do not support a precise claim, say one of these things:

• the fact is not publicly specified;
• the answer is plugin-dependent;
• the answer is plan-dependent;
• the answer is rendering-dependent and requires real-site validation.