Blaze AI Discovery for WooCommerce

AI shopping is growing. ChatGPT, Google AI Overviews and AI Mode, Microsoft Copilot and Perplexity now recommend and sell products inside conversations. Stores whose pages AI crawlers can read, and whose product data is complete, tend to get found. Stores that block the crawlers or leave product data thin tend not to.

People call this work “ChatGPT SEO”, AI visibility, or AEO/GEO (answer engine or generative engine optimization). Whatever the label, Blaze AI Discovery for WooCommerce does the practical parts inside WordPress: it checks that AI crawlers can reach your store, scores your product data, generates the ChatGPT Shopping feed and reports when ChatGPT or Google AI mention you — without giving up the control and ownership that made you choose WooCommerce in the first place. No plugin can promise that an assistant will recommend your store; this one shows you what the assistants can actually see and what to fix.

What it does

AI crawler access
Finds out whether GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended and bingbot can reach your store. Each crawler gets a verdict from your robots.txt, your server’s own bot log and, with cloud checks on, a fetch from outside your network — because a CDN or firewall can turn a crawler away while everything looks fine from inside. When a shopping assistant is blocked the dashboard says so and links to the fix for the layer doing the blocking (Cloudflare, Wordfence, Sucuri, Kinsta or robots.txt).

AI visibility — ChatGPT citations and Google AI Overviews
A monthly report of how often ChatGPT and Google AI answers mentioned your store over the trailing 30 days, which of your pages they cited, and which other domains were named instead. Runs in the background with cloud checks on; it is the closest thing to a rank report that exists for AI answers, and it tells you whether the rest of the work is showing up.

ChatGPT Shopping feed
Generates a product feed in OpenAI’s current CSV specification, validates every product against the required fields and walks you through the submission steps at chatgpt.com/merchants.

AI readiness score
Each product gets a 0–100 score on 10 criteria that assistants use when deciding whether to surface it: title quality, description depth, images, brand, category, attributes, price, identifiers (SKU/GTIN), reviews, and shipping/returns policies. Recommendations tell you what to fix on each product.

AI traffic attribution
Most AI-referred visits hide in your analytics as “Direct” traffic. The tracker detects visits from ChatGPT, Perplexity, Google AI Mode, Copilot, Claude and Gemini using referrer headers, UTM parameters and URL text fragments, then follows them through to WooCommerce orders and revenue.

Schema
Adds the Product properties assistants look for to your existing Schema.org markup — brand, multiple images, GTIN, dimensions, colour, material, itemCondition — working alongside Yoast SEO or Rank Math rather than duplicating them.

llms.txt
Serves an llms.txt file at your site root listing your store, categories and key pages. Some tools read it, so it is generated for you; for a store it is low priority next to crawler access and structured data, and the plugin treats it that way.

Store audit, including Core Web Vitals
Twelve diagnostic checks covering what affects AI discoverability: WooCommerce version, store visibility (WooCommerce “Coming soon” mode), SSL, REST API, existing schema, product data quality, robots.txt rules for AI crawlers, crawler access, Google for WooCommerce status, existing feed plugins, llms.txt and — with cloud checks on — mobile Core Web Vitals measured from real Chrome users.

Key Features

• AI crawler access check — per-crawler verdicts from robots.txt, your bot log and an outside-in probe, with a fix link for your CDN/firewall
• AI Visibility — how often ChatGPT and Google AI mention your store, which pages they cite and who gets named instead (refreshed monthly, covering the trailing 30 days)
• ChatGPT Shopping feed generator with validation against the current OpenAI spec
• Per-product AI readiness scoring with fix recommendations
• AI traffic attribution dashboard with platform breakdown and revenue tracking
• Order attribution — traces AI-referred visits through to WooCommerce orders
• Enhanced Schema.org/JSON-LD that augments your store’s Product schema whether it is printed by WooCommerce, Yoast SEO (with its WooCommerce SEO add-on), or Rank Math (never duplicates)
• Google Merchant Center data quality audit
• Automatic llms.txt generation
• Store readiness audit with 12 diagnostic checks
• Core Web Vitals — mobile field data (LCP, INP, CLS, TTFB) from real Chrome users
• Zero-config — starts tracking the moment you activate
• Works on cached sites (Kinsta, WP Engine, SiteGround, Cloudways, shared hosting)
• Optional cloud checks — off by default, one click to enable
• Privacy-conscious — the visitor’s IP and browser are combined into a salted, irreversible hash, but the referring AI platform, landing page URL, UTM parameters and (for AI crawlers) the raw user-agent string are stored as-is; all of it is deleted after 90 days

