The plugin is the primary future execution plane. It is designed to stay local to the licensed domain, to detect ownership conflicts early and to avoid duplicate or unclear output.
The plugin is intended to run on the WordPress site itself, not as a remote blanket editor. That keeps output logic close to the source, which matters for metadata ownership, heading structure and markup cleanup.
The first planned plugin pilot focuses on the homepage Meta Description. It stays intentionally small: homepage scope only, single signal family, measurable outcome, documented fallback.
The current reference description is 'Global Electro Music Online Radio 24 / 7', which confirms a clear optimization opportunity without justifying abrupt source replacement.
The product does not assume exclusive ownership over metadata. Existing theme, builder and SEO-plugin behavior must be mapped first. Only then can a safer replacement or coexistence path be chosen.
| Topic | This product | Typical alternative |
|---|---|---|
| Metadata ownership | Handled near WordPress source and plugin filters | Edge rules cannot reliably fix ownership confusion |
| Structure fixes | H1, markup and output modules can be scoped per template or page type | Edge layers cannot see enough template intent |
| Conflict detection | Theme, builder and SEO-plugin overlap can be inspected locally | External layers usually infer conflicts too late |
No. The target model is narrow scope first, with explicit allowed scopes and rollback readiness.
Because source ownership must be mapped and replacement logic validated before a safe migration path exists.
Licensing, scope binding and control-plane validation keep the future plugin path disciplined.