Signals
How to monitor competitors on X without trusting search snippets
Discovery and verification are different jobs. Search can find a candidate post; the native post or API should establish who published it and when.
Verify the handle
Check whether the official site links to the account and whether the account links back to the company. For a founder, corroborate the current company relationship through the company site or another reliable public profile.
A verification badge alone does not prove the relationship you care about. Save the evidence used for the match.
Use native fields for dates
Search engines can surface old posts beside current results and snippets can omit context. Store the platform post ID and created_at field when available. The native URL gives reviewers a direct route to the record.
Keep capture time separately. A post published last year but first captured today is not a new competitor move.
Separate original posts, replies and reposts
Replies can reveal product and customer context, but they should not be presented as formal company announcements. Reposts show amplification rather than authorship. Label the post type so the reader understands the evidence.
Control cost and request volume
Poll only active, verified accounts and request posts since the last successful cursor. Cache identity resolution and back off when nothing changes. This is cheaper and more reliable than repeating broad searches for every company.
Working checklist
Use this in the next review.
- Corroborate the company-person-account relationship.
- Store post ID, author ID, native URL and created_at.
- Keep publication and capture times separate.
- Label posts, replies, quotes and reposts.
- Use incremental cursors and cache verified identities.