How to Write Articles for Google Discover: 7 Officially Supported Practices

You may have solid search rankings and still see little or no traffic from Google Discover. That can make the product feel mysterious: should you rewrite the headline, replace the hero image, or publish more often? Discover does not wait for a person to enter a query. It proactively recommends content according to individual interests, so conventional keyword optimization alone cannot make its results predictable.

The short answer is that there is no article template, application process, or hidden setting that guarantees a Discover appearance. You can, however, build the right foundation. Google recommends useful and original people-first content, accurate headlines, compelling large images, and a good overall page experience.

This guide turns those official recommendations into seven practical steps, from checking eligibility to learning from published work. The goal is not to manufacture a guaranteed spike. It is to make every article a credible candidate and a satisfying read when the right audience encounters it.

1. Separate eligibility from guaranteed distribution

According to Google Search Central’s official Discover guide, content is automatically eligible when Google has indexed it and it complies with Discover’s content policies. You do not need a Discover-specific tag, special structured data, or a separate submission.

Eligibility does not mean that a page will appear. Discover selects content according to a person’s interests and activity, so opportunities differ between readers and over time. Even older content can surface when it remains useful and relevant to someone.

Start with the basic technical checks. Use URL Inspection to confirm that Google has indexed the page, make sure you are not blocking crawling or indexing, and review the Discover content policies. If that foundation is broken, headline experiments cannot solve the underlying problem.

This distinction also keeps expectations realistic. “Eligible” is a condition you can verify. “Shown to a particular audience” is an outcome you cannot demand or promise.

2. Plan around the reader’s next decision, not just a trend

Google recommends content that is timely for current interests, tells a story well, or offers unique insights. Merely adding a trending phrase does not create value. Google’s guidance on helpful, reliable, people-first content warns against producing large volumes across unrelated trends primarily for search traffic or summarizing other sources without meaningful added value.

Before drafting, complete this sentence: “After reading this article, the reader will be able to ___.” For a product update, simply restating the announcement is rarely enough. Explain who can use it, what changed, whether the reader needs to change a setting, and what limitations matter.

Add work that saves readers from doing another search. That could be a first-hand comparison, a reproducible test, original photography, a clearly organized procedure, or a careful synthesis of several primary sources. Do not invent personal experience when you have none. A well-supported decision framework can be an original contribution if you distinguish documented facts from your interpretation.

There is also no Google-preferred word count. A complete answer should be as long as the reader’s task requires, without padding the article to reach an arbitrary target.

3. Make the headline interesting and accurate at the same time

Google advises publishers to use titles and headlines that capture the essence of the content. It also warns against misleading or exaggerated preview details in titles, snippets, and images, withholding crucial context, and manipulating curiosity through shock, outrage, or sensationalism.

A useful headline identifies both the subject and the benefit of reading. Instead of “The Shocking New Feature You Can’t Afford to Miss,” try something concrete such as “Three Workflows Changed by the New Feature—and What to Check Before Using It.” Use a number only when the body contains that real organizing structure.

Accuracy does not require a lifeless manual-style label. You can express the question or change the reader genuinely cares about, then give the conclusion, reason, and practical outcome near the beginning. The promise made by the headline, preview image, introduction, and body should remain consistent.

This approach has a tradeoff: an honest headline may look less dramatic than clickbait. The benefit is that it attracts readers with the right expectation and reduces the disappointment caused by a preview that overpromises.

4. Use a relevant 16:9 image at least 1200 pixels wide

Discover is a highly visual surface. Google recommends compelling, high-quality images that represent the article, especially large images that are more likely to generate visits. Its current specifications call for an image that is at least 1200 pixels wide, over 300,000 total pixels, and 16:9.

Enable large previews with max-image-preview:large, then identify the representative image through og:image or schema.org markup. Avoid choosing a generic site logo or a text-heavy graphic as the preferred image.

At thumbnail size, the subject should still be obvious. Keep important details away from unsafe edges because the presentation may involve cropping. Use an image that communicates the actual topic rather than an attractive but unrelated stock scene. If you create several aspect ratios, verify that the landscape version preserves the essential subject.

Large assets also have a cost. Compress them appropriately, use a suitable format, and serve responsive sizes so that visual quality does not create an unnecessarily slow page. A large Discover-ready source image and fast delivery are compatible goals when the implementation is careful.

5. Show authorship, evidence, and honest dates

Readers are less likely to trust a useful-looking article when they cannot tell who wrote it or what supports its claims. Google strongly encourages accurate authorship information and bylines where people would expect them, ideally linking to background about the author. Place primary-source links, test conditions, and the scope of what you verified close to the relevant claims.

Make the publication or update date visible and keep it consistent with structured fields such as datePublished and dateModified. Google’s official byline-date guidance says dates should describe the page’s publication or substantial update, not simply an event mentioned in the story.

Do not change a date merely to make an unchanged article appear fresh. If you materially revise instructions, facts, or conclusions, label the update honestly and make the structured data agree with what readers see.

Authorship and dates are not decorations that repair weak content. Their value is that they let readers judge recency, responsibility, and evidence for themselves.

6. Review the complete mobile experience

Google asks Discover publishers to provide a good overall page experience. Its page experience guidance recommends looking beyond a single metric. Core Web Vitals matter, but so do secure HTTPS delivery, mobile usability, and the absence of excessive ads or intrusive interstitials.

Before publishing, open the article on a real phone or in a realistic mobile view. Confirm that the title, main image, introduction, and conclusion are easy to reach and read. Check whether the hero image pushes the answer too far down, a pop-up covers the body, or cramped controls create accidental taps.

Page experience alone does not guarantee distribution. It does remove avoidable friction after someone becomes interested enough to open the article. Treat content quality and presentation quality as one journey: can the reader reach the promised answer without confusion or interruption?

7. Turn Search Console data into repeatable improvements

After publishing, replace guesswork with measurement. The Discover Performance report in Search Console provides impressions, clicks, and click-through rate, with breakdowns such as page, country, and day. The report appears only after the property reaches a minimum level of Discover impressions, so its absence does not necessarily mean your setup is broken.

Discover traffic is less predictable than keyword-driven Search traffic. Interests change, the types of content shown in the feed evolve, and updates to Google Search can affect distribution. Google recommends treating Discover as supplemental to keyword search traffic rather than a dependable replacement.

Avoid declaring success or failure from one sudden spike or drop. Compare several pages and periods. If impressions rise but CTR stays low, review whether the headline and main image communicate the article clearly without changing the promise. Use your own analytics to consider what happens after the click as well: did readers finish the relevant section or take the intended next step?

Record the date and purpose of meaningful changes. That simple log makes later comparisons more useful, even though outside events and changing interests mean you cannot prove every traffic movement was caused by an edit.

Summary

The practical way to create articles for Google Discover is not to chase a guaranteed hack. First, make the page eligible by ensuring it is indexed and policy-compliant. Then create an original, people-first article that helps a defined reader make a decision or complete an action. Represent it accurately with a clear headline and a relevant large image.

Before publishing, check the 1200-pixel, 16:9 image requirement, max-image-preview:large, authorship, evidence, dates, and the full mobile experience. After publishing, use Discover impressions, clicks, and CTR in Search Console while accepting that feed traffic naturally fluctuates.

For your next article, write one sentence defining who it is for and what that person can decide after reading. Then check whether the title and hero image communicate that same answer honestly.

Standing out in Discover begins less with adding drama and more with editing a timely, useful idea so clearly that the right reader recognizes its value at a glance.