By platform
Test Squarespace website: links a visitor follows
Your pages look right when you open them from the editor, but a first-time visitor starts at the home page and follows the menu, a button or a link from an email. Mimiq sends simulated visitors down those same routes and reports the first link that goes nowhere.
How do I test a Squarespace website before launch?
To test a Squarespace website before launch, start from the home page in a private window and follow the links a stranger would use: the menu, the main button, and any link in your emails or on social media. Open every page on the way, and note each link that loops back, lands on a password or coming soon page, or shows a page you did not expect. A simulated test follows those routes the way a first visit does, and it reports the link where each visitor stopped.
What this looks like in a report
“Services is the second item in the menu. When I tap it, I land on a page that says the content cannot be found. Projects works, so I wonder what else is broken. I open a different firm's site instead.”
The fix. Point the Services menu item at the live services page, then publish and tap every menu item on a phone in a private window. Note each one that shows a not found page, and fix it the same way.
An illustration. Run a test to see your own.See a real sample report
A stranger uses your links, not the page list in the editor
The editor lists every page you have built, so it is easy to think the site is complete when all of them exist. A visitor never sees that list. They see the menu you set, the buttons you placed and the links you pasted, and each of those can point somewhere else: a page you renamed, a draft, or a page you left out of the navigation. A page can be finished and still unreachable from any place a visitor would click, and the editor will not flag it.
- Open the home page in a private window and tap each menu item on a phone.
- Follow the main button. Does it open the page it names, or a different one?
- Open each link in your welcome and reminder emails. Does each one load?
- Look for any page that shows a password or coming soon screen to a visitor.
- Check the footer links too, since some visitors look there for contact details.
The menu decides which pages a first visitor sees
A first-time visitor sees the menu before any of your content, and most of what they do next follows from it. Each item in the menu is a link you chose, to a page that may have been renamed since. If the link was set before the page moved, the menu still points at the old address, and the visitor reaches an error. A menu item can also point at a section of a page that was later deleted, so the page loads and the visitor finds nothing where they expected a price.
Check the menu in the order a visitor reads it. Tap the first item on a phone, go back to the home page, and tap the next, then the one after that. A menu that looks complete in the editor can still hold an item with no link set, and a visitor who taps that item gets nothing at all, not even an error they could report.
Pages a visitor cannot reach from any link
A page can exist and still sit outside every route a stranger takes. It may be left out of the navigation, which keeps it off the menu but leaves its address live. It may be behind a password or a coming soon screen that you forgot to remove. It may be a draft that was published by mistake. Each of these looks fine from inside the editor, because you know the address and you open the page directly.
Test the reachable path, not the list of pages. Start from the home page and follow only links, the way a visitor would. Any page you want a visitor to reach that you cannot reach this way is a gap, even if you can open it yourself. Write the gaps in a list, and treat that list as the work to finish before launch.
Emails, footers and buttons that point elsewhere
Links also leave the site. A welcome email, a booking reminder or a social profile can point at an address you copied from a draft, so the visitor lands on something that looks like your site but is a different page. Footer links often lead to policy and contact pages, which visitors check when they decide whether to trust a site. Open each link from outside the site, in a private window, and check it loads the page you intended.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
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 renamed page leaves an old menu link pointing at nothing
Renaming a page, moving it into another section or deleting a draft can leave an old link behind without any warning. Run the same visitors through the menu and the main button again after each change, and check the links in your emails and footer. If the site is behind a password while you build, that password needs paid credits, and the visitors can only get past it with the password you give them.
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
Why does the menu work in the editor but not on the live site?
Editor previews can differ from the live site, for example when a page is still a draft or a domain has not finished connecting. Open the live address in a private window, tap every menu item, and compare where each one lands with the name on the item.
Can I keep a page out of the menu and still have it live?
Yes. A page can be kept out of the menu and still be online. It then needs a link from somewhere else, such as a button or an email, or a visitor following links will never reach it. Test it the same way as the rest of the site, by following links only.
Will a simulated test show how many visitors will sign up?
No. The test shows which links a simulated visitor could follow and the screen where it stopped. It does not predict how many real visitors would sign up, so use your analytics or a live experiment for that number once the links work.
Do I need to test every page of the site?
Test every route a first visit could take: the menu, the main buttons and the links in your emails. A page that no route reaches is either a mistake to fix or a page you can safely leave unlinked. Decide which one it is before you launch.
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.