Reducing Signal Noise: Negative Keywords, Denylists, and Threshold Tuning

You spent an hour picking keywords. Posts are flowing in. And 40 of 47 new signals are about video game deployments, military exercises, and cryptocurrency mining rigs.

That is noise. And it is the #1 reason teams abandon social listening tools.

That is noise. And it is the #1 reason teams abandon social listening tools.

The good news: noise is fixable. You do not need to start over. You need to pull three specific levers, in the right order, based on where the noise is actually coming from.

Why Noise Kills Social Listening Programs

Noise is not just annoying. It has real costs. Every irrelevant post that matches your keywords enters the analysis pipeline, consuming AI credits. When 80% of your matches are irrelevant, you are burning 80% of your budget on garbage.

But the bigger cost is human. When your team opens the dashboard and sees mostly junk, they stop checking. Signal fatigue sets in within two weeks. By week three, nobody trusts the tool.

The benchmark: A well-tuned listener should have a noise ratio below 80%. That means at least 20% of matched posts become qualified signals. If you are below 1%, your listener needs immediate attention.

What this article covers: Negative keywords, platform denylists, and relevance threshold tuning. For broader keyword optimization, see the 5-Phase Listener Optimization Framework.

The Three Noise Reduction Levers

Lever	What It Fixes	When to Use
Negative keywords	Keyword ambiguity (your terms match unrelated topics)	A keyword has multiple meanings across industries
Platform denylists	Source contamination (specific communities generate junk)	Certain subreddits or accounts always produce noise
Relevance threshold	Borderline matches (AI lets through low-quality signals)	Signal quality is inconsistent

Start with negative keywords (highest impact, lowest risk), then denylists, then threshold tuning.

Lever 1: Negative Keywords

Negative keywords automatically exclude a post from matching. They are the single most effective noise reduction tool.

Building Your Negative Keyword List

Example: B2B deployment software. “Deploy” matches software deployments (what you want), military deployments (noise), and game deployments (noise).

Negative keywords: military, troops, game, gameplay, battlefield, fortnite, COD

Example: CRM software. “Pipeline” matches sales pipelines (want), oil pipelines (noise), CI/CD pipelines (noise).

Negative keywords: oil, gas, petroleum, CI/CD, Jenkins, GitHub Actions, water

Best Practices

Be specific, not broad. Adding “free” as a negative keyword seems smart until you realize people write “looking for a free trial of [your competitor].” That is a buying signal you just killed.

Test before committing. Before adding a negative keyword, search your existing matched posts for that term. Count how many legitimate signals contain it. If more than 5% of your real signals would be excluded, the term is too broad.

Review monthly. Language shifts. New products launch. A negative keyword that made sense six months ago might now be filtering out a new competitor’s name.

Start with proper nouns. Game titles, military operations, unrelated company names, and place names are safe negative keywords. They rarely overlap with B2B buying conversations.

Quick win: 10-15 well-chosen negative keywords typically cut noise by 30-50% on day one.

Lever 2: Platform Denylists

Sometimes the noise is about where people say things, not what they say. Use denylists when a subreddit or source consistently generates irrelevant matches regardless of keyword tuning.

Common denylist targets for B2B:

Platform	Noise Sources
Reddit	r/gaming, r/politics, r/worldnews, r/memes, r/cryptocurrency (if not fintech)
X	News aggregator bots, parody accounts

Start narrow. Block the single worst offender first. Measure impact over a week. Track why you added each entry.

Never denylist an entire platform. If Reddit as a whole is too noisy, your keywords need work.

Lever 3: Relevance Threshold Tuning

After AI analyzes a post, it assigns a relevance score (0-100). The threshold is the cutoff.

Default: 70. Works for most use cases.

Raise to 75-80 if you’re getting too many “maybe relevant” signals, your volume is high enough to lose borderline matches, or your keyword space is crowded.

Lower to 65 if you’re in a niche market with low volume, your team is willing to do more manual qualification, or your keywords are already very specific.

Do not go below 60. The noise will overwhelm any additional signal value.

Tuning Process

1. Run at default (70) for two weeks
2. Audit 50 signals manually. How many are relevant?
3. Check posts that scored 65-69. How many were good leads you missed?
4. Adjust by 5 points based on your audit
5. Wait one week and audit again

Do not change thresholds and keywords at the same time. You won’t know which change caused the improvement.

The Noise Diagnostic Framework

Step 1: Sample 20-30 recent rejected or low-quality matches

Note: what keyword triggered it, what was it actually about, what source, what relevance score.

Step 2: Categorize

Keyword noise (fix with negative keywords): The keyword matched an unrelated topic.

Source noise (fix with denylists): The keyword and topic are correct but the source never produces buying intent.

Threshold noise (fix with threshold tuning): The post is topically correct but intent is weak.

Step 3: Fix in Order

Noise Type	Primary Fix	Expected Impact
Keyword noise	Add negative keywords	30-50% reduction
Source noise	Add to denylist	10-30% reduction
Threshold noise	Raise threshold by 5	15-25% reduction

Measuring Success

Track weekly: signal rate (should trend upward), signal volume (should stay stable), AI credit usage (should decrease), team engagement (are people checking signals?).

The sweet spot: Signal rate between 3-8%.

Automating Noise Reduction

The /listener-tune skill via CatchIntent’s MCP integration automates the diagnostic framework above. It identifies noise sources, suggests negative keywords, flags denylist candidates, and recommends threshold adjustments.

For the full keyword optimization process, see the 5-Phase Listener Optimization Framework.

Frequently Asked Questions

How many negative keywords should I add?

Start with 10-15. Most well-tuned listeners end up with 20-40. If you have more than 100, your primary keywords are probably too broad.

Can negative keywords accidentally filter out real buying signals?

Yes, if you pick overly broad terms. Always test against existing signal history before adding. If more than 5% of real signals contain the term, it is too broad.

How often should I review noise reduction settings?

Full audit monthly for the first three months, then quarterly unless you notice sudden quality changes.

What if my signal volume drops too much after raising the threshold?

Lower it back by 5 points and focus on negative keywords and denylists instead. If raising the threshold kills volume, the real problem is keyword selection or source contamination.

Is there a way to see what the AI rejected and why?

Yes. CatchIntent shows rejection reasons in listener analytics. “Not relevant to product category” means keyword ambiguity. “No buying intent detected” means your keywords catch discussions but not decision moments.