Choose the capacity your team needs.

Yes. The trial lasts 14 days and is subject to plan and usage limits. A paid subscription starts only when you explicitly complete checkout. A trial without payment details does not convert automatically.

Serse explains findings and prepares supported changes for review. Inspect the evidence and proposed effect before approval. Unsupported changes include manual next steps; a connection alone does not make every operation available.

New paid work, generation and automation stop when the trial expires. You keep viewing, export, manual drafting, account management and safe recovery access. Your sites, content and history are retained until you request deletion.

Yes. Review and approval come first. Bounded autopilot requires at least three human-approved, successfully applied and live-verified changes in the same site and operation family, owner or admin opt-in, valid recovery and budget, and no unresolved failures. The 30-day rollback hold also applies. New article publication, major rewrites, GBP changes and outreach still require explicit approval.

Supported operations offer reviewed recovery while their snapshots remain available and unexpired. Check the covered fields, current destination and expiry in the work record. Changes to those fields, missing access or an unresolved provider result can block recovery. Some operations require manual recovery in the provider or a new reviewed change; not every action has an undo.

Yes. Businesses, growth teams and agencies can organize research, briefs, content, technical reviews and reports by site. Portfolio views and workspace roles support work across client sites. Specialist strategy and creative work can remain part of your process.

Connect your website for research and choose a supported publishing destination in Settings. Native workflows cover WordPress, GitHub, Shopify, Webflow, Wix, HubSpot, Sanity and Contentful. Operations depend on provider access, selected resources and field mappings. Local project access requires a runtime that can reach that filesystem. Drafts remain exportable when no publishing destination is connected.

A finding leads to inspectable evidence, a brief or proposed change, human review and a recorded operation. Native publication is separate from checking the customer website. Performance measurement follows a confirmed publication and may remain unavailable or inconclusive.

Add your website and business context, then inspect the setup checklist for that site. Search Console and analytics add performance evidence; a publishing connection enables its supported operations. Setup and collection time depend on provider permissions, site size and available data.