Our social listening stack for Q4 2026
We consolidated from three tools to one. The alerts are good but $199 a month for 10 keywords is steep. If anyone has a per-use alternative with an API, I want to hear about it.
planned
LinkedIn is reserved as a direct source until a real path exists. Indexed public posts arrive as web results with a domain today. Planned.
Today, use site:linkedin.com in a web search or catch. Indexed public LinkedIn posts arrive as web results with domain linkedin.com. Coverage is real but thin. LinkedIn has had no content API since 2015 and every product in this category is thin here. Direct LinkedIn coverage is reserved until a real path exists.
Today: public posts the web index has picked up, as web results with domain linkedin.com. Planned: direct coverage.
Through the web index for now, with site:linkedin.com in the query.
One syntax for every source: quotes, AND, OR, NOT, site:, author:, lang:.
query
site:linkedin.com "your product"One result, as a catch delivers it: source, author, the post, a prescore, thread context, and a suggested action your agent can act on.
We consolidated from three tools to one. The alerts are good but $199 a month for 10 keywords is steep. If anyone has a per-use alternative with an API, I want to hear about it.
LinkedIn public posts are a different signal from other sources. They are written for a professional audience. A post comparing tools is written for peers, not for karma. A post sharing a stack is a real buying signal. These posts are worth more per result than a Reddit comment, and the prescore should reflect that when LinkedIn moves to a direct source.
Every product in this category claims LinkedIn coverage. Few say how they get it. Brand24 has two blog guides but no tool page. Octolens has a tool page but no public documentation of how it accesses LinkedIn. ddevi, TryKeywordAlerts, KWatch, and ParseStream have tool pages on the keyword alerts phrasing, but none say how they reach LinkedIn either. discatch says: today, indexed public posts through the web index. Direct coverage when a real path exists.
Brand24 holds the top two results for "monitor LinkedIn for mentions" with two blog guides. Octolens and Alertly have tool pages. On the "keyword alerts" phrasing, ddevi, TryKeywordAlerts, KWatch, ParseStream, and a Quora thread fill the results. Nobody pushes LinkedIn results to an agent.
LinkedIn has had no content API since 2015. Every product in this category reaches LinkedIn by scraping or through the web index. This is an honest industry-wide constraint. discatch states it rather than hiding it.
Today: indexed public LinkedIn posts arrive as web results with domain linkedin.com. Use site:linkedin.com in your query. Coverage is real but thin. Planned: direct LinkedIn coverage when a real path exists. Only public posts are covered; discatch never logs in as you.
Your product on LinkedIn
site:linkedin.com "your product"Stack-sharing posts
site:linkedin.com "our stack" AND ("social listening" OR "monitoring")LinkedIn is the one source where B2B buyers share their tool stacks in public. A growth lead posting "our monitoring stack for Q4" and naming a competitor is a signal no other source gives you. A CTO asking for recommendations with a budget constraint is a lead. Today these arrive as web results with domain linkedin.com. When direct coverage ships, they will arrive faster and with more context.
The constraint is that LinkedIn posts are part of a feed, not a search index. Even products that claim LinkedIn coverage are thin on it. discatch marks this as reserved and tells you what is available rather than overstating it.
LinkedIn shut down its content API in 2015. Since then, every product that claims LinkedIn monitoring reaches it by scraping or through the web index. Brand24 holds the top two results for "monitor LinkedIn for mentions" with blog guides, not a tool page. This is an industry-wide constraint, not a discatch limitation. discatch states it plainly.
Partly. Use site:linkedin.com in a web search or catch. Indexed public posts arrive as web results with domain linkedin.com. Coverage is real but thin. Direct LinkedIn coverage is reserved until a real path exists.
Thin, late LinkedIn coverage is a category-wide complaint. LinkedIn has had no content API since 2015. Every product in this space scrapes or uses the web index. discatch reaches indexed public posts today and marks the source reserved.
The same as any web search: one search unit per call, plus one result unit per matched item. You are searching the web index with a site: filter.
Only if the page is publicly indexed. Use site:linkedin.com/company/yourcompany in the query.
No. Only public posts that the web index has picked up. discatch never logs in as you.
LinkedIn has had no content API since 2015. Every product in this category reaches LinkedIn by scraping or through the web index. discatch marks it reserved and says what is available honestly.
Brand24 holds the top two results for "monitor LinkedIn for mentions" with blog guides. Octolens and Alertly have tool pages. On the "keyword alerts" phrasing, ddevi, TryKeywordAlerts, KWatch, and ParseStream have tool pages.
LinkedIn results will move from web (with domain linkedin.com) to a dedicated linkedin source. Existing catches with site:linkedin.com will keep working.
Yes. Set the catch destination to a webhook. Today the results come from the web index with domain linkedin.com.
No. discatch never posts on anyone’s behalf. Drafting is your agent’s job.
Yes. Name multiple sources in the catch. A catch on your product name across linkedin, hackernews, and web finds mentions on all three. Today LinkedIn results come from the web index with domain linkedin.com. When direct coverage ships, they move to the linkedin source.
Last reviewed by Parsa Khazaeepoul, founder, dcouple. Facts from docs/data-sources.md and docs/coverage-matrix.md; status from docs/api.md; the search landscape from docs/seo/keyword-map.md.