Before you launch or pay for traffic
Pre launch website: links that lead nowhere
You know which pages are unfinished, so you skip them when you click around. A stranger has no such list, and each link that ends on a template or a password screen tells them the product may not be real.
What should a pre launch website show a visitor before the product ships?
It should show what the product does and who it is for, a sign-up that says what happens next, and only links that lead to finished text. Every link in the menu and footer has to land on a real page or on the waitlist form, and the site has to open at its public address without a password screen. A simulated visitor clicks through the site the way a stranger does, and the report shows the link that ended on a blank page and the step where each visitor gave up.
What this looks like in a report
“The headline is what I need, so I tapped Pricing to see the cost. The page is full of placeholder text, and the price box says Lorem ipsum. If they cannot finish a page, will the app work?”
The fix. Hide the Pricing link until the page has a real price, or point it at the waitlist with a line saying the price comes at launch. Tap every link on a phone before the link goes out, and check that each one lands on finished text, not a template.
An illustration. Run a test to see your own.See a real sample report
Every link to an unfinished page tells a visitor the product is not real
The owner of a placeholder site knows which pages are unfinished and skips them. A stranger clicks what the page offers: See how it works, Pricing, Read the docs. Each link that lands on a template, a blank page or a not-found message ends the visit, and the visitor has no reason to expect a finished product at launch. A password screen does the same damage, because the visitor cannot pass it at all. A visitor who joined the waitlist may still wait for the email, but they will doubt it after the site they saw was empty.
- Every link in the menu and footer ends on a finished page or on the waitlist form.
- The public address opens with no password screen while visitors are meant to read it.
- No page shows a default title such as Untitled in the browser tab or a link preview.
- The waitlist form shows a line on success that says when the product ships, and what comes next.
- Search engine blocking is switched off only when the site is ready to be found.
List the links a visitor can tap, not the pages you built
The wrong version is a footer with Blog, Careers and Docs links that point at pages you started and never finished. You know they are drafts, so you never tap them. The right version starts from the homepage on a phone and taps every link you can reach, writing down where each one lands. A link that opens a builder's template, a blank page or a not-found message goes on the list to fix. Either remove the link until the page exists, or keep it and show one line saying what is coming. The same check finds the social profile link that still points at an account you stopped using.
A password screen looks like a broken site
While a site is being built, owners often put a password on the whole address, or switch on the builder's own preview lock. A stranger gets a prompt they cannot pass, and reads it as a site that is broken or abandoned. A short line on that screen, naming the month the product opens, tells them it is on purpose. Simulated visitors get past a protected preview only if you give them access, with paid credits, through a site password or a bypass secret. Without that access, the report shows the step where the visitor stopped at the prompt, which tells you the lock sits in front of the whole site.
The waitlist step has to say what happens next
The waitlist form is the one step a visitor is meant to finish, and it often ends with a bare thank you or nothing at all. The wrong version shows the success message out of view, below the fold on a phone, so the visitor taps Join again and sees an error saying the address is already in use. The right version puts a line directly under the button that says the address is saved, when the product ships, and that a welcome email is on its way. A simulated visitor's screenshot shows whether that line appeared where the visitor was looking, and whether the step ended there.
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 launch date that slips can leave a stale promise on every page
The launch date moves, a page gets written and a link gets added. Each change can leave a dead end or an old date, and the owner rarely taps through the menu on a phone after an edit. Rerun the same visitors through the menu and footer after every change, so a new link is checked before anyone taps it. With paid credits, visitors can open a protected preview of a build that is not yet public.
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
Should I put up a placeholder site or wait until the product is ready?
That depends on what the visitor can do there. A site that collects interest works when every link leads somewhere finished, the waitlist says what happens next and the product is explained in plain words. A site with dead links loses the people it was meant to collect, and the ones who stay are harder to win back at launch.
Should I block search engines on a site that is not ready?
Block them while pages are unfinished, and remove the block when the site is ready to be found. A block left on after launch hides the site from search. Check that setting on the live address after each deploy, because a new build can bring an old setting back.
Can a simulated visitor tell me whether people will join my waitlist?
No. It does not predict how many real people will join, and a simulated run is not a count of your visitors. It shows which link led to an empty page, where each simulated visitor stopped, and whether the success line appeared. Your join rate has to come from real visitors.
Should I hide an unfinished page or delete it?
Hide it from the menu and the footer, and keep it unlinked until it is finished. Deleting it is fine when nothing points to it. A visitor who reached it from an old post still needs a page that says what is coming, not a not-found message.
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.