Agentic Bridge

Agentic Bridge helps WordPress site owners inspect how safely and clearly their public site can be understood by AI-powered tools. Core functionality works standalone (no registration required).

Standalone / local (no The Dot Dev account required):

• Local Agentic Readiness scan (0–100 score) via bounded same-origin requests to /, /llms.txt, /agent-map.json, /robots.txt, and sitemaps only — never third parties or the control plane.

• Local page and site intent controls with metadata-only capabilities and blocked-claim controls

• Local content eligibility include/exclude controls for posts and pages

• Read-only Crawler Access, Content Health, Link Health, and Answer Structure evidence with source, freshness, scope, and uncertainty

• Prioritised local review queue with page evidence and human review before proposed changes

• Reversible Review Changes for supported Agentic Bridge-owned Page/Post fields: proposal, approval, conflict refusal, apply, verify, restore, and local history

• Preview-gated /llms.txt and /agent-map.json publishing (generate exact preview, then publish; 404 until published)

• On Apache with plain permalinks, publish may add a bounded.htaccess marker ( # BEGIN TDAB Artifacts … # END TDAB Artifacts ) routing exact /llms.txt and /agent-map.json to index.php only; removed on deactivation/uninstall. No physical artifact files. Pretty permalinks and non-Apache setups already routing to WordPress skip this write.

• Kill switch to suppress public artifacts instantly

• Last-known-good artifact storage with revalidation before serving

• Retain settings by default on uninstall (optional purge)

Optional hosted service (administrator-initiated):

• Connect with a pairing code to an administrator-configured HTTPS control-plane API base URL using a two-step preview → confirm flow (pairing codes are never stored or shown in previews)

• No outbound calls before an administrator generates and confirms a connection preview (confirm re-enters the pairing code and sends the exact preview payload bytes)

• After connection, hosted report refresh is an explicit administrator action (Refresh hosted report); opening the settings page makes zero outbound HTTP requests

• Snapshot upload uses a separate preview → confirm flow and sends the exact stored JSON bytes confirmed by the administrator

• Foyer integration is optional and metadata-only; this plugin does not add Foyer Host, dialogue, or action execution UI

Readiness scoring is a product methodology, not an industry certification. It does not guarantee crawler behavior, ranking, indexing, citation, training control, or AI recommendation outcomes.

Privacy

• No outbound telemetry before an administrator generates and confirms a connection preview (confirm sends the pairing payload)

• Hosted report refresh is explicit only; opening Agentic Bridge → Settings makes zero outbound HTTP requests

• Snapshot push requires a separate preview → confirm flow with exact-byte consent binding

• Credentials stored locally in WordPress options; purge available via uninstall retention setting

• Optional hosted retention (after Connect): operator maintenance tombstones snapshots after 30 days and deletes reports after 12 months (CLI only; Scheduler not configured ); disconnect clears credentials; hard-deletion not offered in-product.

External services

No external service is called until an administrator generates and confirms a connection data preview with a saved HTTPS control-plane API base URL and pairing code re-entry on confirm. app ) is prefilled, editable, saved locally, and never called passively — pairing, snapshot sync, and report refresh each need explicit administrator action.

• Agentic Bridge website: https://agenticbridge.app/

• Operator — The Dot Dev: https://thedotdev.com/

• Terms of Service: https://agenticbridge.app/legal/terms/

• Privacy Policy: https://agenticbridge.app/legal/privacy/

• WordPress.org contributor: https://profiles.wordpress.org/thedotdev/

Pairing claim (on confirm connect after preview) may send: pairing code, site URL, site name, WordPress version, and plugin version. Purpose: register this site with the control plane and receive site credentials for signed requests. The preview step never stores or displays the pairing code.

Snapshot sync (separate preview → confirm push) may send JSON snapshot metadata: site/plugin versions, timezone, kill-switch and publish state, artifact-eligible content fields ( id, type, slug, title, url, modifiedAt, indexability flags, status ), outbound claims, and optional last-known-good published artifacts when live. Excluded content is omitted; exclusion IDs are not transmitted. Never post bodies, users, comments, orders, or form submissions.

Findings/report fetch (explicit Refresh hosted report action only) may send: site ID and signed request authentication metadata (timestamp, nonce, payload hash, signature). GET report requests do not send an idempotency key.

No Foyer requirement or runtime is involved in these calls.