Google Discover’s “Dive Deeper” Test: A Publisher Playbook

If Google Discover sends you meaningful traffic, the new “Dive deeper” experiment deserves a measurement plan, not a panic rewrite. The AI-powered card can occupy a feed position that might otherwise show publisher content, then answer part of the user’s need before offering links to the web.

Your immediate job is to separate a plausible traffic risk from an observed traffic loss. Establish a Discover baseline, isolate the content most exposed to the test, and make the value of clicking unmistakable. You can do all of that without guessing at an undisclosed ranking factor or inventing a new schema strategy.

What the test changes in the Discover journey

A normal publisher card offers a relatively direct choice: open the content or continue scrolling. “Dive deeper” introduces another route. A person can enter an AI-generated topic overview and then decide whether one of its linked stories, community reactions, or pieces of original reporting deserves another click.

Google describes those destination links as prominent, but prominence doesn’t remove the added decision point. The overview itself may satisfy a casual reader. A publisher also has to win selection among several related resources rather than win the initial feed interaction alone.

That creates three distinct risks for publishers:

• Displacement: the topic card may use feed space that could have carried a publisher’s individual item.
• Intermediation: the user reaches an overview before reaching a publisher, adding another choice between discovery and the site visit.
• Substitution: the generated overview may provide enough context that some people no longer need the underlying coverage.

Those are mechanisms, not measured outcomes. Google is starting the experiment with videos and trying multiple designs. That makes it premature to treat the interface as a completed rollout, assume every Discover user can see it, or attribute every traffic decline to it.

Measure the test without mistaking correlation for cause

A total traffic chart won’t tell you whether “Dive deeper” affected your site. Publishing volume, subject mix, headline quality, seasonality, and changing audience interest can all alter the same line. You need a Discover-specific view and enough page-level detail to identify the shape of the change.

1. Preserve your baseline. Export Discover clicks, impressions, click-through rate, and landing-page performance from Google Search Console. Use a period long enough to show your site’s normal range rather than selecting only a convenient high point.
2. Record editorial context. Annotate major changes in publishing frequency, topic selection, video output, headlines, and distribution. Otherwise, a newsroom decision can look like a platform effect.
3. Separate video-led content. Because the experiment begins with videos, compare pages built around video with the rest of your Discover inventory. Keep the classification consistent; don’t move a page between groups merely because its performance changed.
4. Inspect pages before aggregates. Identify which landing pages lost impressions, which retained exposure but lost clicks, and which continued to convert after the visit. A sitewide average can conceal all three patterns.
5. Connect visits to outcomes. Pair Discover traffic with the action that matters on your site, such as engaged reading, registration, subscription, or revenue. Fewer visits would still be harmful at scale, but a publisher should know whether the remaining visits became more or less valuable.

Use the pattern below as a diagnostic guide, not as proof of exposure to the experiment.

If you cannot identify which users encountered “Dive deeper,” describe any relationship as an association. A decline that begins during a platform experiment is worth investigating, but timing alone doesn’t establish causation.

Give readers a reason to continue beyond the overview

The wrong response is to make content longer or more mysterious. An overview competes most easily with generic coverage that repeats known facts. Your stronger position is content whose useful part cannot be reproduced by a short topic summary.

Google says the expanded experience can link to related stories, community reactions, and original reporting. Treat those labels as clues about the types of destination that can complete a reader’s journey, not as confirmed ranking factors.

• Make the unique asset visible in the headline. Name the interview, analysis, data, demonstration, timeline, local detail, or expert interpretation the reader will receive. A broad topic label gives the overview little reason to send the user onward.
• Put original evidence near the top. If the page contains reporting, show what was learned and how. Don’t bury the differentiating material beneath a generic explanation that an overview can already provide.
• Define the unanswered question. A useful headline and opening should reveal what the short overview cannot settle: why an event happened, what changed, who is affected, how competing claims differ, or what the viewer can verify in the full video.
• Match the promise to the page. A headline that implies original reporting must lead to original reporting. Artificial curiosity may win an occasional click, but it creates a poor destination and weakens the value of being selected.
• Build a useful next step on your own site. Connect the landing page to genuinely related analysis, primary material, or an update path. If Discover supplies a more fragmented entry point, your internal journey has to restore context quickly.

For video-led pages, audit the complete package: title, thumbnail, opening text, video, transcript or summary, and supporting evidence. The page should make clear what the video contributes beyond the surrounding topic overview. Don’t assume that embedding a video makes otherwise generic coverage distinctive.

Do not invent a schema fix for a user-interface test

This is where technical teams can lose time. Google’s disclosed description of “Dive deeper” does not specify a new structured-data type, an opt-in setting, or a publisher control for the feature. There is therefore no responsible basis for promising that a markup change will secure placement or prevent summarization.

Keep existing Article or VideoObject markup accurate when those types properly describe the page. Make sure visible titles, dates, authorship, media, and structured properties agree. That is sound technical hygiene, but it shouldn’t be presented internally as a “Dive deeper optimization.”

Use this decision rule before approving Discover-related technical work:

• If the change repairs inaccurate or inconsistent markup, make it.
• If the change improves how people understand and navigate the page, evaluate it on that merit.
• If the change depends on an undocumented “Dive deeper” signal, hold it until Google provides supporting guidance or your own controlled evidence justifies the work.

Also keep the product distinction clear in reports. “Dive deeper” is an experiment inside Discover; it is not evidence that every Discover card is being replaced, and it should not be casually relabeled as the search results feature commonly called AI Overviews. Blurring those surfaces makes your measurements and recommendations less reliable.

Reduce the business risk before the interface settles

You don’t need to predict the final design to manage the exposure. Start with channel concentration. Calculate how much traffic, engagement, subscription activity, and revenue comes from Discover, then identify the pages and formats responsible for most of that contribution.

Build scenarios from your own historical range rather than borrowing an arbitrary industry percentage. Your baseline scenario can reflect normal variation. A lower-range scenario can show what happens when Discover underperforms without disappearing. A stress scenario can show which editorial products become uneconomic if referral volume contracts materially.

Assign an action to each scenario before traffic moves. That action might be protecting distinctive reporting, changing the volume of generic video coverage, improving conversion on the visits you retain, or accelerating channels you control more directly. Email subscriptions, direct visits, feeds, memberships, and durable search demand won’t reproduce Discover’s feed distribution exactly, but they can reduce the damage caused by dependence on any single interface.

Avoid across-the-board cuts based on one weak reporting period. A narrow decline in commodity coverage calls for a different response from a broad loss of impressions across original work. The first may be a content-positioning problem; the second may justify a larger distribution and revenue review.

Key takeaways

• “Dive deeper” inserts an AI-generated topic overview between parts of the Discover experience and publisher destinations, creating a credible risk of click compression.
• The experiment begins with videos and may use multiple designs, so its current form should not be treated as a settled, universal rollout.
• Track Discover impressions, clicks, CTR, landing pages, content format, and downstream value separately; aggregate traffic alone cannot diagnose the cause.
• Make original evidence and the reason to continue beyond a summary explicit in the headline, opening, and page experience.
• Do not promise a structured-data solution when Google has not identified special markup or a publisher control for the test.
• Model Discover dependency now so your response is based on business impact rather than fear generated by an unfamiliar interface.

Start with a clean export of your current Discover performance. Classify the leading pages as video-led or non-video, note the distinctive value each one offers, and record the editorial conditions behind the baseline. If the interface begins affecting your audience, you will have evidence for a targeted decision instead of a reason to overhaul everything at once.

References

• Search Engine Land – Google testing “Dive deeper” for Google Discover – it’s not good for publishers