[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Check if your site appears in Google Discover

> Check each day whether your domain is in the Google Discover feed of a signed-in account: position, title, age and topic of each card. Runs daily.

Source: https://cotlet.dev/integrations/google-discover-api-mcp-server/check-if-your-site-appears-in-google-discover

You published a story that should suit Discover, and the Search Console report only shows a total for yesterday. You want to know whether a card from your domain is in the feed right now, and where.

Cotlet does it in your own Google Discover account with check\_domain\_in\_feed and get\_story\_cluster, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=google-discover) [All Google Discover tools](https://cotlet.dev/integrations/google-discover-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Google Discover do this on its own?

Google offers no way to read the feed from code (checked 20 Oct 2026). The Discover report in Search Console shows impressions, clicks and CTR for content that appeared in Discover in the last 16 months, once the data reaches a minimum threshold of impressions. It does not say whether a story is in a given account's feed now, or at which position.

## How you do it in Google Discover today

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.

## How to check if your site appears in Google Discover

Prompt

```
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.

### What you get back

Example data

```
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.
```

### Other ways to ask

- Every morning at 8, scan 60 cards in the US and UK Cloud Browsers and tell me which feed shows example-news.com.
- Check three domains, mine and two I follow, and list who has more cards in my top 40.
- Tell me only when my domain was in the feed yesterday and is not today.

## What Google Discover allows, and what to know first

- Discover recommends content based on a person's Web and App Activity, so two accounts see different feeds.
- Content is eligible automatically when it is indexed and follows the Discover content policies; no special tags or structured data are required, and eligibility is not a guarantee.
- Older content can appear in Discover if it is helpful and relevant to a person's interests.
- Some Discover features are not available in all languages and countries, so the feed depends on the country of your Cloud Browser.

Every tool here only reads, so it can run daily from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [Search Central: Google Discover](https://developers.google.com/search/docs/appearance/google-discover) · [Google Search Help: Customize what you find in Discover](https://support.google.com/websearch/answer/2819496)

## Call check\_domain\_in\_feed from a script

curl

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

Example response

```
{
"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.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/google-discover-api-mcp-server.md#automations)

## Google Discover tools this automation uses

__Cotlet Google Discover tools used to check if your site appears in Google Discover__
| Tool | Parameters |
| ----------------------- | ------------- |
| check\_domain\_in\_feed | domain, limit |
| get\_story\_cluster | url |

[All 13 Google Discover tools with descriptions](https://cotlet.dev/integrations/google-discover-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Google Discover to Cotlet?

Yes. You sign in to Google Discover yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Google Discover once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Google Discover automations

- [Weekly Google Discover performance report](https://cotlet.dev/integrations/google-discover-api-mcp-server/weekly-google-discover-performance-report.md)
- [Hide publishers and topics from your Google Discover feed](https://cotlet.dev/integrations/google-discover-api-mcp-server/hide-publishers-from-your-discover-feed.md)
- [Google Discover API and MCP server: every tool](https://cotlet.dev/integrations/google-discover-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Google Discover.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Google Discover.

[Sign up free](https://cotlet.dev/app/signup?app=google-discover)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.