What breaks
Contact form 7 error contact form not found: fix
The page shows an error where the form should be, so no visitor can send anything. Mimiq opens the contact page as a visitor and shows whether a form is there.
Why does my page show a contact form not found error from Contact Form 7?
The shortcode on the page names a form ID that the plugin cannot find, so the page prints a not found message where the form should be. Check the ID against the plugin's form list: if no form has it, the form was deleted or rebuilt on this site. If the shortcode itself shows as plain text, the block it sits in does not run shortcodes, or the quotes were pasted in curly. A simulated visitor opens the page and reports whether a form is there and what the page shows instead.
What this looks like in a report
“The contact page says contact form not found where the form should be. I looked for a phone number or an email address and found neither. I tried the studio's social media page and got no reply.”
The fix. Replace the shortcode on the contact page with the ID shown for the live form, and type the quotes by hand rather than pasting them. Show the studio's email address beside the contact area as a fallback whenever the form fails to load.
An illustration. Run a test to see your own.See a real sample report
The shortcode points at a form that is no longer where it was
A shortcode is a pointer. It holds a form ID, and the page asks the plugin for that form each time it loads. When the form is rebuilt, the new copy gets a new ID, and the pointer still aims at the old number. Owners duplicate a form to edit it, then paste the new shortcode into one page and leave the old one on another. A form rebuilt on the live site also has a new ID that a copied staging page cannot find. The form still appears in the plugin's list, so the owner assumes the page is fine.
- Read the shortcode on the page. The number in the id must match the ID shown beside a form in the plugin's list.
- Open the plugin's form list and check the shortcode and its ID beside each form name, not only the title you remember.
- Look for curly quotes around the ID. A shortcode pasted from a document often fails on them.
- Check the block type. A code or preformatted block shows the shortcode as text and runs nothing.
- Compare the live and staging copies of the page. A form rebuilt on one site has a new ID.
Three ways the page loses the form
The first is a deleted or rebuilt form. When a form is removed and made again, the new one has a new ID, and every page that pointed at the old one now prints a not found message. The second is a copied page. Duplicating a page copies its shortcode, so the copy keeps pointing at the original form. It works until the original is deleted, and then both pages break at once.
The third is a shortcode that never ran. A code or preformatted block shows the shortcode as text, so the visitor sees bracketed words in place of the form. Curly quotes from a pasted document do the same, because the plugin often does not recognize a quote that is not straight. The fault sits in the page content, not in the plugin, and you can find it by searching the page for the bracket.
What the words on the page tell you
Read the text where the form should be. A bracketed line such as [contact-form-7 404 "Not Found"] means the ID has no matching form on this site. The plain shortcode text, with its brackets still visible, means the page never ran it, so the block or the quotes are the cause. A form that appears and then fails to send is a different fault, and the mail and script checks apply to it.
The ID is easy to confirm. Open the form list in the plugin, read the ID next to each form name, and compare it with the number in the page's shortcode. If the number is missing from the list, the form is gone. Rebuild the form, or point the page at the form that replaced it, and then check the page again.
A simulated visitor finds the form or does not
The visitor opens the contact page from the address you give and looks for the form where a stranger would expect it, below the opening text. If the form is there, it fills in the fields and presses Send. If a bracketed line shows in its place, the report records that step with a screenshot of the text, and any failed request made while the page loaded.
The run cannot read the page source or the plugin's form list, so it cannot tell you which ID the shortcode holds. It shows what a stranger sees. Check the ID in the editor, then run the visitor again to confirm the page now shows the form. Keep a copy of the working shortcode in your notes, so the next rebuild can be checked against it.
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 rebuilt form or a restored backup can change the ID again
The break returns when someone rebuilds the form, restores an older copy of the site or copies a page over from staging. Rerun the visitor who looks for the form after each of those changes, on the live address and on the preview. Owners who gate the site behind a password add it to the run, so the visitor reaches the contact page the way a customer would.
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 plugin list show the form but the page does not?
The list shows the forms that exist on this site. The page works only if its shortcode holds the ID of one of them. A page copied from another site, or from before a rebuild, can point at an ID that is no longer in the list, so the form exists and the page is wrong.
What does the 404 Not Found text in the brackets mean?
It means the ID in the shortcode has no matching form on this site. It is the plugin reporting a missing form, not a fault in the visitor's connection. Find the ID the page holds, compare it with the list, and replace the shortcode with the ID that is there.
Will a simulated visitor show me the shortcode?
No. A run sees the page the visitor sees, so it shows the form or the error, not the bracketed code behind it. It cannot tell you which ID the page holds. Read the shortcode in the editor, and use a visitor run as the final check.
Can a visitor still send a message while the form is missing?
Not through that page. With the form missing there is no field to fill in and no Send button. Keep a plain email address or phone number visible beside the contact area, so a visitor who hits the error has another way to reach you.
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.