By platform
Squarespace form not showing up: which setting
The form is on the page in your editor, but a visitor who opens the page sees the text around an empty space, a password screen or a page that does not exist. Mimiq loads the live address the way a visitor does and shows which of those they get.
Why is my Squarespace form not showing up on the live page?
A form that shows in the Squarespace editor but not on the live page usually sits behind a setting between the editor and the public address. The page may be unpublished, a password may cover it, a visibility setting may hide the block or the section that holds it, or the page may be left out of your menu. Each one gives a visitor a different screen, so check which screen they get before you rebuild the form. A simulated test opens the live address the way a visitor does and reports the screen it got.
What this looks like in a report
“The Contact page loads with the heading and an address. There is no form under them and no message, so I cannot send an inquiry. The menu link is the only way I can see to contact anyone.”
The fix. Publish the contact page, link it from the main menu, and remove any password or hidden-section setting that covers the form block. Then open the live address in a private window while signed out, and confirm the form appears and accepts a test message.
An illustration. Run a test to see your own.See a real sample report
The editor shows the block, and the public address shows something else
The editor shows you a page with every block in place, whether or not a visitor can reach it. The public address is a separate question. It depends on whether the page is published, whether the navigation links to it, whether a password stands in front of it, and whether a setting hides the block or the section that holds it. A visitor who types the address and gets a password screen never sees the form, while the owner who tests from the editor sees it every time. Nothing in the form is broken. The visitor simply never reaches it.
- Open the page address in a private window while signed out. Does it load, or ask for a password?
- Click the page in your site menu. Does the address match the one you typed?
- Check the section that holds the form for any setting that hides it.
- Check whether the page is still a draft, or set to stay out of the navigation.
- Compare the editor preview with the live address. Does the form appear in only one of them?
Four settings between the editor and a visitor
A page can be fully built and still be unreachable. The first setting is publication: a page that is still a draft does not exist for visitors, and the address may show a missing page. The second is navigation: a page can be live but left out of the menu, so the only way to reach it is by typing its address. The third is protection: a password on the page or on the whole site replaces the content with a sign in screen, and the form sits behind it. The fourth is the section or block itself, which a setting can hide from visitors while the block still shows in the editor.
Tell the four apart by the screen a visitor gets
The screen is the clue. A missing page answers the typed address with a page not found message, which points at publication. A page that asks for a password points at protection. A page that loads with the heading and the text but no form points at the block or the section, so check that section's settings first. A page that loads at the typed address but not from the menu points at navigation, and the menu item may be sending visitors to an older page with the same name. Open the page the way a visitor would, from the menu and then from the typed address, and note which one shows the form.
What the test checks, and what stays with you
A simulated visitor opens the live address while signed out, takes the menu path or the typed address, and looks for the form. If the form is there, the visitor fills in its fields and submits it, and the report shows any error on the way. The test does not check that the message reaches your inbox, or whether it lands in spam. Send yourself a message through the form from a personal account, and check your own mail. A form that shows on the live site and accepts a message is working, even when nobody has written to you yet.
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 new page or password can hide the form from visitors again
Each new page, redirect or password you add to the site can put a visitor in front of a screen with no form. After any change to publishing, navigation or page access, load the contact page signed out in a private window, from the menu and from the typed address. Keep that check for every page that has a form, because a form that disappears from the live site is hard to notice from the editor.
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
The form is in my editor. Why can't I see it on the live site?
The editor shows the draft, and the live site shows the published version. Publish the page, then reload the live address in a private window. If the form still does not appear, check whether a setting hides the block or the section that holds it, since a hidden section is easy to miss while you are working in the editor.
Why does my contact page load, but the menu link goes somewhere else?
The page may be set to stay out of the navigation, so you reach it only by its address, or the menu item points at an older page with a similar name. Click the menu link and compare its address with the one you typed. If they differ, edit the menu item so it points at the right page.
Will the test show whether people will send an inquiry?
No. The test shows whether a simulated visitor can see the form, fill it in and send it. It does not predict how many real visitors would send one. Use your analytics for form submit rates, and the test to find the setting that hides the form.
Does the test check that my inbox gets the message?
No. The test can submit the form and show the confirmation a visitor gets. Whether the message reaches your inbox, or lands in spam, is something you check in your own email account, with a message you send through the form yourself.
Can the test get past a password on the page?
On a run with paid credits, you can give the test the site password for a protected preview, and it will go through. Without the password, the report shows the sign in screen as the step where the visitor stopped, which is the answer you need to change the setting.
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.