Agentic Kit install matrixevery platform, every install path.
All 13 platforms BridgeToAgent ships with side-by-side. Per platform: install time, difficulty, install path, the one common gotcha, link to the step-by-step guide. Pick by your platform — or scan the install-pattern groups below if you’re choosing between platforms and want to know which is easiest to ship the kit on.
Last reviewed 2026-05-18
All platforms — ranked by volume share
| Platform | Time | Difficulty | Install path | Guide |
|---|---|---|---|---|
| Shopify | 10 min | Beginner | Content → Files + URL Redirects | Open |
| WordPress | 4 min | Beginner | WP File Manager plugin → webroot | Open |
| Wix | 8 min | Intermediate | Cloudflare Worker (every plan) or Custom Code (Premium) | Open |
| Squarespace | 8 min | Intermediate | Cloudflare Worker (every plan) or Code Injection (Business+) | Open |
| Webflow | 7 min | Intermediate | Webflow Assets + 301 Redirects | Open |
| BigCommerce | 10 min | Intermediate | Storage Manager + 301 Redirects | Open |
| Magento / Adobe Commerce | 6 min | Intermediate | Direct filesystem (pub/) | Open |
| HubSpot CMS | 8 min | Intermediate | File Manager + URL Redirects | Open |
| Drupal 9/10/11 | 5 min | Intermediate | Webroot + .htaccess RewriteRule exceptions | Open |
| Ghost | 8 min | Intermediate | Theme public/ + routes.yaml (Pro) or direct content/public/ (self-hosted) | Open |
| Next.js / Astro / Hugo / Gatsby / SvelteKit / Remix / Vite | 3 min | Beginner | Drop into public/ (or static/) | Open |
| Framer | 7 min | Beginner | Framer Assets + Domain Redirects | Open |
| cPanel / shared hosting | 3 min | Beginner | File Manager → public_html | Open |
Hover any row to reveal the platform’s most common gotcha. Full per-pattern guidance in the sections below.
Note · UCP-native platforms
Shopify auto-enables Google’s Universal Commerce Protocol (UCP) at /.well-known/ucp on every store with an MCP transport binding at /api/ucp/mcp. The other 12 platforms in this matrix have no native UCP support as of May 2026 — implementing it manually is a days-not-minutes engineering project outside the kit’s scope. The kit instead generates the four files UCP doesn’t cover (agents.json, llms.txt, agent-instructions.md, and the auto-discovery <link rel="alternate"> tags). For the orientation, see the three-protocols map or, for the Shopify-specific view, the what the kit adds on top explainer.
The five install patterns
The 13 platforms collapse into five install patterns. If you’re choosing between two platforms and want the kit-friendlier one, the pattern groups below tell you what you’re signing up for on each.
Direct filesystem (the cleanest path)
Drop the three files directly into the platform's webroot or public-output directory. No redirects, no plugins, no asset hosting. Works when the platform gives you actual filesystem access or a build-output convention.
- Magento / Adobe Commerce — 6 min · Direct filesystem (pub/). Gotcha: .htaccess directives may need adjustment for .json/.txt/.md.
- Drupal 9/10/11 — 5 min · Webroot + .htaccess RewriteRule exceptions. Gotcha: Rewrite block placement matters — must sit above index.php rule.
- Next.js / Astro / Hugo / Gatsby / SvelteKit / Remix / Vite — 3 min · Drop into public/ (or static/). Gotcha: HMR doesn't pick up new public/ files — restart dev server.
- cPanel / shared hosting — 3 min · File Manager → public_html. Gotcha: Don't put in subfolders (e.g. /uploads/) — must sit at root.
Plugin-based uploader
The CMS doesn't give you direct filesystem access, but a community plugin does. Install the plugin, use it to upload to the webroot, done.
- WordPress — 4 min · WP File Manager plugin → webroot. Gotcha: Security plugins (Wordfence, iThemes) may block .json/.md.
Files area + 301 redirects
Upload via the platform's file manager, copy the CDN URLs the platform returns, configure 301 redirects from the canonical root paths to those CDN URLs. Most commerce platforms that don't expose the filesystem use this pattern.
- Shopify — 10 min · Content → Files + URL Redirects. Gotcha: Don't use Content → Pages (renders as HTML, corrupts JSON).
- BigCommerce — 10 min · Storage Manager + 301 Redirects. Gotcha: Older themes restrict .md uploads — rename to .md.txt.
- HubSpot CMS — 8 min · File Manager + URL Redirects. Gotcha: Re-uploading mints a new URL — update redirects each time.
Assets panel + redirects
Same idea as files-plus-redirect but the platform calls it Assets and the redirect UI is platform-specific. Visual-builder platforms (Webflow, Framer) live here.
Workaround required (Cloudflare Worker recommended)
The platform locks the install path behind paid plan tiers or doesn't expose a redirect feature you can use. Put Cloudflare in front of the site and serve the three files from a Cloudflare Worker. Works on every plan tier of every platform.
- Wix — 8 min · Cloudflare Worker (every plan) or Custom Code (Premium). Gotcha: Custom Code gated to Premium plans; Cloudflare needs DNS move.
- Squarespace — 8 min · Cloudflare Worker (every plan) or Code Injection (Business+). Gotcha: Code Injection gated to Business+; verify MX records survive DNS move.
- Ghost — 8 min · Theme public/ + routes.yaml (Pro) or direct content/public/ (self-hosted). Gotcha: Routes feature gated to paid Ghost(Pro) plan.
When to pick which path
If you’re building a new site and the platform is still open: direct filesystem > plugin uploader > files+redirect > assets+redirect > workaround required. Direct filesystem is the cleanest because there’s nothing to break later — no plugin to update, no redirect URL to maintain, no asset CDN URL that mints a new value after re-upload. Workaround-required is the most fragile because it depends on a DNS layer (Cloudflare) you didn’t need otherwise.
If you’re installed on an existing site, the decision’s already been made for you — open the platform’s guide and follow the step-by-step. Every path on this matrix is documented to the point where a non-technical site owner can complete the install in one sitting using only the platform’s standard UI.
Frequently asked
Why is Webflow listed as Intermediate and Next.js as Beginner?
Difficulty reflects the surface area the install touches, not the technical depth. Webflow Intermediate because the install spans three places (Assets panel, Site Settings → Publishing, Custom Code → Head). Next.js Beginner because the install is a single file-copy step that needs no configuration — even though the underlying framework is technical, the kit install isn’t.
What if my platform isn’t listed?
The kit is just three files plus three discovery tags. Any platform that lets you serve files at your domain root and edit the head can install the kit. The 13 platforms on this matrix cover ~95% of the public web by platform-share — for the rest, find the closest-match install pattern above and follow the same approach. Common substitutes: any static-site generator → follow Next.js. Any cPanel-shaped shared host → follow cPanel. Any visual website builder → follow Webflow if it has Assets + Redirects, otherwise Squarespace/Wix (Cloudflare Worker).
How often does this matrix update?
Quarterly or sooner when a platform meaningfully changes its install path (admin section renamed, feature gated to a new plan tier, file-manager UI updated). Last reviewed 2026-05-18.
Can I install the kit myself or do I need to buy it?
You can write the three files by hand — the formats (llmstxt.org, agents.json, plain-Markdown runbook) are intentionally simple. The $49 kit automates the parts most operators get wrong: crawling your real sitemap, extracting forms and actions from the rendered DOM, validating every action URL against your live site, and producing output that passes the Lighthouse audits as a build-time gate. The deliverable is the same file format, populated with verified facts. Pick whichever path fits your time-vs-money tradeoff.
Platform-specific agent-ready checklists
Deeper guides per platform — beyond the install row above. Each post covers the four agent-readable surfaces (Schema density, kit files, structured data, WebMCP readiness) and the platform-specific install path in full.
- The 2026 agent-ready Shopify checklist →Beyond Agentic Storefronts — four-surface model for Shopify stores.
- The 2026 agent-ready WordPress checklist →For site owners who don’t write code — plugins, uploads, no FTP.
- The 2026 agent-ready Webflow checklist →Where Webflow’s native Schema gets you 80%, and what the kit closes.
- The 2026 agent-ready Squarespace and Wix checklist →Template-platform pair — paid-plan gate + Cloudflare workaround.
Same kit. 13 platforms. Two-minute generation.
Free 5-second readiness check first. $49 once. Files delivered in under 2 minutes with the platform-specific install guide bundled.