Orzaqo

Description

Publishing a file once is not the same as being listed. Each AI shopping surface accepts products on its
own terms, and a product that satisfies one can be refused by another for a field the merchant never knew
mattered.

Orzaqo checks your catalog against those rules and keeps it republished as the catalog changes. Two
examples of what that means in practice: Google requires a brand on new products and refuses them without
one, while Perplexity keys product identity on GTIN — a product with no GTIN does not appear alongside the
same item from other stores at all. Orzaqo tells you which of your products each destination would
refuse, and why, before you find out from missing traffic.

The plugin’s job is delivery and evidence. It serves the artifacts Orzaqo generates — llms.txt,
robots.txt, sitemaps and your product feed — from your own domain rather than a third-party URL, and it
records which AI crawlers actually fetched them, so “are we being read?” has an answer rather than a
guess.

The plugin is thin by design: all publishing, structured-data generation, and analytics run on Orzaqo’s
servers and improve automatically, without a plugin update. The plugin only delivers those artifacts on
your domain and reports crawler activity — it stores no credentials beyond a single Orzaqo API key
obtained at connect time.

An Orzaqo account is required. The plugin delivers artifacts generated by the Orzaqo service and
cannot function without it. See “External Services” below for exactly what is sent and when.

External Services

This plugin connects to the Orzaqo API at https://api.orzaqo.com, operated by Orzaqo. The plugin is a
thin client: publishing, structured-data generation and analytics happen on Orzaqo’s servers, so the
plugin cannot function without that service. Nothing is sent before you connect a store.

What is sent, and when:

• When you connect. The pairing code you paste and your store URL are sent to the Orzaqo API and
  exchanged for an API key. The plugin then creates a read-only WooCommerce REST key on your store and
  sends it to Orzaqo so your catalog can be pulled.
• When your catalog syncs. Orzaqo pulls product data through that read-only key: titles,
  descriptions, prices, stock status, images, categories, brands and product identifiers such as GTIN.
  Only published products are read. When a product changes or is deleted, its product id is sent so the
  change is picked up.
• About once an hour. The plugin fetches the list of files to serve and reports how many products the
  store publishes.
• When an AI crawler or a shopper requests an artifact. Requests to paths such as /llms.txt,
  /robots.txt, sitemaps and the product feed are proxied to the Orzaqo API, which renders them, so
  they are served on your own domain.
• When an AI crawler visits your store. Its user agent, the path it requested and, on a product page,
  the product id. No IP address is sent.
• When a visitor arrives from an AI assistant. The referring site’s host name (for example
  chatgpt.com) and the page they landed on.
• When a shopper uses your store’s search. The words they searched for, so unanswered demand can be
  reported to you. Orzaqo removes email addresses, phone numbers and long digit runs before storing them.
• When a product page is viewed. Its structured data (JSON-LD) is fetched from Orzaqo and cached on
  your site.
• When an order follows an Orzaqo assistant recommendation. The order number, the order total, the
  total of the recommended item and the currency, so the sale can be attributed. No customer name,
  address, email or payment detail is ever sent.
• In your shoppers’ browsers. If the storefront assistant is enabled for your plan, its script is
  loaded from https://api.orzaqo.com, and the questions shoppers type into it are sent to Orzaqo to be
  answered from your catalog. It sets no cookies; the conversation is kept in the browser tab’s
  session storage and is gone when the tab closes.

What is stored on your site: the Orzaqo API key, your merchant id and name, the API base, the served
route list, the widget key and its appearance settings, your plan’s limits and usage, the id of the
WooCommerce key it created, and short queues of events waiting to be sent. On orders that followed an
assistant recommendation it stores an Orzaqo reference and the time it was reported; until checkout, that
reference is kept in the shopper’s WooCommerce session. Uninstalling deletes every setting and queue; cached
copies of served files expire within five minutes; the order references stay with those orders.

Terms of Service: https://orzaqo.com/terms
Privacy Policy: https://orzaqo.com/privacy