[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)

# Hide publishers and topics from your Google Discover feed

> Clean up a Google Discover feed: hide a publisher, mark topics Not interested and list what is hidden, undone in one call. Runs on your own feed.

Source: https://cotlet.dev/integrations/google-discover-api-mcp-server/hide-publishers-from-your-discover-feed

Your Discover feed keeps showing one publisher and one topic you never read, and each fix means finding a card, tapping More and choosing an option, one card at a time.

Cotlet does it in your own Google Discover account with get\_discover\_feed, hide\_publisher, mark\_not\_interested, list\_hidden\_items and unhide\_item, 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 has no API for these controls (checked 20 Oct 2026). They exist only on a card and in Manage interests. Google says the blocking feature may not be available in all languages and countries.

## How you do it in Google Discover today

1. On a card in the Google app or on google.com, signed in to your Google Account, tap More at the bottom right.
2. Choose Not interested in the topic, or Don't show content from the source.
3. To bring one back, open your profile, then Settings, then Interests, then Not interested, and tap Unhide next to the topic or source. In a browser the path is Settings, then Manage interests under Discover, then Not interested.
4. You find a source only when its card shows up, so a publisher that appears twice a week takes weeks to clear.

## How to hide publishers and topics from your Google Discover feed

Prompt

```
Read the top 30 cards of my Google Discover feed. Hide Example Daily News and mark every card about celebrity gossip as not interested. Then list what I have hidden.
```

1. 01  
### Read the feed  
Your agent calls get\_discover\_feed for the top cards and groups them by publisher and topic. A publisher or topic that fills many cards is the first candidate.
2. 02  
### Match your rule to cards  
The agent applies your prompt: this publisher, or every card whose topic is celebrity gossip. It lists what it will hide before acting, and skips a card whose topic is unclear instead of guessing.
3. 03  
### Hide the publisher  
hide\_publisher presses Don't show content from the source. Hiding a publisher removes all its cards, so the agent runs it once per publisher, not once per card.
4. 04  
### Mark topics  
mark\_not\_interested presses Not interested in the topic on one matching card. One call per topic is enough, so the agent stops after the first card of each topic.
5. 05  
### Confirm with the hidden list  
list\_hidden\_items returns what the account now hides. The agent checks that every item it just added is in the list and tells you the call to undo each: unhide\_item.

### What you get back

Example data

```
Feed of my Google account (US), 30 cards read.
Hidden publisher: Example Daily News (7 cards)
Not interested: Celebrity gossip (5 cards)
Hidden in this account now: 2 publishers, 3 topics
Undo with unhide_item.
```

### Other ways to ask

- Hide every publisher that has more than 5 cards in my top 30.
- List my hidden publishers and unhide the ones I added before September.
- Follow the three publishers that cover home gardening best in my feed.

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

- Hide and Not interested need a signed-in Google Account, and they change only that account's feed.
- Not interested in a topic and Don't show content from a source are separate options on the same card menu.
- Hidden topics and sources are listed under Not interested, where each has an Unhide button.
- Some of these features are not available in all languages and countries.

hide\_publisher, mark\_not\_interested and unhide\_item change only your own Google Discover data and reach no one else, so they run without asking first.

Sources: [Google Search Help: Customize what you find in Discover](https://support.google.com/websearch/answer/2819496)

## Call hide\_publisher from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/google-discover/publisher/hide \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"publisher":"Example Daily News"}'
```

Example response

```
{
"publisher": "Example Daily News",
"status": "hidden",
"undo": "unhide_item"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is google\_discover\_write → hide\_publisher. 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 hide publishers and topics from your Google Discover feed__
| Tool | Parameters |
| --------------------- | ---------- |
| get\_discover\_feed | limit |
| hide\_publisher | publisher |
| mark\_not\_interested | url, topic |
| list\_hidden\_items | kind |
| unhide\_item | kind, name |

[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

- [Check if your site appears in Google Discover](https://cotlet.dev/integrations/google-discover-api-mcp-server/check-if-your-site-appears-in-google-discover.md)
- [Weekly Google Discover performance report](https://cotlet.dev/integrations/google-discover-api-mcp-server/weekly-google-discover-performance-report.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.