Goppa – AI Visibility: llms.txt, IndexNow and AI Crawlers

Changelog

0.7.1

• Apple Intelligence added to the robots.txt access list.

Goppa already counted Applebot-Extended when it visited and already
checked whether your site blocked it. It just never asked it in. The
allow-list had drifted from the two lists beside it; this closes the gap.

0.7.0

• WooCommerce is no longer required. Goppa now runs on any WordPress
  site.

Three things that never needed a catalogue now work without one: the AI
crawler count, IndexNow, and the Content Signal in robots.txt. The
catalogue endpoints, the feed check, the product summary and the FAQ
still need WooCommerce and appear when it is running.

• New: AI crawler visits are counted on your own site, with no
  account. GPTBot, ClaudeBot, PerplexityBot and the others are counted
  by name and shown on the settings screen. The count never leaves your
  server.
• IndexNow now covers pages and posts, not only products. The hook
  was save_post_product, which left every site without a shop out of
  the plugin’s strongest single feature.
• The Content Signal no longer needs a Goppa account. It is a
  permission you grant, not a change of access, so it is on by default
  with a switch on the settings screen. The crawler access rules in
  robots.txt still come from a connected diagnosis, because those do
  change access.
• The settings screen says what is working on a site without WooCommerce
  instead of explaining what is missing.

0.6.8

• robots.txt now carries a Content Signal saying this store may be used in AI answers.

Cloudflare turned the Content Signals format on across more than 3.8 million domains with ai-train=no and ai-input deliberately left blank — they did not want to guess. ai-input is the one that says “you may use this page to build a generative answer”, which is the only thing this plugin exists to achieve. A crawler that reads blank as “no” quietly drops the store from the answers it wants to be in.

Goppa now writes Content-Signal: search=yes, ai-input=yes. It does not touch ai-train — training a model on your catalogue is your call, and some shops want it off on purpose. If you or your CDN already set a Content Signal, yours is left alone.

0.6.7

• Reordered, not rewritten. IndexNow is now the first thing this page
  explains, before the endpoints. A meta-analysis of 54 studies published
  in May 2026 puts URL accessibility as the strongest single factor
  in whether an AI cites a page — 9.5 out of 10, ahead of everything else
  the plugin does. It was described here as a footnote, starting with
  “It also submits”.
• The settings screen now says why the IndexNow number matters, not just
  what it is. The llms.txt line already explained itself; the line for
  the stronger factor did not.
• Nothing was removed. llms.txt is still served and still useful — it is
  simply not the thing that decides whether you get recommended.

0.6.6

• The plugin now declares that it needs WooCommerce. From WordPress 6.5
  that means WordPress itself will not let you activate Goppa without
  WooCommerce, and shows the dependency on the plugin card.
• On WordPress 6.0 to 6.4 that header is ignored, so the settings screen
  now says it in words. Before this, a store without WooCommerce saw
  “0 products”, “0 in the feed” and an empty catalogue on every endpoint,
  with nothing explaining why — which reads as a broken plugin rather
  than a missing dependency. Nothing was ever broken: every WooCommerce
  call was already guarded. What was missing was the sentence.

0.6.5

• New, and off until you turn it on: when a shopper arrives from ChatGPT,
  Perplexity or Claude and buys in that same visit, the order is tagged
  with where they came from, and the totals reach your Goppa dashboard
  split into what an assistant can be shown to have brought and what it
  merely took part in. The two are never added together.
• Nothing about the shopper leaves your site. Only the name of the site
  they arrived from, the currency, the order total and a one-way code so
  the same sale is not counted twice — never a name, email, IP address
  or the order number itself. It uses the session WooCommerce already
  keeps for the cart, not a cookie of ours, and only covers a purchase
  made in the same visit.

0.6.4

• New on the settings page: how many of your products would be accepted
  into the ChatGPT product feed, and exactly what is missing from the
  ones that would not. A product with no image or no brand is dropped
  silently by the channel, with no error anywhere — this tells you
  before that happens, and the same fields feed Google and Perplexity.
• Fixed a real defect in the feed we generate: products without a GTIN
  or MPN were sent without declaring that, which OpenAI reads as a
  claim to an identifier that is not there. Small catalogues rarely have
  GTINs, so this affected most stores.

0.6.3

• The settings page now uses WordPress’s own admin components, so it
  reads as part of your dashboard instead of a wall of text: what the
  plugin has already done comes first, in a card with a status icon per
  line, and the endpoints it serves sit below it in a table you can open
  one by one.
• No stylesheet of ours is loaded for any of it. The page inherits your
  admin theme, dark mode and accessibility settings as they are.

0.6.2

• Renamed from “Goppa Agentic Commerce” to “Goppa – AI Visibility for
  WooCommerce”, so the name says what the plugin is for. Nothing else
  changes: same plugin, same settings, same address. Your site keeps
  updating normally.
• The settings page now shows what Goppa has actually done on your
  store — how many products are being served as structured data, how
  many URLs went to Bing and Yandex — instead of only listing what it
  could do. Until now that summary appeared only for connected
  accounts, so anyone using the plugin on its own saw a form and no
  evidence that anything had happened.
• Asks for a review, once, after a week of real use, inside this
  plugin’s own settings page. Dismissable, and the dismissal sticks.

0.6.1

• The settings page now says what this plugin can and cannot tell you.
  It makes your catalogue readable; whether an assistant actually names
  your store has to be measured by asking, from the outside. The note
  disappears once you connect an account.
