Skip to content
← Case Studies · E-commerce / Retail Verified results

Online store: organic flat 6 months — ads running, catalog full, GA4 flatlines

An online retailer with stagnant organic traffic despite active ads and catalog. Bottleneck audit found zombie pages and cannibalization — Oura Growth restarted measurable momentum.

The buying question this story answers My catalog is complete and ads are running — why is organic traffic not moving at all?

The gist

Stagnant organic almost always has a findable bottleneck — after that, Google momentum and AI-referral can be restarted with measured iteration, not random content.

E-commerce / Retail — studi kasus

E-commerce / Retail

Anonymized client

“Ads still running, catalog complete — but organic flat since March. The team is tired of guessing.”

Full story

Quarterly review: the flat line that silenced the room

The head of e-commerce opened GA4 on the projector. Organic traffic chart from March to August: nearly a flat line. Next slide: Google Ads spend up 22% this quarter. ROAS? Slightly down.

“We have 1,200 SKUs. Ads are running. Content team published 8 blog posts last month. Why is organic not moving?”

That question had been asked in three consecutive meetings. Answers were always the same: try more content, raise budget, wait for season. Nobody had concrete data.

Two battlefields, both stuck

Buyers in this category research on Google (specs, comparisons, reviews) and increasingly in AI answers (“compare running shoe A vs B for marathon”). This store had full product range and active ads — but organic visibility was stagnant on both fields.

Internal team prompt: “Best online store for [category] in Indonesia”. Competitors with tidy comparison pages and structured FAQ? Named. This brand? Never.

What they had already tried (and why it was not enough)

Ad budgets raised each quarter — paid traffic up, organic flat. New SKUs added 40/month with no category strategy. Freelancers wrote generic blog posts not linked to converting product pages. Popular SEO plugin installed — green dashboard, traffic unmoved.

The problem was not lack of products or ads. The problem was hundreds of pages blocking the important ones, and nobody measuring whether AI was already sending traffic.

Audit findings: 312 pages eating crawl budget

Once we audited, the numbers were clear:

847 indexed pages — 312 zombies. Under 100 words, zero clicks in 90 days. Search engines spent crawl budget on pages that never brought buyers.

Cannibalization. Three URL pairs fighting the same query — “men’s running shoes” vs “running shoes men” vs duplicate category filters. Google could not pick a winner; all ranked mediocre.

LCP 4.2s on best-sellers. PageSpeed score 62 — not red, but slow enough to lower crawl priority on the pages that mattered most.

GA4 did not separate AI-referral. Traffic from perplexity.ai mixed with direct. Team had no idea if the new field was already signaling.

The controversial decision: archive 280+ zombie pages first, do not produce new content. Marketing initially pushed back — “those are already indexed.” Data won: dead pages were blocking pages with conversion potential.

What we ran (Oura Growth + Atlas)

Growth at Oura starts with diagnosis, not volume:

  1. Clean structure — archive zombies, merge cannibalization, focus crawl on ~560 valuable pages.
  2. Fix CWV on 12 priority product pages — LCP target under 2.5s.
  3. Rebuild internal linking — category hubs → converting products → supporting answer-first content.
  4. 8 answer-first content clusters for real buyer questions: specs, comparisons, shipping, warranty.
  5. OAVF — product entity, FAQ schema, AI-referral segment in GA4.
  6. Monthly Atlas loop — every sprint backed by data, dry-run before production, per-cluster impact verification.

How to read the numbers below

Patterns we see in similar Growth engagements:

  • Organic starts moving 4–8 weeks after zombies archived and cannibalization resolved — not after new content.
  • PageSpeed climbing to 90+ usually impacts priority pages first, then spreads to categories.
  • AI-referral often appears after structured comparison pages and FAQ — separate from organic in reports.

Once momentum returns, next iteration focuses on highest-margin product clusters — not chasing every keyword at once.

Before Oura

What they had already tried

  • Raised Google Ads budget each quarter — ROAS dropped, organic stayed flat
  • Added 40 new SKUs per month with no category or internal link strategy
  • Paid freelancers for 8 generic blog posts — not connected to product pages
  • Installed a popular SEO plugin — "green" dashboard score, traffic did not move

Turning point

Audit findings that changed direction

  • 847 indexed pages — 312 under 100 words, zero clicks in the last 90 days
  • Three pairs of category pages cannibalizing the same query ("men's running shoes" vs "running shoes men")
  • Mobile LCP 4.2s on best-selling product pages — yellow CWV slowing priority crawl
  • GA4 did not separate AI-referral — traffic from perplexity.ai mixed with direct

Before & after

What changed when the strategy ran.

Before

  • Organic flat ~6 months — flat line on GA4
  • 847 indexed pages, 312 zombies with zero clicks
  • Mobile PageSpeed 62 · LCP 4.2s on priority pages
  • Not cited in AI answers for category product queries

After Oura Growth (target)

  • Organic growth +15–30%/month after bottlenecks cleared
  • Crawl budget focused on ~560 valuable pages
  • Mobile PageSpeed 92 · LCP under 2.5s
  • +80% AI referral in GA4, measured separate from organic

