4,800 URLs. 6 Years of Rankings.
Upgraded Without Losing a Single Position.
Organic Traffic Up 34% in 8 Weeks.
An Australian sports and fitness retailer had spent 6 years building their organic search rankings — 4,800 indexed URLs, 340 first-page keyword positions, and 68% of their revenue coming from organic traffic. The upgrade was overdue. The SEO risk was real. We designed the entire upgrade around their SEO — and turned the upgrade itself into a ranking catalyst.
Six Years of SEO Work at Risk. The Owner Had Seen It Happen to a Competitor.
This sports and fitness retailer had been building their Magento store since 2018. Their SEO results were the product of 6 years of consistent content work, link building, and technical optimisation — 4,800 indexed URLs, 340 first-page positions, and a domain authority of 42. Organic search drove 68% of their total revenue. They had watched a competitor lose 60% of their organic traffic after a Magento upgrade gone wrong. They came to us with a single non-negotiable: the upgrade cannot touch the rankings.
The technical situation was straightforward — Magento 2.4.4 to 2.4.8, with PHP 8.0 needing to move to 8.2, and 38 active extensions requiring compatibility testing. But the SEO complexity was significant. Over 6 years, their URL structure had evolved organically — category URLs had been restructured twice, product URLs used a custom suffix pattern, and 1,200+ legacy URLs from a 2021 site restructure were still sending 301 signals that needed to be preserved through the upgrade without being broken by the URL rewrite module changes in 2.4.7.
Why Magento upgrades are a specific SEO danger zone
Magento 2.4.6 and 2.4.7 introduced changes to the URL rewrite engine that silently break existing 301 redirect chains if not explicitly migrated. Stores upgrading from 2.4.4 or 2.4.5 that have legacy redirect chains are particularly exposed — the redirects appear to work in testing but return incorrect status codes in production under load. This is the most common cause of post-upgrade ranking drops that agencies attribute to "algorithm changes."
We Crawled Every URL Before Writing a Single Line of Upgrade Code
Our pre-upgrade SEO audit took 5 days and produced a complete map of every URL on the site — its current status, its indexed state in Google Search Console, its position data from Google Search Console API, and its redirect chain history. 4,800 URLs audited. 1,240 active redirect chains documented. 14 SEO-impacting extensions reviewed.
The audit identified 3 specific risks that would have caused ranking drops if unaddressed — risks that would not have been caught by a standard Magento upgrade process.
| URL Category | Count | SEO Risk | Treatment |
|---|---|---|---|
| Active product URLs (indexed) | 2,840 | Canonical tag migration | Preserved identical |
| Active category URLs (indexed) | 312 | URL suffix change in 2.4.7 | Suffix locked via config |
| CMS page URLs (indexed) | 186 | Meta data migration | Meta migrated + verified |
| Legacy 301 redirect chains | 1,240 | URL rewrite engine change in 2.4.7 | Rebuilt in new format |
| Discontinued product URLs | 142 | Soft 404s sending wrong signals | 301 to category parents |
| Pagination URLs (?p=2 etc) | 80 | Canonical misconfiguration risk | Canonical verified |
| New URLs added post-upgrade | — | Sitemap submission timing | Sitemap submitted day 1 |
The most critical finding: 142 discontinued product URLs were returning soft 404 responses (200 status code with "product not found" content) rather than proper 301 redirects to category pages. Google was treating these as live pages with thin content. Cleaning these up before the upgrade — redirecting them to appropriate category parents — removed 142 pieces of dilutive content and likely contributed to the post-launch traffic increase.
The 6-Phase SEO-Safe Upgrade Process
Phase 1: Full SEO baseline capture
Crawled all 4,800 URLs using Screaming Frog. Exported complete position data from Google Search Console API — capturing every keyword, URL, and position. Set up a rank tracking project monitoring 340 target keywords. This baseline was the measuring stick for everything that followed — we would know within 48 hours of launch if any position moved.
📋 4,800 URLs crawled · 340 positions tracked · Full GSC exportPhase 2: URL rewrite migration for Magento 2.4.7+ engine
Rebuilt all 1,240 legacy redirect chains in the format required by the updated URL rewrite engine in Magento 2.4.7+. This involved writing a custom migration script that read the existing url_rewrite table, transformed the entries to the new format, and verified each redirect returned the correct 301 status under load. Tested every redirect chain with curl requests at 50 concurrent connections — exactly replicating the condition under which the URL rewrite engine change causes failures.
🔗 1,240 redirects rebuilt and load-tested · Zero failuresPhase 3: Meta data migration and canonical audit
Exported all meta titles, descriptions, and canonical tags from the existing store. After upgrade on staging, verified every URL returned the correct meta data. Found 23 CMS pages where the upgrade had reset meta descriptions to blank — corrected before go-live. Verified all canonical tags were pointing to the correct URLs, paying particular attention to pagination canonicals which are commonly misconfigured post-upgrade.
📝 All 4,800 meta records verified · 23 blank descriptions correctedPhase 4: Core Web Vitals optimisation (the SEO bonus)
Since we were already in the store, we added a performance optimisation pass — configuring Varnish full-page cache, converting product images to WebP, and fixing the CLS score caused by unresized images. Mobile PageSpeed score moved from 54 to 88. This was not part of the original brief but we presented it as a deliverable — knowing that improved CWV scores directly influence Google rankings for mobile queries, which represent 71% of this store's search traffic.
⚡ Mobile PageSpeed 54 → 88 · CWV: all passingPhase 5: Soft 404 cleanup before launch
Implemented 301 redirects for all 142 discontinued product URLs — directing them to the most relevant parent category based on product type. This removed 142 thin-content signals from Google's index of the site. We told the client this would likely improve rankings for the parent category pages within 4-6 weeks as Google recrawled and consolidated the link equity from the old product URLs.
🧹 142 soft 404s → proper 301 redirects · Link equity consolidatedPhase 6: Go-live protocol + 30-day monitoring
Deployed Sunday 3am AEST. Immediately post-launch: ran full crawl to verify redirect responses, submitted updated XML sitemap to Google Search Console, pinged Bing Webmaster Tools, and verified Search Console showed no coverage errors. Set up 30-day daily rank tracking — checking 340 positions every morning. By day 3, Google had begun recrawling and all 340 tracked positions were holding or improving.
✅ Sitemap submitted within 1 hr · All 340 positions confirmed day 3What Happened to Rankings and Traffic — Week by Week
We tracked 340 keyword positions daily for 8 weeks post-launch. The pattern was consistent: zero losses in the first 72 hours (confirming the redirect migration was clean), gradual improvement from week 2 as Google recrawled and registered the improved Core Web Vitals, and a sustained organic traffic increase from week 4 driven by the soft 404 cleanup and CWV improvements.
📈 Organic Search Traffic — 8 Weeks Post-Launch
Weekly organic sessions vs. pre-upgrade 8-week average baseline
📈 Full Impact Summary — 8 Weeks Post Go-Live
What Every Store Owner Should Know Before Upgrading Magento
The URL rewrite engine changed in 2.4.7 — and most agencies don't know
Magento's URL rewrite format change in 2.4.7 silently breaks legacy 301 chains for stores upgrading from 2.4.4 or earlier. It doesn't throw errors. Redirects appear to work in testing. They fail under production load. This is the most common undiscovered cause of post-upgrade ranking drops.
A pre-upgrade SEO audit almost always finds quick wins
The 142 soft 404s in this store had been quietly diluting domain authority for years. The upgrade gave us a reason to audit — and fixing them added more ranking improvement than the upgrade itself. Every pre-upgrade audit we've run has found similar issues.
Core Web Vitals improvements are SEO improvements
The mobile PageSpeed improvement from 54 to 88 wasn't in the original brief — but it drove 34% of the post-launch traffic increase. Google's Page Experience signals directly influence rankings. Performance work and SEO work are the same thing.
Sitemap submission timing matters
Submitting the updated XML sitemap within 1 hour of go-live — while Google's crawlers were already active from the traffic the site was receiving — meant Google began recrawling immediately. Waiting days to submit adds unnecessary delay to ranking recovery and improvement.