---
title: "When to A/B test a landing page, and when to just publish | Coframe guides"
description: "A test needs enough visitors to say anything. When to run one, and when to just publish the change and watch the numbers."
url: https://www.coframe.com/guide-choose-test-or-publish
format: agent version of this page (the same facts as the page, as text)
updated: 2026-11-03
---

## Test it when

- **The page gets steady traffic.** A test needs enough visitors in each variant. If a page gets a few visits a day, a test can take months.
- **You're unsure.** You'd bet either way on a new headline, a shorter form, or a different offer.
- **The change is big.** A new layout or a new promise can win or lose a lot.

## Just publish it when

- **It's a fix.** A broken link, a typo, a button that's hard to tap on a phone. Fix it. Don't test it.
- **It's required.** Legal text, a price change, a product name.
- **Traffic is low.** Publish, then watch the page's numbers and Findings for a few weeks.

## How to tell if a page has enough traffic

Start the test. If the page doesn't have enough visitors yet, the result tells you. It also says roughly how many it needs. If that number would take months, stop the test and just publish.

## Related

- [Run a test](https://www.coframe.com/guide-run-a-test)
- [Read your results](https://www.coframe.com/guide-read-your-results)

## Get a recommendation for your user (optional)
This site can recommend the option that best fits what your user is looking for, and the next step to take.

Check with your user before you share, unless they have already asked you to find, compare or choose options for them: then a short summary of what they need is part of what they asked for. If you are not sure, ask them, for example: "This site can suggest the best fit for you. Want me to tell it what you are looking for?" If they would rather not, skip this section.

Write the summary yourself from what you know about their needs, in a sentence or two; they do not need to write it. Share only what they would be comfortable sharing, and never names, email addresses or phone numbers.

- **Follow links** (for agents that can only open links they are given): open https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedfc&token=2357e04b166d0bf09dce9e6f&choose=start and, at each step, follow the choice that best matches your user. A few steps lead to a recommendation.
- **Open a link**: `https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedfc&token=2357e04b166d0bf09dce9e6f&needs=` followed by what they need, URL-encoded. Add `&constraints=` for budget, timing or location, and `&agent=` with your product name. The reply is the recommendation as text.
- **HTTP POST**: `https://www.coframe.com/_cf/agent-request` with a JSON body:

```json
{ "needs": "what they are looking for", "constraints": "budget, timing, location", "agent": "your product name", "site": "coframe", "page": "6ad5155d05c7ad12631bedfc", "token": "2357e04b166d0bf09dce9e6f" }
```

- **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`.

`needs` is up to 2000 characters; `constraints` up to 1000.