Site map

Site map — visual knowledge graph

Every dot is one of 695 articles. Lines are internal links. Clusters emerge from how topics actually relate, not from design. Drag to rearrange, click any dot to jump in.

The graph is a snapshot of how the site is wired internally. It exists for three reasons:

  1. Transparency — you can see what is here without scrolling through 695 article titles.
  2. Editorial integrity — orphan articles (zero incoming links) get visible; clusters that are over-internal-linked get visible; gaps between clusters get visible. The graph is a tool I use to find weaknesses in the site's wiring.
  3. Curiosity — it is interesting to watch the clusters form. The fact that coneflower-care has 49 incoming links and most articles have 0–2 tells you which pages are doing the heavy lifting of the site's authority.
Filter by hub:

Tip: Larger dots are articles with more total internal connections. The pull of the force layout naturally arranges them so closely-related topics cluster near each other.

## How to read it - **Dot size** = total connections (incoming + outgoing internal links). Big dots are the site's authority anchors. - **Line thickness** = always uniform; we are not weighting edge strength here. - **Color** = hub the article belongs to (see legend above). Articles cluster by hub because they tend to link to others in the same hub. - **Position** = emergent from the force-directed layout, not designed. Articles that link to each other pull together; articles that don't push apart. ## What the graph is good for - **Finding orphans** — search the graph for tiny isolated nodes. Those articles are not pulling internal-link weight and may need updates that link to them. - **Finding authority hubs** — the big nodes at the center are the articles your other content trusts most. They should be your most-polished pieces. - **Finding bridge articles** — nodes that sit between hub clusters often connect different topics. They are valuable for site-wide topical authority. - **Spotting overcrowded clusters** — when a cluster gets too dense, articles inside it start cannibalizing each other for the same keyword. That is a signal to consolidate or de-emphasize. ## Build details The graph regenerates every time the site builds. Source: every published markdown file in `content/guides/`. Nodes are articles, edges are internal hyperlinks. Articles staged for future release (the `release_after` frontmatter field) are excluded — the graph reflects what is actually visible to Google. Built with [D3 force simulation](https://github.com/d3/d3-force). No analytics, no tracking, no server calls — everything runs in your browser. The graph JSON is at [/site-map-visual/graph.json](/site-map-visual/graph.json) if you want to inspect or reuse it.