Jake Labate

Implementing NLWeb on WordPress

Open project for natural-language website interfaces and agent discoverability. This guide is specific to WordPress teams shipping production integrations.

Back to NLWeb Back to protocol collection

Why this implementation exists

NLWeb helps publishers expose schema-backed site knowledge through natural language interfaces and MCP-compatible access patterns.

Use a dedicated plugin as the protocol adapter so all protocol logic, permissions, and observability live outside your theme layer.

Protocol-specific implementation focus

  • Normalize content into schema-rich sources (Schema.org, RSS, JSON feeds).
  • Build retrieval and answer layers with provenance and attribution.
  • Expose safe query surfaces while keeping privileged actions behind policy checks.

WordPress technical foundation

  • WordPress REST API (`/wp-json/wp/v2`) for canonical content retrieval and updates.
  • Custom REST routes with `register_rest_route()` for protocol-specific actions.
  • Nonce + capability checks (`wp_verify_nonce`, `current_user_can`) for every write path.
  • Application Passwords or OAuth layer for service-to-service authentication.

Step-by-step production rollout

  1. Scope the target journey. Pick one high-value flow where NLWeb adds deterministic value and define success metrics (latency, completion rate, human override rate).
  2. Build a protocol adapter service. Keep NLWeb logic in a dedicated adapter layer, separate from CMS templates and page rendering concerns.
  3. Map protocol contracts to WordPress primitives. Define read/write boundaries and strict schemas before implementation starts.
  4. Add authentication and policy gates. Enforce least-privilege tokens, role checks, and explicit approval points for sensitive operations.
  5. Implement idempotency + retries. Make long-running operations safe for replay, and include request IDs for traceability.
  6. Instrument observability. Log capability calls, validation failures, latency, and user escalations with protocol-level correlation IDs.
  7. Run conformance + integration tests. Validate schema contracts, permission boundaries, and rollback behavior before production.
  8. Roll out progressively. Start with read-only capability exposure, then enable controlled writes, then full orchestration.

Security and governance controls

  • Use environment-scoped secrets and rotate credentials for WordPress integrations on a fixed cadence.
  • Treat protocol payloads as untrusted input; validate all schemas before execution.
  • Record human approvals and denied operations for post-incident audits.
  • Apply explicit write allowlists for NLWeb actions that mutate WordPress content or commerce state.
  • NLWeb deployments should be treated as AI product surfaces with retrieval quality checks, source provenance, and safety evaluation loops.

Validation checklist

  • Contract tests for each protocol endpoint against expected schemas.
  • Permission tests for editor, author, and admin roles.
  • Replay/idempotency tests on retries and webhook re-delivery.

Common failure modes and mitigations

  • Protocol adapters executing privileged updates without `current_user_can()` checks.
  • Mixing protocol logic into theme code, making upgrades brittle.
  • Lack of idempotency for async retries, causing duplicate content or orders.

Official references used in this guide

NLWeb references

WordPress references