Connect your self-hosted WordPress site to create or update posts and pages from Omni Impact. The connection uses WordPress Application Passwords and its REST API.
Before you connect
Your site needs WordPress 5.6 or later, HTTPS, Application Passwords, and a reachable WordPress REST API. You do not need an Omni Impact WordPress plugin for this connection.
Use a dedicated WordPress user with the Editor role when that role has the permissions your content needs. This makes the connection's changes attributable to that user.
Connect your site
To connect, enter your site address and approve access on your own WordPress site.
- Open Apps, choose Browse, and select Connect for WordPress (Self-Hosted).
- Enter the HTTPS address in Site URL. Wait for the site check to finish.
- Select Authorize on your site — one click.
- Approve the Application Password on your WordPress site. You return to Omni Impact after the connection is completed.
- Check the Connected tab for your site.
If you prefer manual setup, expand Enter credentials manually instead. Create an Application Password in WordPress admin → Users → Profile → Application Passwords, then enter your Username and Application Password and select Connect.
What publishing changes
Publishing creates or updates the title and body in WordPress. You can also include structured data, a meta description, and a URL slug. Check the resulting post or page before making it public.
| Field | WordPress behavior |
|---|---|
| Title and body | Written to the selected post or page. |
| JSON-LD | Included in the content body when supplied. |
| Meta description | Sets the WordPress excerpt. Yoast and Rank Math description support depends on your WordPress configuration. |
| URL slug | Written when you supply a slug. |
| Publication status | New content defaults to draft. Updating existing content preserves its status unless a status is explicitly supplied. |
Review the draft in WordPress before making it public. A successful Publish action in Omni Impact can mean that a draft was created; it does not mean the page is publicly visible.
When a page changed in WordPress
If a page was edited directly in WordPress after your last Omni Impact update, you may see an overwrite warning. Review the live page before confirming an overwrite.
Review and revert a change
Site Change History shows recorded changes and their details. Revert this change is available for successful self-hosted WordPress updates that have a saved previous body; creating a new page does not provide that previous version.
Open the change, compare the before and after content, then use Revert this change when available. Revert restores the previous title, body, and saved SEO fields affected by that change. Check any notice about fields that could not be restored, especially if your WordPress plugins changed.
Troubleshoot the connection
The site check distinguishes a blocked REST API, disabled Application Passwords, an unreachable site, and an address that does not expose WordPress.
| Message or symptom | What to check |
|---|---|
| Enter your site with https:// | Use your site's HTTPS address. |
| Application Passwords are turned off on this site | Ask your site administrator to enable them in WordPress. A host or security plugin can disable them. |
| Security blocks the connection | Ask your host or administrator to allow the OmniImpactBot user-agent through to the REST API, then re-check. |
| WordPress rejects the credentials | Check the WordPress username and Application Password, or reconnect with a new Application Password. |
| Site is unreachable or not detected | Check the site address and whether its REST API is reachable. |
The publisher identifies itself as OmniImpactBot-Publisher/1.0 (+https://omniimpact.net/bot). See OmniImpactBot and crawler access for the separate crawler identities.
For a persistent failure, contact support with the site-check message. Do not include your Application Password.