Troubleshooting

“We couldn’t find your post” — what’s happening

Indexing lag is the usual cause. Here's how to tell, and the other things to check.

3 min readUpdated 2026-05-31

The verification step scans the sharer’s recent original tweets for the tracked link. About 90% of detection issues are one of these.

Indexing lag

X takes a few seconds (sometimes longer) to make a fresh tweet searchable. We retry once automatically after a short pause; if the second attempt also misses, the dialog asks the customer to tap I’ve posted — check now again.

The handle and the post don’t match

A customer with handle @alexwho posts from a different account won’t verify. The dialog catches this if the handle is mistyped.

The post is protected or deleted

We only see public posts. A protected account or a post deleted before verification will both fail.

A required mention or hashtag is missing

The dialog calls this out specifically — the customer edits and re-posts, then taps I’ve posted — check now.

The post is a reply or retweet

Verification scans original tweets only. Encourage the customer to compose a new post rather than reply to ours.

Didn’t quite get there?

Email a real person — we usually reply the same day.

support@sharecount.app