# Brand mention monitoring on X, Reddit, and Google News

2026-08-15

> A company name in tweets, Reddit posts, and News headlines as JSON. Monitoring, not a tactic to earn LLM citations.

- Index: https://fetcher.sh/blog.md
- This page (HTML): https://fetcher.sh/blog/brand-mention-monitoring-x-reddit-google-news

![Stacks of newspapers on a stand](https://images.unsplash.com/photo-1504711434969-e33886168f5c?auto=format&fit=crop&w=1600&q=80)

Photo by AbsolutVision on [Unsplash](https://unsplash.com/?utm_source=fetcher_sh&utm_medium=referral).

Brand mention monitoring means a company name appearing in public tweets, Reddit posts, and Google News headlines. You run the same string in three places and you keep the union. That is a watch, not a playbook for farming mentions so language models cite you.

X search (and [operators](/blog/x-search-operators-from-since-until)), Reddit search, News search. Headlines-only newsroom work is [news monitoring](/blog/news-monitoring-brands-technology-policy). Local reputation is [Maps and Yelp](/blog/local-seo-maps-yelp-review-monitoring), not this. [Crypto and policy](/blog/crypto-regulation-policy-x-reddit-news) is the same mechanics with a tighter vocabulary.

GEO/LLMO mention-farming is a different internet argument. This page is a watch. We do not tell you how to get cited by a model.

## One string, three GETs

Run the brand as an X query (quoted if you need exact). Run it as a Reddit keyword. Run it as a News keyword with a language edition. Hashtags are optional extra.

- [twitter.fetcher.sh](https://twitter.fetcher.sh) `/api/search`
- [reddit.fetcher.sh](https://reddit.fetcher.sh) `/api/search/post`
- [google-news.fetcher.sh](https://google-news.fetcher.sh) `/api/search`

Quote the brand on X if you need an exact string. Reddit keyword search is looser. News search takes a `languageCode` so US and UK editions do not collapse.

Dedup in your own store. The same story will appear as a tweet, a Reddit link post, and a headline. That is three rows, one event, if you care about events. Keep them labeled if you care about surfaces.

## What this watch is not

Not GEO/LLMO mention-farming. Not ASO. Not review monitoring for a restaurant. Not a Meltwater clone with a PDF. Three public surfaces, one string, stop.

Local shops should not start here; they should start on Maps and Yelp. App makers who want store text should start on Play and the App Store. This watch is *the name in public talk and headlines*.

## A case: a launch week without a listening suite

A company ships a name that is also an English word. They cannot buy Brandwatch this week. They need to know if the launch is a story, a joke, or silence.

They quote the name on X, add `since:` for launch day, and sort Latest. They run the same keyword on Reddit sorted by new. They run News in en-US. They skim the union twice a day. They are not optimizing for LLM citations. They are trying not to miss a reasonably public fire.

A joke thread on Reddit with no headline is not “coverage.” A headline with no tweets yet is coverage that has not hit the timeline. Label the host.

## A case: a name that collides

Their product is named after a common verb. Unquoted search is unusable. They quote on X, they add a second token on Reddit (`productname app`), and they still get misses.

They do not “fix” that with a sentiment API. They fix it with a tighter query and a human skim. News is often the cleanest of the three for collision names, because headlines disambiguate. X is the worst. That is expected.

Hashtags on X and IG are optional extras, not a complete mention graph. People talk about brands without tagging them. A watch that only follows a hashtag will look calm during a disaster that used the company name in prose. Run the string. Add the tag if you have spare GETs.

Local shops that think they want “brand monitoring” usually want Maps and Yelp. A cafe’s reputation is not a News headline. Send them to [local SEO](/blog/local-seo-maps-yelp-review-monitoring) before they pay for three social hosts.

A launch-week cadence that stays sane: twice a day, same three queries, store ids, only alert on *new* ids. After launch week, drop to weekdays. Paying per GET makes “every five minutes” look as silly as it is. A listening suite hides that in a seat; we will not.

If comms wants “share of voice,” they want a dashboard vendor. This watch will not invent a percentage from three JSON lists. It will tell you whether the name showed up, where, and with what URLs.

## A watch, not a citation strategy

Not GEO/LLMO mention-farming. Not ASO. Not review monitoring for a restaurant. Three public surfaces, one string, stop. Docs on the three hosts; 402 or a prepaid key. If the comms team wanted a clipping PDF, they still need a person to write the PDF. We return rows. After the week is over, archive the query strings you actually used. Next launch, start from those strings instead of a blank box. The watch is a habit, not a vendor. Quote English-word brands. Add `since:` on X so last year’s pile does not flood launch day. Reddit `sort=new` for the argument, News for whether it is actually a story. Three labels, every time. If the name is also a cafe, still start on Maps for reputation; this watch will not catch a one-star Yelp pile-on. That is a different job.