Clearway ForgeGet the free plugin

AI is already selling your store. See it. Sell to it. Stay in control.

Assistants send buyers to your shop today, and your analytics files most of them under Direct. This plugin counts that revenue, makes the catalog readable for agents, and holds every agent write until you say yes.

70.6% of AI referrals arrive with no referrerZero external calls in the shopper request path

perplexityclaudechatgptchatgpt

Order+$183.81


Direct106

Your analytics calls this traffic Direct

Assistants open links in a context that strips the referrer. The visit lands in your reports as if the buyer typed a 60 character product URL by hand, so the channel that produced it never shows up in any report you already have.

70.6%

of AI referrals arrive with no referrer at all, measured across 446k visits by The Digital Bloom

26.5%

of the reference store's AI sessions had to be recovered rather than read off a referrer

$229.80

revenue in one month that no report attributed to any channel

Counts

Every assistant becomes a line with a dollar amount

First party attribution, recorded on your own server and joined to WooCommerce orders. The panel below reads the same response shape the plugin serves in wp-admin, filled with the plugin's own test fixture.

AI channelAmerica/New_YorkAug 1 to Aug 31, 2026
$2,545.50across 16 orders and 400 sessions
Revenue, orders and conversion by AI source for the selected window
SourceRevenueShareOrdersSessionsConv.AOV
ChatGPT$1,286.7050.5%72093.35%$183.81
Perplexity$572.0022.5%3923.26%$190.66
Claude$532.9020.9%3397.69%$177.63
Gemini$32.501.3%1224.55%$32.50
Copilot$54.002.1%1119.09%$54.00
Other AI$67.402.6%1273.7%$67.40
Proven by referrer or campaign tag$2,315.70$229.80 more was recovered from visits that arrived with nothing attached

Daily AI revenue, America/New_York106 sessions (26.5%) would have been filed as Direct

Sells

Make the catalog readable, then purchasable

An assistant can only recommend what it can parse and only close what it can call. The plugin publishes the machine surface, keeps it in sync with the catalog, and shows you who is actually reading it.

88%agent readiness, 7 of 8 checks passing

  • llms.txt publishedon
  • llms-full.txt with policieson
  • Product and Offer schemaon
  • FAQ schema on product pageson
  • Machine readable catalog feedon
  • Assistant crawlers allowed in robots.txton
  • ACP product feed for agent discoveryon
  • Agent focused schema enrichmentoff
inboundinbound

Who read the catalog this month

Training crawlers can be turned away without losing a sale. The assistant fetches cannot: those happen while somebody is waiting for an answer.

Crawler hits by vendor, purpose and verification state
CrawlerVendorPurposeHitsAddress check
GPTBotOpenAITraining4,187verified
ChatGPT-UserOpenAILive user fetch612verified
OAI-SearchBotOpenAISearch index933verified
ClaudeBotAnthropicTraining1,504verified
Claude-UserAnthropicLive user fetch208verified
PerplexityBotPerplexitySearch index877verified
Perplexity-UserPerplexityLive user fetch143unverified
BytespiderByteDanceTraining2,291unverified
CCBotCommon CrawlTraining318unverified
GPTBotOpenAITraining46spoofed

A user agent string costs nothing to forge, so a claimed crawler is checked against the address ranges its vendor publishes. Unverified means the vendor publishes none, which is not the same accusation as spoofed.

Guards

An agent can ask. It cannot help itself.

WooCommerce ships an agent API in core, which means the write side is already open on millions of stores. Every ability runs behind a scope check, a risk rule and an append only journal.

HOLD
Atlas Pricingagt_atlas_pricingprice:write

Trailhead Merino Crew

$163.59$0.00

price-dropPrice cut is larger than 30% of the current price.

  • Scope, per key

    Each agent gets its own key with a written list of what it may touch. A call outside that list never reaches WooCommerce.

  • A rule for the change itself

    Scopes answer whether an agent may touch prices at all. Risk rules answer whether this particular change is the one you meant.

  • No undo, no ability

    A write ability that cannot be reversed is not registered at all, so no configuration mistake can let one through.

Your turn. This journal is live.

Deny the held price change and roll back the discount the same agent applied a minute earlier. Two entries get appended below, and their hashes chain onto the last one.

Agent journalsha256 chain
  1. 01woocommerce/get-products
    14:02:11 · 88c40faeb98fafbbc9dcc5ef
    allowed
  2. 02woocommerce/update-product-price
    14:02:52 · b970519e63d016aadc8338cd
    allowed
  3. 03woocommerce/update-product-price
    14:03:47 · 99015a5280cbad82a6ef5fcc
    held

Trailhead Merino Crew$163.59

Denied, price restored from the snapshot.

Nothing here is a mockup: the hashes were produced at build time by the same routine the plugin runs, and a test rebuilds them on every commit.

One email a month, with the number in the subject line

The artifact owners forward to their agency. It is assembled from the same figures shown above.

Clearway ForgeAugust 2026

AI brought you $2,545.50

Orders attributed to assistants16

Best source, ChatGPT$1,286.70

Sessions recovered from Direct106

Agent readiness88%

Agent actions waiting for you1

Your data stays on your server. The digest is rendered from figures your store computed, and the plugin sends nothing else.

Take the tower

Start with the free plugin from the WordPress directory. Upgrade when the number it shows you is worth more than the subscription.

Free

$0on WordPress.org

  • Attribution and dashboard, 30 days of history
  • llms.txt and llms-full.txt
  • Crawler log with citations
  • Monthly digest email
  • Schema enrichment and catalog feed
  • Agent guard rails
Install from the directory

Pro

$19per month

  • Unlimited history, first and last touch
  • Weekly digest email
  • Schema enrichment and catalog feed
  • CSV export of sources and crawlers
  • Agent guard rails
Start a Pro trial

Growth

$39per month

  • Everything in Pro, across multiple stores
  • Product feed tuned for agent discovery
  • Per agent keys and scopes
  • Approval queue, journal, undo
  • Kill switch for every key at once
  • Telegram alerts
Talk to us about Growth

Annual billing takes 20% off. Prices are set for the first cohort and will be reviewed after the first fifty paying stores.

Questions a shop owner actually asks

Does this slow the storefront down?

Visit capture writes to a buffer and flushes in the background through Action Scheduler. The budget for a storefront hit is two milliseconds, and a performance test in CI fails the build if it is exceeded. Nothing in the shopper request path calls an external service.

What leaves my server?

Your licence check, and opt in anonymous telemetry if you enable it. Order data, sessions and the journal stay in your own database. The digest email is rendered from figures your store computed.

How is this different from Google Analytics?

GA4 files most assistant traffic under Direct because the referrer is stripped before the browser arrives. Attribution here happens on your server, where the request actually lands, and it joins to WooCommerce orders rather than to page views.

Do I need the guard if I have not installed any agent?

WooCommerce core exposes agent abilities on its own, so the surface exists whether or not you added anything. The guard is what decides which key may call them and what happens before a write lands.

What happens if an agent does something wrong anyway?

Every write takes a snapshot of the record first and appends a journal line whose hash chains onto the previous one. Undo replays the snapshot, and the rollback is itself journalled. An ability that cannot be undone is never registered in the first place.

Is my data used to train anything?

No. The plugin reads your store and writes to your store. It also lets you decide, per crawler, which vendors may read the catalog at all, and it separates training crawlers from the assistant fetches that bring buyers.