Library hub pattern

01Why this matters

1. IS its own ranking surface — Google sees a curated category page with internal mesh density (link-gravity doctrine). Hub pages outrank leaves for category-level queries. 2. IS a category-CTA surface — "Got a translation gap?" / "Got a pattern that bleeds quietly?" / "Got a question that deserves a realtime answer?" — domain-specific Text PJ asks beat the generic homepage CTA. 3. IS the nav-up surface — visitors landing on any leaf shareable can navigate UP to the library, then sideways to siblings. Lifts session depth + page views + return visits. 4. DOESN'T rewrite any leaf — the library is purely additive. Existing shareables stay exactly as they are. The compound was already there; the library just makes it legible.

02How to apply

Read the doctrine. Apply it on the next ship cycle.

03The closer

2026-05-05 PJ-validated ("sooooo good sooo simple crazy"). When 5+ shareables share a cluster, ship a library hub page that indexes them. Cost ~1hr per library, s hub-page SEO weight + category CTAs + navigability + cross-library mesh. Doesn't rewrite any leaf.

04Text PJ — no Calendly, no meeting