Google Discover Traffic: A Guide for YouTube Publishers

If you want more Google Discover traffic and more visits from YouTube, start with one fact from Google's own documentation: nothing special is required to be eligible for Discover. A page that is indexed and follows the Discover content policies is automatically eligible, and eligibility does not guarantee that anything will show up. YouTube works differently. People type a query or accept a recommendation, and the title, description and thumbnail do the persuading. A publisher can serve both audiences with one editorial plan, as long as the video and the written page cover the same subject and point to each other.

This guide is for people who run a blog, a news site or a brand site. For the mechanics of ranking a video itself, the separate video SEO and YouTube guide goes deeper; here the question is how the two surfaces fit into one traffic plan.

Why Discover and YouTube reward different habits

Publishers often treat Discover and YouTube as two versions of the same thing, a feed that rewards frequent posting. The documentation describes something more specific for each.

What Google says Discover is

According to the Discover documentation (Opens in a new tab), Discover is part of Google Search that shows people content based on their interests and their Web and App Activity. It can draw on many of the same signals and systems as Search. The page states that no special tags or structured data are required, that older content can appear if it is helpful and relevant to someone's interests, and that policy violations can lead to Discover manual actions, which appear in Search Console. It also says traffic from Discover is less predictable than keyword driven Search traffic and should be treated as supplemental.

The habit this rewards is editorial rather than technical: choose subjects people care about, tell them well, and present them honestly. The documentation names timeliness, good storytelling and unique insight as qualities worth aiming for, and it warns against clickbait, exaggerated previews and withholding crucial information.

What YouTube asks of a video page

On YouTube the habits are different. The Help Center page on video description tips (Opens in a new tab) says a description can run to 5000 characters, that keywords can help viewers find the video through search, and that the first few lines matter because they are what viewers see first. It recommends one or two core terms in both title and description, a unique description for every video, credits for collaborators, chapters for longer videos and links to related playlists. It also suggests checking the report that shows how viewers find your video.

None of this promises a ranking. It describes ways to make a video easier to find and easier to understand, and the right reading is as a checklist, not a formula.

Discover versus YouTube at a glance

A decision rule for the first quarter

The question of simultaneous versus sequential investment can be settled with four tests, applied in order.

1. If you publish text weekly and have no video, make the page meet the Discover minimums first. Add video only for the two or three topics that already draw readers.
2. If you already publish video on a schedule, open a companion page for each upload before you invest in anything new. The marginal cost is small because the topic is already researched.
3. If you have both and no reporting, set up reporting before touching anything else. Without it you cannot tell which surface helped.
4. If you have both and reporting, feed the stronger surface and run presentation tests on the weaker one: headline, cover image, description opening.

The logic behind this order is that Discover rewards habits you apply to every page, such as the image standard, while video demands fresh production each time. Cheap, repeatable work goes first, and expensive, topic specific work goes where the evidence already points.

Pairing a video with a written page on the same topic

A video and a page about the same subject can either duplicate each other or complement each other. Complementing is the goal, and it needs planning before either is produced.

Dividing the work between the formats

Video is good at showing: a procedure, a product in use, a conversation. A page is good at being scanned and searched: definitions, comparison tables, sources, current numbers. Resist the urge to paste a transcript into the page. Instead, put detail that would slow the video into the page, and keep demonstrations that are awkward to describe in the video.

Example scenario: a garden tools retailer runs a blog and a channel. For a topic like sharpening pruning shears, the video shows the angle and the motion. The page holds a table matching blade types to sharpening methods, a short list of mistakes, and the embedded video near the top. The description links to the page, and the page links to the channel playlist on the topic.

Embedding the video and marking it up

Google's video structured data documentation (Opens in a new tab) lists name, thumbnailUrl and uploadDate as required VideoObject properties. Each video needs unique text in name, a thumbnail unique to that video, and an ISO 8601 upload date, ideally with a timezone. The documentation recommends contentUrl so Google can fetch the video file, with embedUrl as the alternative when no file URL exists, and it says not to point contentUrl at the page where the video lives.

General structured data policies add that markup must describe content visible on the page, so adding VideoObject to a page that does not show the video breaks the rules. The video page also notes that markup outside the guidelines may lead to a manual action, and valid markup only makes a page eligible for a feature; it does not guarantee that the feature will appear.

