Location Page Program¶

Status: Active (ongoing build + QA) Project: Website · SEO

What this is¶

The firm's program of building and maintaining individual landing pages for every Kentucky city the firm wants to rank in. Each location page targets "Louisville-adjacent + rural KY" metros with localized crash data, dangerous roads, insurance comparisons, FAQs with JSON-LD schema, and city-specific CTAs.

By April 2026 the program had grown to 18+ location pages with structural audits, hero image fixes, cross-linking, and template normalizations as recurring maintenance. The template itself was restructured mid-program from a single wp:html wrapper to a 3-layer native Kadence block (cover hero + sidebar column + body) — which kicked off a wave of repair work on earlier pages that used the old structure.

Template structure (post-April 2026 restructure)¶

Each location page is now built as three Kadence layers: 1. wp:cover hero — full-width, city-specific .webp image, 70% dim, theme-palette2 navy overlay, centered H2 "{City} Personal Injury Representation" in the "larger" font size preset 2. Sidebar column — localized stats, attorney cards, phone CTA 3. Body — content blocks with localized crash data, dangerous roads, FAQ accordion, trust badges

Brand rules applied: - Colors: #0B212D primary, #F89C22 orange accents only (never background), #5D5D5D body text, #F5F5F5 light backgrounds - No dark backgrounds with light text - All content checked against the banned word list - Bigger Share Guarantee banner, no specific fee percentage stated

Build + deploy pipeline¶

Content build: parallel subagents, each handed a city's research pack (KYTC/KSP crash data, dangerous road segments, insurance comps, 8-Q FAQ with JSON-LD)
Deployment: WordPress REST API via Craig Aguiar / App Password, Chrome User-Agent header required to bypass Cloudflare
Parent page: /locations/ (WP page ID 30757)
Template: blank (no Kadence template applied via API)
SEO: RankMath REST API endpoint, objectType: "post" even for pages (RankMath quirk)

Recurring issues¶

Hero background images kept going missing after Kadence updates — multiple troubleshooting sessions needed
wpautop bug caused <p> tags to wrap blocks and break layouts; mitigated via page settings, not a true fix
500 errors on specific pages (e.g. Lexington, Oldham) usually traced to corrupt block JSON from REST API inserts
7 pages broken + FAQ lost in one April 6 incident — recovered via restoration from earlier deploy logs
Cross-linking drift — new location pages weren't added to the hub index automatically; a batch pass added all 18

Key decisions¶

Restructure early pages to match the new 3-layer template rather than maintaining two parallel templates. Called out in the "10 Location Pages" session.
35% fee removal across all 42 location pages — the contingency fee percentage was stripped sitewide in a single batch to align with the Bigger Share Guarantee positioning.
Protected pages rule — location pages with Sam's manual post-deploy edits are marked as protected and skipped by batch deploys.
Noindex decision on Louisville is still pending — flagged in the April 4 sitemap health check as a judgment call.

Active gaps (as of last audit)¶

17 location pages were flagged missing from sitemap in March — resolved by the sitemap audit completion pass
Leitchfield sitemap gap still open (flagged April 4)
Florence post grid fix needed (April 8)
Construction Accident page 404 fixed as part of Bardstown rewrite