ManifolderOverview
Paste your website URL and copy a script onto your site.
Manifolder is a script you put on your website so agents can use the actions you already have: contact forms, quotes, bookings, hours, and similar.
You paste a URL, copy a snippet, and put it on the site.
Who this is for
These docs are for website owners. Sign in, open Snippet, and work from your own site.
What to do
- Sign in and open Snippet.
- Paste your website URL.
- Review detected tools and suggestions.
- Copy the script and paste it on your site.
Where you paste depends on the host we detect (you can change it):
- WordPress: header or footer. Insert Headers and Footers, or the theme header.
- Shopify: catalog and cart often already work. Use the script only for gaps such as quotes or bookings.
- Webflow: Site settings, Custom code, before the closing body tag. Publish.
- Wix: Settings, Custom code, body end, all pages. Publish.
- Squarespace: Website tools, Code injection, Footer.
- Netlify: Site configuration, Snippet injection, before
</body>. - Vercel or custom HTML: shared layout or
index.html, immediately before</body>.
Paste it once in the theme. Contact and other pages pick it up.
To try it without installing, open Snippet, copy the script, open the scanned site in Chrome (150+ with website-tool support), and paste it in that tab's console. Reload clears it.
The script is two tags: a small config block, then webmcp.js. It runs in the
visitor's browser.
Shopify stores
If a scan already finds catalog and cart tools, those already work. Keep any script only for remaining gaps such as quotes or bookings. Do not install a second catalog or cart script.
Retest on production
- Sign in and open Snippet.
- Paste a site URL you control.
- Copy the script.
- Paste it on that site immediately before
</body>, then reload. - Open the page in an assistant browser that supports website tools. Ask it to read a suggested item, such as opening hours, and check its answer.
- On a form page you control, ask it to send a clearly labeled test request. Check both the page's confirmation and the destination where requests arrive.
The script needs a browser with website-tool support. Seeing the script in the page source confirms installation, but does not prove an assistant can use it. A form submission starting does not by itself confirm delivery. Forms that submit to another website, live inside embedded frames, or require additional verification may need a separate integration.
Verify visitor journeys
When website verification is enabled for your account, setup step 4 automatically checks the saved site's installed tools and runs up to four realistic visitor journeys. Returning to the step reconnects to the report. On Sites, open a site to view its latest report, screenshots, evidence, and run history above the tool inventory.
Use Edit visitor journeys to change the visitor goal and expected outcome, add or remove journeys, or disable them. Enable at most four for a run. Save edits before choosing Run verification. Edits apply to the next run, and earlier reports retain their original journeys. Stop ends an active run; you can start another from the same panel.
- Passed: recorded evidence supports the expected outcome.
- Ready to submit: synthetic inputs mapped to valid form fields and reached the submission boundary. Nothing was sent, and delivery is not verified.
- Failed: the tool or result did not meet the expected outcome.
- Blocked: missing tools or execution restrictions prevented the journey.
- Inconclusive: time limits, infrastructure issues, or insufficient evidence prevented a verdict.
Installation status is separate: finding tools alone does not prove a journey works. Verification uses public pages and installed website tools, with no login, purchase, booking, cart change, or live submission. Some dynamic tools or embedded forms cannot be safely verified. Reports identify compatibility execution separately from native browser execution. Screenshots and downloadable browser traces are private to your account and expire after thirty days.
Improve the snippet from a report
Completed reports with failed or blocked journeys generate a proposed snippet repair. For an older report, choose Generate snippet repair. The repair uses that report's evidence to fix missing page mappings or add public read tools. It preserves working tools and contact forms. Unsupported actions remain listed for attention.
Review the proposed changes and checks, then choose Copy updated snippet. Replace your old Manifolder snippet with the complete updated snippet on every page, then publish that change in your website editor. Manifolder cannot change your website automatically.
After installing the update, choose I’ve updated my site, verify again. The original visitor journeys run against the live installed tools. The update is marked verified only when its targeted journeys pass and previously passing or ready-to-submit journeys keep their results. Copying the snippet alone does not prove it is installed.
If the update needs attention, review its verification report. Previous snippet and repair evidence contains the previous version to copy back if you need to restore it. Restoration also requires publishing a change in your website editor. Discard repair dismisses a draft without changing your website. The system checks candidates in an isolated browser and never keeps generating repairs from a repair's own test run.