Check if your site appears in Google Discover

1. Open the Google app, or google.com in a phone browser, signed in to the Google Account whose feed you want to check.
2. Scroll the Discover feed and read the publisher name on each card, looking for your own.
3. Tap More at the bottom right of a card to see Not interested in the topic or Don't show content from the source, which tells you which topic Discover filed the card under.
4. Repeat on another day, because the feed changes through the day and between accounts. Nothing records what you saw, so the position and age of a card are lost the moment you scroll.

Scan the top 40 cards of my Google Discover feed and tell me whether example-news.com appears. List the position, title, age and topic of each match.

1. 01

   Scan the top of the feed

   Your agent calls check_domain_in_feed with your domain and the number of cards to scan. The tool opens the feed of the signed-in account in your Cloud Browser, so the answer holds for that account and the country of that Cloud Browser, not for everyone.

2. 02

   Treat a miss as a miss for this feed

   No match means the domain was not in the scanned cards of this account at this moment. The agent says so and does not claim your story is absent from Discover. Eligibility is not a guarantee of appearing, and Discover traffic is less predictable than keyword search.

3. 03

   Open the cluster of each match

   For every match, get_story_cluster returns the more stories from the same event. The agent reads which other publishers sit next to your card and whether yours is the lead.

4. 04

   Report the position and the topic

   The agent writes one line per match with position, title, age and topic, and compares the position with the previous run if your prompt includes it. A card that disappears between two runs is reported as dropped from the scan, not as removed.

example-news.com in my Discover feed (US), top 40 cards scanned:
Position 3: "Ten herbs that survive a cold windowsill", 3h, topic Home gardening
Position 11: "How to feed a sourdough starter", 1d, topic Sourdough baking
Position 11 shares a cluster with 4 other publishers; yours is not the lead.

curl "https://cotlet.dev/api/v1/google-discover/domain-in-feeds/check?domain=example-news.com&limit=40" \
  -H "Authorization: Bearer $COTLET_API_KEY"

{
  "domain": "example-news.com",
  "in_feed": true,
  "cards_scanned": 40,
  "matches": [
    {
      "position": 3,
      "title": "Ten herbs that survive a cold windowsill",
      "url": "https://example-news.com/guides/windowsill-herbs",
      "age": "3h",
      "topic": "Home gardening"
    },
    {
      "position": 11,
      "title": "How to feed a sourdough starter",
      "url": "https://example-news.com/guides/sourdough-starter",
      "age": "1d",
      "topic": "Sourdough baking"
    }
  ]
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is google_discover_read → check_domain_in_feed. Example data.

• Weekly Google Discover performance report
• Hide publishers and topics from your Google Discover feed
• Google Discover API and MCP server: every tool
• All use cases