Can You See Likes on X? What Is Private and What You Can Check

Separate a count from a list of people

A total answers how many likes a post has. A list answers which accounts supplied them. A history connects one account to the posts it liked. Those are different datasets, even when a tool presents them together.

X’s private-likes announcement distinguishes your own likes and the people liking your own posts from other users’ liked-post history. A public number does not make the list behind it public.

Find your own liked posts

Sign into the account that liked the post, open your profile or account navigation, and look for the view containing your likes. Labels and placement can change between app versions, so your screen may not match an older guide.

If you remember the author or a phrase, searching public posts can be faster than scrolling a long personal list. Save particularly useful references in a separate research note with their URLs and the reason you kept them.

Evaluate a Twitter like viewer before connecting it

Ask the provider to explain the source: data you authorize from your own account, activity on posts you own, public counts, or an older stored dataset. These support different claims. Historical data does not establish a complete current view of a person’s private activity.

An API or analytics dashboard existing is not proof that every account’s history is available. Read the requested permissions and the provider’s explanation of coverage. If a tool cannot tell you what is estimated and what it actually saw, do not rely on it for research.

• What account or posts does the data belong to?
• When was it collected, and when was it last refreshed?
• Is the result complete, sampled, or inferred?
• Can you inspect the original post rather than only a dashboard label?

A worked example: a dashboard is not proof of a private history

Imagine a dashboard labels a founder as interested in onboarding software. It shows a follower count, a public reply, and a list headed engagement. Before using that result, ask which observation supports the label. The public reply might explain a real problem. The other fields may say nothing about whether they would buy.

If the provider says the label comes from older activity, record that date. If it says the result is inferred, keep the inference separate from observed behavior. You may still find the account worth reading, but you have not established what the person privately likes today.

Apply the same standard to your own research notes. Save the public evidence and the question it raises. Do not turn an ambiguous reaction into a claim that someone endorses a product or wants an unsolicited pitch.

Research customers through what they choose to publish

For founder research, public questions and replies often provide better context than a like would. Someone explaining why a workflow fails gives you the language, constraint, and use case. A heart alone tells you very little about intent.

Keep a small evidence table: the post URL, the problem in the person’s own words, and your interpretation in a separate column. Keeping what you saw apart from what you think it means stops a vague reaction turning into a made-up buying signal.

Search public posts by account, phrase, and date

Use your own post activity without overreading it

On your own posts, look for repeated relevant conversations, not just a growing total. A like may express agreement, appreciation, or a plan to return later. It does not by itself show that someone wants a sales message.

If a product post attracts questions from the people it was meant to help, answer those questions and improve the explanation. That teaches you more than trying to guess what strangers like in private.

For a weekly review, choose a few posts that produced relevant replies and record what readers wanted clarified. Group those questions by the underlying problem. One specific misunderstanding can supply a better next post than a long list of uncontextualized likes.

A useful stopping rule is whether you have enough public evidence to write a helpful response or test a content idea. If more dashboard exploration is not changing either action, return to the actual conversations.