Consumer Site Architecture  /  Schematic

Top Tier Strategies

How the nationwide directory is structured to rank: two intersecting silos, with contractor mini-sites as the unique-content engine that keeps every page real instead of templated.

DocW-3 v0.3
StatusDraft
LaunchDFW
StackAstro / CF

Structural schema. This drawing shows the pages and how they link, not the final visual design. The full brand system (color and type) is still in progress.

Page Map & Internal Linking

/ Homepage branding + trust /services/ services hub /{st}/ state hub /blog/ content hub /about · /how-it-works /financing · /legal · trust TOPICAL AUTHORITY /services/{service}/ national service page /{st}/{city}/ city hub: contractor list UNIQUE-CONTENT ENGINE /pros/{contractor}/ contractor master profile MONEY PAGE /{st}/{city}/{service}/ ranks "roofer in Dallas" /{st}/{city}/{contractor}/ contractor in this city /credentials · /work · /reviews mini-site sub-pages (real photos, reviews) Service silo Geography silo Authority + trust Contractor mini-site

Worked example · one contractor across the metro

The same structure, filled in for a real member. This is what the directory generates for one contractor, and where he appears the moment his mini-site goes live versus where he earns a standalone page.

Joe's Plumbing and HVAC

/pros/joes-plumbing-and-hvac/ Trades: Plumbing, HVAC Service area: DFW metro, north to Sherman Cities declared: 8

Where Joe appears

CityIn city rosterOwn city page
Dallas~1.3MListedPage live
Fort Worth~956KListedPage live
Arlington~394KListedPage live
Plano~286KListedPage live
Frisco~220KListedPending
McKinney~207KListedPending
Denton~148KListedPending
Sherman~46KListedPending

He is listed in every city he declares the moment his mini-site goes live, so he shows up in the local results right away. A standalone city page publishes only once he has one real local proof there: a completed job with photos, or a review from that city. Cities order by population, highest first.

The URLs he generates

/ homepage │ ├─ SERVICE SILO/services/plumbing/ national authority · lists Joe in TX │ /services/hvac/ national authority · lists Joe in TX │ ├─ GEOGRAPHY SILO/tx/ state hub │ ├─ /tx/dallas/ city hub · Joe in roster │ │ /tx/dallas/plumbing/ money page · Joe listed │ │ /tx/dallas/hvac/ money page · Joe listed │ │ /tx/dallas/joes-plumbing-and-hvac/ ● PAGE LIVE │ ├─ /tx/frisco/ city hub · Joe in roster │ │ /tx/frisco/plumbing/ money page · Joe listed │ │ /tx/frisco/joes-plumbing-and-hvac/ ○ PAGE PENDING │ └─ /tx/sherman/ city hub · Joe in roster │ /tx/sherman/joes-plumbing-and-hvac/ ○ PAGE PENDING │ └─ CONTRACTOR MINI-SITE /pros/joes-plumbing-and-hvac/ master profile · flat entity hub ├─ /pros/joes-plumbing-and-hvac/credentials ├─ /pros/joes-plumbing-and-hvac/work ├─ /pros/joes-plumbing-and-hvac/reviews └─ /pros/joes-plumbing-and-hvac/blog/

Both Dallas money pages link to his one city page

/tx/dallas/plumbing/ money page, lists Joe /tx/dallas/hvac/ money page, lists Joe /tx/dallas/joes-plumbing-and-hvac/ his one city page
Why the master profile stays flat. /pros/joes-plumbing-and-hvac/ is Joe's one entity hub: it collects his backlinks, anchors searches for his name, and lists his full service area. It is not nested as /pros/hvac/tx/dallas/... because Joe runs two trades across eight cities, so no single trade or city owns that URL, and keywords stuffed into the path are a negligible ranking signal. The "plumbing in Dallas" relevance lives where it belongs: on /tx/dallas/plumbing/ (where he is listed) and on his live city page /tx/dallas/joes-plumbing-and-hvac/. The geography pages do the local ranking; the master profile is home base.

Reading the diagram

Solid line: navigation and hierarchy (top to bottom)
Dashed amber: authority and cross-links (service authority into money pages, blog links down, contractor pages back to the master profile)
Service silo (national topical authority)
Geography silo (state, city, city + service)
Contractor mini-site (the unique content that makes pages real)
Authority + trust (blog, about, financing, legal)

URL patterns

/  homepage
/services/{service}/ national service page
/{st}/ state  ·  /{st}/{city}/ city
/{st}/{city}/{service}/ money page
/pros/{contractor}/ master profile
/{st}/{city}/{contractor}/ contractor in city
/blog/{slug}/   /about   /financing

State as 2-letter code (/tx/), never spelled out. No trade baked into the city slug.

01

Real data, not templates

Each contractor's own specialties, photos, credentials, and reviews make every page unique. That is what survives Google's 2026 crackdown on mass-produced pages.

02

Money pages win local search

The city + service page is where "roofer in Dallas" searches land. It lists every qualifying contractor in that city, drawing authority from the national service page above it.

03

No empty pages, depth first

A contractor is listed everywhere he serves right away, but his own city page publishes only on real local proof there. Launch Dallas-Fort Worth fully before opening new markets. Thin nationwide pages get buried.

04

Clean crawl, no bloat

Only real pages get indexed. Filters and sort orders stay as on-screen tools, not separate URLs, so search engines spend their budget on the pages that matter.