Feature overview

Feature layers for WordPress SEO, performance, release safety and scoped delivery.

The product combines observe-only intelligence, policy-aware planning and a future plugin execution plane that stays domain-bound, conflict-aware and rollback-ready.

Control plane learns from reports, trends and rollback evidencePlugin MVP stays in safe_mode or observe_only by defaultRelease, policy and rollback objects remain domain-scoped

Read the architecture docs See the safety model

Reference Modeobserve_only

Portal Gateapproval_required

Homepage Status200

Response Time236.9 ms

HTML Size183,759 bytes

Sitemap Status200

Observe and learn

Reference intelligence before execution

The Hetzner control plane remains responsible for observing, learning, validating and planning. It turns raw report data, historical trends and pilot evidence into safer execution decisions.

Historical rollups for 1d, 7d, 30d and 365d
Read-only report harvesting and domain result summaries
Trend and doctrine checks before any future live action

Use the docs entry point

Plugin-first execution

Local WordPress execution with narrow scope and conflict checks

The plugin path is the primary future way to improve metadata, heading structure, markup quality and other on-page issues that belong close to the WordPress rendering layer.

Homepage Meta Description pilot path
H1 consolidation and markup hygiene as later scoped modules
Conflict detection against themes, builders and SEO plugins

Inspect the plugin path

Release and rollback

Domain-bound delivery objects instead of vague global rollout

Licenses, channels, manifests, policies and rollback profiles are modeled per domain. That keeps product delivery traceable and avoids unclear multi-domain side effects.

Stable, pilot and rollback channels
Policy narrowing instead of policy expansion
Rollback profiles linked to domain and scope

Review licensing and scope

Differentiation

Feature emphasis

Topic	This product	Typical alternative
SEO structure	Metadata, H1, markup and content ownership stay close to WordPress output	Edge-only fixes miss template and plugin root causes
Performance discipline	Performance work is evaluated alongside scope, conflict risk and rollback cost	Performance tweaks are often treated as isolated wins
Domain governance	Licensing, releases and policies stay domain-scoped	Shared logic can drift into accidental cross-domain effects

FAQ

Frequently asked questions

Why is the WordPress plugin the primary execution path?

Because the current highest-value opportunities are metadata, headings, HTML weight and markup quality, which belong closest to WordPress rendering.

Does the product already run live changes on customer sites?

No. The current product state remains controlled, local and approval-gated for any real external effect.

Next step

Want the full model behind the features?

The docs, security and licensing sections explain how these features remain controlled and reversible.

Review validation and rollback See scope and license boundaries