| 开发者 | karan08 |
|---|---|
| 更新时间 | 2026年9月30日 22:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. This plugin only observes and reports. It never changes what visitors or agents see.
An agent is verified in one of two ways. If it signs its request with Web Bot Auth, the signature is checked against the public keys its operator publishes; ShopBouncer only uses the key directories of operators that document them (OpenAI for ChatGPT's agent, Google for Google-Agent), and the dashboard names the operator that signed. If it doesn't sign, its IP address is checked against the ranges its operator publishes: inside means verified by IP, outside means impostor. A user-agent string with nothing to check it against is recorded as "unverified (name only)", because anyone can send it.
Yes, once you tell ShopBouncer where the visitor's IP arrives: open the AI Shoppers page and set "Visitor IP comes from" to Cloudflare, X-Forwarded-For or X-Real-IP. The page warns you when it detects a proxy header. Until then, requests from private addresses are left unchecked rather than flagged.
From WooCommerce's built-in Order Attribution (WooCommerce 8.5 and later), which already records where each order came from. ShopBouncer counts the paid orders whose source is an AI assistant's website, such as chatgpt.com or perplexity.ai. If Order Attribution is switched off, the dashboard tells you where to turn it on.
No measurable impact for human visitors. Agent visits are recorded after the response is finished.
The visit table and settings are deleted. Evidence saved on agent orders stays on those orders, because it is part of the order record.