2026-07-30 — Sitemap split into a master + generated exports (for the GoHighLevel website page): this file moved to Foundation/Sitemap/ and is now the master and single source of truth — the only file to edit. A build step (build.py) parses it into sitemap.html (body fragment for the GHL Custom Code element), sitemap.css, sitemap.js, and preview.html; those four are generated and must never be hand-edited. The build converts all inline handlers to addEventListener bindings (GHL strips inline handlers) — 211 stopPropagation guards collapse to one delegated listener, and 6 data-act + 1 data-act-input are bound from a whitelist. Publishing is manual: GHL's public API is read-only for site pages (websites share the funnels endpoints, which expose zero write operations), so the exports are pasted into the builder or driven through the UI. Deployment steps: Foundation/Sitemap/GHL-DEPLOY.md.
2026-07-16 — Phone System Repair cluster added (source: Chris Duncan's June email thread + July 16 keyword pull): new sitewide page /phone-system-repair/ (fix-or-replace intercept; SoundCurve never repairs — every call converts to a same-cost replacement, and the page says so honestly, with cited Mitel/Avaya/Panasonic/Nortel decline facts). Three GBP services added to all four profiles under Telephone Company (Phone System Repair & Replacement · Phone System Technician · Legacy PBX Replacement), covered by ONE local service page per location (variant consolidation per Master 02): Encino in the TC Add set, other locations queued for phase 2. Full spec + copy: Content/Phone_System_Repair_Page_Plan.md + mockup. Do-not-chase note: "mitel support"/"avaya support" are navigational.
2026-07-16 — Group order standardized: within each category, action groups now read Keep → Add → Drop & Redirect.
2026-07-16 — One redirect group (Christian): the separate "301 → service page" and "301 → category page" groups collapsed into a single Drop & Redirect group per category — one operation, one group. Each line item's badge states the target type (301 → SERVICE, blue = intent-equivalent service page, target must cover the term · 301 → CATEGORY, red = category parent, topic exits the site). The location-level drop group is gone; its four pages redistributed into their categories' groups (SP 7, TC 5, ES 3).
2026-07-16 — Redirect semantics (Christian's pushback, adopted): "Merge"/"Drop" implied content operations that don't happen — every one of these is a redirect. Labels renamed to say what's real: 301 → SERVICE (redirects to an intent-equivalent service page, which must cover the redirected term) and 301 → CATEGORY (redirects to the category parent; the topic exits the site). Line items now read "301 to X" instead of "merge into X." Company Directory moved to the 301 → CATEGORY group where it belongs (its target is the primary category page), with the feature-bullet coverage note attached. No copy is ever ported in either operation.
2026-07-16 — Decided pages regrouped; map de-noised: Enterprise Networking Solutions, Telecom Project Management, and Data Center Solutions moved from Keep to the Drop group (each 301s to its category page when executed); Company Directory moved to Merge (→ primary category page; it's a phone feature, covered as a feature bullet — its off-pattern slug is thereby mooted). The 12 projected copies of these four at McMinnville/Walnut/Chico were deleted from the build map (do-not-build, recorded here). All long resolution notes stripped from leaf entries per convention — badges + short notes on the map, full rationale in this log. Cross-category merges now say so on the line item (Cloud Telephony → Cloud Phone System in Telephone Company; Contact Center → Call Center in Telephone Company; PBX Installation → Hosted PBX in Service Provider Add set; Smart Office → Telephony Integration in Telephone Company; IP Phone Installation → IP Phone Systems in Equipment Supplier). Group counts recomputed.
2026-07-16 — Merge protocol (DECIDED): none of the merging pages rank or carry traffic (June + July data), so there is no equity and no proven copy worth porting. Rule: 301 always; port no copy by default. Before closing each merge, check whether the target page covers the merged term; if not, add a sentence or H2 covering that keyword variant on the target (per Master 02's variant-coverage practice). The merged page's content itself is thin AI-era copy and dies with the URL. Clarified same day: functionally every merge/drop is "page dies + 301" — the labels only encode the redirect target (Merge = intent-equivalent sibling, which must cover the term; Drop = category parent, term exits the site). GBP consequence: to preserve the service↔page 1:1 rule, merged AND dropped service entries come off the Encino GBP at consolidation (~42 → ~31 services + the 4 new AI entries, still above the Core30 20–30+ target).
2026-07-16 — Encino slug deviations (RESOLVED, moved off the map): two Encino slugs were off the Core30 pattern. June + July data confirm neither URL ranks, so 301s are safe. Call Monitoring: 301 /call-monitoring-services-in-encino-ca/ → /call-monitoring-in-encino-ca/ at the next build touch. Company Directory: mooted — the page is DROPPED in the consolidation (feature, not service).
2026-07-16 — Title-tag rule for primary category pages (DECIDED, moved off the map): keep the title as primary GBP category + city per Core30 — Telecommunications Service Provider in Encino, CA (exact match), with the money term appended as context words: … in Encino, CA | Business Phone Systems & VoIP. The H1 = city + descriptive, led with commercial phrasing: "Encino Business Phone Systems & Cloud VoIP." The high-demand "business phone systems [city]" query is captured in the Map Pack via GBP category relevance + title context words + service-page copy + the national homepage — NOT by overriding the category title. Apply this pattern to every location's primary category page (McMinnville, Walnut, Chico) when built.
2026-07-16 — Relevance flags resolved with Christian: DROP Enterprise Networking Solutions, Telecom Project Management, Data Center Solutions (not SoundCurve services; data-center is a customer vertical at most), and Company Directory (feature, not service — merge + feature bullet, slug deviation mooted). Applied across all four locations (Encino live pages → drop in consolidation; projected pages at McMinnville/Walnut/Chico → do not build). KEEP Telecom Hardware Sales — confirmed, SoundCurve sells/rents VoIP devices. Encino slug-deviation flag resolved (Call Monitoring 301 at next build touch; Company Directory mooted). Title-tag note relabeled as the decided rule. Document reorganized into Site Map / Log tabs.
2026-07-16 — Four AI-answering GBP services added to all four profiles (AI Receptionist, AI Answering Service, Virtual Receptionist, After-Hours Answering); per Core30, 16 matching service pages joined the build map: 4 in the Encino Add set (group now 6 pages), 4 each as ADD + NEEDS CREATION under the McMinnville, Walnut, and Chico primary categories, each linking up to the sitewide /ai-receptionist/ page.
2026-07-16 — Page-fate updates from the industry/AI rebuild plan: Legal re-slugs to /law-firm-answering-service/ (301 from /legal-voip-service/; targets the legal answering/intake keyword cluster); Healthcare re-slugs to /hipaa-compliant-phone-system/ (301, exact-match keyword); /call-ai/ marked MERGE — 301 into /ai-receptionist/, content absorbed as the "After every call" section; /ai-receptionist/ marked KEEP as the absorbing rebuild (title adds "AI Answering Service"). Builds due 2026-07-31, before the Aug 3 social cycle.
2026-07-15/16 — Oregon consolidation confirmed and specced: Yamhill + Marion county pages 301 into the McMinnville anchor (/voip-phone-service-mcminnville-or/), plus the thin /location/ McMinnville city page; Oregon GBP website field repoints after publish. Homepage repositioned to "fully managed" (business phone systems umbrella keyword). Full specs in Content/.
2026-06-18 — Document created: every page reconciled live against the three sitemap.xml files and the GBP category→service taxonomy (211 live, 135 to create). Encino confirmed 1:1 with its GBP (3 categories + 42 services); Keep/Merge/Add action groups added per the Encino service-page SEO analysis, nested inside each category.
Convention: log every structural change here AND in TRACKING.md. This log is the page-level record; TRACKING is the workspace-level record.