Sitemaps were timing out.
The logs showed repeated failures when Googlebot requested article sitemaps. Generating them on demand was a likely bottleneck, so we recommended a more reliable cached or static approach.
Publisher SEO case study
Publisher SEO
recovery
Getting organic growth moving again.
Organic traffic had fallen. We helped an entertainment publisher find the technical issues holding it back, work through the fixes and build a stronger base for recovery.
ClientEntertainment publisher · anonymised
FocusCrawlability, indexability & search visibility
ApproachAudit → prioritise → support → validate
The challenge
Plenty of content.
Less traffic coming in.
The publisher had a large archive and kept publishing new articles. But organic traffic had dropped, and we needed to understand whether search engines could reliably reach that content.
We started with a technical SEO audit and server log analysis. Then we worked with the publisher’s development and editorial teams to prioritise the fixes and check what changed after implementation.
Before asking the team to publish more, we needed to make sure search engines could reach what was already there.
The trajectory
Organic search is picking up again.
Recent search performance shows stronger traffic peaks after a quieter period. There is still work ahead, but the direction is encouraging: organic search is moving again.
Organic search: decline, stabilisation and renewed momentum
Illustrative search-click index · synthetic values
Illustrative chart with invented values and simplified timing to protect client data. It reflects the broad trend, not exact results or the isolated impact of our work.
What the technical SEO audit uncovered
First, we checked whether Google could get in.
Crawlers were hitting dead ends.
Broken URLs were receiving crawler requests, and access restrictions needed checking. We reviewed the internal links and crawl rules behind those problems.
The fixes needed to work at scale.
Missing metadata, schema gaps and archive settings affected more than individual articles. We documented changes the teams could make across templates and large groups of pages.
Our approach
Find the problem.
Help fix it.
Check it worked.
We stayed involved after the audit, helping the teams work through the priorities and checking progress.
Look at what Googlebot was actually doing
A crawl tells you a lot, but it does not tell you everything. We checked server logs too, so we could see which URLs Googlebot requested and where those requests failed.
Fix sitemap delivery first
We explained the sitemap failures and the options for fixing them. The publisher’s developers implemented caching. Our follow-up checks found that sitemap delivery and crawl access had improved.
Give each team a practical action list
We reviewed internal linking, broken URLs, metadata, headings, structured data and archive indexation. We also checked News sitemaps and IndexNow submissions. Each finding went into a prioritised action list for the people who could address it.
Check performance without ignoring the ad stack
We investigated loading speed, responsiveness and layout shifts. Some issues came from rendering and third-party advertising scripts. Those needed development work and testing, so we documented the findings rather than calling them solved.
Go back and check the changes
We crawled again and reviewed fresh logs after implementation. That gave us a way to check whether access had improved and identify anything that still needed attention.
The outcome
Better access to content.
A more promising traffic trend.
Improved crawlability and indexability
Follow-up checks showed better sitemap delivery and crawl access. The team had addressed real obstacles we found in the audit.
A recent upward trend in search clicks
Recent search clicks show stronger peaks after the slump. It is an encouraging sign of recovery, and something to keep building on.
Clear priorities for the next stage
The teams had a clear list of technical SEO, structured data and performance priorities, plus support while they worked through them.
AI search visibility as a separate signal
The recent data also shows spikes in AI search visibility. That is worth monitoring alongside ordinary search performance, without treating it as a proven result of the technical changes.
The technical improvements were verified in follow-up checks. Traffic is also influenced by content demand, seasonality and search updates, so we do not attribute every gain to these fixes.
Has your organic traffic dropped?
Let’s look at what could be holding your site back.
Publisher SEO questions
What can other publishers learn?
Where should an organic traffic recovery investigation start?
Start by checking the decline against search performance and technical access. For this engagement, log analysis and sitemap testing revealed actionable issues that needed attention alongside the wider SEO audit.
Why use server log analysis in a technical SEO audit?
Logs show requests made by crawlers, including the URLs reached and the responses returned. In this project, they exposed repeated sitemap failures and helped guide follow-up checks after changes.
Does publisher SEO include Core Web Vitals?
Yes. This review included loading, responsiveness and layout stability. Recommendations considered the publisher’s templates, third-party scripts and ad stack, with some remaining work dependent on development and advertising teams.
Can technical SEO alone explain a traffic recovery?
This case study does not make that claim. Improved crawling is a documented outcome; renewed organic momentum is a separate observation. A stronger attribution claim would require more detailed analysis.
Mauna Growth / SEO for publishers
Let’s find what’s holding
your organic growth back.
Whether your traffic has dropped or you want to grow further, we can help you understand the problems and decide what to tackle first.
Tell us about your website and what you’d like to improve. We’ll get back to you to discuss the next steps.