A brand name can also be a common word, another company's name, or an old product label. A text match is therefore a candidate observation, not conclusive evidence that an answer mentioned your business.
Review the surrounding description, domain, product category, and context. Record what establishes identity and what remains ambiguous. A visibility report should not gain apparent mentions because the matching rule is broad enough to collect unrelated words.
The examples below use a fictional approval product called Anchor. They describe an original classification method, not a claim about any real company using that name.
Classify the candidate mention
Keep a distinct state for confirmed identity, unrelated use, and unresolved ambiguity. That is more informative than forcing every match into a yes-or-no brand count.
| Invented answer fragment | Identity judgment | Reason |
|---|---|---|
| Use an anchor to keep the boat in place. | Unrelated | Common noun in a different topic |
| Anchor routes purchase requests to designated approvers. | Candidate requiring context | Category fits, but identity still needs sufficient evidence |
| Anchor is linked to the verified product domain and described accurately. | Confirmed in this example | Domain and product context agree |
| Anchor offers video-editing templates. | Different entity or unresolved | Description conflicts with the fictional target product |
Do not assume a matching category always proves identity. Two products can have similar names and functions. Use the evidence available in the actual answer rather than adding facts the answer never supplied.
Maintain a small identity record
Record the current brand name, verified domain, known former names, product aliases, and dates when those names were actually used. Link each real-world identity fact to a primary company record.
Keep typos and abbreviations separate from approved aliases. A broad abbreviation may produce many unrelated matches. Add it to candidate detection only if the review process can resolve the ambiguity without inflating the final count.
For a renamed product, preserve the naming timeline. An answer using the former name may still identify the same business, but it can also reveal outdated information. Record identity and recency as separate fields.
Review the complete passage
Read enough context to understand whether the answer is discussing the product, quoting another source, or merely listing a word. A name in a citation title is not automatically a recommendation in the answer body.
If the answer links to a domain, inspect the actual destination when permitted. A display label can differ from the link target. Keep a record of redirects that materially affect identity rather than assuming the visible URL text is definitive.
When the evidence is insufficient, leave the observation unresolved. Do not search for a favorable external interpretation and attach it to an answer that never made the connection clearly.
Report ambiguity in the denominator
Suppose a hypothetical scan finds twenty text matches. Twelve clearly identify the product, five are unrelated uses, and three remain ambiguous. Report those states. Calling all twenty brand mentions would overstate the evidence.
If you report a rate, specify whether it uses all valid answers or only answers with resolved identity. Keep unresolved observations visible so a reader can assess coverage. Use the same rule in later runs.
Apply the mention and recommendation distinctions after identity is established. Correct entity matching is the first step; it does not prove positive sentiment, suitability, citation support, or commercial impact.