• The connection field used to ask for a token without saying where one
  comes from. It now links to the page that issues it, with this site’s
  address already filled in.

0.6.0

• New: a short summary on product pages. Two factual lines and a
  spec list, built only from fields you already filled in — name,
  category, brand, price, stock and attributes. Your own description is
  never read, changed or rewritten. Off by default.
• New: your category guide, as a draft. The comparison guide written
  on the platform can now land here as a draft post instead of being
  copied and pasted. It is created once, it is always a draft, and once
  you touch it the text is yours — we never write over it. Off by
  default.
• New: your official profiles in the schema (sameAs). The store
  identity block already told an assistant your name and address. It now
  also links the profiles you confirm on the platform, which is what
  tells a model that this shop, that review page and that social profile
  are the same business. Nothing is published until you confirm each one.
• New: the FAQ can also be text on the page. Google no longer uses
  FAQ Page markup and AI reads the page itself, so the same questions and
  answers can now appear as visible text. Off by default: hidden markup
  does not change what your customers see, and this does.
• New: FAQ on category pages. Built from the products in that
  category — how many there are, what they cost, which brands you carry.
  Counted from your own catalogue, never written for you. Also off by
  default.
• New: see when an AI actually used your shop. Until now the plugin
  only reported the agent files it serves, so an assistant reading a
  normal product page went unseen. It now reports two things that are
  real counts, not estimates: pages fetched by AI crawlers, and visits
  from people who clicked a link inside an AI answer.
• The dashboard separates the two that matter. ChatGPT-User,
  Claude-User and Perplexity-User fetch a page because someone
  asked a question right then — those are counted as real use.
  GPTBot and the other sweeping crawlers are shown separately, because
  a crawler passing through says nothing about being recommended.
• Privacy: only the referring host is recorded (for example
  chatgpt.com), never the full address, which can contain the
  visitor’s conversation id. No IPs, no raw headers, and ordinary
  visitors are still not recorded at all.

0.5.1

• Fixed a privacy bug: hidden products were being served to AI agents.
  If you had set a product’s catalogue visibility to Hidden, or
  protected it with a password, it was still included in the catalogue
  the plugin publishes for AI assistants. Nothing changed on your
  storefront, so there was no way to notice. Those products are now
  excluded. If you use hidden products for B2B pricing, discontinued
  items or testing, update.

0.5.0

• New: the plugin now applies the fixes by itself. Once an hour it
  asks Goppa whether your latest diagnosis found anything it can repair,
  and repairs it: serving llms.txt, allowing AI crawlers and declaring
  the sitemap in robots.txt, and filling in structured-data fields your
  products were missing. Before this you had to copy and paste them.
• It will never touch what you wrote. Titles, descriptions, prices
  and policies are refused by the plugin itself, not only by the server
  — so even a bug or a breach on our side cannot change how your store
  looks to a shopper. Only data that AI agents read is ever modified.
• Settings now show exactly what was applied and when, and the plugin
  does nothing at all until your store is connected.

0.4.0

• New: IndexNow. Your product URLs are submitted to Bing and Yandex
  whenever a product is added, updated or removed. This matters more than
  it sounds: ChatGPT and Copilot answer shopping questions from Bing’s
  index, so a product that is not in that index cannot be recommended,
  however good its structured data is. IndexNow cuts the wait from weeks
  to hours. The verification key is generated and served automatically —
  nothing to configure. Turn it off under Settings if another plugin
  already submits your URLs.
• Fixed: uninstalling did not remove the goppa_schema option, so a
  setting from 0.3.0 survived the plugin being deleted.

0.2.1

• Fixed: on stores running the stable WooCommerce release, every endpoint
  served an empty catalogue. The plugin routed on init at priority
  0, the same priority WooCommerce uses, and loaded first — so
  wc_get_products() ran before WooCommerce had registered the product
  post type. Routing now runs at priority 20.
• Fixed: an empty catalogue was cached for ten minutes. If the first
  request happened before products existed, products added afterwards
  stayed invisible to agents. Only a non-empty catalogue is cached now.
• Fixed: search ignored accents. “tenis de corrida” ranked a t-shirt
  above a running shoe, because “tenis” did not match “Tênis”. Accents
  are folded on both sides now, covering the Latin alphabet (including
  ß, ø, æ, ł, ğ).
• Fixed: a match in the product name now outranks a match in the
  description.
• Fixed: get_product also matches without accents, so a lookup cannot
  fail where the search succeeded.
• Fixed: deactivating left the hourly reporting task scheduled forever.
• Fixed: uninstalling did not remove the store token or the telemetry
  options, leaving a secret in the site database.
• Changed: text domain is now goppa-agentic-commerce, matching the plugin
  slug, so translations resolve.

0.2.0

• Rewrote the UCP manifest to conform to the published specification,
  checked against a live Shopify manifest. The previous version used
  fields that do not exist in the spec.
• The manifest now declares only what the plugin does — catalogue search
  and lookup. No checkout, cart or payment handlers.
• Corrected llms.txt and the plugin description, which claimed the store
  was transactable by agents. It is not; purchase happens on the store.
• Hardened the MCP server against malformed input. Batches, null, bare
  numbers, parameters sent as strings and arguments of the wrong type
  used to raise errors — which would surface as HTTP 500 on the
  merchant’s site. All of them now return proper JSON-RPC errors, and
  batch size is capped.
• Added optional reporting of agent activity.

0.1.0

• First release: UCP manifest, llms.txt, MCP server, schema.org catalogue
  endpoint, settings page, catalogue cache.