All use cases

Use case · Optimization

Run A/B tests on your live site.

Choose a conversion, check how it is measured and let Autopilot test a focused change. Read the counts and the outcome before calling it an improvement.

  • One active test
  • Measured conversion
  • Wins, controls and inconclusive results

Eligible plan, published site, connected domain and a measured goal.

A laptop showing a terminal window.

What Frontpage does

Give Autopilot a goal. Let it test a small change.

A button label is easy to change. Knowing whether it helped takes a working measurement, a fair comparison and enough visitors. Frontpage keeps those parts with the site: the page, the challenger and the experiment report.

Autopilot runs one test at a time on an eligible published Frontpage site with a connected custom domain. You describe the conversion you want, check how it will be measured and choose whether to enable automatic testing and publication.

A goal you can check

Choose a visitor action, then review the measurement before starting the test.

One narrow change

Test a headline, CTA label or another allowed change while keeping the offer and prices intact.

A report with uncertainty

Compare visitor and conversion counts. A leading challenger is not automatically a proven winner.

An outcome that can be inconclusive

Autopilot can keep the control or finish without a winner. It does not have to call every test an improvement.

Side by side

Choose suggestions or automatic tests.

Growth Advisor
Autopilot
Purpose
Suggest site improvements for you to review
Run automatic A/B tests against a chosen conversion
Your choice
Accept or decline a suggestion
Enable automatic testing and check the measured goal
Publication
Accepting a suggestion starts work on the draft
Can keep a winner and publish automatically
Result
A proposed or completed site change
A win, a retained control or an inconclusive test
Availability
Included on every plan, including Free
Available on Scale, Enterprise and Internal plans

The problem

A leading variation is not the same as a winner.

An A/B test needs more than two versions of a headline. The conversion has to mean the same thing for both versions, and the result has to reflect enough activity. A small difference early in the test can disappear as more people visit.

The goal is vague

“More engagement” is hard to judge. Choose the action that matters, such as a particular signup or CTA click.

The change moves the goalposts

Keep the destination and tracking intact when testing a button label. Otherwise you may be comparing different actions.

A percentage hides tiny counts

Read visitors and conversions alongside the rate. One extra conversion can look large in a small sample.

The test is asked to decide too soon

A live test may need more data or finish inconclusive. Starting tests regularly does not guarantee a useful result on the same schedule.

A dim server room at night with closed laptops and unattended equipment.

How it works

Set the goal. Follow the test. Read the outcome.

  1. 01

    Prepare the site and goal

    Use an eligible plan, publish the site and connect the custom domain. In Autopilot Setup, describe the conversion and review its measurement.

  2. 02

    Enable testing and follow the comparison

    Autopilot runs one test at a time. Read the exact change and compare visitor and conversion counts in Activity.

  3. 03

    Check the outcome

    A supported winner can be kept and published automatically. Other tests retain the control or finish inconclusive. Review history before deciding what to do next.

Before you enable it

What to check before enabling Autopilot.

Keep the setup focused on one real customer action.

An eligible site

Scale, Enterprise or Internal, with a published build and connected custom domain.

A measurable action

Describe the conversion and verify the page or action Autopilot will count.

A stable comparison

Keep the underlying offer, destination and tracking consistent while testing the allowed change.

Clear instructions

Tell Autopilot the constraints that matter to the site. Review the allowed change types and keep public facts accurate.

A publishing decision

Enable automatic testing only when automatic publication fits how you manage the site.

A way to read the result

Use Activity and history to see the change, counts, status and available owner actions.

The testing process

Set up a comparison you can trust.

Keep the action consistent, the change small and the publishing behavior clear.

  1. 01

    Check how the conversion is counted

    Describe the visitor action in Setup and review the measurement Autopilot identifies before enabling it.

  2. 02

    Keep the experiment narrow

    Use one allowed change, such as “Request a quote” versus “Get a quote.” Do not change pricing, legal wording or the meaning of the offer.

  3. 03

    Read the full report

    Check the control and challenger, visitor counts, conversions and confidence. Use the result’s status rather than the largest displayed percentage.

  4. 04

    Keep control of automatic publishing

    Autopilot can publish the working copy when it keeps a winning change. Applying a challenger or rolling back also publishes; review other draft work before using those actions.

Score the current stack

Check the customer path before the experiment.

A website audit can help find usability problems before a test. Fix a broken customer path before trying to optimize the wording around it.

Free · No credit card · Results in your inbox

Two engineers in a dim ops room reviewing abstract experiment results on a monitor.

Two working processes

Choose how the next change happens.

Use Growth Advisor when you want suggestions to review. Use Autopilot when you want the automatic testing workflow and understand its publishing behavior. Neither establishes a fixed traffic or conversion improvement.

How Growth Advisor works →
A person in a hallway outside a glass server room looking something up on a phone.

What the result means

Measure the action you chose.

An experiment measures the conversion you chose. It does not establish that the page will rank higher or be indexed. Keep useful content, titles and links intact while measuring the customer action.

  • Read visitors and conversions together
  • Keep the offer and tracking consistent
  • Treat search indexing as a separate outcome
How Autopilot works on Scale →

See it in action

Start with the action, not a promised lift.

An illustrative setup conversation, not a measured customer experiment.

Review the actual measurement in Autopilot Setup. The example does not promise a winner or a conversion increase.

frontpage · your site
I want to measure clicks on the Request a quote button on our services page. Keep its destination, prices and offer unchanged.
Review the identified conversion in Autopilot Setup so you can confirm the action being measured.
We want to test small wording and layout changes. Keep the service terms and legal wording unchanged. We understand that enabled Autopilot can publish automatically.
Use those constraints in the setup, then enable testing when the site and draft are ready. Follow the experiment counts and outcome in Activity.

The gaps we fill

Three results are useful. Only one is a win.

The purpose is to learn which version to keep, not to produce a success claim every time.

Winner

The challenger earns enough support

A challenger needs enough visitors and evidence before the automatic decision can keep it. A displayed lead by itself is not that decision.

  • Visitor counts
  • Conversion counts
  • Decision status

Control

The existing version can be the right choice

Keeping the control is a useful outcome. It avoids turning every experiment into a permanent site change.

  • Same measured action
  • A comparison you can inspect
  • The existing version can stay

Inconclusive

Sometimes there is not enough evidence

Low traffic or a small difference can leave a test without a clear result. Say that plainly rather than turning a tentative rate into a proven improvement.

  • No forced winner
  • A recorded outcome
  • No guaranteed uplift

Questions

Before the first experiment.

Can I use Autopilot on another website builder?

This workflow tests a published Frontpage site on its connected custom domain. It is not a testing script for arbitrary external sites.

Which plans include it?

Autopilot is available on Scale, Enterprise and Internal plans. Growth Advisor is separate. Check current plans for current availability and limits.

Does hourly testing mean a winner every hour?

No. Start cadence limits when another test can begin. A running test still needs sufficient evidence and may finish without a winner.

Can it change prices or test a new offer?

Its current change policy excludes pricing values, legal text and changes to the meaning of the offer. Use allowed copy or layout changes that preserve the underlying facts.

What happens when I pause it?

Pause stops new experiments. A running experiment can still finish. Check the current experiment before treating pause as a stop to all activity.

Can Autopilot publish other draft work?

Yes. Its winning-change workflow publishes the working copy. Applying a challenger or rolling back also publishes. Review other unpublished work before enabling or using those actions.

Put the next test on the site.

Build a site around a clear customer action. When the site is ready, decide whether automatic testing and publication fit your workflow.

Autopilot can publish automatically. Review other draft work before enabling it.