The same mention twice: deduplicate without losing the conversation
A public post can appear in search, a repost and a later discussion. Counting each appearance as a new lead inflates the queue and can lead to repeated replies to the same person. Start with the original source. Keep discovery records separate from decisions about whether a reply is appropriate.
A public post can appear in search, a repost and a later discussion. Counting each appearance as a new lead inflates the queue and can lead to repeated replies to the same person. Start with the original source. Keep discovery records separate from decisions about whether a reply is appropriate.
A repeated result is not a second opportunity
A public post can appear in search, a repost and a later discussion. Counting each appearance as a new lead inflates the queue and can lead to repeated replies to the same person. Start with the original source. Keep discovery records separate from decisions about whether a reply is appropriate.
Choose a stable reference
Keep the original URL and any source-provided post identifier. A title alone is weak because different people can ask the same question. Tracking parameters may differ on links to the same item, but do not strip them blindly: some identify actual content or comments. Confirm the destination before combining records.
Preserve new information
Attach copies to one record instead of deleting the evidence immediately. Keep the author, date and reason each copy matters. A repost without added text may be redundant; an update saying the work is filled changes the result. A similar request from another author is not automatically a duplicate.
Check reply history separately
Record whether someone on your team already replied and link the actual reply if available. Reviewed does not mean sent. Before another response, check the current thread and community rules. Finding a new copy does not grant permission for another promotional message.
Measure requests, not search hits
Show discovered items, unique source posts and relevant requests separately. Keep inaccessible originals labelled unverified. This is a manual review method, not a claim that HeyKeyword automatically merges every network or sees private groups. Public indexed discovery is partial; a clean list still needs someone to understand the conversation.