Working with WP Engine?

WP Engine ceiling, overage or migration headache? We fix it.

Most WP Engine accounts that reach us are either paying overage charges every month, locked out of a plugin the platform disallows, or trying to move on or off and finding neither side is as straightforward as the sales pitch suggested. We look at the actual constraint and work the problem from there.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

wpengine.log

still failing

What it is

WP Engine at a glance

WP Engine, Inc. is a managed hosting platform built specifically for WordPress, founded in 2010 in Austin, Texas, and now majority-owned by the private equity firm Silver Lake. It covers everything a WordPress install needs on the operational side: automatic core updates, a page cache layer, dev, staging and production environments, Git push, an SSH Gateway, a bundled CDN, and daily backups kept in off-platform storage.

Over the years the company has absorbed several well-known pieces of the WordPress ecosystem. StudioPress and its Genesis Framework came in during 2018, Flywheel and the Local development tool followed in 2019, and Faust.js plus the Atlas product now cover headless WordPress deployments. Since 2024 WP Engine has been involved in a widely reported dispute with Automattic over access to WordPress.org resources, which in practice has affected how customers update plugins and themes.

Type
Managed WordPress hosting
First released
2010
License
Proprietary SaaS
Maintained by
WP Engine, Inc.
Typically used for
Production WordPress sites that need managed caching, staging and daily backups, agencies hosting client sites, headless WordPress via Atlas

The honest version

WP Engine pros and cons

No technology is all upside. This is where WP Engine earns its place and where it tends to cause trouble.

Where WP Engine is strong

  • Managed WordPress done wellCore auto-updates, a tuned page cache, and daily off-server backups are included and set up out of the box. You do not have to glue the pieces together yourself.
  • Proper dev, staging and productionEvery install ships with three separate environments and a one-click copy between them. Agencies get somewhere safe to try things before they reach the live site.
  • Git push and SSH GatewayCode can be deployed from a Git remote, and the SSH Gateway lets you run WP-CLI and move files without opening SFTP sessions by hand.
  • CDN is included in the planA global CDN ships with every account. Static assets are fronted automatically, so you are not shopping for a separate provider on day one.
  • Strong developer experienceLocal by Flywheel is bundled for building on your own machine, and the User Portal exposes logs, PHP versions and redirect rules without a support ticket.
  • Atlas for headless WordPressIf the front end is a React or Next.js app, Atlas hosts it alongside the WordPress back end with Faust.js wiring the two together, in one bill.

Where WP Engine bites

  • Priced well above shared hostingEven the entry plan runs several times what cPanel shared costs. For a brochure site that barely sees traffic, you are paying mostly for features it will never use.
  • Plans gated by three different ceilingsVisits, bandwidth and site count all cap independently. Cross any one of them and the plan jumps or overage charges begin at the end of the month.
  • Disallowed plugin list is longPopular caching and backup plugins are blocked because the platform handles those jobs itself. That is defensible, but it surprises owners who expected their existing stack to come along.
  • No email hosting of any kindMailboxes live somewhere else entirely. If the current host handles both site and mail under one roof, moving means picking a mail provider at the same time.
  • mod_security is aggressiveThe web application firewall occasionally blocks admin-ajax, REST API calls and plugin uploads that are entirely legitimate. Each case needs a support ticket or a custom rule exception.
  • Redirect rule ceiling bites during migrationsA site moving from an older platform often brings thousands of legacy URLs. The per-site limit on platform-managed redirects forces some of them into code or an edge rule instead.
  • Automattic dispute adds uncertaintyThe public disagreement with WordPress.org's steward has, at various points since 2024, affected plugin updates and login flows for WP Engine customers. The situation is still shifting.

Sound familiar?

Common WP Engine problems we fix

The WP Engine problems that bring people to us, and what you have once each one is fixed.

visits: 118%

The plan ceiling keeps being crossed

Bots, uptime pingers and image hotlinking count toward billable visits alongside real humans. Overage charges show up on the next invoice.