How It Works With Caching

Unlike server-side-only tracking that fails on cached pages, our tracker uses the same proven architecture as Independent Analytics: a lightweight inline script (delay-loaded via requestIdleCallback for zero performance impact) that sends data to a local REST endpoint. Works perfectly with full-page caching, edge caching, and CDNs.

External Services

This plugin can connect to Blaze Commerce cloud services. These connections are off by default and only run after you click “Enable cloud checks” in the plugin (WP admin → AI Discovery → Store Audit). You can turn them off again at any time from the same screen.

Blaze Commerce cloud services (api.blazecommerce.io), operated by Blaze Commerce (https://blazecommerce.io, privacy policy)

• Crawler access check — Sends your store’s public URL, one public product URL and the plugin/WordPress/WooCommerce/PHP version numbers to https://api.blazecommerce.io/v1/crawler-access, which fetches those public pages with AI crawler user-agents and returns what each crawler saw. Fetches are made through Evomi’s proxy network (terms, privacy) so the store is tested from residential and datacenter IP addresses. Before the first probe the service makes a single inbound request to https://<store>/wp-json/blazeaid/v1/ping to confirm the plugin is installed; that endpoint returns only the plugin id, version and a random site token (no personal data). Runs when the store audit runs and only after you enable cloud checks.
• Data sent: your store’s public URL, one public product URL, and version numbers. No customer, order or user data.

• Data retained: call metadata (site URL, timestamp, response codes) is retained for service operation and abuse prevention; no customer or order data is ever sent. The per-crawler result is saved in your own WordPress database as part of the audit results.

• Core Web Vitals check — Sends your store’s public URL and the plugin/WordPress/WooCommerce/PHP version numbers to https://api.blazecommerce.io/v1/cwv, which looks up the mobile Core Web Vitals (LCP, INP, CLS and TTFB at the 75th percentile over the last 28 days) that real Chrome users recorded for your store’s origin in the Google Chrome UX Report API (terms, privacy) and returns them. No page of your store is loaded or tested by the service. The same inbound ping verification described above is made before the first request. Runs when the store audit runs and only after you enable cloud checks.

• Data sent: your store’s public URL and version numbers. No customer, order, product or user data.

• Data retained: call metadata (site URL, timestamp, response codes) is retained for service operation and abuse prevention, and the returned metrics are cached by the service for 24 hours; no customer or order data is ever sent. The metrics are saved in your own WordPress database as part of the audit results.

• AI Visibility report — Once a month (on the 2nd at 03:00 UTC, in the background via Action Scheduler) and when you click “Refresh” on the AI Visibility page, sends your store’s registrable domain, store country, site locale, up to five product category names and the plugin/WordPress/WooCommerce/PHP version numbers to https://api.blazecommerce.io/v1/visibility. The service looks up how often ChatGPT and Google AI mentioned your domain over the trailing 30 days, which of your pages they cited and which other domains were named, using DataForSEO’s LLM Mentions data (terms, privacy), and returns a report that the plugin renders on the AI Visibility page. The same inbound ping verification described above is made before the first request. Never runs while a page loads, and only after you enable cloud checks.

• Data sent: your store’s registrable domain, country, locale, up to five product category names, and version numbers. No customer, order or user data.
• Data retained: call metadata (site URL, timestamp, response codes) is retained for service operation and abuse prevention, and the report is cached by the service per domain for the month it was generated in; no customer or order data is ever sent. The returned report is saved in your own WordPress database and removed when cloud checks are turned off or the plugin is uninstalled.

All other features — attribution, scoring, schema, feed generation, llms.txt, the remaining audit checks — run entirely on your server. If cloud checks are off, no request leaves your site.