the challenge
A LARGE SEARCH LANDSCAPE. LIMITED EDITORIAL CAPACITY.
BETSA works in German construction and renovation, where services, regulations, materials, subsidies and local buyer questions create a wide long tail of search demand. A traditional editorial rhythm could not cover it fast enough. The goal was not to flood Google with generic text, but to build a repeatable publishing system tied to the real business and then judge it by Search Console data.
our solution
A CONTROLLED CONTENT PIPELINE.
Automation handled the repetitive production and publishing loop. Topic rules, business context and search data remained the guardrails.
-
01
MAP DEMAND
We mapped services, locations, regulations and long-tail buyer questions.
-
02
SET RULES
Templates and guardrails tied every article to BETSA's actual offer.
-
03
AUTOMATE
The engine produced and published roughly six articles per day.
-
04
WATCH GSC
We tracked which URLs entered search, earned impressions and moved up.
-
05
MEASURE THE TAIL
After publishing ended, we measured whether the launched pages kept working.
the results
AUTOMATION BUILT THE ASSET. SEARCH KEPT IT WORKING.
1,222WordPress articles published
550 → 2,600Organic clicks in equal 202-day windows
+373%Rounded click growth during publishing versus the equal baseline window
108,067 → 443,531Search impressions in equal 202-day windows
2,216Post-run clicks from the launched-page proxy cohort
311,756Post-run impressions from the launched-page proxy cohort
volume is the mechanism. durable demand is the result.
after the engine stopped
PUBLISHING ENDED. THE COHORT KEPT WORKING.
For January–June 2026 we isolated a launched-page proxy cohort: URLs first seen in Search Console during the publishing run and still visible after it ended. This proxy cohort continued to earn clicks and impressions without the same publishing pace.
2,216Post-run organic clicks from the launched-page proxy cohort
311,756Post-run search impressions from the launched-page proxy cohort
6 moPost-run measurement window
the footnote
WHAT CHANGED
IN THE BUSINESS.
The system published 1,222 articles in 202 days.
- measured period
- Публікації: 2025-06-13–2025-12-31, 202 дні. Порівняння GSC: попередні 202 дні проти 202 днів публікацій. Післядія когорти: 2026-01-01–2026-06-30, 6 місяців.
- fader
- Automation & AI
- source
- public case on grandma.agency, numbers as recorded in the account — no rounding beyond what the label says
who this is for
BEST FOR TEAMS THAT NEED RESULTS.
For businesses with a wide field of search demand that need to systematically cover services, locations, regulations and buyer questions — without publishing every article by hand.
- You have enough real topics and search queries to sustain regular, large-scale content production.
- You want automation to run the repetitive loop while topic rules keep every article tied to your offer.
- You judge output by Search Console data, not article count alone.
timeline
HOW THE SYSTEM WENT LIVE.
- Map demand
Services, locations, regulations and buyer questions were structured before production began.
- Set rules
Templates, topic rules and business context set the guardrails for the publishing loop.
- 202-day publishing run
From 13 June to 31 December 2025, the system published 1,222 WordPress articles.
- Stop & measure
After publishing stopped, Search Console data measured the launched-page proxy cohort from January through June 2026.
asked about this case
Was this a one-off campaign or a system?
A controlled system: topic rules and business context guided production, automation ran the repetitive loop, and results were monitored in Search Console.
Can we get a similar setup for our market?
First we check the volume of real search demand, how well topics fit the business offer, and where human review must stay mandatory.
