Before you launch or pay for traffic
Website checklist for beginners: the public site
A website builder's editor shows your draft, and a visitor sees only what you last published. This checklist opens the public address the way a stranger does, and simulated visitors show where a first-time site stops.
What should a first-time website owner check before publishing?
Check the public address in a private window signed out of your website builder, because the editor shows your unpublished draft. Look for placeholder text, a page title that still says Untitled, a form that sends nowhere and a menu link to a template page. A simulated test opens the public address the way a visitor does and shows the step where each one stops, with a screenshot of the page at that step.
What this looks like in a report
“My son wants guitar lessons, but this page is a table of lorem ipsum with a price of zero. I cannot see the times, which are the one thing I came for. I will ask the other parents.”
The fix. Replace every sample line with the real schedule and price, then open the public address in a private window on a phone. Search the page for lorem ipsum and the word sample before you share the link.
An illustration. Run a test to see your own.See a real sample report
The editor shows your draft and the public site shows your last publish
Most website builders keep your edits as a draft until you publish them. You work in the editor, where the page looks finished, and you test it while signed in, so the menu, the form and the fonts behave the way they do for you. A visitor opens the public address, which shows the last version you published, in a browser that has never seen your login. Anything you changed after that publish, and anything the editor treats differently, stays invisible to you until a stranger runs into it.
- Placeholder text such as lorem ipsum, a sample address or a price of zero
- The page title in the browser tab, which should name the business and not Untitled
- The contact form: does it reach an inbox you read, and does it confirm the send?
- Menu links that point to a template's demo page or to the editor's own preview
- A site password or coming-soon setting that hides the whole site from a visitor
How it works
- 01
Sign out of the builder, then open the public address
Open a private window and type the address exactly as you will share it. The editor preview runs under your login, so it can show a page no stranger can see yet.
- 02
Read every line that is not yours
Look for sample text, stock photos, a sample phone number and any price that reads zero. A visitor takes those lines as facts about the business.
- 03
Send one message through each form
Submit the contact form with a real question, then check the inbox you set up for it. A form that shows a thank-you message and sends nothing is easy to miss on a first site.
- 04
Tap every menu link on a phone
A template often ships with menu links to demo pages. Each link should open a page you wrote, and the page name should match the menu label.
Publish, then check the address, not the editor
Most builders keep your edits as a draft until you press publish, and the public address serves the last version you pushed. A headline you changed and never published shows up in the editor and never reaches a stranger. The page title is a separate setting in most builders, the words in the browser tab, and a template often ships it as Untitled or as a sample name. Check the public address after each publish, and read the tab title at the same time, because the headline does not set it.
Placeholder text is what a stranger reads first
Templates ship with sample text, so a first-time owner tends to replace the headline and forget the rest. The price, the opening hours, the address and the team photos often keep their sample values. A visitor reads those lines as facts. A stranger who finds a sample address, or a team member named Team Member One, decides the business is not real yet, and leaves without the phone number you meant to show them.
A form and a menu that look connected but are not
A builder can show a contact form that is not linked to any inbox until you link one. The form may show a thank-you message while the submission goes to a placeholder address or nowhere at all. Menu links can point to a template's demo page or to a page you deleted. Send a real message through the form, read it in your own inbox, and click each menu item on a phone. Write down which links open a page you wrote, and fix the rest before you share the address.
Where to look, and what each view hides
| Where you look | What it hides | What it shows you |
|---|---|---|
| The editor preview | Whether the last publish reached the public address | The layout and text as you last drew them |
| Your phone, signed in | The public view a stranger gets when they are not signed in | How the menu and text fit a small screen |
| A private window, signed out | Your own habits, such as the links you already know | The public address, the tab title and the placeholder text |
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A template update can bring demo links back into your menu
A first site changes after launch: you add a service page, the builder pushes a template update, or a new domain takes over the address. Any of these can restore a demo page to the menu or reset the form's destination. Open the public address in a private window after each one, and compare the stop with your last run. A site you share on a social profile needs the check before each post.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Do I need to know code to check my site?
No. Everything on this checklist is visible on the page: the text, the menu, the form and the tab title. If you can open a private window and type an address, you can run the first step.
How soon after publishing should I check the public address?
Right after each publish, before you share the link anywhere. Check again after a change to the menu, the form or the domain, since those are the parts that carry settings from the editor to the public site.
Can a simulated visitor tell me whether my site is good?
No. It shows whether a visitor can read the page, reach the form and find the links, and where a visitor stopped, with a screenshot. It does not judge your writing and does not predict how many people will get in touch.
Will a simulated visitor send my contact form?
It can fill in the form and submit it the way a visitor would, and the report shows what the visitor saw after the submit. The test does not check where the message ends up, so send one real message yourself and read it in your own inbox.
Does the test work on every website builder?
It works on any public address a browser can open, so it does not depend on the builder. It cannot read the builder's settings, though, so a hidden site shows up as a visitor who stopped at the first page.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.