Lula — ICP traffic roadmap (Q2-Q3 2026)

12-week execution plan to grow ICP organic traffic. Replaces the prior open-ended content production cadence with a focused 4-play strategy.

Strategic context

The v2 comprehensive audit (2026-04-23) found a 23% hit rate on published ICP content — 8 of ~35 URLs ranking meaningfully. The constraint is not content volume; Lula has shipped ~30 articles in 6 months. The constraint is content-to-query fit + structural issues (soft 404 hub, brand-led titles, entity recognition).

This roadmap stops new content production on tangential topics and concentrates effort on 4 plays that compound:

1. Make-Ready cluster expansion — compound on the only proven flagship
2. Ship + activate the drafted hub landings — unlock existing zero-ranking spokes
3. Sitewide "Lula" entity disambiguation — fix foundational entity-recognition issue
4. PMS integration page refresh — capture high-intent commercial demand

Everything else is deferred. See "What we're NOT doing" below.

12-week sequencing

Phase 1 (Weeks 1-4: 2026-04-28 → 2026-05-23) — Ship drafted assets + start make-ready cluster

Outcomes by end of Phase 1:

• /work-order-software-for-property-management LIVE (soft-404 fixed)
• /predictive-maintenance-software LIVE
• /lumi LIVE if Nate unblocks (May 8 deadline)
• 2 make-ready spokes published
• Make-ready downloadable lead magnet shipped
• Entity disambiguation applied to top 5 pages
• /articles/foresight-property-maintenance-software title rewritten

Week 1 (2026-04-28 → 2026-05-02)

• Send both hub drafts to Nate for sign-off (predictive-maintenance + work-order)
• Draft make-ready spoke #1: "Make-ready checklist for apartment turnovers"
• Build downloadable PDF of the make-ready checklist
• Apply Lula entity disambiguation to top 5 pages: /, /foresight, /services, /articles/what-is-a-make-ready, /articles/best-property-management-maintenance-software
• Dashboard Phase 1: scaffold + deploy with Sections 1-3 manual data, send link to Nate Monday (vibe-coding time, parallel workstream)
• Friday check-in with Nate

Week 2 (2026-05-05 → 2026-05-09)

• Make-ready spoke #1 publish + GSC submit
• Draft make-ready spoke #2: "How long does a make-ready take?"
• Rewrite /articles/foresight-property-maintenance-software title + H1 + meta to commercial query
• Ship work-order soft-404 fix (Nate handles deploy)
• LuMi: if unblocked, prep landing + announcement article
• Friday check-in

Week 3 (2026-05-12 → 2026-05-16)

• Make-ready spoke #2 publish
• Draft make-ready spoke #3: "Make-ready cost benchmarks for multifamily"
• Ship predictive-maintenance hub (Nate handles deploy)
• Wire internal links: existing Cluster 4 spokes → new hub
• LuMi launch if approved (Lula Day May 8)
• Friday check-in

Week 4 (2026-05-19 → 2026-05-23)

• Make-ready spoke #3 publish
• Apply entity disambiguation to next 10 pages (15 total)
• Audit /rentvine, /appfolio, /buildium, /rentmanager, /propertymeld for current ranking + content state
• Phase 1 measurement check
• Monthly check-in

Phase 2 (Weeks 5-8: 2026-05-26 → 2026-06-20) — PMS pages + complete make-ready cluster + Cluster 1/4 spoke alignment

Outcomes by end of Phase 2:

• 5 make-ready spokes live (full cluster)
• 5 PMS integration pages refreshed with co-brand framing from Master Copy Deck
• 4 brand-led Foresight/predictive titles rewritten to commercial queries
• Internal link graph: spokes → hubs → spokes wired across both clusters
• Make-ready cluster shows first measurable ranking lift

Week 5 (2026-05-26 → 2026-05-30)

• Draft make-ready spoke #4: "Make-ready vs unit turn (terminology)"
• Refresh /buildium page (highest converter per Hubspot Apr 16 analysis)
• Title rewrite: /articles/predictive-maintenance-strategies
• Friday check-in

