Autonomous Mode

Autonomous mode lets HubSEO execute fixes itself instead of preparing them for you. It is opt-in, capped, and deliberately conservative.

The defaults

• Off. The default state is auto_deploy_safe_changes: false.
• Even enabled: at most 3 deployments per week.
• Protected directives are excluded by architecture, not by policy: canonical tags, 301 redirects, robots.txt, URL migrations. These always require explicit human verification. No configuration can override this.

What qualifies as safe

A change can execute autonomously only when all of these hold:

• Classified safe_auto by the intervention system.
• Confidence ≥ 0.85.
• A verified rollback plan exists.

Anything else waits for your click. When you come back, each waiting intervention shows its evidence, its classification, and its rollback plan.

Where autonomy fits the tiers

• Diff view only · the default: everything is prepared, nothing executes.
• Deploy and verify · you approve each deploy; the verification re-scan is automatic.
• Autonomous · safe interventions execute within the weekly cap.

Autonomy requires a Pro, Business, or admin access level. See Plans.

The operating loop

1. Audit finds a blocking finding.
2. A fix is generated with a rollback plan.
3. The change is classified.
4. safe_auto + high confidence: executes, then re-scans.
5. Anything else: queued for you.
6. The finding closes only when the re-scan confirms the measurement.

Why so conservative

Autonomous SEO tools that push redirects and robots changes without a human are how sites lose traffic overnight. HubSEO's position: the machine prepares and verifies; the human owns anything that can change what Google sees. If a change is protected, it needs your hand on purpose.