Your page can be crawlable, polished and successful in search yet receive little or no Google Discover exposure. The common mistake is treating Discover as another blue-link ranking system. It is a personalized, visual feed with gates that can remove a page or publisher before ranking begins.
That changes how you should diagnose a weak result. First verify eligibility and card integrity. Then examine interest fit, predicted click appeal, freshness and user feedback. This order helps you fix the layer that is actually limiting visibility instead of rewriting content that never reached the ranking stage.
Discover ranking starts after several ways to disappear
Discover uses multiple qualification, matching, ranking, presentation and feedback stages. Ranking is only one part of that pipeline:
- Google crawls and interprets the page.
- It extracts card information such as the title and image.
- It classifies the content, including whether it is breaking, recent or evergreen.
- Eligibility rules and blocks can remove it.
- Remaining candidates are matched with a person’s interests.
- A server-side model predicts the likelihood of a click.
- The feed layout is assembled.
- The selected card is served.
- Interactions and feedback are recorded.
This sequence explains why a ranking-focused edit may accomplish nothing. A missing image, an exclusionary meta tag or a publisher block can stop the page before its title, historical engagement and predicted click-through rate have a chance to compete.
Publisher blocks are especially consequential. When a person chooses not to see content from a publisher, the domain can be removed from that person’s candidate set before interest matching. That is broader than dismissing one URL, although it does not mean the domain is suppressed for every user. No mirror-image domain-wide boost was exposed in the same pipeline.
Start every investigation by distinguishing absence from underperformance. If the page is not producing meaningful exposure, inspect qualification, card construction, age and audience fit first. If it is being shown but attracts few clicks, the title-image combination and its relevance to the matched audience become more plausible constraints. Neither symptom proves a single cause, but the distinction keeps your audit pointed at the right stage.
The ranking signals you can actually work on
Once a page survives the earlier filters, a server-side predicted click-through rate model estimates whether someone is likely to open it. The model and its weights have not been disclosed. Client-side telemetry does, however, expose several of the inputs and conditions surrounding that decision.
| Signal or condition | How it enters the feed | What to check |
|---|---|---|
| Title | The card title is taken from og:title. If it is missing, Google may fall back to a Twitter title or the HTML title. | Inspect the emitted HTML and make sure all title fields describe the same page. Do not let an old template value become the unintended fallback. |
| Image | Image dimensions, quality and successful loading affect card treatment. A missing image can leave the page without a card. | Open the exact og:image URL, verify that it loads and confirm that the asset is at least 1200 pixels wide if you want eligibility for the larger card presentation. |
| Freshness | Content age is grouped into decay windows, with the strongest advantage during the first seven days. | Record the real publication age before diagnosing a later decline as a title or technical problem. |
| URL history | Previous clicks and impressions for the URL can inform predicted engagement. | Evaluate a page in the context of its own exposure history. A result from another URL or topic is not a clean substitute. |
| Personal relevance | Broader interest data and individual actions such as follows, saves, dismissals and reading engagement help shape the feed. | Define the specific interest the page serves. A generally interesting subject is not the same as a strong match for a particular person. |
| Publisher context | Publisher-level signals can include Publisher Center registration, while a person’s publisher block can exclude the domain from that person’s feed. | Keep publisher identity consistent and treat every card as part of a domain-level relationship, not only as an isolated URL. |
The image threshold deserves literal treatment. An asset that is 1199 pixels wide does not meet a 1200-pixel requirement. Smaller images may still appear as thumbnails, but thumbnail cards generally provide less visual space and tend to attract fewer clicks. The practical target is therefore not merely having an image. You need a suitable, accessible image attached to the metadata Google reads.
The title fallback chain is another frequent source of confusion. Your editorial interface may show the intended headline while the page emits a stale og:title. In that case, the social card field can govern Discover’s title. Check the final HTML delivered by the page rather than assuming the visible on-page heading and metadata match.
Two less obvious meta directives also belong in the qualification audit. The exposed behavior indicates that nopagereadaloud and notranslate can prevent Discover appearance. If either directive is generated by a sitewide template, localization plugin or publishing workflow, confirm that its presence is intentional before changing copy or images.
Do not turn this signal list into a formula. Predicted click-through rate is a model output, not a field you can set, and the available evidence does not reveal a reliable weight for each input. Your job is to remove preventable defects and create a truthful, immediately understandable card. A title-image combination that wins a click but disappoints the reader can still lead to a dismissal or publisher block.
Freshness creates a clock, not an automatic expiration date
Content age is not treated as a smooth, uniform curve from the moment of publication. The exposed freshness model uses four practical age bands:
| Age of content | Expected freshness treatment | Operational implication |
|---|---|---|
| 1-7 days | Strongest freshness boost | Complete metadata, image and loading checks before publication so the best window is not spent repairing the card. |
| 8-14 days | Moderate visibility remains possible | Separate a normal reduction in freshness from a technical failure. Review exposure and click behavior before making large changes. |
| 15-30 days | Visibility tends to fall | Expect age to become a stronger competing explanation when performance declines. |
| More than 30 days | Gradual decay continues | Do not assume exclusion. Determine whether the page has durable evergreen value and whether a substantive update is editorially warranted. |
These bands describe relative treatment, not guaranteed traffic. A one-day-old page can still fail eligibility or interest matching, while older content may receive an evergreen classification. Freshness is an advantage after the page qualifies; it cannot repair a missing card, an accidental block or a weak audience match.
The first seven days should change your publishing workflow. Finish the large image, metadata and page-loading checks before the URL goes live. If those tasks wait until the next morning, part of the strongest freshness window has already passed. Coordinate the initial distribution during that same period rather than treating publication and promotion as unrelated jobs.
Do not read the decay model as permission to change a date without changing the content. Nothing in the exposed mechanics establishes that a timestamp edit alone reliably resets classification or restores distribution. If a mature page deserves renewed attention, make the update useful on its own merits, confirm the card again and then judge the result without assuming a reset.
User feedback can narrow future opportunity
Discover is not just personalized when the feed is first assembled. It learns from direct actions and reading behavior. Follows, saves, story dismissals and time spent with content can influence what a person sees next. The feed can also add, remove or reorder cards while someone scrolls, without requiring a manual refresh.
The scope of each negative action matters. A dismissal is stored for the specific URL and prevents that story from reappearing for that person. A publisher block is broader: it can remove the domain from that person’s feed before future pages are matched with interests. That asymmetry makes a misleading card a publisher-level risk, even when it succeeds at generating the first click.
Use that distinction when reviewing content. For an individual URL, ask whether the title and image promise the same experience the page delivers. At the publisher level, look for repeated patterns that could make someone reject the whole domain: unclear topic fit, cards that routinely overstate the content or inconsistent value between pages. You may not be able to attribute every block to a specific card, but you can remove the recurring reasons a reader would choose one.
Feed experiments add another layer of noise. During one observed period, about 150 server-side experiments and more than 50 card-presentation features were active. Two people with similar interests can therefore receive different layouts or selections because they are in different experimental groups.
A single device check is useful for spotting a broken image or malformed title, but it is not a ranking test. Do not treat one person’s feed position, card shape or absence as a stable benchmark. Look for repeated patterns across comparable URLs and time windows, while remembering that a page moving down after its first week may reflect freshness decay rather than an editorial mistake.
Run your Discover audit in pipeline order
When visibility disappoints, use the same sequence the feed uses. Stop at the first failed check, correct it and verify the result before redesigning everything downstream.
- Confirm basic qualification. Make sure Google can crawl and interpret the page, then check for
nopagereadaloud,notranslateor another intentional publishing restriction. - Inspect the delivered metadata. Read the final
og:titleandog:imagevalues from the page. Check the Twitter and HTML titles as possible fallbacks rather than relying only on the CMS preview. - Validate the image as a card asset. Open the exact image URL, verify that it loads and confirm a width of at least 1200 pixels for the larger presentation. A visually attractive file that fails to load is still a failed signal.
- Place the URL in its freshness band. Record whether it is 1-7, 8-14, 15-30 or more than 30 days old. Use that context before interpreting a rise or decline.
- Name the intended interest match. Complete the sentence: this page is for a person who follows or engages with this specific subject. If the answer is only a broad demographic, the content proposition is probably not precise enough for a personalized feed.
- Review the predicted-click inputs. Put the title and image together as a card. Check whether they communicate a specific, accurate reason to open the page without depending on context that appears only inside the body.
- Assess feedback risk. Compare the card’s promise with the first screen and the substance of the page. Remove gaps that might win an initial click but invite a URL dismissal or publisher block.
- Interpret results as a pattern. Compare similar pages and equivalent age windows. Treat a single feed view as a rendering check, not proof of ranking success or failure.
Key takeaways
- Google Discover can filter a page or publisher before interest matching and ranking begin.
- The ranking stage uses a server-side predicted click-through rate model, but its formula and signal weights are not public.
- Card titles primarily come from
og:title, with Twitter and HTML title fields available as fallbacks. - Images should load correctly and be at least 1200 pixels wide for eligibility for a prominent card treatment.
- Freshness is strongest at 1-7 days, moderates at 8-14 days, falls at 15-30 days and gradually decays beyond 30 days.
- A story dismissal applies to one URL for one person, while a publisher block can remove the entire domain from that person’s feed.
- Experiments and live feed reordering make individual screenshots unreliable as performance benchmarks.
Choose one recently published URL and run only the first three audit steps before changing its writing. If qualification, metadata or image delivery fails, fix that layer first. If all three pass, move to interest fit, predicted click appeal, freshness and feedback in that order. This gives you a defensible diagnosis even when Discover itself remains variable.
Leave a Reply