Keeping description and page distinct

Copying the same paragraphs into both places is the easy path and the weak one. The Help Center recommends a unique description for each video, and the same spirit applies to the page. A workable split:

• The description carries a one or two line summary, the page link, chapters, credits and playlist links.
• The page carries context, sources, tables, dated notes and links to related articles.
• Both use the same vocabulary for the topic, but neither repeats the other's sentences.

Which element lives where

Building a topic cluster around one video

A single pairing is a start. A small cluster is better: one main video with its main page, two or three short pages on sub questions, and a playlist that holds the short videos. Link the sub pages to the main page and back. Because each page has its own headline and image, each is a separate candidate for the Discover feed, and none is a duplicate of another.

Example scenario: a travel site covers a coastal hiking route. The main page and video describe the route as a whole. Sub pages cover footwear choices, seasonal considerations and getting there without a car. Each has its own cover image and each links back to the route page.

Image and editorial minimums for Discover

The Discover documentation is specific about images and content. Treat the following as a pre-publication filter, and check the live page for changes, because limits and wording in Google's documentation can change.

Editorial rules in plain terms

Headlines should capture the essence of the content. Avoid clickbait, misleading or exaggerated previews, and withholding crucial information. Avoid sensationalism aimed at morbid curiosity, titillation or outrage. The documentation says Discover may not recommend job applications, petitions, forms, code repositories or unframed satire, and that SafeSearch filtering removes content seen as shocking or unexpected.

The helpful content guidance (Opens in a new tab) reinforces the point from another angle. It asks why a page exists, and it treats summarising others' work without adding value, chasing trends your audience does not care about and changing dates without substantive updates as warning signs. These are not Discover-only rules, but they describe the kind of page a feed should be willing to show.

The honesty test for headlines

A practical test: after someone opens the page, does the headline's promise hold? A line such as "Three mistakes that dull your shears" works if the page lists mistakes and explains them. It fails if the page is a product listing. When the answer is no, rewrite the headline or the page, not the image.

Image requirements from the documentation

The documentation asks for images at least 1200 px wide, with more than 300,000 total pixels (its example is 1280x720, or 921,600 pixels), in a 16:9 ratio. Large previews are enabled with the max-image-preview:large robots setting or by using AMP. When you crop manually, important details should survive the landscape crop and the preferred image should be specified with og:image or schema.org markup. Generic images such as a logo, and text-heavy images, are discouraged.

If you need more on how images behave in Google Images, the guide on optimizing images for Google covers file names, alt text and formats. For Discover the main point is simpler: the lead image should explain the story at a glance and survive a wide crop.

Related structured data guidance

Google's general structured data policies say images named in markup must be relevant to the page and that image URLs must be crawlable and indexable. A cover image that sits behind a login or a robots.txt block undermines that.

Final check before you hit publish

• Is the page indexed and reachable at its own URL?
• Does the headline describe what the page actually delivers?
• Is the lead image at least 1200 px wide and relevant?
• Does the robots meta tag include max-image-preview:large, and does no other rule restrict it?
• Does the page read cleanly on a phone within the first seconds?
• If a video is embedded, do the thumbnail and markup match what visitors see?

Past mistakes worth avoiding

Three recurring mistakes show up in publisher workflows. First, reusing a small social media image as the lead image, which can fall below the width the documentation asks for. Second, embedding the video at the very bottom of the page and never mentioning it in the headline or intro, so readers and systems do not connect the two. Third, writing one generic description template for every upload, which cuts against the Help Center's advice on unique descriptions. Fix the image standard first, the headline discipline second and the video links last, because the first two affect every page while the third only affects pages that have a video.

For publishers who also place sponsored articles, expectations for sponsored content in Discover are covered in a separate guide.

Connecting channel, site and reporting

Choosing where to invest requires a way to see results. The setup below keeps reporting simple enough for a small team.

Discover reporting in Search Console

The Discover report shows impressions, clicks and average CTR for your content. The documentation says it covers the last 16 months and appears once your property reaches a minimum number of Discover impressions; the number is not published. It includes Chrome traffic and tracks Discover traffic across surfaces. To understand queries and pages in the standard report, see the walkthrough on the Search Console performance report.

YouTube side reporting

