Read-only local campaign artifact

website-architecture.md

direct-seo-wave-39/website-architecture.md

# Website Architecture Candidate

## Status: PARTIAL

### Boundary

This is a proposed information architecture based on retained homepage labels, not a claim that routes exist or that a redesign is approved. Keyword volume, difficulty, current URL paths, CMS, hosting, theme, components, analytics, and service-area scope are not available.

## Proposed local-service IA

```text
Home
+-- Services
|   +-- Residential Cleaning
|   +-- Deep Cleaning
|   +-- Move In/Out Cleaning
|   +-- Airbnb Cleaning
|   +-- Commercial Cleaning
|   +-- Office Cleaning
|   +-- Medical Facility Cleaning
|   +-- Window Cleaning
|   +-- Pressure Washing
|   +-- Emergency Cleaning
|   +-- Green Cleaning
+-- About
+-- FAQ
+-- Blog
+-- Contact / Request Estimate
+-- Legal
    +-- Privacy
    +-- Terms
```

The service list mirrors labels present in retained text only. It does not establish that every named service is currently offered, should have its own URL, or is within the approved brand scope.

## Proposed URL conventions

| Page type | Candidate path | Decision needed |
|---|---|---|
| Homepage | `/` | Preserve if current canonical host/redirect policy confirms it |
| Service hub | `/services/` | Confirm whether the existing site has a real hub page |
| Service page | `/services/{service-slug}/` | Confirm routes, scope, and cannibalization before creation or changes |
| About | `/about/` | Confirm live route |
| FAQ | `/faq/` | Confirm live route and visible FAQ ownership |
| Blog | `/blog/` | Confirm content strategy and existing archive behavior |
| Contact | `/contact/` | Confirm form, tracking, privacy, and routing requirements |

## Content and component boundaries

| Layer | Candidate responsibility | Evidence needed before implementation |
|---|---|---|
| Site shell | Header, footer, navigation, contact CTA | Current theme, mobile behavior, approved brand assets |
| Service template | Single service intent, supporting FAQs, related links, estimate CTA | Approved service details and unique page content |
| Trust module | Licensure/insurance/process information | Documentary substantiation and legal approval |
| Testimonials/reviews | Third-party or customer proof | Source, permission, and profile-policy review |
| Local entity module | Name, address, phone, hours, service-area facts | Verified NAP and Google Business Profile/CMS facts |

## Technical architecture decision gates

| Area | Candidate | Current state |
|---|---|---|
| CMS/theme | Keep existing WordPress implementation unless a measured limitation requires change | Unknown; do not recommend migration |
| Mobile system | Mobile-first responsive QA at 320, 640, 768, 1024, 1280, and 1536px | Needs current visual inspection |
| Performance | Optimize actual LCP image, fonts, scripts, cache, and third-party tags after measurement | Needs CWV/lab capture |
| SEO foundation | One H1, semantic landmarks, canonical, sitemap, robots, JSON-LD, OG | Needs live DOM and headers |
| Security | Headers, plugin/theme lifecycle, backups, least privilege | Needs hosting/CMS evidence and authority |
| Deployment | Stage, test, approve, then publish | No CMS/hosting authority supplied |

## Acceptance gate

Approve a route map only after a fresh crawl, service/offering signoff, keyword/intent research, current URL inventory, measurement baseline, and written owner approval. No redirect, page creation, theme change, schema deployment, or hosting change is authorized by this candidate.