Link Graph Encyclopedia

Foundations

The bow-tie structure

Seen from its largest strongly connected component, the web looks like a bow tie. Pages that reach the core sit on one side, pages the core reaches sit on the other, and stragglers hang off both.

In 1999 a team from AltaVista, IBM and Compaq mapped a crawl of 203 million pages and found that its connectivity had a shape. A giant core of pages all reach each other. An IN set of pages reach the core but cannot be reached from it, and an OUT set can be reached from the core but cannot get back. Drawn with IN on the left and OUT on the right, the picture looks like a bow tie. The model gives names to the parts of any directed graph relative to its largest strongly connected component, and those parts behave very differently under every ranking method.

CORE largest SCC IN reaches the core OUT reached from it tube: IN to OUT, bypassing the core tendril tendril disconnected
The bow-tie decomposition. Every node belongs to exactly one part, defined by whether it can reach the core, can be reached from it, both, or neither.

The parts

Let CC be the largest strongly connected component. Every other node falls into one part:

In the running example (see web graph) the core is {A, B, C}. D and E form IN, since both reach the core and nothing in the core reaches them. G is OUT. F is a tendril: E, in IN, reaches it, but F cannot reach the core.

Computing the decomposition

The decomposition costs a few linear passes:

  1. Find the strongly connected components and pick the largest, CC (Tarjan’s algorithm, one depth-first search).
  2. Run a breadth-first search forward from all of CC at once. Every node it reaches outside CC belongs to OUT.
  3. Run a breadth-first search backward, on the transposed graph, from CC. Every node it reaches outside CC belongs to IN.
  4. Search forward from IN and backward from OUT, skipping the core, to separate tendrils and tubes from the disconnected remainder.

Each search costs O(n+m)O(n + m), so the whole decomposition is linear in the size of the graph (see paths and distance).

How big are the parts?

The proportions depend heavily on the crawl:

Part Broder et al., 1999 crawl Meusel et al., Common Crawl 2012
Pages 203 million 3.5 billion
CORE 27.7% 51.3%
IN 21.3% 32.0%
OUT 21.2% 6.1%
Everything else (tendrils, tubes, disconnected) 29.8% 10.7%

Broder’s crawl gave four parts of nearly equal size, a striking symmetry that became textbook material. Thirteen years later, Meusel, Vigna, Lehmberg and Bizer found a core twice as large and a tiny OUT set in Common Crawl’s 2012 page graph. They argued that the proportions depend largely on how a crawl is gathered, so they describe the crawler as much as the web. The shape recurs; the sizes do not.

Common Crawl’s 2026 domain graph has a core of 30,219,288 domains, 25.2% of the total. Its 76 million domains with no recorded out-links cannot be in the core or in IN, so they must sit in OUT, the tendrils or the disconnected remainder. Most of them are domains the crawl saw only as link targets.

Why the parts matter for ranking

The fractal view

Each part of the bow tie, examined alone, often looks like a smaller bow tie. Dill and colleagues found the pattern in thematically and geographically defined subsets of the web soon after Broder’s study. The bow tie is less a fixed architecture than the generic shape of a directed graph built by many independent actors who link mostly to things that already exist.

References

Edit this entry on GitHub