SurfacedBy AI Visibility - AI Traffic, Crawler Analytics & llms.txt

The plugin checks requests in WordPress and uses a small script on pages served from a cache. The effect on your site's speed depends on your hosting and traffic, so check performance on your own site after installing it.

Yes, for visits that appear to come from a supported AI assistant. It does not count visits from Google, social media, or direct links as AI referrals. For an AI referral, it records the referring site, the page visited, the time, and pseudonymous identifiers used to link a later order or signup. Store integrations and window.sbAi.track calls can record sale or signup details as described under External Services. On connected installs, anonymous page observations also cover visits from other sources, to measure AI referrals as a share of observed traffic. These counts use no visitor or session identifier, cookie or visitor storage.

Connecting sends the crawler, visit, and sales or signup records from your site to your SurfacedBy dashboard. You can then see them alongside your site's AI visibility and cited pages. The WordPress features continue to work when the plugin is not connected.

The plugin shows which crawlers you are blocking and what each one does (training, search indexing, or live answers). You choose the policy; the plugin never edits your robots.txt.

Yes. You can keep using Yoast, Rank Math, AIOSEO, or SEOPress. The llms.txt generator follows their noindex and nofollow settings, so excluded content stays out of its list.

Yes. When WooCommerce or MemberPress is active, the plugin records supported purchases, renewals, refunds, and signups against the AI visit that brought the customer in. No shortcode or checkout change is needed. For a checkout outside WordPress, your developer can send a purchase with window.sbAi.track('purchase', { event_id, value, currency }).

Yes. SurfacedBy > Settings has a "Track conversions" switch. Turning it off stops every integration and the JavaScript API at the source; nothing is recorded or forwarded.

Yes, with Easy Digital Downloads 3.0 or later. The plugin records completed payments as purchases and tracks refunds separately, including partial refunds.

Yes. Turn on "GTM bridge" in SurfacedBy > Settings. The plugin listens for purchase events in Google Tag Manager and uses the GA4 transaction ID when it records them. Use the same order number in WooCommerce and GTM so a purchase reported by both is counted once.

Yes. SurfacedBy gives each domain a webhook URL and an HMAC-SHA256 secret that signs each delivery. Reveal the secret in the Setup drawer on the SurfacedBy dashboard's Tracking page, then POST events to https://api.surfacedby.com/api/v1/tracker/webhook/conversions with the X-SurfacedBy-Site-Id, X-SurfacedBy-Timestamp, and X-SurfacedBy-Signature: t=<unix>,v1=<hex> headers. The signature covers <timestamp>.<body> with HMAC-SHA256, the same scheme as SurfacedBy's outgoing webhooks. Requests older than 5 minutes are rejected, and each Site ID can send up to 100 requests a minute. Example: curl -X POST https://api.surfacedby.com/api/v1/tracker/webhook/conversions \ -H "X-SurfacedBy-Site-Id: SB-XXXXXXXXXXXX" \ -H "X-SurfacedBy-Timestamp: 1715990400" \ -H "X-SurfacedBy-Signature: t=1715990400,v1=" \ -H "Content-Type: application/json" \ -d '{"event_type":"purchase","event_id":"4821","value":99.99,"currency":"USD","occurred_at":"2026-05-18T12:00:00Z"}'

When this plugin, the GTM bridge, or a webhook reports the same purchase, SurfacedBy matches the records by event ID and keeps one. The dashboard shows when other sources reported it too. Use the same order number as the event ID in each source.

Yes. Implement \SurfacedBy\AIVisibility\Conversion\Adapters\ConversionAdapter and register your class with the surfacedby_aiv_conversion_adapters filter. Integrations that provide an optional static events_covered() method appear in the dashboard's coverage table.