All Pro Services · allproutah.com · v5 rebuild

New Site Map & Structure Rationale

The information architecture for the rebuilt site — a lean, restoration-focused structure that replaces today's 400-page site. Each major decision carries the reasoning behind it.

Brand direction Modern, clean, and restoration-focused · simplification over heavy dropdowns · reinforce operational activity, responsiveness, trust & local presence · established and credible, not corporate or "SEO-heavy."
~56
total pages (≈ half of the prior plan's 114)
13
service pages, restoration-first
21
local city pages + statewide
12
curated blog posts kept (of ~350)

The four structural decisions

How the site is organized — and why

These four calls frame the whole map. They hold regardless of visual design; wireframes build on top of them.

01 · URL scheme

Namespaced folders, keyword-rich slugs

Services under /services/, cities under /service-areas/, blog flat under /blog/, core pages at root.

Why: the folder structure maps 1:1 to the CMS content model, and the keyword still lives in the slug and page title.

02 · Local coverage

One page per city — no combo pages

~21 city landing pages, each covering all services and cross-linked to the 13 service pages. No "service × city" matrix.

Why: a city-by-service matrix would balloon to ~286 thin pages — the doorway-page sprawl the rebuild is escaping. Add specific combos later only if demand shows up in Search Console.

03 · Blog

Flat URLs + one pillar tag per post

12 curated posts at /blog/{slug}, each tagged to one service pillar.

Why: the tag powers hub-and-spoke linking — each post links up to its service page, and each service page lists its posts. 12 posts don't need a heavy category system.

04 · Navigation

Lean header, one light dropdown

Header carries a single light Services dropdown (restoration lines only); Service Areas is a plain hub link. Blog, Careers & Privacy live in the footer.

Why: direct response to the brand feedback — simplification over heavy dropdown navigation, with the header focused on getting a homeowner to call.

The hierarchy

Every page, in four branches

Home anchors the site; everything hangs off four branches. Colored top-bars mark the branch type; the emergency-amber accent flags what's foregrounded for an emergency-led business.

/
Home · emergency-led, call-first

Core & Utility

6
/ · root-level
  • About/about
  • Careers/careers
  • Project Gallery/gallery
  • Contact/contact
  • Privacy / Legal/privacy
About absorbs four old pages (management team, about-aps, culture, insurance). Careers & Gallery stay standalone — recruiting SEO and "show me your work" proof.

Services

1 + 13
/services · hub + detail
Restoration-first: only these lead lines appear in the header dropdown; specialty lines sit a tier down on the hub. All 13 pages are kept — this is about prominence, not scope.
Restoration & Emergency · lead tier
  • Water Damage Restoration/services/water-damage-restoration
  • Flooded Basement Cleanup/services/flooded-basement-cleanup
  • Commercial Water Damage/services/commercial-water-damage
  • Fire & Smoke Damage/services/fire-smoke-damage
  • Mold Remediation/services/mold-remediation
  • Sewage Cleanup/services/sewage-cleanup
  • Storm & Disaster Cleanup/services/storm-disaster-cleanup
Cleaning & Specialty · secondary
  • Air Duct Cleaning/services/air-duct-cleaning
  • Carpet Cleaning/services/carpet-cleaning
  • Hoarding & Biohazard Cleanup/services/hoarding-biohazard-cleanup
  • Asbestos & Lead Abatement/services/asbestos-lead-abatement
  • Reconstruction & Remodeling/services/reconstruction-remodeling
  • Janitorial Cleaning/services/janitorial-cleaning

Service Areas

1 + 22
/service-areas · map-led hub
Map-led "Areas We Serve," not a wall of keyword links. This keeps the full local footprint reading as local presence, not "SEO-heavy." One template, many records.
Salt Lake County · 11
midvalewest-valley-citymurray west-jordansouth-jordansandy draperrivertonmillcreek taylorsvillecottonwood-heights
Utah County · 5
provooremlehi pleasant-groveamerican-fork
Davis + other markets · 5
bountifulogdenpark-city tooeleheber-city
Statewide · 1
/service-areas/utah

Blog

1 + 12
/blog · index + posts
Kept for AI visibility: 7 of these are cited by Google AI / SearchGPT. Keep the question-style headings and FAQ blocks so those citations survive the rebuild.
  • Remediation vs. restoration AI/blog/remediation-vs-restoration
  • How long does restoration take (SLC) AI/blog/how-long-does-water-damage-restoration-take-slc
  • Cost of water damage restoration (UT) AI/blog/water-damage-restoration-cost-utah
  • Top water damage services AI/blog/top-water-damage-services
  • Filing insurance claims AI/blog/filing-water-damage-insurance-claims
  • How fast should remediation begin AI/blog/how-fast-should-water-damage-remediation-begin
  • Category 3 water damage AI/blog/category-3-water-damage-remediation
  • Rebuilding Draper Draper anchor/blog/rebuilding-draper-water-damage-restoration
  • Water damage emergency: what to do/blog/water-damage-emergency-what-to-do
  • Sump pump maintenance/blog/sump-pump-maintenance-prevents-flooding
  • Replacing subflooring/blog/when-to-replace-subflooring-after-water-damage
  • Dry fog mold removal Mold/blog/dry-fog-mold-removal

The cross-link mesh

Why "flat" isn't "sparse" — the depth runs sideways

The tree above is only two tiers deep by design. The richness isn't in nesting — it's in how the pages link across to each other. One service page's outbound links, below; this hub-and-spoke repeats for all 13 services.

CITIES SERVED RELATED POSTS Sandy Draper Murray West Jordan + 18 more cities Remediation vs restoration How long does it take Filing insurance claims Category 3 water damage + 8 more posts Water Damage Restoration ONE OF 13 SERVICE PAGES

One service page's outbound links. Multiply by 13 services — and every city page links back to all 13 — and the site is a web of ~600 contextual internal links, not a flat two-tier tree.

Where did the third tier go?

  • Sub-services became sections, not pages. Water extraction, structural drying, dehumidification, pack-out and the rest are now sections inside the Water Damage Restoration page — not ten thin child URLs. One authoritative page outranks ten that cannibalize each other's keywords, which is exactly the failure the audit found on the old site.
  • Shallow is the right default at this size. Every page sits within two clicks of home; deep nesting is for large catalogs, not a focused ~56-page site.
  • The one real tier-3 pattern is deliberately deferred. City × service combo pages (~286 of them) would reintroduce doorway-page sprawl — we add specific combos only if search demand shows up.
services ⇄ cities

Services ↔ Cities

Each service page lists the cities it serves; each of the ~22 city pages links to all 13 services. That mesh alone is ~570 cross-links — the local-SEO engine.

services ⇄ blog

Services ↔ Blog

Every post carries one pillar tag: it links up to its service page, and that page surfaces it under "related reading." Blog authority feeds the pages that convert.

city = local hub

Cities as local hubs

Each city page is a self-contained landing page — all services, a call CTA, local proof — so a visitor arriving from "[service] + [city]" search never hits a dead end.

Global navigation & components

What every page carries

The header is deliberately simple and call-first; the "operational, responsive, trustworthy, local" cues from the brand feedback live in shared components rather than extra pages.

Header

One light dropdown, no mega-menu — per brand feedback.

Services Service Areas Our Work About Contact (801) ···-···· 24/7 Emergency
Footer ▸ all 13 servicesall citiesAbout CareersBlogGalleryContactPrivacy phone · hours · Google profile

Trust & operational cues

Design-layer components, not pages.

  • Recent projects feed — pulls from the gallery · signals active crews
  • 24/7 response messaging + response-time framing
  • Est. 1987 · licensed & insured · certifications · reviews
  • Coverage map — local presence at a glance