
A $100m global ecommerce brand rebranded and replatformed. By May, the number of keywords ranking in Google's top 3 had fallen 69% and estimated organic traffic was down 72%. @audits was brought in to review the migration and help with the brand's longer-term ecommerce SEO strategy. As part of the investigation, we connected the site to @Saliencecom to see what was happening when Googlebot and other crawlers visited. A few things stood out: - Googlebot was fetching robots.txt around 5x more often than on a sister site. - Googlebot crawl activity had halved in a month, while the sister site was being crawled 6.6x as often. - 16.6% of requests were being rate limited (429), including roughly 1 in 5 homepage requests from clients identifying as Googlebot. - Some important pages were returning 404s, while paginated category URLs were switching between 200 and 404 responses. - AI crawlers making 1.8x more requests than Googlebot. The logs helped us identify the symptoms, but we needed Google Search Console and live header checks to understand what was causing them. That uncovered two issues: - An A/B test was assigning Googlebot to different variants across crawls. - robots.txt and the sitemap were being served uncached from a legacy backend, which was also setting three session cookies on every request. The recommendations were fairly straightforward: bypass the A/B test for crawlers and serve robots.txt and the sitemap from the edge cache. Six weeks after the first fixes in late May, keywords ranking in the top 3 were up 182% on the May low and estimated organic traffic had doubled. The biggest jump came in August, about 11 weeks after the fixes. Since the May low, according to Ahrefs US data: - Keywords ranking in Google's top 3 are up 28x. - Keywords ranking in Google's top 10 are up 52x. - Estimated organic traffic is up 9x. Anyone who's worked on recovering a failed migration will know how long it can take Google to catch up, particularly when the problems have been around for months. For me, the most useful part of combining Salience's server log data with Search Console was having enough evidence to explain what was happening, justify the recommendations and get the client's development resources allocated to fixing them. That can often be the hardest part. We've since built checks for all issues discovered into Salience and tested them against the site's logs. A lot of what we build comes from real SEO projects like this, with the aim of making this level of analysis and monitoring accessible to everyone.













