On this page

• Why use this
• How it works
• How it differs from related options
• Step-by-step setup
• Common errors and troubleshooting

Why use this

• Your site runs on WordPress and you publish content regularly.
• You want real-time sync — new posts appear in the assistant within seconds of publishing.
• You want updates and deletes mirrored automatically.
• You're comfortable installing a WordPress plugin for verification.

How it works

The integration has two parts.

1. Initial import via REST API. Echo calls your WordPress REST endpoint (/wp-json/wp/v2/posts, /wp-json/wp/v2/pages, etc.) and pulls every published post. The HTML body is converted to Markdown so headings, lists, and code blocks survive intact. If Markdown conversion fails for a post, Echo falls back to plain text.
2. Ongoing sync via Echo plugin webhooks. The Echo WordPress plugin registers as a verified source on your site and posts events to Echo when content changes. Publish a new post → Echo creates a content item. Update a post → Echo refreshes the item. Delete a post → Echo removes the item.

Each synced post carries its WordPress ID, slug, type, status, author, and taxonomies as metadata. The original WordPress permalink is preserved so visitors can click through from citations.

How it differs from related options

• vs Website synced source — Website crawls via sitemap and re-crawls on demand. WordPress uses the REST API + webhooks, which is faster, more reliable, and updates in real time. If you have WordPress, prefer this.
• vs URL manual upload — URL handles one page at a time with manual refresh. WordPress imports every post and stays in sync without intervention.
• vs the WordPress plugin guide — that guide covers the plugin's full feature set (chat widget embed, etc.). This page is about using the plugin for content sync only.

Step-by-step setup

1. Install and activate the Echo WordPress plugin on your site. The plugin handles verification and registers the webhook endpoints.
2. In Echo, open Integrations from the dashboard's Synced content sources section.
3. Click Add source and select WordPress.
4. Enter your WordPress site URL (e.g. https://example.com or https://example.com/blog). Echo accepts URLs with or without http(s) and with or without a trailing slash.
5. Complete the verification step. Echo confirms the plugin is active and the REST API is reachable.
6. Select which assistant should receive the synced content.
7. Submit. Initial import begins in the background.

Watch the integration card status. Once initial import completes, future changes sync within seconds.

Common errors and troubleshooting

• "Plugin not detected" — the Echo WordPress plugin isn't installed or isn't activated. Re-check the plugin status in WP Admin → Plugins.
• "REST API not reachable" — WordPress security plugins (Wordfence, iThemes, etc.) sometimes block REST API access by default. Whitelist Echo or enable the REST API for the relevant endpoints.
• "Failed to fetch WordPress content" — a specific post returned a non-2xx response during import. 4xx responses are treated as "deleted" and skipped silently; other errors are logged on the integration.
• Posts not syncing in real time — webhooks may have failed to register, or your host blocks outbound HTTP. Check the plugin's settings panel for webhook delivery logs.
• Content looks like raw HTML — Markdown conversion failed and Echo fell back to plain text. This is usually fine for AI ingestion; check the source post for unusual shortcodes or invalid HTML.
• Old posts still in the library after deleting in WordPress — confirm the webhook fired (plugin logs). For one-off cleanup, refresh the integration to force a full re-sync.