Week 6 (2026-06-02 → 2026-06-06)

• Make-ready spoke #4 publish
• Draft make-ready spoke #5: "Single-family make-ready process"
• Refresh /appfolio page
• Title rewrite: /articles/foresight-vs-manual-processes
• Friday check-in

Week 7 (2026-06-09 → 2026-06-13)

• Make-ready spoke #5 publish (cluster complete)
• Refresh /rentvine page
• Refresh /rentmanager page
• Title rewrite: /articles/predictable-maintenance-outcomes-property-management OR retire if too off-target
• Phase 2 mid-point measurement
• Friday check-in

Week 8 (2026-06-16 → 2026-06-20)

• Refresh /propertymeld page
• Title rewrite: /articles/ai-maintenance-operations
• Internal link audit + manual wiring across all clusters
• Sitemap submission verification in GSC for all refreshed pages
• Monthly check-in + Phase 2 review

Phase 3 (Weeks 9-12: 2026-06-23 → 2026-07-18) — Geo programmatic + retire dead weight + measure

Outcomes by end of Phase 3:

• 5 geo-page templates live (top Lula markets) — programmatic SEO
• Legacy 2023-2024 non-performers retired (301 or noindex)
• Apr 14 batch (vendor-onboarding, vendor-compliance-checklist, etc.) re-evaluated — keep, refresh, or retire each
• Quarterly revisit doc with Phase 4 scope recommendation

Week 9 (2026-06-23 → 2026-06-27)

• Build geo-page template (one canonical structure for /property-maintenance-services-{city})
• Ship first 2 geo pages (top 2 Lula markets — likely Kansas City + one TBD)
• Friday check-in

Week 10 (2026-06-30 → 2026-07-04)

• Ship next 3 geo pages (5 total live)
• Audit + retire decision on 2023-2024 legacy articles (/articles/who-is-responsible-for-pest-control..., /fastest-growing-companies, /tenant-caused-damages, /how-to-improve-resident-retention)
• Friday check-in

Week 11 (2026-07-07 → 2026-07-11)

• Apr 14 batch evaluation: which articles in the 3Cs cluster are getting traction (impressions even if not clicks)? Which to refresh, which to retire?
• Surgical page-1 pushes:
  • /articles/deferred-maintenance pos 2 → pos 1
  • /articles/best-property-management-maintenance-software pos 5 → top 3
  • /articles/what-can-a-handyman-do pos 5 → top 3
• Friday check-in

Week 12 (2026-07-14 → 2026-07-18)

• Quarterly revisit doc: what shipped, what ranked, what didn't, Phase 4 scope
• Review with Nate
• Update v2 audit with Q2 actuals
• Plan Q3 (Phase 4)

What we're NOT doing (explicit deferrals)

