How to test your website like a real customer, not like its builder

To test your website like a real customer, start from the public URL, signed out, on a phone, with one concrete goal such as "buy a gift under a budget" or "start a trial and create a first project." Walk the path without using anything you know as the builder, and record every hesitation as well as every error. Then fix the most expensive hesitation first and walk the same path again. That loop, repeated, is how small teams find the problems that cost them sales.

Why is the builder the worst tester of their own site?

You know where every button is. You know which links are broken and silently avoid them. You are probably signed in, on a fast laptop, with an empty cache that is never empty. None of that is true for your customer.

Builders also test features, not journeys. You check that the contact form sends. A customer wants to ask whether the product fits their use case, and the form is just one step on the way. If the path to it is confusing, the working form does not matter.

What is a customer goal, and how do I write one?

A goal is a sentence that describes an outcome a real visitor wants, in their words, not yours.

• Weak goal: "Test the checkout."
• Strong goal: "Buy a medium hoodie in black as a gift, and have it delivered to a different address."
• Weak goal: "Check signup."
• Strong goal: "Sign up for the free plan, invite a teammate, and create a first report."

Strong goals force you through the real path, including the parts in between features. Write three to start: one for your most common visitor, one for a skeptical first-timer, and one for a visitor with a specific constraint such as a budget, a deadline, or a phone-only setup.

How do I set up a realistic session?

• Use a private window, signed out.
• Start from the page most visitors land on: often a product page from an ad, or a blog post from search, not your homepage.
• Use a phone width unless your audience is clearly desktop.
• Clear any saved form data, coupons, or cookies that a new visitor would not have.
• Do not open your admin panel in another tab. You are not the admin right now.

What should I record during the session?

Record more than errors. Most lost sales are not caused by an error message. They are caused by a pause.

• Moments you reread something because it was unclear.
• Moments you scrolled looking for information, such as the price or the delivery time.
• Moments you felt doubt: is this secure, will I be charged, can I return it?
• Moments you went back.
• Anything that did not work at all.

For each, write three short lines: what I tried, what I saw, what I expected. These notes are specific enough to fix.

How do I turn notes into fixes?

Group the notes by how close they are to the money.

1. Anything broken on the money path. Fix immediately.
2. Anything that made you doubt you should continue. Add the missing proof or information right where the doubt appeared.
3. Anything that made you search. Move the information to where you looked first.
4. Anything that simply took too long. Remove a step or a field.

Then run the same goal again. If you used an AI tool to build the site, paste the three lines for each finding into your editor as a prompt. Specific notes produce specific fixes.

How often should I repeat it?

Run it whenever something changes: a new theme, a new app, a new pricing plan, a new release of your product. Many teams add it to their release routine, because the bugs that hurt conversion are usually introduced by a change nobody thought touched the money path.

Can this be automated without losing the realism?

The realism comes from three things: a fresh, signed-out start, a goal in the customer's words, and notes about hesitation as well as errors. A good automated tool keeps all three.

Persqo runs exactly this method with AI visitors. You give it a URL and goals, it creates realistic visitors with different backgrounds and intentions, and each one tries to complete the goal in a real browser. You get screenshots, a session replay, and a written account of where each visitor hesitated or got stuck, plus a fix prompt for Claude Code or Cursor if you build with AI. Sessions stop before entering payment details or submitting anything sensitive.

Read more about the visitors themselves in AI persona testing. Try it with a free check, or see the builders page and the developers page for the full workflow.

The real-customer testing checklist

• Write three goals in the customer's words.
• Start each session signed out, in a private window, from a real landing page.
• Use a phone width unless your audience is clearly desktop.
• Record hesitations, searches, doubts, and back-clicks, not only errors.
• Write each finding as tried, saw, expected.
• Fix the finding closest to the money first.
• Re-run the same goal after each fix.
• Repeat after every change to the store or product.

Questions people ask