Discover Feed #
The vertical scroll of cards that appears on the Google app, the Chrome new-tab page on Android, and Pixel home screens. It is generated per-user from interest signals — there is no single global ranking.
Every term that matters when you work with Google Discover — algorithm signals, eligibility, structured data, engagement metrics. Concise, technical, and in plain English.
The vertical scroll of cards that appears on the Google app, the Chrome new-tab page on Android, and Pixel home screens. It is generated per-user from interest signals — there is no single global ranking.
The atomic building block of the feed. A standard card shows a hero image (16:9 or 4:3), the title, the source name, and a freshness signal. Larger formats exist ("big card") for breaking news.
Separate surface inside Google Search that aggregates news content. Eligibility overlaps with Discover but is not identical — News favors recency and original reporting.
When Discover detects strong engagement on a topic, it temporarily over-weights related cards in the same browsing session. This is the mechanism behind the typical "Discover spike".
The small interest pills users tap to refine their feed (e.g. "AI", "Premier League"). Subscribing to a chip pushes related publishers up the user's personal ranking.
The minimum technical bar a URL must clear to be considered for Discover: indexable in Google Search, mobile-friendly, served over HTTPS, and free of policy violations. Eligibility ≠ ranking — it just opens the door.
Public Google-hosted page at profile.google.com/cp/<ID> that aggregates a publisher's signals (logo, social links, last 30 days on Discover). The presence of this URL is the cleanest existence proof that a domain is recognized as a Discover entity.
Google's push-indexing endpoint. Officially restricted to job postings and live-stream pages, but news publishers often use it as a fast-lane for breaking content. Use carefully — abuse triggers throttling.
Google's dashboard at publishercenter.google.com where publishers manage their logo, sections and Following-button identity. Mandatory for News-tab inclusion, optional but recommended for Discover.
An XML list of canonical URLs the publisher wants indexed. For news, a dedicated news.xml with <news:publication> blocks accelerates crawl of articles less than 48 h old.
<meta name="robots"> tags that instruct Googlebot. The combo index, follow, max-image-preview:large, max-snippet:-1 is the de-facto Discover-eligibility recipe.
The robots-meta value that grants Google permission to display large image previews. Without it, your hero image will not be used as a Discover card thumbnail. Single most under-set tag in eligibility audits.
Open protocol (Bing, Yandex, Cloudflare) that pings search engines when a URL is published or updated. Google does not officially support it, but many CDNs flip it on by default — neutral for Discover but useful for general SEO.
The recommended format for declaring schema.org markup on a page. A single <script type="application/ld+json"> block in <head> can carry multiple typed entities (Article, BreadcrumbList, FAQPage, …).
Schema.org type for editorial content. Required fields for Discover-grade markup: headline, image, datePublished, author, publisher.
Stricter sub-type of Article reserved for time-sensitive news. Adds dateline and recognizes printSection. Misusing it on evergreen content can trigger demotions.
Schema declaration of the page's hierarchical position. Powers the breadcrumb that sometimes replaces the URL line in cards and search snippets.
Schema sub-entity to declare an image with explicit width, height and url. Strongly recommended inside Article markup so Google can pick the right hero crop.
Experience, Expertise, Authoritativeness, Trustworthiness — the four-letter framework Google's quality raters use to evaluate content. Heavily weighted on YMYL topics.
Topics that materially affect the reader's wellbeing: health, finance, legal, safety, parenting, civics. Discover applies an extra layer of scrutiny here, including stricter author-page expectations.
Google's system (rolled into the core algorithm in 2024) that demotes sites whose content is written primarily for search engines rather than humans. A site-wide signal — one bad section can drag the rest down.
Policy targeting third-party content (often affiliate or coupon) hosted on a high-authority domain to siphon its rankings. Active since May 2024 and aggressively enforced via manual actions.
The catalogue of behaviors that get content removed from Discover entirely: cloaking, sneaky redirects, doorway pages, scraped content, hidden text, hacked content, automatically generated content lacking value.
Showing different content to Googlebot than to human visitors. Hard violation — triggers manual action and full Discover suspension.
The top visual of an article, also called the lead image. This is the asset Google selects (in 92% of cases) for the Discover card thumbnail.
The width-to-height proportion. Discover crops cards to either 16:9 (mostly) or 4:3. Anything below 1200 px wide gets pillar-boxed and ranks worse.
Google's official guidance: hero images must be at least 1200 px on the longest side. Below that, the image becomes ineligible to render at full size in Discover, even if everything else is correct.
C2PA / IPTC metadata that flags an image as AI-generated. Discover does not penalize AI imagery per se but expects editorial visuals to be disclosed when they are not photographic evidence.
The alt="" attribute. Used for accessibility and as a tie-breaker when Google has to choose between competing candidates for the card thumbnail. Keep it descriptive, not keyword-stuffed.
The single first-level heading on the page. It should match the title users see in the Discover card — divergent H1 vs Title leaks ranking signals and confuses Google's title-rewriting layer.
The <title> in <head>. Discover often shows it verbatim, sometimes truncated to 70 characters. The single highest-leverage piece of copy on the entire page.
The 150–160 character summary in <head>. Discover only renders it on a fraction of cards but it remains a tie-breaker for click-through prediction.
The og:* meta family that controls how the URL renders when shared on social. Discover falls back to og:image when no <link rel=image_src> or schema image is present.
The single authoritative URL for a piece of content, declared via <link rel="canonical">. Discover uses it to consolidate signals across duplicate or syndicated copies.
Clicks ÷ impressions. Discover's primary feedback signal. A 5% CTR is the rough median; sustained <2% suppresses future distribution; 10%+ unlocks sticky sessions.
Time elapsed between a click and the user returning to the feed. Long dwell = signal that the article matched the promise of the title. Short dwell = the title oversold.
When a user clicks a card, returns to the feed within seconds, then clicks a different card. The dual signal (short dwell + immediate alternative) is the most damaging engagement pattern.
Internal Google distinction. A long click ends the user's task (no further query); a short click sends them back to search. Discover uses the same distinction adapted to the feed.
User-event Discover instruments specifically: tap card → arrive on article → press back → return to feed. The latency between "arrive" and "back" is one of the cleanest quality proxies available.
Google's structured database of entities (people, places, organizations, concepts). A topic that maps cleanly to a Knowledge Graph entity surfaces faster in Discover than free-form keywords.
Site-level credibility on a defined topic cluster. Built by depth (multiple in-depth articles), recency (sustained publication cadence), and citations (links from other authorities).
The user-account setting (myactivity.google.com) that gates personalization. Disabled = the user sees a generic, geo-only Discover; enabled = full personal feed.
The user-specific re-ranking layer applied on top of the global ranking. Inputs: search history, site-following, topic-chip subscriptions, time-of-day patterns, language, location.
Counted when a card enters the viewport for at least one second — strict definition vs. Search where impression = position in result page. A scroll-past does not count.
Tap on the card thumbnail or title that opens the article. Multiple clicks within a session de-duplicate to one in Search Console.
The non-linear traffic burst typical of Discover — easily 10–100× a publisher's organic baseline. Rare per article (~5% of eligible URLs trigger one), volatile, and impossible to forecast.
An article's traffic typically halves every ~6 hours after the first impression burst. Half-life varies by topic — evergreen guides decay slowest, news decays fastest.
Boost given to articles published or substantively updated in the last 24–48 h. Updating dateModified without changing real content is detected and demoted.
An algorithmic downgrade applied at the URL, section, or domain level. Different from removal — content remains indexable but loses Discover distribution.
Human-reviewed penalty visible in Search Console. Triggered by clear policy violations (spam, hidden text, hacked content, site-reputation abuse). Requires a reconsideration request to lift.
Silent demotion not reported in Search Console. Detectable only by sudden, sustained drops in Discover impressions while Search remains stable.
Periodic algorithm refreshes (3-6 per year). Core updates re-tune ranking; Spam updates target policy-violators specifically. Discover impact is often more violent than Search impact.
Free Google dashboard at search.google.com/search-console. The only authoritative source of impressions, clicks and CTR for both Search and Discover.
Search Console's dedicated Discover view. Only appears once your domain has accumulated >100 Discover impressions in 16 months — its mere existence is a signal that you are eligible.
Google's dashboard at publishercenter.google.com. Lets publishers manage their logo, sections and Following-button identity. Optional but recommended for Discover.