GeotargetingStories, WebkickLocalStories, Astria: Local Discover explained

Google Discover's Layer 4 handles the local and geographic dimension. It's composed of 3 pipelines with very different logics: geotargetingstories, webkicklocalstories and astria. Combined, they account for only ~4% of the French feed volume — but they are existential for regional press and largely under-exploited by national publishers. Here's the 1492.vision data describing them, and how to activate each.

Why call it "Layer 4" and not just "local"

When publishers talk about "local Discover," most imagine a single mechanism. The reality is more subtle: Google Discover handles local via three pipelines with radically different logics, identified by 1492.vision in its 42-million-card analysis. Each has its own function, its own dominant-domains profile, and its own exclusivity level.

This architecture sits within the broader chain of Discover's 20+ pipelines. Layer 4 comes after Layer 1 (Content, Moonstone, Aura) and complements distribution with the geographic filter. Its precise internal function isn't documented by Google — but behavioral observation reveals behaviors distinct enough to be exploitable.

geotargetingstories — mainstream content filtered by geolocation (4.5% FR reach)

The first pipeline, geotargetingstories, takes "mainstream" national/regional content and serves it to users based on their geolocation. It's the pipeline of "mainstream content with a local angle".

FR figures (1492.vision)

• FR reach: 4.5% (share of devices seeing these URLs/day in the targeted area)
• Type: mainstream content filtered by user geolocation
• Target profile: national publishers adapting content by region, and regional publishers expanding to a national angle

How to activate it

The main lever is naming precise geographic entities (cities, metropolises, regions, departments) in the title or first paragraphs. An article mentioning "Lyon, Marseille, Bordeaux" will be compared against one mentioning "several major cities." The first activates Knowledge Graph geographic entity resolution; the second flies under the radar.

Failure signature: your article names a single city and stays confined to its strict geographic zone, without penetrating the comparable metropolises where the topic is equally relevant.

webkicklocalstories — the existential highway of regional press (1.8% reach, 67% exclusive URLs)

The second pipeline, webkicklocalstories, is the most singular in Layer 4. Its reach is the lowest of all Discover pipelines (1.8% in FR) — but that's an architectural choice, not a signal of weakness: the content is geographically targeted, so only users in the relevant area see it.

FR figures (1492.vision)

• FR reach: 1.8% (the lowest of all pipelines)
• FR volume: 0.8%
• Median age: 4.8 hours
• Co-occurrence with content: only 33% → 67% exclusive URLs
• Dominant domains: actu.fr (11.0%), Sud Ouest (9.7%), Ouest-France (8.6%), France Bleu (7.8%), Le Dauphiné (4.2%)
• No national title in the top 10

The "impossible to bypass" pipeline for regional press

For regional press, this pipeline is existential. Without webkicklocalstories, two-thirds of regional media content simply wouldn't exist in Discover. It's the only entry door for hyperlocal content that isn't meant for a national audience.

Overrepresented keywords map France's local geography: municipales, mayor, commune, elections, and department names (Loire, Vosges, Rhône, Moselle). The topical profile is clear: proximity news, municipal life, local human-interest stories.

How to activate it (for a national publisher)

If you're a national publisher, you can try to activate webkicklocalstories by adding a strong local angle to your articles. Attested example from the DiscoReady guide:

Before: "The new real estate tax reform"
After: "These 5 French cities where the new real estate reform changes the game most"

Naming 5 specific cities activates geographic entity resolution and can open the door to local/geo pipelines. Caveat though: webkicklocalstories remains heavily dominated by entrenched regional press — a national title will never sustainably enter it.

astria — local authority lifestyle with +1.5-day delay (4.6% reach)

The third pipeline, astria, has the most atypical temporal signature in all of Layer 4. It holds articles 1 to 3 days before pushing them into the feed — median 1.5 days. No other Discover pipeline shows this behavior.

FR figures (1492.vision)

• FR reach: 4.6%
• Publication delay: +1.5-day median (holds 1-3 days before push)
• Topical profile: local authority + long-life lifestyle — horse racing, astrology, wine, cultural events

Why this delay?

Astria's precise internal function isn't documented by Google. The most consistent hypothesis with observations is that this pipeline filters long-life content — pieces that stay relevant 2-3 days after publication. Astria holds them long enough to validate they aren't just "hot" for 24h, then distributes them to an audience consuming this type of content at a slower rhythm.

