Questions, answered.

Think of it as a marketing site that maintains itself. Rollouts watches your pages, your rankings, and your competitors, then does the work — new pages, SEO repairs, outreach drafts — and hands you each change to review. It runs every day, not once at setup.

It's how Rollouts works. It monitors your site, rankings, traffic, and competitors continuously; it acts by building pages, fixing SEO, and drafting outreach; and it surfaces everything as clear next steps you can review or approve. The dashboard is just how you check its work.

No — it absorbs the grunt work. Page builds, SEO chores, and first drafts stop eating your team's week, so the humans stay on positioning, brand, and judgment. Headcount leverage, not headcount replacement.

No. It starts from your current site: hand over the URL, wait out the one-minute scan, and it works within the pages and stack you have now. Nothing needs migrating before you begin.

About a minute after you connect, the scan and a ranked opportunity list are ready. A first optimized page is usually live before the day ends — review speed is the only real gate.

It builds and rewrites pages, fixes technical SEO, adds schema and internal links, drafts account outreach, and runs experiments. You decide how much runs automatically versus what waits for your review.

Only if you turn that on. By default every autonomous change ships as a reviewable pull request — nothing goes live behind your back.

Yes. The scan extracts tokens, type, and voice from your live site into a design contract, and everything the agent ships is generated against it — new pages match on arrival.

Yes. Everything syncs to a Git repo your team owns, so developers keep full version control and can refine anything in their own IDE.

It ranks opportunities by winnable impact — the pages and fixes most likely to move traffic and pipeline first, not a random backlog.

It watches competitor pages, rankings, new content, and ad activity continuously, and flags meaningful changes with the action to take — so you hear about a competitor's launch from Rollouts, not from a lost deal.

An alert that names what moved and pairs it with the counter-move: the page to build, the comparison to refresh, the query to defend. One click routes it to the agents.

Yes. Rank positions for you and each rival, topics neither side has covered, pages of yours losing ground — all of it is tracked, so decay shows up as an alert instead of a quarterly surprise.

Yes. Rollouts tracks which AI engines cite you and your competitors, so you can see the answer-engine battle, not just the classic SERP.

That's Rollouts Grow, which is rolling out now. When it's live, Grow will resolve anonymous sessions to company names, check each one against your ICP, enrich the strong fits, and sync them to your CRM — turning traffic from a chart into a call list. Today's live product is the Web engine: site building, SEO, and AI-answer optimization.

AEO means structuring pages so answer engines — ChatGPT, Perplexity, Google AI Overviews — quote you when they answer a buyer's question. Rollouts handles the mechanics: schema, FAQ blocks, passages an engine can lift cleanly. Authority counts for less here, so smaller sites can win.

Start free — a daily credit allowance, no card required. Paid plans start at $50/mo, and everything runs on one simple credit system with no per-seat fees.

Each action has a credit price — building a page, identifying a visitor, running an experiment — and everything meters from a single balance. Usage is the bill; seats and add-ons never appear on it.

Data is encrypted in transit and at rest, sessions are signed server-side, and a formal third-party security audit is planned ahead of GA. Integrations get scoped permissions, so you decide what each one can read or touch.

Tell us what you're trying to run. The library already spans the usual growth motions, and new Playbooks get built with customers every month — describe yours and the team will scope it.