# Lead Radar keyword tester

Test exact, broad and negative Lead Radar keywords against pasted examples with the extension’s matching engine. See match reasons without scanning Facebook.

Canonical: https://groupposting.com/tools/keyword-tester/

[← All free tools](<https://groupposting.com/tools/>)

 Free browser tool

See why a phrase would match before you use it in Lead Radar. Paste example posts, try exact and broad rules, and check what your exclusions remove.

- No sign-up
- Inputs processed in your browser
- Copy & download

1. Set your rulesUse one keyword phrase per line or separate phrases with commas. Add negative phrases to exclude unwanted examples.
2. Paste example postsSeparate up to 20 examples with a line of three dashes. The tool tests only the text you provide.
3. Read the reasonSee the matching mode or negative veto. A phrase match does not establish buyer intent.

## Test your matching rules

At least one exact or broad phrase is required. Up to 100 phrases per rule type, 160 characters per phrase and 30,000 characters of example text.

Exact phrasesA contiguous phrase with Unicode word boundaries. Written-without-spaces scripts use substring matching.

Broad phrasesEvery token must appear, in any order. This can match a wider set of conversations.

Negative phrases (optional)A matching negative phrase excludes the example before any positive rule is checked.

Example post textSeparate examples with a line containing only --- . This does not read or monitor Facebook.

Test matching rulesTry an illustrative example

Your inputs stay in the tool. They are processed in this page and are not sent by the tool. The site’s normal analytics and consent rules still apply. The tool does not save your work; copy or download before leaving.

## Use the actual matching behavior

This tool ships the same side-effect-free matching core as the Group Posting extension. It normalizes case, Unicode compatibility forms, smart quotes and hyphen variants on both the keyword and the post text. Terms are treated as literal text, not user-provided regular expressions.

Exact phrases match a contiguous sequence. Broad rules require every token but allow a different order. Negative rules use the same phrase boundaries and veto first. For scripts normally written without spaces, the core uses substring matching for the phrase.

Use examples that include both relevant and irrelevant conversations. A broad rule can find more text without making that text useful for your business. Read the original conversation and the group’s rules before deciding whether to reply.

### Illustrative example

recommend a bakery matches “Can anyone recommend a bakery near Riverside?”. A broad birthday cake rule also matches “Birthday coming up — where should I buy a cake?”.

A negative free rule excludes “Looking for a free birthday cake”, but does not exclude “I’m a freelancer looking for a cake”. The word boundary matters.

## Common questions

### What is the difference between exact and broad matching?

Exact matching looks for the contiguous keyword phrase with Unicode word boundaries. Broad matching requires every token in the phrase, in any order. The native engine uses substring matching for phrases containing scripts normally written without spaces.

### Why did a negative phrase remove a positive match?

Negative phrases are checked first. If one matches, the example is excluded and positive rules are not evaluated. Exclusions use the same phrase boundaries, so free does not exclude freelancer.

### Does a match mean this person is a buyer?

No. It means the pasted text matched your rules. This tool does not scan Facebook, verify people, qualify intent or send messages. Read the actual conversation before deciding whether a reply is useful.

Technical references: [The published native matching core](<https://groupposting.com/js/radar-matcher.js>) · [MDN: Unicode normalization](<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/normalize>).

### Use it in your workflow

Take the output into your own workflow. You decide what is appropriate for each group.

- [How to monitor buying signals →](<https://groupposting.com/group-posting/how-to-monitor-buying-signals/>)
- [How Lead Radar works →](<https://groupposting.com/features/lead-radar/>)
- [Check the group before posting →](<https://groupposting.com/tools/group-post-checklist/>)
- [Apply this to a business posting workflow →](<https://groupposting.com/for/local-business/>)

Your next step

## Put your keyword ideas in context

Treat these terms as planning suggestions. This tool does not verify search demand or access private client leads.

- ### For content planning

  Translate audience questions into a clear contribution and truthful offer.

  [Use the campaign brief →](<https://groupposting.com/group-posting/facebook-group-campaign-brief/>)
- ### For client services

  Build a repeatable publishing service with clear permissions and responsibilities.

  [See the agency service guide →](<https://groupposting.com/for/agencies/offer-facebook-group-posting-as-a-service/>)