SurfacedBy AI Visibility
| 开发者 |
surfacedby
alikhallad |
|---|---|
| 更新时间 | 2026年8月19日 06:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- AI Bot Analytics. Which AI crawlers are reading your site, what they are after (training data, search indexing, or live retrieval), and how often. Covers GPTBot, ClaudeBot, PerplexityBot, Meta-ExternalAgent, and the long tail.
- AI Referral Tracking. Real visits from chatgpt.com, claude.ai, perplexity.ai, gemini.google.com, copilot.microsoft.com, grok.com, and meta.ai. Proven referrer hosts only, no behavioural guessing.
- AI Readiness Diagnostics. A one-click check on robots.txt, your llms.txt, and the schema types answer engines look for (Organization, Article, FAQPage, Product). It tells you what is broken.
- llms.txt Generator. Publishes a clean
/llms.txtindex of your posts and pages so AI tools can find your content. Respects Yoast, Rank Math, AIOSEO, and SEOPress noindex rules. - AI Conversion Tracking. Detects WooCommerce and MemberPress
automatically and credits purchases, renewals, signups, and refunds
to the AI source that drove the customer. Custom checkouts call
window.sbAi.track()to ship the same data. Attribution holds from first visit through to purchase, even days later.
安装:
- Install the plugin from the WordPress.org directory or upload the zip.
- Activate it.
- Visit SurfacedBy > Dashboard in the WordPress admin.
- Run the AI Readiness checks; the local features start collecting bot and referral data immediately.
- Pair the plugin with SurfacedBy: sign in or create an account at surfacedby.com, add your site, copy your Site ID, paste it into SurfacedBy > Connect, and save. Your data starts syncing to the dashboard once verification completes.
屏幕截图:
常见问题:
Does this plugin slow down my site?
No. Bot detection runs server-side before the response is sent and adds under 10 ms per bot request. Normal human requests are untouched.
Does this plugin track human visitors?
Referral tracking runs only when someone arrives from a confirmed AI tool. Visits from Google, social, or direct links are not logged as AI referrals. For a qualifying visit, the plugin stores the referrer host, request path, event time, a short session nonce, and a pseudonymous visitor ID. Enabled commerce integrations and explicit window.sbAi.track calls can also record conversion details as described under External Services.
What does pairing the plugin with SurfacedBy give me?
Pairing pushes the data the plugin already captures (bots, referrals, conversions) up to the SurfacedBy dashboard, where it lines up next to the AI ranking and citation analytics for your domain. The local features keep working the same way whether you pair or not.
What if I block AI bots in robots.txt?
The plugin shows you which bots you are blocking and what that means (training, search indexing, or retrieval). You choose the policy. The plugin never edits your robots.txt.
Will the plugin work with my SEO plugin?
Yes. Keep Yoast, Rank Math, AIOSEO, or SEOPress for Google rankings, and let SurfacedBy handle the AI side. The llms.txt generator reads noindex and nofollow flags from your existing SEO plugin, so excluded content stays excluded.
Does the plugin track WooCommerce orders or MemberPress signups?
Yes, automatically, with no shortcode or checkout edits. Activate
WooCommerce or MemberPress and the plugin starts recording purchases,
subscription renewals, refunds, and signups against the AI source
that drove the customer. For non-WordPress checkouts (headless
Shopify, custom front-ends), call
window.sbAi.track('purchase', { event_id, value, currency }) and
the data lands in the same place.
Can I turn conversion tracking off?
Yes. SurfacedBy > Settings has a "Track conversions" toggle. Disabling it stops every adapter and the JS API at the source; nothing is logged or forwarded.
Does it work with Easy Digital Downloads?
Yes. EDD is auto-detected the same way WooCommerce and MemberPress are. Completed payments ship as purchases and refunds ship as separate negative-value rows so partial refunds compose cleanly.
Can I forward Google Tag Manager purchases to SurfacedBy?
Yes, with one toggle. Enable "GTM bridge" in SurfacedBy > Settings and
the plugin subscribes to dataLayer purchase events and forwards them
to window.sbAi.track('purchase', ...) using the raw GA4 transaction
ID. The dashboard's cross-source dedup pass collapses this row with the
WooCommerce-adapter row keyed by the same order number, so a site
running both does not double-count. The dedicated GTM tag template
(integrations/gtm-tag-template/) is the more flexible option when you
need to forward refunds or custom event types.
Can I send conversions from outside WordPress (server-side webhook)?
Yes. SurfacedBy publishes a per-domain webhook URL plus an HMAC-SHA256
shared secret that signs each delivery. Reveal the secret in the
SurfacedBy dashboard's Tracking page Setup Drawer, 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, matching the outbound
SurfacedBy webhook scheme. Replay window is 5 minutes; the per-Site-ID
rate limit is 100 requests / minute.
Example curl:
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=<hex>" \\ -H "Content-Type: application/json" \\ -d '{"event_type":"purchase","event_id":"4821","value":99.99,"currency":"USD","occurred_at":"2026-05-18T12:00:00Z"}'
How does cross-source deduplication work?
If you wire multiple sources for the same site (this plugin plus the GTM bridge plus a server-side webhook), SurfacedBy automatically deduplicates by event ID. The strongest source wins (plugin first, then webhook, then JS), and the others appear in the dashboard as "+ N sources" on the surviving row. To make dedup most accurate, use the order number as the event ID across every source so the underlying keys line up.
Can I add my own conversion adapter?
Yes. Implement
\SurfacedBy\AIVisibility\Conversion\Adapters\ConversionAdapter and
register your class via the surfacedby_aiv_conversion_adapters
filter. Adapters that expose an optional static events_covered()
method will appear in the dashboard's coverage matrix.
Can I point the plugin at a local SurfacedBy backend during development?
Yes. Hook the surfacedby_aiv_api_base filter from a mu-plugin and
return your local URL (for example http://host.docker.internal:8000)
so the plugin sends events to your local backend instead of the
production API. The filter applies to every HTTP call the plugin
makes, including heartbeat and event shipper.
更新日志:
- Changed: The browser tracker now sends its events through the WordPress handler built for submissions from logged-out visitors. Tracking behaviour and the data recorded are unchanged.
- Fixed: Exported CSV files no longer let a recorded page address be treated as a formula by a spreadsheet application when the file is opened.
- Fixed: A tracking request carrying an unexpected value type is now ignored cleanly instead of adding a PHP warning to the site's error log.
- Fixed: When SurfacedBy rejects a batch of events, the plugin now reports that and moves on instead of resending the same batch on every scheduled run until it expires, which held up the events queued behind it.
- Fixed: Purchases recorded from WooCommerce, Easy Digital Downloads, and MemberPress no longer report the home page as the page that earned the sale. These run after checkout, away from any page, so the sale is now recorded without a page instead of being credited to the wrong one.
- Fixed: The top converting pages list no longer counts sales that have no page attached to them.
- Fixed: Button labels remain readable in their normal, visited, hover, focus, and active states throughout the WordPress admin.
- Security: Browser event writes are gated by a WordPress nonce that is verified in the REST permission callback before the write runs.
- Security: Duplicate conversion detection now uses a prepared WordPress database query instead of inspecting the database driver directly.
- Fixed: Admin icons and generated markup are escaped at output time using a narrow SVG allow-list.
- Improved: Plugin-owned cache keys use the full surfacedby_aiv prefix.
- Improved: Privacy disclosures now describe pseudonymous identifiers, local storage, advertising click IDs, and individual event forwarding. Logged-in attribution can be exported and erased with WordPress privacy tools.
- Compatibility: No settings changes or data migration are required.
- Compatibility: Tested with WordPress 7.0.2.
- Changed: The browser tracker no longer requires a SurfacedBy account. It records AI referrals and conversions into your own database on a fresh install, with no Site ID and no pairing. Connecting an account only syncs that data to the dashboard.
- New: Events captured before you connect are kept and sync automatically once you do, so pairing an existing install does not start from zero.
- New: Settings shows how many events are stored locally and waiting to sync.
- Fixed: Conversion logs were never pruned by the retention cron, so the table grew without bound on sites that kept their data local.
- Fixed: A commerce integration that declared its event list as a non-static method caused a fatal error when the plugin read it.
- Hardened: Cookie, header, and server values are sanitised on read, and the referrer host recovered from the attribution cookie is validated as a hostname before it is stored or forwarded.
- New: Trials are a first-class conversion type, so a trial start, its conversion to paid, later renewals, and refunds each show up separately instead of collapsing into one purchase.
- New: Bot identity verification. A request claiming to be an AI crawler is checked against the bot's published address ranges, so spoofed traffic is not counted as a real AI bot.
- Improved: AI crawls of
robots.txtandllms.txtare now recorded, so you can see which crawlers are reading your AI access rules. - Improved: The attribution cookie is capped at 13 months from the first time it was set.
- Improved: AI visits are now tracked reliably on sites that use caching or a CDN such as Cloudflare. This works automatically; you can turn it off under Settings if you ever need to.
- Improved: AI visits are still matched to the sale on browsers with strict privacy settings, such as Safari, so your conversion reports stay accurate.
- Improved: Subscription renewals are now credited to the AI source that won the original sale, so recurring revenue keeps showing up in your AI reports for the life of the subscription.
- New: AI conversion tracking. Auto-detects WooCommerce and MemberPress and records purchases, renewals, signups, and refunds against the AI source that brought the customer in.
- New:
window.sbAi.track()JavaScript API for custom front-ends and non-WordPress checkouts (Shopify Hydrogen, headless storefronts). - New:
sb_attrattribution cookie so conversions are credited to the AI platform even days after the original visit. - New: Conversions admin tab with 7-day totals, by-type breakdown, and a recent-activity table; only shown when at least one supported platform is detected.
- New: Adapter registry (
surfacedby_aiv_conversion_adaptersfilter) for downstream plugins that want to register additional adapters without forking. - Improved: Event shipper now drains conversion rows alongside bot and referral rows on the same hourly cron + page-render shutdown path.
- Improved: Idempotent end-to-end ingest. Rows are deduplicated on a stable event_id so a re-fired purchase or replayed webhook is a no-op.
- Initial release.