How an Outdated ExpressionEngine Installation Affects Your Google Rankings
Running an old version of ExpressionEngine has consequences beyond security. Here is how an outdated installation affects the factors Google uses to rank your site.
A server migration is one of the most reliable causes of unexplained search ranking drops on ExpressionEngine sites. The migration appears to go well. The site loads. The content is there. But over the following weeks, search visibility declines in ways the business owner attributes to algorithm changes or seasonality. In most cases, the cause is the migration, and the damage is preventable.
Redirects that did not carry across
The most common single cause of post-migration ranking drops is redirect rules that existed on the old server and were not replicated on the new one. If your old EE site had .htaccess redirects handling old URLs, retired pages, or URL structure changes from a previous migration, those rules were probably not documented and were certainly not automatically transferred. When Google revisits URLs it previously indexed and finds errors instead of redirects, it loses the ranking signals associated with those URLs.
The base URL and canonical handling
ExpressionEngine's base URL configuration determines which version of the site is considered canonical. After a migration, particularly one that involves moving from HTTP to HTTPS, or changing the domain, this configuration needs to be updated correctly. If it is not, the site may be accessible at multiple URLs simultaneously, splitting its ranking signals and creating duplicate content that Google does not know how to handle.
Caching and performance configuration
Server migrations often involve changes to caching configuration. If the previous server had opcode caching or server-level page caching in place that the new server does not, the site will load more slowly. If the new server is in a different data centre from the previous one, latency for the primary audience may increase. Both of these affect Core Web Vitals scores, which are a Google ranking factor. The impact is gradual but cumulative and begins immediately after the migration.
What a properly managed migration looks like
The preventive approach is to treat a server migration as a technical SEO project rather than a hosting change. That means crawling the site before the move, documenting all redirects, testing the new environment before switching DNS, configuring the base URL correctly, replicating all caching settings, and monitoring search performance weekly for the first month after go-live. On ExpressionEngine sites specifically, the base URL, template routes, and .htaccess configuration all deserve attention before and after the switch.
If the drop has already happened
If rankings have already fallen after a migration, the first step is a crawl of both the old URLs, if accessible, and the current site to identify what changed. In most cases the damage is recoverable, but recovery time is proportional to how long the broken state persisted and how significant the affected pages were. The sooner a specialist ExpressionEngine developer is engaged after the migration, the faster the recovery.
If your search rankings dropped after a migration, get in touch with Karl to find out what can be recovered.
Topics
ExpressionEngine