• Cluster 5 (After-Hours), Cluster 6 (Disconnected Systems), Cluster 7 (Inventory/CapEx), Cluster 8 (Training) — Not started, not on Q2 roadmap. Revisit Q3 based on Phase 1-3 measurement signal.
• More Foresight/predictive blog spokes — Existing 10+ spokes get title rewrites and link wiring; no new spokes until current ones rank.
• AEO citation tracker build — Measurement infrastructure, not traffic-generating. Defer to Phase 4 (Q3) — manual baseline only this quarter.
• Wikipedia attempts — Failed once; time-intensive; defer indefinitely unless higher-priority.
• Tangential blog posts (lease renewals, fair housing, landlord-tenant disputes, etc.) — Small TAM, distract from compounding work. No new posts in these areas this quarter.
• Provider-recruitment geo page cleanup (~55 /become-a-provider/* URLs) — Non-ICP. Flag duplicates to Nate; Gemma doesn't own.
• Help center subdomain SEO — Pros audience, not ICP. Untouched.
• Wikipedia / Crunchbase / external entity-building — Per memory: failed on Lula previously. Skip for SMB PropTech.

Dependencies (need from Nate)

Measurement

Leading indicators (weekly check)

• New rankings entering top 20
• Pages indexed via GSC URL Inspection
• Backlinks acquired
• Landing pages live + in sitemap

Lagging indicators (monthly review)

• Total organic keywords (baseline 2026-04-23: 141)
• Monthly organic traffic — Ahrefs estimate (baseline: 2,442; flag yesterday's anomaly)
• Keywords in pos 1-3 (baseline: 76)
• ICP-attributed demo requests (requires attribution clarity from Nate)
• Make-ready cluster traffic (baseline: 258 + 11 + 24 = 293/mo)
• Foresight cluster traffic (baseline: 9, all branded)
• Cluster 1 cluster traffic (baseline: 46, deferred-maintenance only)

Quarterly targets (2026-07-23 review)

• Hit rate: 23% → 40%+
• Total organic traffic: 2,442 → 4,000+
• Make-ready cluster traffic: 293 → 800+
• Foresight cluster: 9 (branded only) → 50+ (with commercial queries appearing)
• Cluster 1 cluster: 46 → 150+
• 5+ geo pages indexed and starting to rank

What success looks like at quarterly review

By 2026-07-23, the answer to "is the strategy working" is binary:

• ✅ If: make-ready cluster compounding, Foresight hub starting to rank for primary kw, PMS pages refreshed and pulling integration searchers, hit rate climbing
• ❌ If: hubs published but nothing moves in 8-12 weeks → diagnose deeper structural issue (authority, indexing, on-domain spam signals)

Cadence

• Weekly check-in (Fridays): Gemma + Nate. ~30 min. Shipped this week, blocked, next week. Log per-meeting in clients/lula/work/weekly-check-ins/YYYY-MM-DD.md.
• Monthly check-in (last Friday of month): Phase progress vs plan. ~45 min. Update active-work.md.
• Quarterly revisit (2026-07-23): Full scope review, Phase 4 scope. ~90 min. Update audit + roadmap.

Companion docs

• v2 comprehensive audit: content-audit-2026-Q2-v2-comprehensive.md (the data foundation)
• v1 audit (deprecated): content-audit-2026-Q2.md
• v1 execution plan (superseded): content-audit-2026-Q2-execution-plan.md
• Active work anchor: ../operations/active-work.md
• Decision log: ../work/decisions/2026-04-23-icp-traffic-strategy-4-plays.md
• Master Copy Deck (source of truth): ../brand/foresight-master-copy-deck-2026.md (TO BE SAVED — currently in chat)

Lula — Audit execution plan (Q2 + Q3 2026)

Turns content-audit-2026-Q2.md from strategy into sequenced work. Time-boxed phases, explicit owner splits, and acceptance criteria per phase so progress is legible at the quarterly revisit.

Assumptions this plan rests on

• Lumi AI content work is ON HOLD as of 2026-04-22 pending Nate go-ahead. Lumi unveiling at Lula Day May 8 2026 is a fixed external date but Gemma cannot start Lumi work until Nate confirms positioning and URL decisions. Plan re-sequences to pull make-ready and Foresight diagnostic work forward while waiting.
• Engagement is content + SEO strategy retainer. Phase 4 (Scale / Iterate) per product-led-content-growth.md.
• No AirOps / no dedicated AEO tracker. AEO measurement gap exists. A lightweight tracker (manual or built) is a Phase 4 deliverable.
• Dependency order matters. Once Lumi is unblocked, it becomes the urgent priority. Until then, Phase 1 reshapes around work that does not depend on Nate input.
• Gemma has CMS publishing permissions for blog articles and can deploy 301 redirects herself. Landing-page structural changes may need Nate or dev involvement.

Scope split — what Gemma does vs. what needs other owners

Gemma writes solo:

• Blog articles (all of /articles/*)
• Meta title / meta description updates
• Internal-link weaves
• 301 redirects
• Audit / diagnostic work

Needs Nate:

• Lumi landing page URL decision (/lumi or /lumi-ai or alt)
• Lumi positioning + approved messaging
• Lumi customer stories (if any exist)
• Cluster prioritization confirmation
• GA4 / HubSpot attribution setup clarity

Needs dev or technical help:

• SEO plugin root-cause on the Feb 18 phantom lastmod (non-blocking)
• Provider-geo template audit (non-blocking)
• Schema updates if the Lumi landing page needs custom schema
• noindex verification on -paid variants

Dependency spine (read before phasing)

Lumi landing page spec (Gemma + Nate)
    ├─→ Lumi landing page live
    │       └─→ Lumi supporting articles (2) → internal-link to landing
    │               └─→ Launch-week promotion (blog, social, PR)
    ├─→ Make-ready cluster expansion (independent, can run parallel)
    └─→ Technical cleanup (duplicates, /13033-2) — parallel, fast

Foresight diagnostic
    └─→ Foresight content decision (consolidate existing OR write new)
            └─→ Foresight ski-ramp build

Work Order Chaos cluster scoping
    └─→ Cluster landing + 3 articles

Phase 1 (2026-04-22 → 2026-05-09) — Foresight diagnostic + make-ready cluster start + Lumi prep (when unblocked)

External deadline: Lumi public unveiling May 8 2026 — contingency only, since Lumi is on hold.

Business outcome by end of Phase 1:

• Foresight diagnostic complete with findings + recommendation written.
• First 1-2 make-ready spoke articles drafted (one published).
• Three technical cleanup 301s deployed (duplicate provider pages, /13033-2).
• At least one page-1 surgical push shipped.
• Lumi work scoped and ready to deploy the moment Nate unblocks.

Waiting on Nate (non-blocking for Phase 1 start):

• Lumi landing page URL slug
• Approved Lumi positioning + messaging from the Launch Content & SEO Strategy Package
• Lumi-specific stats or customer stories cleared for public use

Week 1 (2026-04-22 → 2026-04-26) — audit, diagnostic, quick wins

• Tue (today): content audit v1.0 + execution plan drafted. Lumi work flagged as on hold.
• Tue-Wed: Foresight diagnostic — pull per-URL GSC + Ahrefs data on the 6-7 Foresight / predictive-maintenance articles. Evaluate impression signal, query-to-URL fit, cannibalization between articles, internal-link scaffolding. Write findings + recommendation (consolidate vs. rewrite vs. new content).
• Wed-Thu: first make-ready spoke drafted: "Make-ready checklist for apartment turnovers." Internal-link up to /articles/what-is-a-make-ready.
• Thu: technical cleanup 301s deployed — /become-a-provider/austin-2, /tampa-fl, /indianapolis-area, /13033-2. Verify -paid variants have correct canonical / noindex.
• Fri: weekly check-in.

Week 2 (2026-04-28 → 2026-05-02) — make-ready cluster build + surgical push

• Mon: first make-ready spoke published. Submit to GSC.
• Mon-Tue: surgical page-1 push on /articles/deferred-maintenance (pos 2 → pos 1). Minor copy refresh + internal-link weave. ~2-3 hours.
• Tue-Wed: second make-ready spoke drafted: "How long does a make-ready take?"
• Wed-Thu: if Lumi unblocks → pivot to Lumi landing + supporting article #1. If still on hold → third make-ready spoke: "Make-ready cost benchmarks for multifamily."
• Fri: weekly check-in. Phase 1 mid-point review.

Week 3 (2026-05-05 → 2026-05-09) — Lumi contingency or continued make-ready build

If Lumi has unblocked: Lumi work takes over Week 3 entirely. Landing page live Mon, supporting article #1 published Tue, supporting article #2 published Thu (Lula Day). Make-ready cluster work pauses.

If Lumi still on hold: continue make-ready cluster. Second make-ready spoke published Mon. Third spoke drafted Wed. Fourth spoke ("Make-ready SOPs for multifamily property managers") drafted Fri. Surgical page-1 push on /articles/what-can-a-handyman-do (pos 18 → page 1 on "what does a handyman do," KD 4, vol 450) mid-week.

• Fri: weekly check-in. Phase 1 wrap-up.

Phase 2 (2026-05-12 → 2026-06-06) — Make-ready cluster build + Foresight diagnostic

Business outcome by end of Phase 2:

• 4 make-ready spoke articles published (full cluster live).
• Foresight diagnostic complete with written findings + recommendation (consolidate existing OR write new).
• Two more page-1 surgical pushes shipped.
• First measurable ranking shift on make-ready cluster (expect lift 2-4 weeks post-publish).

Week 4 (2026-05-12 → 2026-05-16)

• Make-ready spoke #1 published (from Week 3 draft).
• Make-ready spoke #2 drafted: "How long does a make-ready take?"
• Foresight diagnostic starts: pull per-URL GSC + Ahrefs data on all 6 Foresight/predictive-maintenance articles via gsc-mcp. Evaluate impression-level signal, query-to-URL fit, internal-link scaffolding. Document findings.
• Weekly check-in.

Week 5 (2026-05-19 → 2026-05-23)

• Make-ready spoke #2 published.
• Make-ready spoke #3 drafted: "Make-ready cost benchmarks for multifamily."
• Foresight diagnostic continues: competitor content benchmarking for Foresight-target queries. Identify content gaps vs. ranking competitors.
• Surgical page-1 push on /articles/what-can-a-handyman-do (pos 18 → page 1 on "what does a handyman do," KD 4, vol 450).
• Weekly check-in.

Week 6 (2026-05-26 → 2026-05-30)

• Make-ready spoke #3 published.
• Make-ready spoke #4 drafted: "Make-ready SOPs for multifamily property managers."
• Foresight diagnostic complete. Written recommendation: consolidate existing OR write new ski-ramp articles. Specifics to land in Phase 3 scope.
• Weekly check-in.

Week 7 (2026-06-02 → 2026-06-06)

• Make-ready spoke #4 published. Make-ready cluster complete.
• Surgical page-1 push on /articles/best-property-management-maintenance-software (pos 5 → top 3).
• Phase 2 measurement: make-ready traffic trend vs. baseline (Ahrefs + GSC via gsc-mcp).
• Monthly check-in.

Phase 3 (2026-06-09 → 2026-07-11) — Foresight ski-ramp + Work Order Chaos beachhead

Business outcome by end of Phase 3:

• Foresight content re-architected per diagnostic (either 3 new articles OR 3 consolidated rewrites).
• Work Order Chaos cluster has a dedicated landing + 2 supporting articles (Lula's core differentiator finally has a content beachhead).
• /foresight product page traffic lifts measurably from baseline.

Weeks 8-9 (2026-06-09 → 2026-06-20)

• Foresight ski-ramp action based on Week 6 diagnostic:
  • If consolidate: 301 redundant articles, strengthen survivors with updated copy + internal links.
  • If write new: draft 2 of 3 new Foresight articles with cleaner query-to-URL mapping.
• Internal-link audit: ensure /articles/what-is-a-make-ready (highest authority article), homepage, and other high-traffic pages link to /foresight.
• Weekly check-ins.

Weeks 10-11 (2026-06-23 → 2026-07-04)

• Complete Foresight ski-ramp work.
• Scope Work Order Chaos cluster: landing URL (TBD — /work-order-software or similar), primary query targets, ICP-aligned positioning. Reference Lula's LuCI Smart Triage + Smart NTE differentiators.
• Work Order Chaos landing page drafted.
• Work Order Chaos supporting article #1 drafted.
• Weekly check-ins.

Week 12 (2026-07-07 → 2026-07-11)

• Work Order Chaos landing + article #1 published.
• Work Order Chaos article #2 drafted.
• Phase 3 measurement review.
• Monthly check-in.

Phase 4 (2026-07-14 → 2026-07-22) — Quarterly revisit + measurement framework

Business outcome by end of Phase 4:

• Lightweight AEO tracker live (manual LLM-query baseline OR tool-built).
• Measurement framework documented (leading + lagging indicators; demo-attribution approach clarified with Nate).
• Quarterly revisit doc written with Phase 5 scope recommendations.

Week 13 (2026-07-14 → 2026-07-18)

• Work Order Chaos article #2 published.
• AEO tracker: baseline 30-50 priority ICP queries across ChatGPT / Claude / Perplexity / Gemini. Log whether Lula is cited and where. If building an MCP-based tracker, scope it now.
• Measurement framework doc drafted. Capture: priority queries, ranking baselines, traffic baselines, conversion signals (once Nate confirms attribution stack).

Week 14 (2026-07-21 → 2026-07-22)

• Quarterly revisit doc written. Includes: wins shipped, measurement movement, gaps remaining, recommended Phase 5 scope.
• Review with Nate.

What this plan does NOT include

• Vendor management cluster (README Cluster 3). On hold per Nate Apr 2026. Explicitly skipped.
• Provider recruitment geo-page cleanup (the ~45 /become-a-provider/* pages). Non-ICP, technical SEO concern only. Flagged to Nate but not Gemma's scope.
• Full technical SEO audit (Core Web Vitals, schema, robots, etc.). Separate workstream if needed.
• Paid-media content — any -paid URL variants. Paid-side work is Tyler's scope.
• Sales collateral / case study production — not in scope of this content audit execution plan.

If the plan slips

• Lumi misses May 8 deadline: Lumi work stays in Phase 1 until it ships. Every subsequent phase delays by the slip. Acceptable because Lumi is the one hard external anchor.
• Make-ready spokes fall behind: compress by cutting spoke #4 (lowest priority in the cluster). Don't compress by skipping the Foresight diagnostic.
• Foresight diagnostic reveals messier problems than expected: treat Phase 3 Foresight work as a new workstream to re-scope, not force into Phase 3 calendar. Tell Nate early.
• Nate input doesn't arrive on time: explicit check-in Mon 2026-04-28 on Lumi inputs. If nothing by EOD Wed 2026-04-30, Gemma drafts with best available information and flags for Nate review at sight.

Dependencies summary (one-liner each)

1. Nate approval on Lumi URL, positioning, customer stories — due by 2026-04-28.
2. Nate confirmation on Cluster 3 (vendor) remaining on hold — asked at 2026-04-28 check-in.
3. Nate confirmation on conversion attribution stack (GA4 / HubSpot) — due by Phase 4.
4. SEO plugin root-cause on Feb 18 lastmod anomaly — non-blocking, investigate when technical session available.
5. Provider-geo template audit for duplicate content — non-blocking, flag to Nate in Phase 2.

Measurement (light)

Leading indicators (weekly pulse)

• Ahrefs organic-keyword count (142 baseline 2026-04-22)
• Ahrefs monthly organic traffic estimate (4,555 baseline)
• Keywords in positions 1-3 (77 baseline)
• Make-ready cluster article count (1 baseline, target 5 by end of Phase 2)

Lagging indicators (monthly review)

• GSC clicks + impressions on /foresight, /lumi, Work Order Chaos landing, make-ready flagship + spokes
• AEO citation presence across 4 LLM providers (baseline TBD in Phase 4)
• Demo form submissions attributed to ICP content (requires Nate's attribution confirmation)

Quarterly revisit (2026-07-22)

• What shipped vs. what was planned
• What ranked vs. what didn't
• Where ICP traffic actually moved
• Phase 5 scope recommendation

Self-accountability system

Match the rhythm used elsewhere in Gemma's operating model:

• Weekly check-in (Fridays, 15 min): what shipped this week, what's blocked, what carries to next week. Log in clients/lula/work/weekly-check-ins/YYYY-MM-DD.md.
• Monthly check-in (last Friday of month, 30 min): did the month's outcome hit? What's one thing to change? Update cluster-level progress.
• Quarterly revisit (2026-07-22): full scope review, Phase 5 recommendations.