Visit count brought under the cap

disallowed plugin: wp-super-cache

A plugin we rely on is blocked

WP Engine disables plugins it considers redundant or risky. Usually there is a platform feature doing the same job, but the switch is not automatic.

Equivalent set up and verified

PHP 7.4 scheduled for removal

The PHP version is being retired

An older theme or plugin that only works on PHP 7.4, with an auto-upgrade date already on the calendar.

Code brought up to a supported version

500 on admin-ajax.php

mod_security is blocking the site admins

The firewall catches a Gutenberg save, a form builder submission or a WooCommerce call, and the editor sees a 500 with no explanation.

Rule tuned, admin working again

migration stuck pre-cutover

The move onto or off WP Engine stalled

Large database, LargeFS-stored media, and DNS that was pointed before the staging push finished running.

Cutover completed, mail still routing

redirects: 3000/3000

Legacy URLs will not fit the rule limit

A migration from an old CMS brings thousands of redirects that the per-site platform cap refuses to store.

Rules split between platform and edge

handover: no portal access

The previous developer still owns the account

The User Portal, billing and the environment are all in someone else's login. Nothing can be changed until ownership moves.

Account and billing in your name

What we do

WP Engine help, from overage to moving off

Call us for one blocked plugin, or hand us the whole platform decision.

Overage review
Working out which visits are real, which are bots, and which belong on the CDN before they ever hit the origin.
Plugin replacement
Swapping disallowed plugins for either platform features or allowed equivalents, without breaking the editor workflow.
PHP upgrades
Testing themes and plugins against the target PHP version on staging first, then rolling the production environment forward.
Migrations onto WP Engine
Bringing a site in from cPanel, Kinsta, Pantheon or a self-managed server, keeping URLs, media and search engine signals intact.
Migrations off WP Engine
Moving to a platform that better fits the budget or workflow when WP Engine no longer earns its keep, mail provider sorted as part of the plan.
Handovers
Taking over an environment from a departed developer, with billing, portal access and SSH keys all moved into your name.
Managed Tech
Someone watching the account, catching plan creep and mod_security surprises before they become support tickets you have to write.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running WP Engine alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

WP Engine questions

Something else? Call+1 737 727 7327

Can you move our WordPress site to or off WP Engine without downtime?

Yes. We rehearse the move on a staging copy first, bring the database and uploads across, and only point DNS once the new side is verified against the old one. Mail is handled separately because WP Engine does not host mailboxes, so if the current provider does both we pick a mail destination as part of the plan rather than after the fact.

Why is our WP Engine site using more visits than our Google Analytics says?

Analytics only counts browsers that run JavaScript. WP Engine counts every request that reaches the origin and is not already a known static asset, which includes search engine crawlers, uptime monitors, feed readers and the hotlinked image traffic other sites pull from yours. The gap is usually explained once you compare server logs against the dashboard.

Can you take over a WP Engine environment from a previous developer?

Routinely. The portal account, billing contact and SSH keys all need to be transferred into your name, and the previous developer's access revoked once the handover is complete. We handle the WP Engine support side of the transfer and leave you with an environment you actually control.

Why are mod_security rules blocking our site admins?

The platform-level web application firewall is deliberately strict, and it occasionally flags legitimate admin-ajax, REST API or form submission requests as attacks. The fix is normally a targeted rule exception requested through support, backed by a log line showing the specific rule ID that fired.

Should we stay on WP Engine given the Automattic dispute?

For most of our clients the answer has been to stay put and watch, because leaving a working host mid-dispute costs more than it saves. If plugin updates or logins through WordPress.org actually stop working for you, that calculus changes and we would plan a move. We will give you our read on your specific setup rather than a blanket recommendation.

How much does WP Engine help cost?

Estimates are free. Share the install URL and a short note on what is going wrong, and you get a plan and a price before anything is touched.

Free estimate

WP Engine giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.