Feedship AI Catalog Feeds for WooCommerce

FAQ

How do I get my WooCommerce products into ChatGPT Shopping?

Install the plugin, run the 3-step setup wizard, then copy your hosted JSONL feed URL from WooCommerce > Feedship AI Catalog Feeds and submit it through OpenAI’s merchant onboarding for ChatGPT Shopping. The feed rebuilds automatically on your chosen schedule, so prices, stock and new products stay current without manual exports. Listing your products in ChatGPT is handled by OpenAI’s onboarding process and is subject to their terms.

Does the free version require an external account, SaaS service, or API key?

It does not. All feed generation (.jsonl, .csv, /llms.txt, /llms-full.txt), discovery manifests (/.well-known/acp.json, /.well-known/ucp), and AI Readiness Scores run entirely on your WordPress server, without an external account, an API key, or a SaaS service.

What is the ACP?

ACP (Agentic Commerce Protocol) is OpenAI’s open standard, built with Stripe, for passing merchant catalog and checkout data to ChatGPT. This plugin publishes a /.well-known/acp.json discovery manifest plus a JSONL/CSV product feed following the published Commerce Feed Reference, so a WooCommerce store can provide the data the protocol describes without writing code.

What is /llms.txt and why does my WooCommerce store need one?

/llms.txt is a Markdown format (llmstxt.org) that gives AI models a compact map of your site instead of full HTML pages. This plugin publishes an e-commerce-flavored trio: /llms.txt (short store index), /llms-full.txt (every product with prices, stock and buy links) and /llms-commerce.txt (shipping, returns and payments guide). If Yoast SEO or Rank Math is already publishing /llms.txt, the plugin extends their output via native filters instead of duplicating the file.

What is the difference between /llms.txt, /llms-full.txt and /llms-commerce.txt?

/llms.txt is the concise index – your store summary plus section links. /llms-full.txt carries the full catalog: every purchasable variation with SKU, current price, availability, variation matrix and a direct product link. /llms-commerce.txt describes shipping options, return policy and accepted payment methods in one place.

What is the Universal Commerce Protocol (UCP)?

UCP is the open standard co-developed by Google and Shopify for AI-led buying flows. The plugin publishes a /.well-known/ucp discovery manifest and a UCP catalog search REST endpoint, so a store can expose the endpoints the protocol defines alongside the OpenAI ACP files.

Which AI platforms does this cover?

The plugin publishes files and endpoints for these destinations: an ACP feed for ChatGPT Shopping and OpenAI Ads; a UCP manifest and search endpoint for Google implementations; the /llms.txt family for any assistant that reads it; Product JSON-LD for search engines. The built-in crawler monitor reports reachability for GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, CCBot and Amazonbot.

Do my products need GTIN, MPN or brand data?

The OpenAI Commerce Feed Reference expects product identifiers where available, and missing GTINs are among the most common product-feed errors. The 1-click field mapper pulls GTIN, UPC, EAN, ISBN, MPN and Brand from WooCommerce core, Yoast, Rank Math, Germanized or any custom meta key, validates GTIN check digits with Modulo-10, and can apply a store-wide fallback brand. The AI Readiness Score tells you exactly which products are missing what.

Why do feed images need to be JPEG or PNG?

OpenAI’s Commerce Feed spec requires image_url to be a direct JPEG or PNG file. If your store serves .webp or .avif images, those URLs do not meet the spec. The plugin automatically resolves the underlying JPEG/PNG image for every feed row.

What is the AI Readiness Score and how is it calculated?

A deterministic 0-100 score from a 7-point audit: required feed fields, brand, image format, description depth, GTIN/MPN identifiers, product attributes, and FAQ coverage. Scores render as colored badges in Products > All Products, the dashboard groups your catalog into AI Ready / Needs Polish / AI Blocked, and one click recalculates the whole catalog. Because the audit is deterministic, the same product data always produces the same score.

Will this conflict with Yoast SEO, Rank Math, or WooCommerce Core ACP?

The plugin is built to run alongside them. When Yoast SEO or Rank Math is active it owns /llms.txt: the plugin detects it and steps aside, appending its commerce appendix to their output through the native wpseo_llmstxt_content and rank_math/llmstxt/content filters rather than writing a second file. Product JSON-LD is enriched the same way through their schema filters (wpseo_schema_graph, rank_math/schema/json).

