Treat the text match and the image match as two independent leads. Read the page where the text appears and the pages where the image appears, and note what each page actually states about attribution. Only note a connection if the same public page or an explicit public statement supports it. If the two leads never converge, write down the exact unresolved point and stop.
Find public social profile clues with our TraceSeek app.
Separate the text branch from the image branch
Begin by treating the two results as unrelated evidence until something in the public record links them. The text branch comes from recognized characters; the image branch comes from visual similarity. They answer different questions: what words appear, and where does this picture appear. Visual search results can include similar images and websites containing the image or a similar one, so a shared phrase or a similar photo is a lead to inspect, not a conclusion. Keep a separate note for each branch so a later observation in one does not silently overwrite the other. [Google Search Help: visual search and source-page results]
Inspect attribution on each public page
For the text branch, open the page where the text appears and check which account or page hosts the words. For the image branch, open the pages that contain the image or a similar one and note whether the image is credited, reposted, or used as illustration. Attribution is a property of each page. Two pages may both be public and still attribute the same text or image to different accounts, and that divergence is the finding to record rather than a conflict to force into one story. [Google Search Help: visual search and source-page results]
Record what each method can and cannot show
Text recognition confirms that characters are visible in an image; it does not authenticate who wrote them or when. Visual search confirms that a public page contains a similar picture; it does not confirm that the pictured person is the account operator, or that the picture is current. Live Text recognition is also not available in every region or language, so an absent text match may simply mean the characters were not recognized. Write these limits beside each observation so a reader does not mistake a retrieval result for proof. [Apple iPhone Guide: selecting text in photos and paused videos]
| observation | limit | next step |
|---|---|---|
| Text appears in the screenshot and on a public page | Does not show who authored or owned the text | Check the page hosting the text and note its stated attribution |
| A similar image appears on another public page | Similarity is not identity; the picture may be reused or illustrative | Note whether the page credits an account or treats the image as a repost |
| Two public pages attribute the item to different accounts | Public adjacency does not connect the accounts | Record both attributions separately and mark the link unresolved |
Do not join accounts from adjacency
A text result and an image result appearing together in one result set, or on pages that cite each other, is not evidence that the accounts belong to one person. Keep the branches unjoined unless a public page explicitly states the connection. Resist the temptation to build a single timeline out of two partial clues: that move converts two uncertain observations into a confident but unsupported claim.
Write unresolved and connected source notes
Use two short note types. An unresolved note states the observation, the page where it appears, and the precise reason it does not connect to the other branch. A connected note is best reserved for when one public page, or an explicit public statement, ties the text to the same account that hosts the image; quote or paraphrase that link. If it helps a later reader, jot the retrieval method and the date you checked, but treat that as optional note-keeping rather than a tracked field.
- Keep one line per branch: method, page, attribution, date checked
- Mark a note connected only with an explicit public link
- Mark everything else unresolved with the exact missing link
When the source is absent, private, or ambiguous
If the page behind a match is missing, requires a login, or attributes the item ambiguously, record that limit and stop. Do not attempt to reach a private account, identify anyone from a photo, or fill the gap with inference. A public photo or screenshot input can surface public-profile clues, but coverage is not guaranteed and no result proves current activity or ownership. Ending an unresolved note at the precise limit is a complete, honest outcome, not a failure of the search. [TraceSeek: product overview and operator-confirmed capabilities]
A couple more questions
If a screenshot's text appears on one public account and its image on another, are they the same person?
Not on that evidence alone. Text and visual matches are separate clues, and similarity does not establish identity. Treat the two accounts as unconnected unless a public page explicitly links them, and write the gap down as unresolved.
What should an unresolved note contain?
The observation, the public page where it appeared, the retrieval method used, the date checked, and the precise reason the two branches do not connect. That keeps the limit visible instead of hiding it behind a guess.
Does a similar image on a public page prove who the pictured person is?
No. Visual search shows that a page contains the image or a similar one; it does not verify the pictured person, authorship, or current use. Record it as a lead and keep the attribution question open.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
- TraceSeek: product overview and operator-confirmed capabilities ↗
- Google Search Help: visual search and source-page results ↗
- Apple iPhone Guide: selecting text in photos and paused videos ↗
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.