Bilateral evidence profiles
Relationship studio
Compare two profiles through their documented relationships and shared records. An indirect connection is not evidence of a direct relationship.
Bilateral query
Build an exact profile-to-profile route
Declared bilateral profile
Google StatCounter Global Stats
All declared links / 3 hops- Shortest route
- 3declared hops
- Shortest paths
- 1deterministic routes
- Common neighbors
- 0exact intersections
- Packet edges
- 32 cited sources
- Official attributions
- 5
- Selected-layer neighbors
- 6
- Total neighbors
- 6
- Latest year
- N/A
- Access date
- 2026-07-17
- Selected-layer neighbors
- 9
- Total neighbors
- 9
- Latest year
- 2026
Supporting edge ledger
Every bridge remains an inspectable declaration
3 exact edges support the shortest paths and common-neighbor intersections in this layer.
Google Search appears in the Search engines source row for 2026 at 85.16%.
Search engine market share in United States of America, April 2023-April 2026 supports the profile's definition, observation, participant row.
Google's official product directory lists Search as a Google product.
Bilateral graph contract
A route is not a finding about its endpoints
Each hop keeps its own evidence label, confidence, source custody, and edge-specific limitation.
A bilateral atlas route preserves a sequence of declared edges for navigation and audit. A direct edge, common neighbor, or multi-hop path does not make the endpoints equivalent, establish ownership or control, assign liability, define an antitrust market, make unlike measures comparable, or show causation.
Reusable bilateral packet
Carry the exact route into analysis
JSON preserves endpoints, shortest paths, common neighbors, nodes, and edge metadata. CSV flattens the complete supporting ledger.