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.
What is sent, and when:
- When you connect. The pairing code you paste is 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. Your store URL is sent with it. - 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. No customer or order data is read or sent. - 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. The requested path and the requesting user agent are sent.
What is stored on your site: the Orzaqo API key, your merchant id and name, the API base, the served
route list, and the publishable widget key. Nothing else. Uninstalling the plugin deletes all of them.
Terms of Service: https://orzaqo.com/terms
Privacy Policy: https://orzaqo.com/privacy
Installation
- Upload and activate the plugin.
- Go to Settings -> Orzaqo.
- Paste the pairing code from your Orzaqo dashboard and click Connect.
To point the plugin at a non-production Orzaqo API (e.g. local development), define
ORZAQO_API_BASE in your wp-config.php.
FAQ
-
Do I need an Orzaqo account?
-
Yes. The plugin delivers artifacts that Orzaqo generates, so it needs an account to pair with. You paste
a pairing code from the Orzaqo dashboard; the plugin does the rest. -
What data leaves my store?
-
Product data only — titles, descriptions, prices, stock, images, categories, brands and identifiers — plus
your store URL and the user agents of crawlers requesting your AI artifacts. No customer data, no orders,
no personal data of your shoppers. See “External Services” above for the detail. -
Does it slow my store down?
-
Publishing and analysis run on Orzaqo’s servers, not yours. The plugin serves artifacts on your domain
and records crawler visits; it adds no work to a normal page load. -
What happens when I uninstall it?
-
Every option the plugin stored is deleted: the API key, merchant id and name, API base, route list and
widget key. The read-only WooCommerce key it created is revoked when you disconnect. -
Can I point it at a different Orzaqo environment?
-
Yes. Define
ORZAQO_API_BASEinwp-config.phpand it takes precedence over everything else. This is
also how a store behind split-horizon DNS reaches the API on an internal hostname.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Orzaqo” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Orzaqo” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.1.1
- The assistant now paints your own colour on its first frame instead of briefly showing a default one.
- Only published products are read, as this page has always said — drafts are no longer requested.
- Artifact responses carry an explicit content type chosen by the plugin, and
X-Content-Type-Options: nosniff. - Orzaqo’s own requests identify themselves, so they are no longer counted as crawler traffic on your store.
0.1.0
- Initial release: one-click connect (pairing code), on-domain artifact delivery, and AI-crawler sensing.