Tools · Ethical OSINT and privacy self-defense · 18 / 25
A search snippet is not the live page
A search result card is the engine’s snippet and a link. The live page is what you fetch. Write the card and the fetch separately, and do not file a snippet as the current document.
The card is the engine’s copy
A result card shows a title, a URL, and a short snippet the engine chose. That text is what the index stored when it last crawled. It can quote a sentence that is no longer on the page, or a file that now returns an error. The card is a lead. It is not the document.
The date on a card, when one appears, is the engine’s date. It is not the day you looked, and it is not automatically the day the organization published the file.
The page is the response you get
Open the URL, or request it, and record the status and the time. A 200 with the body you saved is the live page. A 404 or a login wall means that URL did not give you the document the snippet described. Write the status. Do not paste the snippet into the finding as if the fetch had succeeded.
This check is for your own site or an organization that authorized the review. You are confirming what your pages still show, not collecting a stranger’s documents from a search.
What to write down
File the query only if you need to repeat it, the card’s title and snippet labeled as the card, the URL, the status, the UTC time of the fetch, and a short quote from the body if the status was 200. If the body and the snippet disagree, keep both and say which one is current.
Lab: a card that still names a retired note
On a lab domain you control, a result card titled “Lab closure note” snippets the sentence “The lab closes on Friday.” The URL https://example.org/lab-status returns 404 when you fetch it on 2026-11-03. A draft says the closure note is still public because the card shows it.
The note quotes the snippet as the card and the 404 as the fetch. The closure sentence is not filed as a current page. The follow-up, if the organization wants the card gone, is to ask the engine to recrawl after the page is gone, which is a separate request. The finding itself stops at the disagreement.
card title: Lab closure note snippet: The lab closes on Friday url: https://example.org/lab-status fetched: 2026-11-03T11:05:00Z status: 404 write: card and 404 not: the note is still public
Diagram
The result card and the fetch
Only the fetch is the page you can cite as current.
Holds. Title, URL, and a snippet
Time. The engine’s crawl, if shown
Does not. Prove the body is still there
Holds. Status and the body you saved
Time. When you requested it
Use. When you say what the page shows now
Check yourself
1. A result card quotes a sentence. What is that sentence?
2. The URL from the card returns 404. What may the finding say is public now?
3. The body you saved and the snippet disagree. What do you keep?