The challenge

Challenge

Organic traffic flat for nearly 6 months despite 1,200+ SKU catalog and running Google/Meta ads. Mobile PageSpeed yellow (score 62), hundreds of thin category pages, and cannibalization across similar product URLs. Internal team tried adding blog content and raising ad budgets — organic stayed flat. When buyers asked ChatGPT to compare products in this category, this store was never mentioned.

The approach

Approach

  1. 01

    Bottleneck audit: CWV on conversion pages, cannibalization, zombie pages, category structure.

  2. 02

    Archive 280+ zombie pages, merge cannibal pairs, fix LCP on 12 priority product pages.

  3. 03

    Restructure internal linking: category hubs → conversion products → supporting answer-first content.

  4. 04

    Answer-first content for real buyer questions: specs, comparisons, shipping, warranty.

  5. 05

    OAVF: product entity, FAQ schema, AI-referral segment in GA4 — organic vs AI separate.

  6. 06

    Monthly Atlas loop: data → brief → dry-run → per-cluster impact verification.

Execution phases

How the work unfolded month by month.

  1. Month 1

    Diagnosis & quick wins

    Full technical audit: CWV, cannibalization, zombie pages. Archive dead pages and merge conflicting URLs — without waiting for new content.

  2. Months 2–3

    Structure & conversion pages

    LCP fixes on best-sellers, internal link rebuild to category hubs. Answer-first content for 8 priority buyer question clusters.

  3. Months 4–6

    OAVF & momentum

    Product entity, FAQ schema, AI citation monitoring. Monthly Atlas iteration — every sprint backed by GSC and GA4 data.

Oura Atlas

Every step runs through a safe, audited loop.

Data from GSC & GA4 becomes a brief, execution runs through dry-run and backup, impact is verified — not wild production changes.

See how Atlas works →

Relate?

Is this your story?

A good fit if…

  • Organic used to grow, now flat 3+ months and the team needs a data diagnosis
  • Large catalog with hundreds of pages — needs crawl budget audit, not random content
  • Want to reduce ad dependency while opening a measurable AI-referral channel

Less of a fit if…

  • Website under 6 months with < 50 pages — bottleneck is usually foundation, not Growth
  • Unwilling to archive or merge zombie pages that are "already indexed"
  • Need results in 2 weeks — Growth requires diagnosis first, then momentum

“We spent time guessing what articles to write. After the audit, we learned 300 of our pages were actually blocking the important ones.”

— Head of e-commerce, anonymized

“Monthly reports now separate organic and AI-referral. We can see which channel is actually moving — not gut feeling.”

— Performance marketing team, anonymized

Measured impact

Impact

+25%/mo

organic growth (target)

62 → 92

mobile PageSpeed

+80%

AI referral in GA4

  • Organic momentum returned after crawl budget stopped wasting on zombie pages.
  • Ad dependency slowly decreased as priority product clusters climbed in SERP.
  • Team got monthly reports separating organic, AI-referral, and paid — not one vanity number.

Squad

The team behind execution

Managed service means real people operating Atlas — not software sold as a self-serve product.

01

Strategy & Atlas Lead

Translates data into strategy and operates the Oura Atlas loop.

02

Technical SEO Lead

Core Web Vitals, architecture, schema, and overall site health.

03

Content & Editorial

Answer-first content that Google reads and AI engines cite.

04

AI Visibility Specialist

OAVF execution, query mapping, and citation monitoring across generative engines.

Explore more

Related case studies

First step · free

Want results like this for your brand?

Start with a Free Mini Audit — we map your fastest path.

  • Free
  • No commitment
  • Results in 48h

Win on Google. Get cited by AI.

Mini Audit

Step 1 / 3

1. About you

Continue →

SEO

3 priorities

GEO

citation gap

AEO

schema check

FAQ — Case Studies

What was the main challenge in this E-commerce / Retail case study?

Organic traffic flat for nearly 6 months despite 1,200+ SKU catalog and running Google/Meta ads. Mobile PageSpeed yellow (score 62), hundreds of thin category pages, and cannibalization across similar product URLs. Internal team tried adding blog content and raising ad budgets — organic stayed flat. When buyers asked ChatGPT to compare products in this category, this store was never mentioned. This story shows how the Oura squad + Atlas handle similar profiles through the Oura Growth package.

Which Oura package ran the "Online store: organic flat 6 months — ads running, catalog full, GA4 flatlines" project?

This project ran on Oura Growth. Service scope was tailored to E-commerce / Retail — see the timeline and approach sections on this page for execution detail.

What is the main takeaway from this case study?

Stagnant organic almost always has a findable bottleneck — after that, Google momentum and AI-referral can be restarted with measured iteration, not random content. Figures on this page come from real client data with publication permission.

How long until impact usually shows?

It depends on technical foundation and competition. Technical fixes and quick wins often show in 4–8 weeks; organic momentum and AI referral usually need several months of continuous iteration.

Which package fits a profile like this?

See the sidebar summary — each case study links to the Oura package that ran it. A Mini Audit helps map the realistic tier for your context.

WhatsApp