feat(seo): enhance local SEO architectures and GEO layout structures for multi-location landing pages

### Rationale
As we scale our Next.js 15 App Router applications from single-tenant SaaS starters (like DannFlow) into local service platforms and marketplaces (like AttyJuan.ai or multi-location businesses), our current SEO baseline is missing critical signals required for Local Search Map Packs and Generative Engine Optimization (GEO/AI Overviews).

To ensure search bots and LLM search agents (Google AI Overviews, Perplexity) crawl, understand, and surface our landing pages, we need to implement granular local routing protections, strict responsive asset pipelines, and AI-extractable layout patterns.

### Checklist / Requirements

#### 1. Advanced Local Structured Data (JSON-LD)
- [ ] Migrate local dynamic routes away from generic `Organization` schema to specific `LocalBusiness` subsets (e.g., `AutoDetailing` for automotive, `LegalService` for law-related modules).
- [ ] Ensure all local routes inject a complete NAP-G data array:
- `name`
- `address` (with structured `PostalAddress` including `postalCode` and `addressRegion`)
- `telePhone`
- `geo` (`GeoCoordinates` with absolute `latitude` and `longitude` strings)
- `openingHours`
- [ ] Implement site-wide breadcrumb tracking via `BreadcrumbList` structured data matching the actual URL pathing hierarchy to build geographical topical authority.

#### 2. Dynamic Route Canonical Protections
- [ ] Audit dynamic route folders (e.g., `app/locations/[city]/page.tsx`). Replace static `metadata` exports with async `generateMetadata` handlers.
- [ ] Dynamically construct `alternates.canonical` matching the incoming runtime params to prevent self-referencing duplicate loops across multi-location landing variants.

#### 3. Generative Engine Optimization (GEO) Layout Patterns
- [ ] Introduce structural layout zones optimized for AI extraction models. Each high-intent local page must contain at least one Question-Heading (`

`/`

` utilizing *What, How, Where, Why*) mapped directly to a tightly-scoped paragraph block (40–60 words).
- [ ] Enforce high-density structural components (HTML ``, `

`, `
`) for complex local details such as localized pricing brackets, service checklists, and regional boundary coverage.

#### 4. Core Web Vitals Optimization for Local/Mobile
- [ ] Audit custom image renderings on landing pages. Every `next/image` component displaying localized showcase assets must implement a responsive `sizes` attribute string to prevent oversized desktop payloads over local mobile networks.

### Proposed Implementation Path
1. Create dedicated types/schemas for local business definitions in `src/types/schema.ts`.
2. Update the Claude `/seo-check` and `/seo-fix` instructions to natively check and patch these constraints.
3. Execute `/seo-fix all` on target sub-routes to build out compliance baselines.