| 开发者 | waheedev |
|---|---|
| 更新时间 | 2026年9月27日 20:50 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
ORZAQO_API_BASE in your wp-config.php.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.
Product data; your store URL; AI crawler visits (user agent and path, never an IP address); the host name of AI assistants that send you visitors; the words shoppers search for on your store; and, for orders that followed an assistant recommendation, the order number and totals. No customer names, addresses, emails or payment details. See "External Services" above for when each is sent.
Publishing and analysis run on Orzaqo's servers, not yours. On storefront pages the plugin adds the assistant's script if your plan includes it, and product pages fetch their structured data from Orzaqo when it is not already cached (with a 5-second limit). Crawler and search reports are queued and sent in batches.
Every setting and queue the plugin stored is deleted, and its cached copies expire within five minutes. Order references added to attributed orders stay with those orders. The read-only WooCommerce key it created is revoked when you disconnect.
Yes. Define ORZAQO_API_BASE in wp-config.php and it takes precedence over everything else. This is
also how a store behind split-horizon DNS reaches the API on an internal hostname.
X-Content-Type-Options: nosniff.