- AI traffic shows zero: attribution needs a referrer, a campaign tag or an assistant fetch of the same page; give it a few days of traffic. Estimates are shown separately and labelled.
- Numbers differ from GA4: GA4 has an AI Assistant channel, but it classifies by referrer, most assistant traffic arrives without one, Perplexity and Claude are not in Google’s list, and a session in analytics is not an order in your database. The two are complementary.
- The crawler log shows everything as “Says so”: address verification is off. Turn it on in Settings; it downloads the vendors’ public address lists once a day.
- An agent asks for something and gets a refusal: the journal line says why (for example
scope-missing: the key does not carry the scope the call needs). Give the agent a key with that scope, or leave the refusal as it is. - llms.txt not visible: flush permalinks and any page cache; the file is served by the plugin, not written to disk.
What Clearway Forge Does Not Do
- It does not guarantee that agents will buy, and it has no agent checkout of its own.
- It does not send store or visitor data to third parties. The only outbound requests are the public crawler address lists (off until you switch verification on) and, in the add-on, the licence check and the update check.
- It does not let an agent write to the store: the agent API only reads today, and writes are not open to agents yet.
- It does not run an MCP server, generate content, or survey language models about your brand.