WordPress
Publish content straight from Averi to your WordPress site as drafts or live posts.
Averi's WordPress integration pushes finished content directly into WordPress. Pick the flow that matches your setup — WordPress (Managed) for sites hosted on WordPress.com, or WordPress (Self-Hosted) for WordPress.org sites you run yourself (including WP Engine, Kinsta, or your own server).
Not sure which one you have?
A quick way to tell:
- You probably have WordPress (Managed) if you signed up at wordpress.com, you log in at
wordpress.com/log-in, and you pay WordPress.com directly for your plan. Your site address often ends in.wordpress.com, though you may have a custom domain pointed at it. - You probably have WordPress (Self-Hosted) if you log in at
yoursite.com/wp-admin, you pay a separate hosting company (like WP Engine, Kinsta, Bluehost, SiteGround, GoDaddy, or your own server), and you (or your developer) installed WordPress yourself.
If you're still unsure, ask whoever set up the site — or reach out to us and we'll help you figure it out.
WordPress (Managed)
For sites hosted on WordPress.com. You'll sign in with your WordPress.com account — no passwords or technical setup required.
What You'll Need
A WordPress.com account with publishing access to the site you want to connect.
How to Connect
Open Integrations
In Averi, go to Integrations on the bottom left.
Connect WordPress (Managed)
Find WordPress (Managed) under Publishing and click Connect. You'll be redirected to WordPress.com's login screen to authorize Averi.
Select Your Site
Once you're back in Averi, pick the WordPress.com site you want to publish to from the list of sites you have access to.
Set Publishing Options
Choose how posts should land in WordPress:
- Save as Draft (default) — Posts land as drafts. You publish manually in WordPress when ready.
- Publish Immediately — Posts go live on your site as soon as they're sent.
Then pick any optional extras:
- Extract featured image — Pulls the first image from your content and sets it as the WordPress featured image (it won't also appear in the post body).
- Use SEO slug — Uses the slug (the URL-friendly version of your title, e.g.
my-blog-post) from your content's SEO settings. Otherwise WordPress auto-generates one from the title. - Use meta description as excerpt — Sends your SEO meta description as the WordPress excerpt (the short summary shown in post listings).
Review & Save
Confirm your settings and click Configure WordPress. You can re-open Integrations anytime to switch sites or change options.
WordPress (Self-Hosted)
For WordPress.org sites you host yourself. You'll connect with an Application Password — a special WordPress-generated code that's separate from your normal login.
What You'll Need
- WordPress 5.6 or newer with the REST API enabled (the default on modern WordPress installs).
- A user account with permission to create posts — Administrator, Editor, or Author.
- An Application Password generated in WordPress (instructions below).
Generating an Application Password
In your WordPress admin:
- Go to Users → Profile.
- Scroll down to Application Passwords.
- Enter a name (e.g.
Averi) and click Add New Application Password. - Copy the 24-character code it shows you (e.g.
abcd efgh ijkl mnop qrst uvwx). You won't be able to see it again after closing the page.
Your Application Password is not your regular WordPress login password. It's a separate code generated just for Averi, and you can revoke it anytime from the same screen.
How to Connect
Open Integrations
In Averi, go to Integrations on the bottom left.
Connect WordPress (Self-Hosted)
Find WordPress (Self-Hosted) under Publishing and click Connect.
Enter Your Credentials
Fill in:
- WordPress Site URL — Just the base URL, like
https://example.com. Don't include/wp-adminor other paths. - WordPress Username — The username you use to log into WordPress.
- Application Password — Paste the 24-character code you generated.
Choose a Sync Status
Under Sync Status, pick how posts should land:
- Sync as Draft (default) — Posts land as drafts for review in WordPress.
- Sync as Published — Posts go live on your site immediately.
Pick Optional Fields
Decide what else to send with each post:
- Extract featured image — Pulls the first image from your content and uploads it as the WordPress featured image.
- Include slug — Uses the slug from your content's SEO settings.
- Include meta description — Sends your SEO meta description. If your site uses an SEO plugin, pick it from the SEO Plugin dropdown — Yoast SEO, RankMath, or All in One SEO — so the description lands in the right field. Pick None (use as post excerpt) to send it as the WordPress excerpt instead.
- Include read time — Sends the estimated reading time with the post.
Under Keywords, choose what to send as WordPress tags (merged and deduplicated):
- Include focus keywords — The content's primary keywords.
- Include long-tail keywords — The content's supporting long-tail terms.
- Include strategy map path (Content Pillar + Focus Area labels) — The pillar and focus area names from your Strategy Map.
Keyword tags require the connected WordPress account to have permission to manage categories. If that permission is missing, WordPress may ignore the tags without showing an error.
Have Yoast SEO active on your site? When Yoast is installed, it takes over the SEO meta fields on your posts — and Yoast's REST API is currently read-only, meaning standard WordPress REST API requests (including Averi's) can't write to those fields. To get meta descriptions and other SEO fields landing in Yoast, you'll need a companion plugin that exposes Yoast's fields to the REST API.
Add a Custom Header (optional)
Most people won't need this. Some hosts with firewalls or security plugins strip the authentication header by default. If your host has given you a specific header to pass through auth, add it under Custom HTTP Header.
Save & Test
Click Connect WordPress to save, then click Test Connection. You'll see a green Connected confirmation once Averi can reach your site.
If the test fails or WordPress cannot be saved because the connection check did not pass, see Connection diagnostics below.
Connection diagnostics
For WordPress (Self-Hosted), when Test Connection fails from the configuration window, or saving the integration fails because Averi cannot reach or authenticate to your site, Averi shows diagnostic messaging so you know what went wrong and what to try next.
From the Configure / Edit window
- A Connection failed dialog summarizes the problem and suggests next steps.
- When relevant, you may see a copyable Potential fix snippet (for example Nginx, Apache, or
web.configguidance your host can apply). - Verify in your terminal — a sample
curlcommand that hits your site’s REST API the same way Averi does, so you or your team can reproduce the response outside Averi. Treat anything you copy from this panel as sensitive: the command can include your username and Application Password. Do not paste it into public chats or tickets. - Error log — technical detail (status, headers, response excerpt) that is useful for support or your host.
- Email this to me — sends the diagnostic to the email address on your Averi account. The emailed version redacts the Application Password in the
curlline (replaced with a placeholder) so you can forward it to your host or IT team more safely than copying from the dialog.
From the Integrations list (without opening Configure)
If you run Test Connection from the integration card, a notification shows the same issue title and advice text. Open Configure on the integration and run Test Connection again there if you need the full dialog (snippets, terminal command, error log, and email).
Publishing Content
Once you're connected, push content to WordPress by clicking Send to CMS in the editor or Publish from the finalized column. For details on the end-to-end flow, see Manual Publishing.
Depending on the publishing mode you picked, the post will land as a draft for review or go live immediately. You'll get a confirmation with a link to the new post.
If you want to schedule and auto-publish posts from Averi to your WordPress site, make sure Auto-Publish is toggled to ON in your Integrations page.
Tips
- Start with drafts. Until you're confident formatting is landing the way you want, publish as drafts so you can review in WordPress before anything goes live.
- Featured images come from your content. If you turn on Extract featured image, the first image in your article is pulled out and set as the featured image — it won't also appear in the body.
- Reconfigure anytime. Head back to Integrations to switch sites, change publishing mode, or rotate your Application Password.
- Hitting auth errors on self-hosted? Some hosts strip the Authorization header before it reaches WordPress. Use the Connection failed diagnostic (open Configure and run Test Connection) for host-ready snippets and a reproducible
curlcommand.
Updating Your Configuration
Your settings aren't locked in. Go to Integrations, find WordPress (Managed) or WordPress (Self-Hosted), and click Configure to change the site, credentials, publishing mode, or optional fields at any time.
Troubleshooting
If you're running into issues connecting or your content isn't publishing as expected, check the following:
WordPress (Managed)
- No sites listed during setup — Make sure the WordPress.com account you connected actually owns (or has publishing permissions on) the site you're looking for. Disconnect and reconnect with the right account if needed.
WordPress (Self-Hosted)
- Read the diagnostic first — When a connection test or save fails, open Configure and review the Connection failed panel (or use Email this to me for a shareable, password-redacted copy). It often pinpoints stripped auth headers, REST API blocks, Cloudflare rules, and similar issues more precisely than a generic error.
- Authentication failed — Double-check the username and Application Password. The Application Password is not your regular WordPress login password.
- REST API not found — Verify your site URL is correct and the WordPress REST API is enabled. Some security plugins disable it — check your plugin settings.
- Connection refused — Confirm the site URL is reachable. If your site is behind a firewall or uses Cloudflare, you may need to allowlist Averi's requests.
- WP Engine or Nginx hosting — Some managed hosts strip the Authorization header before it reaches WordPress. If you're on WP Engine, contact their support and ask them to add
fastcgi_param HTTP_AUTHORIZATION $http_authorizationto your site's Nginx config.
Either setup
- Content didn't publish — Confirm the integration is still connected in Integrations and that the post was Finalized before publishing. See the Drafting Workflow for how content moves through stages.
- Featured image missing — The Extract featured image option must be enabled in your configuration, and your content needs at least one image for Averi to pull from.
- Slug or meta description not showing — Make sure the corresponding option is toggled on in your configuration, and those fields are filled in on the content itself.
- Still stuck? — Book a technical help call with our team and we'll walk through it together.
Need Help?
Reach out to us at [email protected] - you'll always get a human to talk through solutions with.