AI Agentic Browsing

Get found by AI shopping agents — not just search engines

Shoppers are starting to ask AI assistants to compare products, fill in checkout forms, and find a store's return policy on their behalf. If those agents can't read your storefront, they skip it. Agentic Browsing prepares your CS-Cart or Multi-Vendor store to be found, understood, and safely acted on by AI agents — and to score well on Chrome's new Lighthouse Agentic Browsing checks — without touching a single core file.

Install it once and every storefront on your installation gets its own, independently configurable results. Run five brands from one CS-Cart engine? Each domain gets its own llms.txt, its own catalog, its own security.txt, its own Asset Links, its own schema extras, and its own settings.

Full setup guide and field reference: Agentic Browsing documentation.

Why store owners are adding this now

• Be readable to AI agents, not just crawlers. Publishes the exact files and markup that AI browsing agents and the Lighthouse Agentic Browsing audit look for — so your store shows up ready instead of failing checks your competitors already pass.
• Set up in under five minutes. Install, enable, clear cache — done. Sensible defaults are on from the first save; every advanced field is optional and editable in plain settings tabs.
• Built for multi-storefront and Multi-Vendor setups. One installation, unlimited domains, independent results for each. No duplicate installs, no per-domain workarounds. Works on single-storefront installs too.
• Virtual or writable .well-known — your host, your choice. Virtual (default) serves /.well-known/* from CS-Cart with no discovery files on disk. Writable creates per-storefront files such as security_st1.txt / ard_st2.json while the public URL stays /.well-known/security.txt on each domain — ideal when nginx only serves static files under /.well-known and you cannot edit the vhost.
• Nothing to maintain on the server for Virtual mode. No file uploads to your document root, no cron jobs, no core overrides — virtual URLs update from addon settings the moment you save.
• Granular control, storefront by storefront. Turn any single feature off for one storefront without touching the others — useful for staging domains, regional stores, or vendor-specific storefronts in Multi-Vendor.

What your store gets

• llms.txt — a clean, editable Markdown summary of your store at https://your-domain/llms.txt, with placeholders that auto-fill your store name, catalog, cart, and account links per storefront. Aligned with the llms.txt convention and the Lighthouse llms.txt audit.
• Optional robots.txt — off by default. When enabled, serves an SEO-safe, AI-friendly /robots.txt per storefront (single User-agent: * so LLM crawlers follow the same Disallows). When off, CS-Cart core robots still apply.
• Optional security.txt — off by default. Editable RFC 9116 body at /.well-known/security.txt with placeholders such as [host], [current_path], and [expires]. Virtual by default, or security_st{ID}.txt in writable mode. Your custom lines are kept — the add-on does not overwrite a saved body.
• Optional Asset Links — off by default. Editable /.well-known/assetlinks.json for Android Digital Asset Links / App Links, virtual or writable per mode.

• Agentic Resource Discovery catalog at /.well-known/ard.json (plus a legacy-compatible copy at /.well-known/ai-catalog.json) — a structured map of your home page, store summary, and product search tool, referenced from every public page via rel="ard" links, a matching HTTP Link header, and JSON-LD. Built to the Agentic Resource Discovery spec.

• WebMCP-enabled forms — your existing storefront forms gain declarative tool names, descriptions, and parameter descriptions, plus a registered product-search tool, so agents can search and submit without guessing your markup. Addresses the Lighthouse forms missing declarative WebMCP, registered WebMCP tools, and WebMCP schema validity checks.
• Published search tool schema — the same validated contract is also available at /.well-known/search-products.schema.json for agents and auditors that fetch the schema by URL.
• Validated JSON Schema — the search tool's input contract is written to JSON Schema draft 2020-12 and checked before the page even registers the tool, so you're not shipping a broken schema to agents. Verify independently anytime with the JSON Schema tooling page.
• Schema.org structured data — optional Organization and WebSite markup (including site search and your saved company phone, email, and address), plus normalized product markup for the SEO add-on. Confirm results instantly with Google's Rich Results Test or the Schema Markup Validator.
• Extra JSON-LD — paste your own Schema.org object (or an array of objects) into settings — for example Store, LocalBusiness, or FAQPage. The add-on merges it into the same page graph. Placeholders such as [store_name] and [store_url] work inside the JSON. No <script> tags required — paste raw JSON only. Copy-paste examples: Schema markup docs.

• Accessible names for agents — fills in an accessible name wherever a button, link, or field is missing one, so agents (and screen readers) can identify and act on it. Existing labels are always left untouched. See Accessibility for agents.

Discovery URLs at a glance

• /llms.txt — always virtual
• /robots.txt — virtual when enabled
• /.well-known/ard.json and /.well-known/ai-catalog.json
• /.well-known/search-products.schema.json — when WebMCP is on
• /.well-known/security.txt — when security.txt is on
• /.well-known/assetlinks.json — when Asset Links is on

In Virtual mode, delete any physical root .well-known discovery folder/files and pass all of those URLs to PHP (not only security.txt). In Writable mode the add-on writes *_st{ID}.* files for you — no vhost change required.

Who it's for

Any CS-Cart, CS-Cart Ultimate, or Multi-Vendor store owner who wants to stay visible as shopping shifts toward AI assistants — and who wants a head start on the Lighthouse Agentic Browsing checks before they become table stakes. Especially valuable for stores running several storefronts or brands from a single installation — and still simple on a single domain.

Compatibility

• CS-Cart and CS-Cart Ultimate
• Multi-Vendor
• Single-storefront and multi-storefront installations
• Responsive theme, Vivashop, and ABT Unitheme2 — plus any theme that inherits Responsive
• Global or per-storefront settings, your choice
• Zero core file modifications

Install in five steps

1. Download the add-on package.
2. Go to Add-ons → Manage add-ons.
3. Upload, install, and enable Agentic Browsing.
4. Clear the CS-Cart cache once.
5. Open /llms.txt and /.well-known/ard.json. Default mode is Virtual: delete any root .well-known discovery files/folder and ensure the vhost passes /.well-known/* to PHP. Use General → Writable .well-known folder only if you cannot change the vhost.

Detailed settings walkthrough (including Extra JSON-LD examples): https://docs.sonotrix.cloud/docs/cs-cart-addons/cs-cart-agentic-browsing/.

References

• SonoTrix documentation
• Extra JSON-LD / Schema markup examples
• RFC 9116 — security.txt
• Google Digital Asset Links
• Lighthouse: llms.txt
• Lighthouse: Agentic Browsing scoring
• Lighthouse: Forms missing declarative WebMCP
• Lighthouse: Registered WebMCP tools
• Lighthouse: WebMCP schema validity
• Lighthouse: Accessibility for agents
• Agentic Resource Discovery
• llms.txt
• Google structured data