A Step-by-Step OSINT Guide

The Problem

A public official declares a project complete. A witness describes a route that no longer exists. A document claims land use that satellite images contradict.

You can verify all of it — from your desk, for free, right now.

Satellite and street-level tools are not navigation software. They are forensic archives. Used correctly, they produce hard evidence that challenges institutional narratives, validates testimonies, and documents changes that official records ignore.

What This Method Does

It turns visual geography into verifiable proof.

Three inputs: a claim, a location, a time frame. One output: confirmation or contradiction, documented with spatial data.

No coding. No subscriptions. No field access required.

Step-by-Step Execution

Step 1 — Define the claim you’re checking

Be precise. “The building was completed in 2018.” “This road was accessible before 2020.” “This land was green space.”

Write it as a falsifiable statement before opening any tool.

Step 2 — Open satellite view, set the location

Go to Google Earth (desktop version for full historical access). Type the location. Switch to satellite view.

Do not rely on the default current-date image.

Step 3 — Activate the historical timeline

In Google Earth Pro, drag the timeline slider backward. The archive goes to 1984 in most areas. Urban zones have more coverage than rural ones — factor that into your confidence level.

Look for changes in structure, land cover, and infrastructure. Compare the official claim date against what the satellite actually shows.

Step 4 — Switch to street-level view for ground detail

Drop into street view. Navigate to the specific location. Click “See other dates” to access the historical archive.

This layer captures what the satellite cannot: road signage, building facades, vehicle access points, surveillance camera positions, pavement type.

Step 5 — Identify fixed reference points

Fixed points are elements that do not change: mountain profiles, bridge structures, road curves, architectural details, permanent signage.

Identify at least three. These become your forensic anchors — the elements you cross-match against photos, documents, or testimonies you’re verifying.

Do not proceed with fewer than three confirmed fixed points. One or two create ambiguity. Three create verifiable correspondence.

Step 6 — Measure what matters

Use the ruler tool to calculate distances and surface areas. This is not cartographic decoration — it’s operational data.

A measurement tells you whether physical claims are geometrically possible. If a document says a building was constructed in a certain footprint, the satellite measurement either confirms or contradicts it.

Step 7 — Cross-check with a second platform

Google Maps has a documented urban bias. Rural paths, unpaved roads, and elevation data are often incomplete or absent.

For those environments: switch to OpenStreetMap. For elevation and slope data on unmapped terrain: activate the cycling layer or the fuel efficiency setting on mobile. Both force the system to calculate elevation indirectly.

Step 8 — Document everything with timestamps

Screenshot each satellite date used. Record the URL or coordinates. Note the date range of each Street View capture.

Your evidence chain depends on the reproducibility of what you found. If you cannot direct someone else to the same image at the same date, the evidence is incomplete.

Common Mistakes

Trusting the default view. The current-date image is rarely the one you need. Always go to the historical archive first.

Using one fixed point. A single architectural match is a coincidence. Three is correspondence. Fewer than three: do not publish.

Pattern completion bias. Your brain fills in partial information automatically. A partial sign that reads “ROMAN…” is not confirmed as “Romano.” Verify every character, every detail, manually. Do not let visual intuition substitute for cross-matched data.

Ignoring platform limitations. Google Maps fails on rural terrain. Satellite timestamps in low-coverage areas may span years. Know the gap before claiming precision.

Practical Application

You receive a document claiming a publicly funded construction project was finished and operational by a specific year. The budget has been fully disbursed.

Open satellite view. Navigate to the site. Set the timeline to that year. If the satellite shows an open construction site or an empty lot — that is your evidence of a reporting discrepancy.

Cross it with Street View for ground-level confirmation. Measure the footprint with the ruler. Screenshot both views with timestamps.

You now have a three-layer verification: document claim, satellite contradiction, ground-level confirmation.

What You Get

A reproducible evidence package: spatial data, timestamps, cross-platform confirmation, and a documented chain linking visual proof to the original claim.

This is admissible in editorial fact-checking, publishable as supporting documentation, and resistant to counter-narratives that rely on verbal denial alone.

One Rule to Keep

Every hypothesis produced by automated tools — reverse image search, AI pattern recognition, map suggestions — requires manual validation against at least three independent fixed points.

Automation finds the lead. Verification closes it.