Agentic Commerce for WooCommerce
| 开发者 | xpaysh |
|---|---|
| 更新时间 | 2026年8月8日 17:46 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0.3 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
AI Traffic & Sales Tracking for WooCommerce — ChatGPT Ads, Product Feed & AI Visibility
Something is already sending you customers, and your analytics can't see it.
When a shopper asks ChatGPT "find me a cordless drill under $80 that ships in 2 days" and buys from the store it names, that order lands in WooCommerce looking like ordinary direct traffic. Google Analytics shows you nothing. Your reports show you nothing. You cannot tell whether AI assistants are worth your attention, because you cannot see them at all.
This plugin makes the AI channel visible, then makes you the answer it gives — and lets you buy more of it.
Three jobs, in that order:
- Measure it. See which AI crawlers reach your store, which pages they read, and which of your real WooCommerce orders came from an AI assistant — broken out by ChatGPT, Claude, Perplexity, Gemini, Copilot and a dozen more, reconciled against your actual orders so you know the number is true.
- Win it. Publish your catalog, prices, stock and answers in the formats AI shopping assistants actually read, so you're the store they recommend.
- Buy it. Run ChatGPT Ads — campaigns, budgets, creative and results — from inside WooCommerce, measured against your real orders rather than the ad platform's own scorecard.
- AI crawler analytics → — which assistants visit (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, PerplexityBot, Google-Extended and more), what page types they read, whether they reached your catalog, and how that compares against your human traffic. Opt-in, off by default, known AI bots only — never your shoppers.
- AI-attributed orders — real WooCommerce orders traced back to the assistant that referred the buyer, with revenue split by source. Strictly non-PII: no names, emails, addresses or payment data ever leave your store.
- Agent-readiness audit → — a live score for how well AI shopping assistants can read, understand and recommend your catalog, with a prioritised fix list.
- Agent delivery speed → — AI crawlers give up on slow pages. See how fast your catalog,
/llms.txtand product pages answer when requested by the AI crawlers themselves, and what to do when one is too slow. A diagnostic — it won't fight your caching plugin.
- An agent-readable product feed — your full catalog with live prices and stock, hosted on xpay's CDN, so assistants reading it never touch your origin. Refreshed within ~30 seconds of any product or stock change, with an hourly safety net.
- AI-shopping structured data —
Product,Offer,AggregateOffer,BuyActionandItemListJSON-LD on product pages, shop archive and home page. Detects Yoast, Rank Math and WooCommerce core schema and fills only the gaps — never a duplicate. - The real AI shopping standards, on your own domain —
/llms.txt(llmstxt.org) and an explicitrobots.txtallowlist for AI user-agents. If you already publish your own/llms.txt, this appends to it and leaves your content untouched. - Cart deep-link — an assistant can hand a shopper a one-click Buy link that pre-fills your existing WooCommerce cart and lands them on your existing checkout.
- Product FAQs and return policy —
FAQPageandMerchantReturnPolicystructured data answering the delivery, returns and variant questions AI shoppers ask, for products you approve. Optionally shown to your shoppers too, as a product tab, a summary block, or an[xpay-faq]shortcode — off on new installs. - AI storefront assistant → (optional) — an on-site shopper chat that answers from your own catalog. Never appears without your explicit say-so.
- Campaign management inside WooCommerce → — create, edit, budget, activate and pause ChatGPT Ads campaigns and ad groups without switching to another tab. Results land next to the orders they produced.
- Your numbers, not just theirs — every campaign shows the orders we reconciled against your real WooCommerce data alongside what OpenAI reports. The gap between the two is the most useful number on the screen.
- A ChatGPT product feed — your catalog serialised to OpenAI's specification and delivered on a schedule, with a per-product health score so you can see exactly which listings are incomplete and fix them inline.
- Eligibility, up front — ChatGPT Ads requires a minimum catalog size and is currently limited to the US, Canada, Australia and New Zealand. The plugin tells you where you stand before you invest time, and points you at the organic path if ads aren't open to you yet.
- Tracking that works with what you have — already running Pixel Manager, PixelYourSite or a GTM container? This verifies their pixel is firing and reconciles it, instead of asking you to rip it out and install another one.
- Yoast SEO / Rank Math / SEOPress — detects existing Product and FAQ schema and fills only what's missing.
- AdTribes Product Feed PRO / CTX Feed / Google Listings & Ads — separate feeds for separate channels; nothing conflicts.
- Pixel Manager / PixelYourSite / GTM / WooCommerce core Order Attribution — attribution here is additive and non-destructive.
- WP Rocket / LiteSpeed / Autoptimize / SiteGround Optimizer — automatically excluded from JS optimization so nothing breaks.
- HPOS and Cart/Checkout Blocks — declared compatible.
- Storefront / Astra / Divi / Elementor and the standard page builders.
- It doesn't touch your checkout. Stripe / WooPayments / PayPal / Square / whatever you already use — payment runs through them, unchanged. Your payout schedule is unchanged.
- It doesn't see your customers. No buyer names, emails, addresses, IPs, payment cards, order line items, refunds, or PII of any kind passes through xpay. Ever. The plugin is non-custodial.
- It doesn't require a new account or contract to start. Free to install and get going — paid plans available as you grow. See pricing.
- It doesn't slow down your site. The JSON-LD block is tiny and cached; the catalog feed is served from xpay's CDN, not your origin.
- Install the plugin from this directory or upload the zip.
- Activate. You'll land on the xpay✦ Commerce dashboard.
- Click Connect store. You're redirected to app.xpay.sh, where you grant a read-only WooCommerce REST API key.
- Your catalog goes live on AI surfaces within about 10 minutes. The built-in readiness checklist turns green as each piece confirms, and tells you in plain English what to do about anything that doesn't.
- WooCommerce 7.0+ on WordPress 6.2+ and PHP 7.4+.
- Declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and Cart/Checkout Blocks.
- Works alongside Yoast SEO, Rank Math, WooCommerce Blocks, WooPayments, Stripe for WooCommerce, and the standard Storefront / Astra / Divi / Elementor themes.
- Anonymous lifecycle telemetry is off by default. On first activation a single admin notice asks once. Pick "No thanks" and the plugin never contacts our backend for analytics. Pick "Enable" and you can change your mind any time under xpay✦ Commerce → Settings → Privacy. System-wide opt-out via
define( 'XPAY_WC_TELEMETRY', false );inwp-config.php. - Full data disclosure at install.xpay.sh/woocommerce/privacy.html — every byte the plugin sends, when it sends it, how to opt out, how to request deletion.
- Agentic commerce, explained — what changes when AI assistants, not people, do the browsing.
- Plugin listing and version history — feature detail, release notes and compatibility, kept current.
- ChatGPT Ads for store owners — eligibility, costs and what to expect before you spend anything.
wp-content/plugins/agentic-commerce-for-woocommerce/ on your own server the moment you install it. You can read it, fork it, modify it, redistribute it and self-host it without paying anything. Full technical changelog: install.xpay.sh/woocommerce/CHANGELOG.md. Questions or bug reports: merchants@xpay.sh, or the support forum on this page.
安装:
From the WordPress.org plugin directory
- In your WordPress admin, go to Plugins → Add New.
- Search for "Agentic Commerce for WooCommerce".
- Click Install Now, then Activate.
- You'll be redirected to xpay✦ Commerce → Settings. Click Connect store.
- Approve the WooCommerce REST API permissions on app.xpay.sh, then you'll be redirected back to your store.
- WordPress 6.2 or higher
- WooCommerce 7.0 or higher
- PHP 7.4 or higher
- SSL (
https://) on the store domain — required for the agent discovery files to be honored by AI surfaces
屏幕截图:
常见问题:
Will this slow down my store?
No. What we add to your pages is a few lines of invisible data. Your catalog is served from our CDN, so AI shoppers reading it never touch your server at all.
Does xpay see my customers or their payment details?
No — never. Payment runs through your existing gateway exactly as it does today. No buyer names, emails, addresses, cards or order contents ever reach us.
Will it change how my product pages look?
Almost everything we add is invisible to shoppers. The one exception is the product FAQ block, and it is off on new installs — nothing appears on your store until you ask for it.
I already use Yoast or Rank Math. Will this conflict?
No. We check what they've already published and add only what's missing, so you never end up with two of anything.
How much does it cost?
Free to install and use. Paid plans as you grow — see pricing.
What does it send to xpay, and when?
Nothing until you click Connect store. After that: your public product details (name, description, price, stock, images, categories) so we can publish your catalog for AI shoppers. Optional anonymous diagnostics are off by default and you're asked once. No customer data, no order data, ever. Full disclosure.
How do I remove it?
Plugins → Deactivate → Delete, and everything the plugin wrote is removed from your database. To also delete your catalog from our CDN, email privacy@xpay.sh from your admin address.
I run several stores. Do I install it on each?
Yes — each store gets its own catalog and its own settings.
Do you support Subscriptions, Bookings or Memberships?
Simple, variable and grouped products today. The others are on the roadmap — email merchants@xpay.sh if one is blocking you and we'll tell you where it stands.
My host blocks /.well-known/ — does discovery still work?
Yes. There's an automatic fallback that AI shoppers find on their own. If your host intercepts those paths, nothing breaks.
Is the source code available?
Yes. GPLv2-or-later, shipped as plain readable PHP in wp-content/plugins/agentic-commerce-for-woocommerce/. Nothing minified, obfuscated or loaded from a remote script. Developers: add_filter( 'xpay_wc_faq_visible', '__return_false' ); turns the FAQ block off from code, whatever the dashboard says.
I have a question that isn't answered here.
Email merchants@xpay.sh, or post in the support forum on this page — we answer both, and we aim to reply within one business day.
更新日志:
The full machine-readable changelog lives at install.xpay.sh/woocommerce/CHANGELOG.md (Keep-a-Changelog format). The summary below is the WP.org-required mirror.
0.7.1
- Widget loading latency improvement.
- See your AI traffic without connecting anything. The plugin now counts which AI assistants read your store — ChatGPT, Claude, Perplexity, Gemini and others — and shows it to you on a new dashboard, using only your own site's data. No account, no key, and nothing is sent anywhere. Previously every number needed a connected store first.
- A new xpay Commerce menu, with dashboards for AI revenue, ChatGPT Ads, your product feed, tracking and your storefront. Your settings page has not moved — everything you had bookmarked works exactly as before, and the new menu links straight to it.
- AI-attributed orders now show a match rate. Every figure states what share of your real orders it accounts for, and where orders could not be traced we explain the reasons that causes. A revenue number you cannot check is not worth having.
- Catalog health scoring — see which products are missing a description, image, price or identifier before any of it reaches an AI shopping surface, and why each one matters.
- ChatGPT Ads eligibility is checked up front, so you find out whether your store qualifies before setting anything up rather than after.
- Pixel checking rather than pixel installing. If you already run Pixel Manager, PixelYourSite or a Tag Manager container, keep it — this checks what you have instead of adding a second pixel that would count every sale twice.
- A storefront page that shows exactly what shoppers can see, with a direct link to switch each one off. Having access to a feature and agreeing to display it are separate decisions.
- The first-run diagnostics prompt is a third of its previous length and says plainly what is and is not sent. The choice, the default (off) and the disclosures are unchanged.
- Agent-attributed orders that never completed are now reported too. If a shopper referred by an AI assistant reaches checkout but the order ends up cancelled or failed, that outcome is now sent to your xpay dashboard alongside the successful ones, so your attributed totals are not quietly flattering. Applies to connected stores only, and carries no customer, payment or personal data — as before.
- More resilient. Each part of the plugin now starts independently, so a fault in one can no longer affect your storefront or the rest of the plugin.
- The AI Storefront Assistant now loads reliably alongside caching/optimization plugins. When WP Rocket, LiteSpeed Cache, Autoptimize or SiteGround Optimizer minifies, combines, delays or self-hosts JavaScript, it could break the assistant loader so the chat bubble never appeared — while everything looked fine in an incognito/preview window. The loader is now excluded from those optimizers automatically, so you no longer need to add a manual exclusion. (For W3 Total Cache or an edge cache, which have no runtime hook, the plugin still shows a one-line manual-exclusion note.)
- Fixed: the assistant could show "Array" instead of your store name on multilingual stores. A localized store name is now resolved to your store's language before it's displayed.
- No other storefront changes — reliability fixes only.
- Your approved product FAQs can no longer be wiped by a partial or interrupted sync. Previously, every FAQ sync replaced the entire stored set with whatever it received — so if a sync ran with an incomplete list (a dropped connection, a catalog still rebuilding), any product left out had its FAQ silently deleted. A sync that would shrink your FAQ set by more than half is now refused unless it explicitly confirms a full replace, so an accidental one fails loudly instead of clearing your pages.
- A single product's FAQ can now be updated on its own. Approving one new product, editing one answer, or changing the heading no longer resends every FAQ — the update touches only the products it names and leaves the rest exactly as they were. Only the changed product pages are cleared from your cache.
- No visible change to your storefront; these are safety improvements to how xpay keeps your FAQs in sync. Older releases (0.1.0 – 0.6.1) are listed in the full changelog: https://install.xpay.sh/woocommerce/CHANGELOG.md