YouTube Analytics shows how viewers find a video, including search terms. The Help Center suggests using that data when you refine descriptions. Menu names inside YouTube Studio may vary with account language, so if your interface is set to another language, labels can look different from the English names used here.

Tracking visits from channel to site

Put a consistent tagging pattern on every page link in descriptions, so your site analytics can show how many visits came from the channel. The exact tool is outside this guide, but the rule is short: one address per video, one tagging format everywhere.

How often to look

Daily checks mislead on a surface that Google describes as less predictable. Weekly or monthly views are more honest. The Discover documentation lists changing user interests, shifts in content types and Search updates among causes of traffic change, and says some shifts are unrelated to content quality or posting frequency. Judge a topic over three or four weeks before changing the approach.

When to change direction

Use this rule: if a topic is weak on both surfaces for two consecutive four week periods, change the subject or its presentation. If it is weak on only one, keep feeding the strong surface and test headline, cover image or description opening on the weak one. If it is strong on both, add sub topics. The rule has no numeric thresholds on purpose, because the right level depends on your site's own history.

A 30 day rollout plan

The plan fits a small team and aims at a durable routine rather than a quick spike. Timings describe working rhythm, not expected results.

Days 1 to 7: baseline

Review the last five published pages for image width, robots meta and index status. Check whether the Discover report opens in Search Console and note it if the property has not reached the threshold. Review the last five video descriptions: do the first lines state the topic, is the page linked, is each description unique?

Days 8 to 14: pair topics

List videos and pages in one table. Mark topics with video but no page and topics with a page but no video. Choose the two topics with the most reader interest and plan the missing format for each.

Days 15 to 21: produce and link

For the two chosen topics, link video and page both ways. Write a unique description, embed the video, add VideoObject markup if the page shows the video, and prepare a cover image of at least 1200 px with the important detail inside a landscape crop.

Days 22 to 30: measure and decide

Compare Discover and YouTube data, channel to site visits and the page's own analytics. Write down which surface seemed to respond and which format to prioritise next month. If the evidence is unclear, repeat the routine for another month.

If the plan underperforms

There are three likely reasons. The topics may not interest the audience, the headline and image may promise something the page does not deliver, or the period may simply be too short to reveal a pattern. The first two are in the publisher's hands; the third requires patience. Record each presentation change separately so you can tell which change mattered.

Roles on a small team

Even three people need clear roles. The editor checks that headlines keep their promise. The designer checks size, crop and licence of the lead image. The video owner writes the description, adds chapters and places the page link. On a one person team, one checklist run before each publication replaces the roles and costs far less than fixing mistakes afterwards.

Related guides: How to Read the Google Discover Performance Report, Large Images for Google Discover, YouTube Video Descriptions and Chapters: Writing Guide.

Conclusion

Discover and YouTube work on different logic. One recommends content from interests, the other helps people who search or accept suggestions. A video and a page that support each other give you a chance on both surfaces, though Google guarantees neither. Meet the Discover minimums first, which are an indexed page, an honest headline, a lead image of at least 1200 px wide and permission for large previews. Then pair the video with the page, set up reporting, and decide each month from evidence.

If you need editorial placement to support a publishing plan, you can look at our guest post service.

Frequently Asked Questions

Do I need special markup to appear in Discover?

According to Google's Discover documentation, no special tags or structured data are required. Content that is indexed and follows the Discover content policies is automatically eligible, but eligibility does not guarantee that it will appear.

How large should a Discover image be?

The documentation asks for at least 1200 px width and more than 300,000 total pixels, using 1280x720 as an example. Large previews need the max-image-preview:large setting or AMP. These numbers can change, so check the current page before you apply them.

Will my YouTube video show up in Discover?

The Discover report includes a Videos appearance type, but the documentation does not give a condition that guarantees any video will appear. A page that embeds the video and marks it up correctly is still a sound foundation.

Can I reuse the same text in the video description and on the page?

It is better to separate them. The YouTube Help Center advises a unique description for each video, and the page should add context, tables and sources beyond the video.

What should I do if Discover traffic drops for a week?

Google describes Discover traffic as less predictable than Search traffic and says some changes have nothing to do with quality. Look at weekly and monthly trends before changing strategy.

Why can't I see the Discover report?

The report appears once the property reaches a minimum number of Discover impressions. The documentation does not publish the number. A missing report does not mean your content is poor; the threshold has not been reached.