Publishing a file once is not the same as being listed. Each AI shopping surface accepts products on its\nown terms, and a product that satisfies one can be refused by another for a field the merchant never knew\nmattered.<\/p>\n\n
Orzaqo checks your catalog against those rules and keeps it republished as the catalog changes. Two\nexamples of what that means in practice: Google requires a brand on new products and refuses them without\none, while Perplexity keys product identity on GTIN \u2014 a product with no GTIN does not appear alongside the\nsame item from other stores at all. Orzaqo tells you which of your products each destination would\nrefuse, and why, before you find out from missing traffic.<\/p>\n\n
The plugin's job is delivery and evidence. It serves the artifacts Orzaqo generates \u2014 llms.txt,\nrobots.txt, sitemaps and your product feed \u2014 from your own domain rather than a third-party URL, and it\nrecords which AI crawlers actually fetched them, so \"are we being read?\" has an answer rather than a\nguess.<\/p>\n\n
The plugin is thin by design: all publishing, structured-data generation, and analytics run on Orzaqo's\nservers and improve automatically, without a plugin update. The plugin only delivers those artifacts on\nyour domain and reports crawler activity \u2014 it stores no credentials beyond a single Orzaqo API key\nobtained at connect time.<\/p>\n\n
An Orzaqo account is required.<\/strong> The plugin delivers artifacts generated by the Orzaqo service and\ncannot function without it. See \"External Services\" below for exactly what is sent and when.<\/p>\n\n This plugin connects to the Orzaqo API at https:\/\/api.orzaqo.com, operated by Orzaqo. The plugin is a\nthin client: publishing, structured-data generation and analytics happen on Orzaqo's servers, so the\nplugin cannot function without that service. Nothing is sent before you connect a store.<\/p>\n\n What is sent, and when:<\/p>\n\n What is stored on your site: the Orzaqo API key, your merchant id and name, the API base, the served\nroute list, the widget key and its appearance settings, your plan's limits and usage, the id of the\nWooCommerce key it created, and short queues of events waiting to be sent. On orders that followed an\nassistant recommendation it stores an Orzaqo reference and the time it was reported; until checkout, that\nreference is kept in the shopper's WooCommerce session. Uninstalling deletes every setting and queue; cached\ncopies of served files expire within five minutes; the order references stay with those orders.<\/p>\n\n Terms of Service: https:\/\/orzaqo.com\/terms\nPrivacy Policy: https:\/\/orzaqo.com\/privacy<\/p>\n\n\n To point the plugin at a non-production Orzaqo API (e.g. local development), define\n ORZAQO_API_BASE in your Yes. The plugin delivers artifacts that Orzaqo generates, so it needs an account to pair with. You paste\na pairing code from the Orzaqo dashboard; the plugin does the rest.<\/p><\/dd>\n Product data; your store URL; AI crawler visits (user agent and path, never an IP address); the host name\nof AI assistants that send you visitors; the words shoppers search for on your store; and, for orders that\nfollowed an assistant recommendation, the order number and totals. No customer names, addresses, emails or\npayment details. See \"External Services\" above for when each is sent.<\/p><\/dd>\n Publishing and analysis run on Orzaqo's servers, not yours. On storefront pages the plugin adds the\nassistant's script if your plan includes it, and product pages fetch their structured data from Orzaqo\nwhen it is not already cached (with a 5-second limit). Crawler and search reports are queued and sent in\nbatches.<\/p><\/dd>\n Every setting and queue the plugin stored is deleted, and its cached copies expire within five minutes.\nOrder references added to attributed orders stay with those orders. The read-only WooCommerce key it created is revoked when you disconnect.<\/p><\/dd>\n Yes. Define External Services<\/h3>\n\n
\n
\/llms.txt<\/code>,\n \/robots.txt, sitemaps and the product feed are proxied to the Orzaqo API, which renders them, so\nthey are served on your own domain.<\/li>\n\n
wp-config.php<\/code>.<\/p>\n\n\n\n
Do I need an Orzaqo account?<\/h3><\/dt>\n
What data leaves my store?<\/h3><\/dt>\n
Does it slow my store down?<\/h3><\/dt>\n
What happens when I uninstall it?<\/h3><\/dt>\n
Can I point it at a different Orzaqo environment?<\/h3><\/dt>\n
ORZAQO_API_BASE<\/code> in wp-config.php<\/code> and it takes precedence over everything else. This is\nalso how a store behind split-horizon DNS reaches the API on an internal hostname.<\/p><\/dd>\n\n<\/dl>\n\n\n0.1.5<\/h4>\n\n
\n
0.1.4<\/h4>\n\n
\n
0.1.3<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
X-Content-Type-Options: nosniff<\/code>.<\/li>\n0.1.0<\/h4>\n\n
\n