Does it support variable products with multiple sizes, colors or materials?

Yes. Every purchasable variation becomes its own feed row built to OpenAI’s published Commerce Feed Reference, linked to the parent group_id, with a variant_dict whose options always match the row’s top-level attributes and deep-link URL, unique attribute combinations only (duplicates are never exported), and per-variation deep links in /llms-full.txt.

How do I hide a single product from AI channels?

Open the product, find the Feedship AI Catalog Feeds box, and tick “Exclude this product from all AI feeds and llms.txt output”. The product disappears from the JSONL/CSV feeds and llms-full.txt, and its list badge switches to Excluded.

Where do the Conversational Q&A pairs I add in the product metabox show up?

They appear in /llms-full.txt inside the product block (as “FAQ: question / Answer: …” lines). They also power the FAQ check of the AI Readiness Score (2+ pairs = full points) and are published as FAQPage JSON-LD for search engines. The OpenAI JSONL/CSV feed intentionally does not carry them: the published OpenAI feed spec has no FAQ field, and unknown fields can make a feed row invalid.

Can I change how often the feeds rebuild?

Yes. Open WooCommerce > Feedship AI Catalog Feeds > Settings and pick Hourly, Twice a day, Once a day (default), Once a week, or External cron / manual only. There is also a toggle to rebuild automatically whenever product data changes (batched, about a minute after the save), and a secret rebuild URL you can call from a real cron job or uptime monitor.

Will this slow down my store?

Feeds are generated on a schedule (WordPress cron or your own cron URL), not during shopper page loads. They are written atomically as static files and served straight from disk; the plugin adds no front-end scripts or styles. Large catalogs are scanned in pages of 100 products so memory stays flat, and generation never runs inside a shopper’s request.

How many products can it handle?

The plugin does not impose its own product cap: one feed row is generated per purchasable variation in your catalog. Practical limits come from your hosting – generation time scales with catalog size, and very large catalogs are scanned in pages of 100 products so memory stays flat while generation runs in the background. Output is a static file, so serving a 10,000-row feed works the same way as serving a 10-row one.

Does this replace my Google Shopping feed?

It is not a replacement – it targets a different channel. Google Shopping integrations export XML for Google Merchant Center; this plugin publishes the AI-native formats: OpenAI’s ACP JSONL/CSV feed, UCP discovery for Google implementations, the /llms.txt family for LLMs, plus an AI Readiness Score, FAQPage JSON-LD and AI crawler monitoring. All of those files are generated and stored on your own server.

Will AI crawlers be blocked by my robots.txt, security plugin or firewall?

The AI Bot Allowlist & Crawler Monitor scans your effective robots.txt output for the eight AI crawlers, live-probes /llms.txt and your feed URL, and shows which bots are blocked so you can fix the cause before you submit your feed. WordPress-level blocks (from SEO or security plugins) are detected directly; hosting firewalls and CDNs sit outside WordPress, and the monitor tells you when a check cannot see that far.

Which prices are exported – with or without tax?

The same amounts your storefront displays. The plugin asks WooCommerce for the display price (wc_get_price_to_display), so your tax settings – “prices entered with tax” and “display prices in the shop” – decide whether feeds carry tax-inclusive or tax-exclusive amounts. Sale prices are exported the same way next to the regular price.

Is WordPress multisite supported?

Activate it per site: the plugin is single-site focused, and network activation does not propagate settings, schedules or rewrite rules to subsites. When the optional clean uninstall runs, it does remove data from every site in the network.

I already have a physical /llms.txt file in my web root. Which one wins?

The physical file – web servers serve it directly before WordPress runs. Remove or rename it and re-save Settings > Permalinks if you want this plugin to manage /llms.txt. Yoast SEO and Rank Math users need nothing: the plugin hands /llms.txt over to them and merges its commerce appendix into their output.

Is any store or product data sent to a third-party server?

No. Feeds, llms.txt files, manifests and scores are generated and stored on your own server under wp-content/uploads/feedship-feeds/ (directory listing disabled), and the plugin makes no calls to third-party services carrying your catalog data – its only HTTP requests are loopback checks to your own site during the built-in diagnostics. Deactivating stops generation; the optional clean uninstall removes every stored trace. Note that the published feed and discovery URLs are intentionally public: AI agents must be able to read them, exactly like your product pages.