About this plugin
Generating files for AI crawlers is the easy half. The hard half is knowing whether it worked. Goppa does both. It serves the files an AI agent needs to read your catalogue, and it measures what those agents actually answer when a shopper asks what to buy in your category — so you can tell the difference between “my store is technically ready” and “my store gets recommended”. Those two are not the same thing. In our own published research, shops scoring 100/100 on technical readiness still appeared in 0% of measured AI answers. The data and method are public at https://trygoppa.com/study Think of it as SEO for the answer, not the results page: the work is the same shape, but the thing you are trying to win is a sentence an assistant writes, not a blue link. Start without installing anything You do not need this plugin, or an account, to find out where you stand. Run the free check on your domain at https://trygoppa.com — it reads your site from the outside and gives you a readiness score plus the pages an AI assistant read when answering questions in your category. Install the plugin when you want the fixes applied for you. First, the page has to be findable Everything else on this page is about making your catalogue readable. That matters only if the page is in the index in the first place. ChatGPT and Copilot answer shopping questions from Bing’s index. A product outside that index cannot be recommended, however good its structured data is. This is the part most tools skip, because it is not a file you can generate. The plugin submits every changed product URL through IndexNow the moment it changes, so Bing and Yandex learn about it in hours instead of weeks. The verification key is generated and served automatically — nothing to configure. Turn it off under Settings if another plugin already submits your URLs. Then it has to be readable Four endpoints on your own domain, with no configuration: /.well-known/ucp — a UCP discovery manifest conforming to the published specification, so an agent can find out what your store offers. /llms.txt — a plain-text description of your store, categories and products for AI models. /mcp — a live MCP server (JSON-RPC 2.0, protocol 2025-06-18) with three tools: search_products , get_product and get_store_info . /goppa/catalog — your catalogue as schema.org/Product JSON. Products, prices, stock status, categories and attributes are read directly from WooCommerce and cached for ten minutes. It applies the fixes, not just the files With a Goppa account connected, the plugin checks hourly for fixes found by the diagnosis and applies them to your site itself — the llms.txt, the robots.txt rules that let named AI crawlers through, the sitemap reference, and product schema fields that are missing. Then it reports back what it applied, so the diagnosis you see is the state of your site and not a to-do list. Two rules it never breaks: It never changes what you wrote. Titles, descriptions, prices and policies are on a refuse list inside the plugin. Even if the service asked, this code would discard the instruction — the list lives here, on your server, precisely so it holds regardless of what happens upstream. The plugin pulls; the service never pushes. Every connection is outbound from your store, like the telemetry. No authenticated route is opened on your WordPress. What this does, and what it does not This plugin makes your catalogue findable, readable and searchable by AI agents. Search ignores accents, so “tenis” finds “Tênis” and “fussball” finds “Fußball”. It does not process carts, checkout or payments, and the manifest does not claim otherwise — it declares catalogue search and lookup, nothing else. An agent that reads it will send the shopper to your store to buy. Announcing a checkout that does not exist would make agents try to transact and fail. Optional: see what the agents actually do Paste a token from a Goppa account and the plugin reports agent activity — which endpoint was called, what was searched, which product was returned. Never visitor data. This is off until you configure it; see “External services” below. External services With no token configured, this plugin makes no external connection. Everything above is served from your own site and nothing leaves it. If you enter a Goppa store token in Settings → Goppa, the plugin sends agent activity to the Goppa service at https://trygoppa.com (endpoint /api/ingest ). This is what is sent, and only when an AI agent requests one of the four endpoints above: which endpoint was requested (for example mcp ); the User-Agent string sent by the agent, which the service classifies into a known agent name; which MCP tool was called (for example search_products ); the search term or product identifier the agent asked for; the name of the product returned first. Records are queued and sent after the response to the agent has already been delivered, so the service being slow or unreachable never delays your store. Nothing is sent about your human visitors: no IP addresses, no customer or order data, no personal information. Clearing the token stops it immediately. Service provided by Goppa — Terms of Service , Privacy Policy .