For a lifestyle / leisure / culture publisher, astria is an opportunity: no freshness race, no pressure on exact publication timing. Content can "mature" 24-36h before reaching its audience.

The asymmetry between the 3 local pipelines

The 3 Layer 4 pipelines don't target the same publishers or the same content. Here's the reading grid:

• You're a national publisher wanting to reach specific regions → target geotargetingstories. Lever: naming precise geographic entities.
• You're regional press → you're already in webkicklocalstories. Lock in your local keywords (departments, municipales, mayor) and publish fast (4.8h median age).
• You're a lifestyle / leisure / culture / wine / horse-racing publisher → target astria. Don't rush; publish when the article is solid. The 1.5-day delay is an asset, not a handicap.

Layer 4 is under-exploited because its logic is specialized by publisher profile, not universal. But whoever positions there picks up ~4% of FR volume that flies under the radar of generic "Discover" strategies.

The 2 cross-pipeline activation tactics

Tactic 1 — Add a national angle to local content

Activates geotargetingstories and potentially moonstone.

Before: "Rennes: new tram schedules in effect"
After: "Rennes follows Paris: the new tram schedule model spreading to metropolises"

Adding the national comparative angle opens distribution to other comparable metropolises (geotargetingstories) and boosts engagement through comparison (moonstone — see our Content, Moonstone, Aura article).

Tactic 2 — Add a local angle to national content

Activates webkicklocalstories and astria.

Before: "The new real estate tax reform"
After: "These 5 French cities where the new real estate reform changes the game most"

Naming 5 specific cities activates Knowledge Graph geographic entity resolution and can open local pipeline doors.

The under-known accelerator: expired domains with active GMB listing

For a new publisher wanting to activate Layer 4 quickly, the purchase of an expired domain with an active Google My Business listing is the most documented accelerator (source: DiscoReady guide). An active GMB listing carries signals directly exploited by local pipelines:

• A physical location validated by Google
• Customer reviews (sometimes hundreds)
• Business seniority
• Inbound links to the site from the listing
• A Google Maps connection and its entity ecosystem

Per the DiscoReady guide, these signals can trigger webkicklocalstories in 4-6 weeks instead of 6-12 months for a new site without geographic anchoring. The angle is under-exploited because it requires crossing two markets (expired domains + GMB listings), but specialized marketplaces exist.

Action plan — activating Layer 4 per your profile

1. Audit your current pipeline profile via Search Console > Performance > Discover. If your "local" articles perform geographically (traffic concentrated in specific regions), webkicklocalstories is probably already active.
2. Lock in geographic entity resolution. Name cities, departments, metropolises precisely in titles and first paragraphs. Our Profiler helps verify your site itself is a recognized Knowledge Graph entity.
3. If you're a national publisher, systematically apply Tactic 2 to 30% of your news articles — the fastest way to open webkicklocalstories without abandoning your national editorial line.
4. If you're a lifestyle / leisure publisher, don't force freshness. Astria rewards depth and longevity, not speed. Bet on editorial quality and the natural 1.5-day delay works for you.

Conclusion

Discover's Layer 4 isn't the biggest or the most glamorous. It accounts for ~4% of FR volume. But it's structural for certain publisher profiles (regional press, long-life lifestyle) and under-exploited by others (national publishers ignoring the local dimension of their content). The 3 pipelines — geotargetingstories, webkicklocalstories, astria — each have their own logic, and the strategy that works is targeting the one matching your profile, not trying to activate them all at once.

Sources

• 1492.vision — Sylvain Deauré & Damien Andell: primary source for FR figures (reach, volume, median age, dominant domains, overrepresented keywords) — analysis of 42M Discover cards Dec 2025 - Feb 2026
• Metehan Yesilyurt — metehan.ai: Google App SDK decompilation (87,498 Java classes), independent validation of pipeline names observed by 1492.vision
• SearchEngineLand — Inside Google Discover: 20 pipelines, 42 million cards: public relay of the 1492.vision analysis (aggregated all-language figures)
• DiscoReady Premium Edition 2026 Guide — activation tactics, GMB accelerator, use cases per publisher profile

Frequently asked questions