WP Engine manages the WordPress — the plugin keeps its blog publishing.
Because WP Engine hosts managed WordPress, DraftSEO’s plugin goes in like any other and turns each article into a native post whose images sit in the Media Library. What gets in the way is anything guarding the environment: password protection takes the Authorization header every DraftSEO request is signed with, and a Global Edge Security challenge is something a server cannot solve.
| Publishing | Native WordPress posts via the plugin — images imported to the Media Library, with slug, category and SEO fields applied |
|---|---|
| Password protection | Must be off — HTTP Basic auth claims the Authorization header, and WP Engine states APIs can’t get through |
| Transferable environments | Password protection stays on — WP Engine does not let you turn it off on them |
| Which environment | Production, on your own domain — not environmentname.wpenginepowered.com, staging or development |
| Global Edge Security | Keep challenges off — Under Attack Mode and country challenges turn DraftSEO’s servers away |
Who does what
Nothing, once production is connected with its password wall and edge challenges out of the way. New articles publish on their own; switch to draft mode if you want each one to wait in WP Admin for a read-through.
WP Engine keeps the site running; DraftSEO keeps it posting.
Setup
The plugin itself installs normally — the work is making sure nothing stands between DraftSEO and production.
Choose WP Engine in Connect a site; the WordPress plugin connection opens with WP Engine’s notes at the top.
Under a minute
On your production environment, go to WP Admin → Plugins → Add New, search for “DraftSEO”, then install and activate it.
~1 minute
Switch password protection off for the environment: its HTTP Basic auth takes over the Authorization header DraftSEO signs requests with, and transferable environments do not allow switching it off. On Global Edge Security, leave both Under Attack Mode and country challenges disabled for this site.
~2 minutes
Signed in to DraftSEO, open the production environment (not a staging or development copy) and first check Settings → General → WordPress Address (URL) shows your real domain — the plugin connects the address saved there, not the one in your browser, not environmentname.wpenginepowered.com. Then choose Connect with DraftSEO.ai from the plugin’s settings page.
~1 minute
Your WP Engine blog now gains researched, illustrated articles on a steady cadence, with no one at the keyboard.
Ongoing · zero clicks
FAQ
Yes. Sites on WP Engine are WordPress, so the DraftSEO plugin installs from the plugin directory and publishes native posts, their images stored on your own site. The one condition: the environment you connect must not be password protected.
WP Engine’s password protection uses HTTP Basic auth, which occupies the Authorization header — the same header each DraftSEO request is signed with — and WP Engine itself notes that APIs cannot connect through it. Turn it off for the environment you connect. On a transferable environment it cannot be turned off.
Neither. DraftSEO belongs on production, reached through your own domain — not its environmentname.wpenginepowered.com address, and not a staging or development copy.
It can. Under Attack Mode and country challenges both demand that a browser challenge is solved first, and DraftSEO’s servers have no browser to solve it with. When your site sits behind Global Edge Security, leave both switched off for it.
No card required. Production connected in about two minutes.