Lula — Active work

What Gemma is currently delivering to Lula. Update weekly. This is the anchor doc for every conversation — read first to know current state without re-deriving from chat.

Roadmap source: ../strategy/icp-traffic-roadmap-2026-Q2-Q3.md.

🔔 Pending Nate verification

Items awaiting Nate sign-off before shipping. Surface in weekly Friday check-ins until resolved.

Active delivery streams

1. Make-Ready cluster expansion — HIGHEST PRIORITY — IN PRODUCTION (updated 2026-05-21)

Compounding on the only proven flagship (/articles/what-is-a-make-ready — 273 visits/mo May 2026, 33 keywords, ranks #1 on 10+ commercial-adjacent variants). Cluster strategic plan locked 2026-05-14 via Ahrefs Agent A trial.

• 6 spokes + money-page rewrite + hub light optimization. Spokes: (1) Checklist, (2) Cost, (3) Timeline, (4) vs Apartment Turnover, (5) Technician (backlink magnet), (6) Reduce Days Vacant (highest commercial intent).
• Money page rewrite /make-ready-service repositions around commercial intent. Page bled 53 → 19 visits/mo over 12 months as the hub cannibalized informational queries; needs distinct commercial angle ("near me" / metro / SLA / pricing).
• Hub link-out edits: add contextual links from existing hub copy to all 6 spokes + new H2 stub pointing at the Checklist spoke.
• Projected ~1,300 net new visits/mo at 12 months (conservative; assumes pos #3-5 average for spokes; upside if the Checklist PDF-gap is won).
• Downloadable PDF lead magnet mirrors the Checklist spoke (test gated vs ungated).
• Status (2026-05-27): Spoke 1 (Checklist) taken through a full brief and article production pass via the Lula skill stack: verified ~2,650-word draft, pending Gemma final read and publish. Money-page rewrite completed by Gemma and signed off. Lead magnet locked: existing "Make-Ready Operations Toolkit" Google Sheet, gated week 1. Hub patch document produced: 9 find-and-replace patches for the live hub article (stale Multifamily Dive citation swapped for NAA 2025 data, the 3-day vs 72-hour inconsistency fixed, 9 to 11 metros, 4 voice hard-stops removed, Spoke 1 cluster-activation link added, fallback anchors reserved for the other 5 spokes), ready to apply in WordPress. Remaining spokes, revised production order with Spoke 5 deferred 2-3 weeks to absorb the Cluster 6 centralized-maintenance spoke pull-forward: 4 (vs Apartment Turnover), 6 (Reduce Days Vacant), 2 (Cost), 3 (Timeline), then 5 (Technician) following the Cluster 6 ship. Update (2026-06-01): Spoke 4 (vs Apartment Turnover) is drafted and now in editing. Remaining production order: 6 (Reduce Days Vacant), 2 (Cost), 3 (Timeline), then 5 (Technician). Update (2026-06-16, per editorial board): Spoke 2 (Cost — "How Much Does a Make-Ready Cost?") and Spoke 4 (vs Apartment Turnover) are now PUBLISHED. Spoke 1 (Checklist) and Spoke 6 (Reduce Days Vacant — "How to Reduce Days Vacant on Rental Properties") are drafted and sitting in Ready-for-editing. Make-ready lead magnet is queued for WP. Update (2026-06-16, end of day): Spoke 3 (Timeline — "How Long Does a Make-Ready Take?") is now drafted and in Ready-for-editing. Update (2026-06-17): Spoke 5 (Technician — "What Is a Make-Ready Technician?") is now drafted, the backlink-magnet piece with salary benchmarks and a copy-pasteable job description. All six spokes are now published or in editing; the cluster is fully drafted. Update (2026-07-02): Spokes 2 (Cost), 3 (Timeline), 4 (vs Apartment Turnover), and 5 (Technician) are all LIVE. Two spokes remain to publish: Spoke 6 (Reduce Days Vacant — "How to Reduce Days Vacant on Rental Properties (2026 Playbook)") and Spoke 1 (Checklist — "The Complete Apartment Make-Ready Checklist (with Free Toolkit Download)"). Remaining: publish those two, the make-ready lead-magnet WP load (mirrors the Checklist spoke), and the hub light-optimization patch. Update (2026-07-06): Spoke 6 (Reduce Days Vacant) is now LIVE at https://lula.life/articles/reduce-days-vacant. Only Spoke 1 (Checklist) remains to publish. Update (2026-07-08): Spoke 1 (Checklist) is now LIVE at https://lula.life/articles/apartment-make-ready-checklist, a 67-item room-by-room checklist with a free toolkit (tracker + priority matrix). All six spokes plus the hub are now published; the Make-Ready cluster is fully live. Published ahead of the toolkit being embedded, so it may be pulled briefly if Nate prefers to wait for the embed. Remaining: confirm the toolkit/checklist embed, the make-ready lead-magnet WP load, and the hub light-optimization patch.
• Canonical metro count: 11 (Atlanta, Cincinnati, Columbus, Dallas, Houston, Indianapolis, Kansas City, Minneapolis, Oklahoma City, Phoenix, St. Louis) — confirmed against the live /make-ready-service page. Hub article + earlier Spoke 1 drafts said 9; Spoke 1 patched to 11. Hub still says 9 (in the hub-optimization scope below).

2. Hub landings ship + activate — LIVE (2026-05-12)

All three Foresight landings now LIVE. Published 2026-05-12 after Nate sign-off at:

• /predictive-maintenance-software (Cluster 4 — Reactive vs. Predictive Maintenance) — KD 4 / SV 2,600 target.
• /ai-work-order-software-for-property-managers (Cluster 1 — Work Order Chaos & Triage Bottlenecks).
• /ai-scheduling-software-for-property-maintenance (Cluster 2 — Scheduling Inefficiency & Technician Burnout).
• Strategic frame (per Gemma's Slack note): "the idea is to create a number of these types of pages targeting different keywords / entry points to see what sticks." Multi-cluster Foresight surface area, not a single hub.
• Post-publish wiring verified COMPLETE 2026-05-18: All Cluster 1 + 2 + 4 spokes link to the correct live hub URLs (curl-verified across 8 spokes + 4 Cluster 4 spokes). The 2026-05-15 /blog/property-management-work-order-system buyer's guide also links correctly. /foresight has 2 reciprocal links to each of the 3 new hubs. Live HTML snapshots of all 3 hubs archived to content/drafts/2026-05-18-*-live-snapshot.html.
• Post-publish work remaining: rewrite brand-led titles on existing spokes (where not already done); resolve open product-team flags (/ai-scheduling-software-for-property-maintenance 5 flags + Smart NTE on work-order page) via surgical edits when product team returns.
• Nate priority signal (2026-04-24): confirmed Foresight is "front of the line" — landing page + supporting assets need to go deeper. Foresight cluster needs lead magnets + nurture-ready landing pages so leads from each pain point have a pathway. Kaytlynn owns email/nurture downstream; Gemma's scope is the assets.

Lead-magnet substream (closes the loop on each cluster):

• Cluster 1 (Work Order Chaos): lead magnet IS LIVE. Popup UX needs work — flagged to Kaytlynn 2026-04-27.
• Cluster 2 (Scheduling): Canva first-pass created over the weekend (pre-Claude). Worth a Claude rebuild to lift design quality before external share.
• Cluster 4 (Reactive vs Predictive): in-flight today (2026-04-27) — Gemma working on the lead magnet to close the cluster loop.

3. Sitewide "Lula" entity disambiguation

Foundational fix per Apr 4 Google NLP discovery (Lula tagged as PERSON not BRAND).

• Top 5 pages Week 1.
• Top 15 pages by Week 4.
• Pattern: meta + H1 + first body mention as "Lula, the property maintenance software for..." or equivalent.

4. PMS integration page refresh — THESIS NEEDS REVISION (2026-05-18 diagnostic)

Original plan: refresh /buildium, /appfolio, /rentvine, /rentmanager, /propertymeld Weeks 5-8 to capture high-intent commercial demand per Apr 16 traffic analysis ("/buildium punches above its weight"). Buildium diagnostic (2026-05-18) falsifies the SEO premise:

• /buildium has 0 ranking organic keywords (Ahrefs). 22 weeks of GSC: 84 imp / 0 clicks. Half of those impressions are site-operator/typo noise.
• All buildium maintenance/work-order/integration query variants return volume 0 in Ahrefs Keywords Explorer. Only buildium integration(s) (vol 50-70, KD 0-1) and buildium api (vol 200, dev intent) have measurable demand.
• SERP for buildium integrations: Buildium owns 8 of 11 ranked URLs (marketplace, partners, help, blog, customer stories, staging). Only LeadSimple (DR 61) ranks as a true third-party. Lula's realistic organic ceiling is ~40-80 visits/mo even at perfect ranking.
• The "highest converting PMS integration page" claim from Apr 16 HubSpot analysis is almost certainly measuring direct/branded traffic, not organic search. Lula doesn't use HubSpot — provenance of the claim is itself an open question for Nate.
• Re-scope direction: treat /buildium (and likely the other 4 PMS pages) as conversion landing pages for direct/branded arrivals, not organic acquisition pages. Run the same 1-hour diagnostic on the other 4 PMS pages before Phase 2 Week 5 to confirm the pattern. If it holds, kill the SEO refresh, reframe as a 5-page conversion-rate-optimization batch + Buildium Marketplace partnership push (out of Gemma scope — partnerships hand-off).
• Quick wins regardless of Phase 2 direction: fix the /buildium meta description typo ("power" → "powerful"), add H2s (currently zero), bump dateModified from 2026-01-08 (4 months stale), submit to GSC re-index. ~30 min CMS work.
• Full diagnostic + refresh spec at work/artifacts/2026-05-18-buildium-diagnostic.md.

5. Geo programmatic SEO (Phase 3) — 16 OF 17 LIVE, ST. LOUIS BUILT AND READY TO LOAD (updated 2026-08-14)

17 Lula markets get local make-ready pages from the existing /make-ready/ hub. 16 of 17 are LIVE: Atlanta, Cincinnati, Cleveland, Columbus, Dallas-Fort Worth, Dayton, Houston, Indianapolis, Kansas City, Memphis, Minneapolis, Oklahoma City, Orlando, Phoenix, Tampa, and Tulsa. Each page features the market's local W-2 field manager (photo, bio, direct contact), market-specific make-ready content (seasonality, climate, neighborhoods, county coverage, and ZIP-code service area), and a "Talk to a Field Manager" CTA. Counties, neighborhoods, employers, climate, and every ZIP code were fact-checked against public sources and the master coverage sheet. St. Louis, the seventeenth and final market, is now built and ready to load into WordPress, closing the set.

• Atlanta sample page built — full local-SEO city-page template at clients/lula/work/make-ready-city-pages/atlanta.html. Includes on-brand dark statement block, Service + LocalBusiness + FAQPage + BreadcrumbList JSON-LD schema, NAP block, embedded Google Map, county/state variation, 10 city-specific FAQs, and ~50% unique-per-city content target. Iterated to match Nate-call framing (the W-2 field manager coordinates the work; vetted Pros execute it).
• 17-city data spreadsheet built at clients/lula/work/make-ready-city-pages/city-data-spreadsheet.csv. 13 [LULA] columns for the team to fill (FM name + photo + bio + years, turns YTD per city, vetted Pros count, local phone, GBP URL, customer testimonial, real cost range, lead-paint handling specifics). 11 [RESEARCH] columns pre-populated for every city (avg SFR rent, daily vacancy cost, peak SFR turnover season, days to lease, counties, neighborhoods, ZIPs, climate factors, pre-1978 stock notes, employer/school patterns, Google Maps embed URL).
• GBP setup note: Each metro needs its own Service-Area Business listing (one per city, FM home address used for verification only, hidden from public profile). 17 listings to claim or create.
• Markets section wired to city pages (2026-06-17, St. Louis added 2026-08-14): the make-ready service page links each metro to its own city page as a button, and every city page links back to the service page. The St. Louis placeholder button has now been turned into a live link to /make-ready-service/st-louis, so all 17 pills point somewhere.
• Structured data written for all 17 pages (2026-06-17, St. Louis added 2026-08-14): per-city JSON-LD (Service markup with county-level coverage, FAQ, and breadcrumb) is complete and has been passed to Nate to deploy via Google Tag Manager. The St. Louis block is appended to the bundle in market order; all 17 blocks parse clean and every FAQ answer matches its page copy word for word. Worth a quick verification of the phone numbers and the few unconfirmed cost figures before pages and markup go live together.
• St. Louis page built (2026-08-14): the final market, built from the same template at clients/lula/work/make-ready-city-pages/st-louis.html with Jeffrey Richardson as the local field manager (photo, bio, direct line). Market content is St. Louis specific throughout: the WashU and SLU calendars stacked on the Webster Groves, Kirkwood, Ladue, Clayton, Rockwood, and Parkway district cycles; humid continental climate with 90-degree summers, freeze-thaw winters, and April-June storm claims; one of the highest pre-1978 housing concentrations of any major US metro, with brick rowhouses, two-flats, and four-family flats driving plaster, window, and friction-surface work; and the St. Louis City / St. Louis County split as two separate jurisdictions, plus St. Charles and Jefferson counties.
• Icon-stripping defect found on the live St. Louis and Houston pages (2026-08-14): every inline <svg> icon has been stripped from both pages, leaving empty pale boxes where the four why-card icons, the eight pain/outcome check and X marks, the ten service chips, and the phone glyph should sit. Counted <svg> across all 17 live city pages: the healthy baseline is 30 to 33, and St. Louis and Houston are both at 9, which is theme chrome only. The photos are unaffected on both pages, all 11 image URLs return 200, and the St. Louis CSS survived intact (117 of 117 braces, zero <br />, cleaner than Atlanta, which carries a stray </p> in its style block). Cause is WordPress stripping <svg> from content saved outside the Code Editor, so the fix is a re-paste of the paste-ready file via the Text tab rather than any change to the markup. Houston has been live in this state since early July and is worth fixing in the same pass.
• Open items on St. Louis before publish: the supplied direct line is a (913) Kansas City area code rather than a St. Louis one (314, 636, or 618), flagged in-page for Nate the same way Memphis was; the $1,500 to $4,000 cost range and the $1,400 rent / $47 per day figures carry the standard CONFIRM comments; no LinkedIn was supplied so that button is omitted; and the Google Map is still the generic embed pending a St. Louis GBP listing.
• Next: load St. Louis into WordPress and publish; Nate to deploy the per-city schema via GTM (now all 17); confirm the St. Louis phone line and a local number for the few markets still showing a shared one; then Yoast config per city; verify the phone numbers and the few unconfirmed cost figures on the live pages.

7. Cluster 6 pull-forward — centralized maintenance spoke — LIVE (2026-05-29)

Single-spoke pull-forward from Cluster 6 (Disconnected Systems & Visibility Gaps), targeted at portfolio operators across SFR, multifamily, and mixed books. Argues that team-and-software centralization is incomplete without vendor-network centralization, and frames the hidden cost the decentralized vendor layer carries across a portfolio.

• Published: https://lula.life/articles/centralized-maintenance (2026-05-29).
• Keyword target: centralized maintenance (KD 0, vol 30, AI Overview present). The "hidden cost of decentralized maintenance" framing sits inside the article rather than in the URL or title.
• SERP read: active multifamily category conversation (Multifamily Dive, Happy.co guide + podcast, IrisCX LinkedIn) plus industrial-CMMS noise. Lula has zero current presence. Wedge nobody in the SERP makes: vendor-layer centralization is the missing piece. Same structural advantage mapped in the agentic-maintenance synthesis, applied to the current Core services + Foresight + LuMi product line.
• Scope swap: Make-Ready Spoke 5 (Technician) deferred 2-3 weeks to absorb this work. Logged at work/decisions/2026-05-27-cluster-6-spoke-pull-forward.md.
• Update (2026-07-02) — indexation miss found + fixed: the 30-day check (window 6/28) showed zero rankings and zero GSC impressions. GSC URL Inspection: "Discovered - currently not indexed," never crawled, ZERO internal referring URLs (orphan page). The blog prev/next nav links to it but that is not enough weight to get it crawled. Fixed by adding three in-context internal links from indexed, high-authority pages (make-ready hub, best-property-management-maintenance-software, deferred-maintenance), plus a GSC Request-Indexing. Measurement window RESET: re-measure ~3 weeks after it indexes. Contrast: the Source7 article (published 6/5) is indexed because it had an internal link, confirming this is a one-off wiring gap, not systemic.
• Lead-magnet seed: 5-question "Centralization Gap" assessment inside the article. Candidate for a downloadable scorecard PDF as the Cluster 6 lead magnet.
• Next: 30-day measurement window 2026-06-28 (rankings, impressions, AI Overview presence on centralized maintenance and related variants).

8. PM-partner PDF backlink program — PDF DRAFTED + DESIGNED, 87 PROSPECTS FINAL — LIST NOW WITH NATE (2026-07-02)

PM-partner outreach campaign locked with Nate 2026-05-28: brand-neutral 2-4 page owner-facing make-ready research PDF distributed to PM companies, who host it as a lead-gen asset for their owner-investor audience. In exchange they place a contextual "learn more about make readies" text link or embed pointing to /articles/what-is-a-make-ready. Expected yield ~10% (Nate's estimate) = ~10 contextual editorial links per 100 PMs pitched.

• Cluster order: Make Ready (Phase 1, now) → Foresight (Phase 2) → Core Services (Phase 3). 100 PMs per cluster.
• Sender: Nate, outside of sales, additional touchpoint. Does not step on Kaytlynn email/nurture scope.
• Asset: brand-neutral 5-page owner-forward make-ready research brief (the benefit of a professionally managed make-ready and what it means for owner wealth), repurposed from /articles/what-is-a-make-ready. Drafted + designed 2026-06-01, pending Nate review. Sourcing resolved: cites the 2025 US median single-family rent ($2,100, Rentometer 2025 Annual SFR Report); the Peter Lohmann reference was dropped (latest is a 2024 report with no make-ready/turn data), and the portfolio-wealth math is framed as illustrative on the owner's own turn numbers rather than a claimed national benchmark. Draft at clients/lula/work/backlinks/pdf-draft-makeready-owner-brief-v1.md, spec at pdf-asset-spec.md.
• Sourcing (2026-06-01): six PMS-vendor ecosystems mined for referring domains (AppFolio, Buildium, Rentvine, DoorLoop, Yardi, Propertyware). Candidates verified individually before listing; brokerages, owner-operators, software vendors, and non-US firms screened out.
• Master prospect tracker live: Google Sheet with 87 verified US property-management companies in tiers: A (18 with explicit make-ready language on their site, pitch first), B (69 confirmed PMs without explicit make-ready language). Top of Tier A: utopiamanagement.com (multi-state west US, explicit make-ready), cloverleafpropertymanagement.com (San Antonio), managementone.com (SoCal).
• Sourcing method note: referring-domain mining has reached diminishing returns; each additional vendor now surfaces only a handful of new PMs. The final stretch to 100 will come from vendor customer/case-study pages and the NARPM member directory, which name PMs directly.
• Revisit 2026-09-28. Kill threshold: fewer than 3 confirmed links by then.
• Prospect sourcing closed (2026-07-02): the 87-PM list is final on Gemma's side; the "clear to 100" task is dropped. Prospect enrichment now sits with Nate. Gemma no longer owns list-building.
• Next: Nate review of the PDF (owner-audience tone + factual check), Nate to enrich the prospect list further, then hosting URL slug and Nate-voiced outreach email draft.

6. Foresight-light competitive intelligence — READY FOR NATE REVIEW (2026-05-25)

Cross-competitor synthesis for the 90-day Foresight-light / autonomous-coordination product build per the 2026-05-22 call.

• Three competitor deep-dives at clients/lula/competitive/agentic-maintenance/: Vendoroo, Mason (thisismason.com), Haven (usehaven.ai). Each covers product + positioning + pricing + GTM + team, with marketing-usable language banks (verbatim hero copy, taglines, customer testimonials with attribution, voice/tone analysis).
• Cross-cutting synthesis at _synthesis.md. Like-for-like wedge stack ranked: vendor-network-included as primary (the only structural advantage no competitor can copy in V1), data scale (200K+ work orders) and voice-AI category capture as supporting, multi-language and PM-native team as tactical.
• Next: cross-reference the named competitor customers against the Lula book to identify at-risk accounts; wedge-stack confirmation with Nate; pricing-model decision (per-door vs per-work-order vs free-software + network-commitment); draft V1 site spec.

9. Maintenance Fundamentals cluster — DRAFTING UNDERWAY (2026-06-24)

New hub-and-spoke cluster filling a property-maintenance content gap: the Ahrefs competitor analysis showed Lula ranks for none of the core maintenance-fundamentals terms, with Property Meld holding most. Framed for property managers and single-family rentals (not apartments or commercial, which the broad head terms skew toward).

• Pillar: "Property Maintenance" (broad informational head, AI Overview present), framed for rental owners and managers, linking into the existing software, deferred-maintenance, and make-ready pages.
• Spokes: Property Maintenance Checklist, Preventive Maintenance Examples, Property Maintenance Strategies, Common Property Maintenance Issues.
• Status (updated 2026-07-01): pillar is PUBLISHED at https://lula.life/articles/property-maintenance-for-rentals, and the Preventive Maintenance Examples spoke is now LIVE at https://lula.life/articles/preventive-maintenance-examples. Two drafted spokes sit in the editorial queue for Nate to edit and publish: Checklist (scoped to stay clear of the existing rental-inspection-checklist page, work performed vs condition documented) and Maintenance Strategies (/articles/property-maintenance-strategies, targeting property maintenance strategies, frames the four strategy types and how to weight the mix, links back to the pillar's maturity model). The final spoke, Common Issues, is in draft.
• Next: Common Issues spoke in draft; Nate edits and publishes Checklist and Strategies from the queue, wiring internal links to the live pillar as each lands; confirm the book-a-demo CTA link; decide whether to add a downloadable checklist PDF. Pillar 30-day measurement window 2026-07-26.

Recently completed (last 7 days)

• 2026-08-24: GA4 traffic-source corruption diagnosed and passed to Nate. Lula.life was appearing as a traffic source for lula.life in GA4. Traced to a single misconfigured rule in Tag Manager container GTM-TTTNMQT, on the Google tag for G-2GB4DFDMV2: a campaign_source configuration setting pointing at a RegEx Table variable that maps fb to facebook and ig to instagram, with "Set default value" checked and the default set to the full Referrer URL. Whenever utm_source is absent, or is anything other than exactly fb or ig, the session source is overwritten with the complete referrer address. Confirmed by pulling the live container and reading the configuration, not inferred from the report data. This is not a self-referral problem and the standard self-referral fixes would not have touched it, since GA4 suppresses same-host referrals automatically and records referral sources as bare domains rather than full URLs with query strings. Scale: across 26 May to 23 August, roughly 4,100 sessions produced about 200 with a usable source, so on the order of 95% of acquisition data for the window is unrecoverable. Google organic reads as full results-page URLs, and utm_source=chatgpt.com and utm_source=linkedin are discarded on arrival because they fail the full-match test. Facebook campaigns are fragmented across roughly 60 single-session rows. Fix is one change: delete the campaign_source configuration setting and publish. Four secondary findings: ad tracking parameters are being stripped on paid landing pages, so paid sessions begin on an untagged pageview; the production measurement ID is live on lula-staging.com and api.lula-dev.com; /wp-admin/ is tracked and internal traffic is not excluded, worth about 130 sessions in the window; and /help/category/pros/help.lula.life/future-pros/en is a malformed help-center URL drawing 34 sessions. Cross-domain measurement also needs configuring across lula.io, provider.lula.io, api.lula.io, partnerapi.lula.io, careers.lula.life, n.lula.life, wo.lula.life, help.lula.life and lulauniversity.com, but only after the tag fix, since genuine self-referrals stay invisible until the override is gone. Diagnosis: work/artifacts/2026-08-24-ga4-traffic-source-diagnosis.md. Next: Nate routes the Tag Manager change to whoever holds publish rights; Gemma verifies in Realtime once published. Recommend 14 days before reading anything into acquisition reports, to establish a clean baseline. Search Console and the ad platforms are unaffected and remain the source for this window.

• 2026-08-18: After-hours page published by Nate at /after-hours-maintenance. Live as "After-Hours Maintenance Answering Service", published 2026-08-18 and last modified 2026-08-19, while Gemma was out of office. Slug differs from the 2026-08-07 and 2026-08-14 build, which was written for /after-hours-answering-service. The published title keeps the answering-service phrasing, so the primary target (after hours answering service property management, 250 volume, KD 1) is still addressable, but the three-way cannibalization split assigned on 2026-08-07 now needs re-checking against the actual URL. Two live issues found on check: /after-hours-answering-service and /best-property-management-answering-service both return HTTP 200 while serving the Foresight PropTech Breakthrough article, which is soft-404 behavior and should either 404 properly or 301 to the published page; and /articles/after-hours-maintenance-calls is a hard 404, so the how-to article re-point is still outstanding. Next: confirm with Nate whether the four gating claims (work-order creation, live-agent hours and escalation paths, overnight dispatch coverage, after-hours pricing) were resolved before publish, and whether the placeholder language-support and pricing FAQ blocks shipped as-is; re-point the how-to article; fix the two soft 404s.

• 2026-08-14: St. Louis market page built, closing the 17-market local set. The last outstanding city page, blocked since mid-June on field-manager details, is now built at work/make-ready-city-pages/st-louis.html off the same template as the other 16. Jeffrey Richardson runs the market: over 15 years of hands-on maintenance and remodel work across luxury rentals, single-family homes, and multifamily, based in St. Louis, with photo, bio, and direct line on the page. Bio used as supplied, with its two em dashes swapped for a colon and a comma per house style. The market content is genuinely St. Louis rather than a find-and-replace: two university calendars (WashU and SLU) stacked on the Webster Groves, Kirkwood, Ladue, Clayton, Rockwood, and Parkway school-district cycles, which is what makes May through August the crunch; a humid continental climate where 90-degree summers stretch paint cure times and stress HVAC commissioning while freeze-thaw winters crack masonry, drive ice dams, and burst supply lines in vacant units, with April to June storm and hail claims on top; one of the highest pre-1978 housing concentrations of any major US metro, where the pre-1940 brick rowhouses, two-flats, and four-family flats of Tower Grove, Soulard, Benton Park, The Hill, Dutchtown, and North City make plaster repair, window replacement, friction-surface repainting, and original-wood-trim refinishing the recurring make-ready triggers rather than the drywall-and-carpet pattern of the newer markets; and the St. Louis City / St. Louis County split, since the city is an independent city and a scattered portfolio can therefore sit across two separate jurisdictions plus St. Charles and Jefferson. Also shipped alongside it: the per-city JSON-LD at _schema-per-city/st-louis.html, appended to the all-cities bundle in market order between Phoenix and Tampa (all 17 blocks parse clean, and every one of the 10 FAQ answers was diffed against the page copy and matches word for word), and the markets pills file updated so the St. Louis placeholder is now a real link to /make-ready-service/st-louis, taking all 17 pills live. Four things to settle before publish: the supplied direct line is (913) 303-7761, a Kansas City area code rather than a St. Louis one (314, 636, or 618), flagged in-page for Nate the same way Memphis was and worth resolving since the whole page argues local; the $1,500 to $4,000 cost range and the $1,400 rent / $47 per day figures carry the same CONFIRM comments as the other markets; no LinkedIn was supplied, so that button is omitted; and the Google Map is still the generic embed pending a St. Louis GBP listing. Next: load into WordPress and publish, and Nate's GTM schema deploy now covers all 17 rather than 16.

• 2026-08-14: After-hours landing page rebuilt for the WordPress build, recolored to Lula Green. Took the 2026-08-07 draft to a paste-ready build for /after-hours-answering-service. Copy changes: hero H1 is now Maintenance Handled 24/7 with a rewritten subhead covering routine repairs alongside emergencies, and scenario 3 now says LuMi runs initial diagnostic checks (thermostat settings, breakers, HVAC filters, pilot lights). The 2 a.m. headline moves to variant A in Tyler's paid test set. Color change: the page now runs on Lula Green (Success ramp #28B97B / #229B67 / #1B7D53), with purple reserved for the surfaces where LuMi itself is the subject: the hero call card, the capability list, the triage node in the routing diagram, and the training-data stats. The earlier build used Tailwind purples (#7C3AED), which are not Lula's AI ramp; corrected to the brand deck values (#7A5BF8 / #6839EF / #5826DC). Accent sits in CSS variables, so moving the page to brand blue is a seven-line change. Three build defects fixed, all verified against the live theme stylesheet rather than assumed: the theme defines .column-40 and .column-60 outside every media query, so the dark LuMi section would have rendered as two narrow strips on a phone; the theme force-centers .header-container p and #primary.content-area h1 with !important below 768px, and the ID-scoped rule outranks any class-only override, so the mobile overrides had to reuse the ID; and inline min-width on the scenario cards could not be relaxed by a later class rule, which pushed the page sideways on a 320px screen. Card sizing moved from inline styles to classes to fix the last one. Demo CTA wired to Gravity Form 23. Internal links removed at Gemma's direction and the copy restored to the approved doc wording, so the page ships with none; the inbound and outbound linking for this cluster gets handled separately alongside the article re-point. A fourth defect surfaced only once the page was pasted into WordPress and is the reusable lesson here: the CSS must be minified onto one line with no comments. WordPress runs wpautop over page content, which converts blank lines to </p><p> and newlines to <br />; inside a <style> block that shreds the stylesheet at every gap, so early rules survive and later ones die. The result looks partly styled, with colors and inline styles holding while every flex grid collapses to a stacked column and gradient backgrounds disappear. The known-good services paste file has zero newlines and zero comments inside its <style>; this build had 300 newlines and 26 blank lines. Now matched to the services convention and render-tested in headless Chrome, confirming the 40/60 dark section stacks to full width on a phone, the hero stays left-aligned against the theme's ID-scoped centering rule, and there is no horizontal overflow. A fifth defect showed up only in production and is worth carrying forward: the card rows were built with flex plus calc() widths and a gap, which double-counts the gutter. Measured against the live container (1120px wide, 40px padding, so 1040px usable), the three-card row came to 1040 - 1 and the four-card proof strip to 1040 - 0, meaning 1px and 0px of slack. Sub-pixel rounding decided whether a row held its cards or wrapped, and it wrapped on Gemma's machine while rendering fine locally. Rebuilt on CSS Grid with repeat(N,1fr), which sizes tracks after subtracting gaps, so the count is exact at any width and every card in a row is identically wide and, through stretch, identically tall. Verified at 1920, 1440, 900 and 390: three scenario cards at 332x332 identical dimensions on desktop, symmetrical 2x2 proof strip on tablet, single column on mobile, no orphan rows. Integrations section rebuilt on Lula's own markup: now uses the theme's #pm-works-with-any-software block with the real partner logos instead of text chips, which brings the theme's desktop and two-up mobile logo styling for free. Two things to confirm with Nate: Property Meld appears in that block elsewhere on the site but was dropped here because it is on the do-not-name competitor list, and appfolio.svg is commented out in the source block and replaced by a Primary Inc wordmark still carrying alt="appfolio logo", so the real AppFolio mark was restored since the page copy names AppFolio. Section order changed so no two dark bands sit together: the logo block is dark, and next to the dark "Built on seven years" section it read as one muddled slab with a visible seam between the flat #0f172a and the navy gradient. Integrations now sits between the routing section and the escalation section, giving a clean alternation of dark, white, dark, light, dark, light across the page. It also reads better there, answering "where does the work order actually go" straight after the routing scenarios. Two further build lessons, both only visible in production: HTML comments must be stripped from the paste file entirely, because WordPress wraps loose nodes including comments in <p> tags and inside a grid container each one becomes a phantom item occupying a cell (three <!-- Scenario N --> comments were what pushed the third card onto its own row and centred it, and that row was the only container with comments in it); and the section openers had drifted to different inline margins (44px, 56px, 16px), which is what read as uneven spacing under the headings, now normalised to one rhythm of eyebrow 14px, h2 18px, lede 48px. Hero card trimmed from 496px to 402px against a 469px text column so it sits inside the text block rather than towering over it. Last defect, and the one worth remembering: the theme draws a decorative 60x5px bar above every h2 through article.page h2:before (style.css L5798). It is brand blue, and it uses margin:0 auto, so it centres itself even above a left-aligned heading. Confirmed on the live /services page, where the one left-aligned h2 reports margin-left:225px while its heading sits flush left. On this page that put a stray blue bar in the middle of three left-aligned sections. Recoloured to Lula Green and made to follow whatever heading it belongs to. The local preview now wraps the page in #primary.content-area > article.page, because the rule is scoped to that wrapper and was therefore invisible in preview while breaking in production, which is the same class of mistake as the wpautop and phantom-grid-item bugs above. Next: four claims still gate publish and none are resolved in source-of-truth: work-order creation (scenario 1), live-agent hours and escalation paths, overnight dispatch coverage, and the after-hours pricing model. The language-support and pricing FAQs are still placeholder blocks and cannot go live as they stand. Josh on the first three, Nate on pricing. The article re-point at /articles/after-hours-maintenance-calls is still outstanding from the 2026-08-07 entry.

• 2026-08-13: SLA article repositioned around maintenance response times, and its internal link map rebuilt. Rewrote /articles/sla-tracking to lead with the operational question (how a team sets a response commitment, holds it across a portfolio, and catches a request drifting late before the resident feels it) rather than the SLA acronym. URL unchanged. The linking work was the larger half. Outbound: 15 internal links placed on verbatim phrases in the draft, one per destination, covering the scheduling cluster (maintenance-scheduling-software, technician-scheduling-software, how-scheduling-maintenance-saves-time-and-money, the Foresight scheduling landing, /foresight), the operations pages (property-management-work-order-system, maintenance-kpi-dashboards, in-house-vs-outsourced-vs-hybrid-maintenance, ai-maintenance-operations, /integrations), and the consequence pages (deferred-maintenance, how-to-improve-resident-retention, vendor-scorecard, property-management-compliance). Two links dropped from the previous version: best-property-management-software (landlord-facing, wrong audience) and best-property-management-maintenance-software (no response-time relevance). Inbound: the page carried 8 editorial inbound links; added 10 more from maintenance-automation, guide-to-navigating-landlord-tenant-disputes, property-management-compliance, predictive-maintenance-strategies, maintenance-kpi-dashboards, rental-property-maintenance-management, centralized-maintenance, how-to-improve-resident-retention, property-management-work-order-system, and vendor-scorecard, each placed inside the section that already discussed response times rather than bolted on. That takes the page to 18. Anchors: every existing inbound link used SLA phrasing, so two were kept on the term (deferred-maintenance, ai-maintenance-operations) for term coverage and the rest moved to response-time language to match the new positioning. The new vendor-scorecard link also sits on the term, since that page already spells out "service level agreements (SLAs)" in its own copy. Keyword check: no other page in the blog inventory claims a response-time or SLA term, so the repositioning has no cannibalization risk against a sibling. Two external citations recommended: the IT service management origin of the SLA term, and a habitability statute on the response-window FAQ. Next: fill the inventory row (new H1, date, both link lists, keyword and intent columns, which are blank). Two verification items block publish: internal Lula data on SLA adherence before and after predictive scheduling (the prior draft's high-90s claim had no source and was removed), and whether Lula publishes standard response windows by category.

• 2026-08-05: Kansas City Maintenance Cost Index built as the first worked metro edition. A full metro report for Kansas City MO-KS (14 counties), built to show what the cost index program produces rather than describe it. Runs entirely on public primary sources (ACS 2020-2024 5-Year, NOAA 1991-2020 climate normals at KCI, BLS, Census County Business Patterns, HUD KC market analysis, and the municipal code), so it can ship ahead of Lula's own quarterly export. Five findings: SFR stock 67.1% pre-1980 vs 60.3% national (metro-wide rental housing reads younger than national, which is why everyone gets this wrong); 65.3% utility gas heat vs 46.5% national; 10.9 hail days/year, exceeding NOAA's own hail alley; roofers the only under-supplied trade at LQ 0.92, in the highest-hail market in the report; MO and KS sides are a regulatory mirror image, with federal lead rules changing administrator at State Line Road. Seven circulating claims contradicted, three via full-text search of the current code (Supplement 139). The "79 freeze-thaw cycles per NIST" figure is untraceable and is replaced with 81.3 derived from NOAA daily observations. Unpublished finding: KCMO has no CO alarm ordinance for long-term rentals despite the gas-heat concentration; the city gives detectors away free via Healthy Homes instead. Operational read: Jackson/Wyandotte portfolios run ~3/4 pre-1980 vs under half in Olathe/Platte, so two books an hour apart carry different maintenance profiles; ~76,500 KC SFRs pre-1980. Precision rule kept in: cite pre-1980, never pre-1978, since ACS bins by decade. Next: Nate confirms this is the format for the program, then which metros follow and whether they run ahead of the data export or wait for it.

• 2026-08-04: Homepage rebuild recommendation delivered, off 23 site teardowns. Tore down 23 homepages across property maintenance, proptech, field service, marketplace, fintech, and B2B SaaS, read against Ahrefs organic performance (pulled 2026-08-03/04). Delivered as a teardown, a screenshot gallery of specific patterns, a separate read on strong sites outside the category, a design mockup, and the rebuild recommendation itself. The diagnosis: the homepage carries seven products (Coordination in both tiers, Pro Network, Flat Rate, Make-Readies, LuMi, Foresight, Lula Pros), and breadth pushes copy up the ladder of abstraction until it says nothing. The fix: one anchor sentence ("Every maintenance job, from the resident's first message to the closed invoice, run by one team") that everything hangs off, which also sets the page boundary so Foresight gets its own module rather than sitting in the main flow. Recommended hero: "The maintenance department you don't have to hire" — a category claim rather than an adjective, keeping the headcount argument that unlocks budget. 14 blocks specified in page order with copy written to be used, each naming its pattern source. Four removals: cartoon illustration, generic benefit copy, service-provider path in body, any unsourced round number. Sequenced this week / next sprint / quarter. Stated limit: this converts existing traffic, it does not create it (2,361 organic visits across 161 keywords; benchmark sites convert 70 and 55 visits per referring domain against Lula's 2.1). Open items: Core vs Core Boost one-liner, Flat Rate catalog scope, and the placeholder figures in the comparison table + named outcomes, which show shape only and must be replaced with verified Lula data before publication. Next: Nate decides scope and order; the two zero-effort wins (methodology lines under existing stats, real figures in the comparison table) can go this week.

• 2026-08-07: After-hours answering service landing page drafted. Built /after-hours-answering-service as the conversion destination for the paid after-hours lead-gen effort with dayparted bid adjustments, and as the commercial organic play for the same space. Primary keyword after hours answering service property management (250 volume, KD 1), also targeting property management answering service (1.6K). The SERP gap is the reason this page exists: every page-1 result is a how-to telling property managers how to handle after-hours calls themselves, and nothing on page 1 positions a service that does it for them. Copy is written for the person landing at 10pm while personally on the hook for the call. Cannibalization split assigned across three assets: this page takes commercial intent, /articles/after-hours-maintenance-calls takes the how-to intent, /articles/best-property-management-answering-service takes evaluation. The article draft currently targets the commercial term and must be re-pointed at the how-to term before either goes live, linking up to this page. Delivered as copy plus a paste-ready build, with three headline variants for Tyler to test. Schema via Yoast (Service + FAQPage), no manual JSON-LD. Next: Nate + Josh review; confirm the three-way intent split; re-point the article draft.

• 2026-08-07: Full blog library inventoried for a strategy relook. Gemma pulled the complete /articles inventory by hand (URL, H1, last-updated date, internal links, external links, primary keyword, secondary keywords, search intent, source doc) to re-examine strategy against what is actually published rather than against what the roadmap assumes. Roughly 70 live articles. Saved to content/2026-08-07-blog-content-inventory.md. First read: the announcement and partnership pieces (Inc. 5000, Ingram's, Rent Manager, Rentvine, Buildium, Bridge Homes) carry no primary keyword, no secondary keywords, and no intent assignment, and several carry no internal links; a block of 2025-dated pages has not been touched since publish. Both groups are refresh-queue candidates rather than reasons for new drafts. Why it matters operationally: two calls this period (stopping the tracking-software outline, correcting the technician scheduling intent) both came from checking a proposed piece against what is already live. The inventory makes that check fast instead of a per-brief investigation. Next: rank the refresh queue against the Q3 priorities.

• 2026-08-07: Technician scheduling article rewritten and republished. Updated and republished /articles/technician-scheduling-software, the one Cluster 2 scheduling spoke Google had crawled but never indexed. The page had been written as a burnout and staffing argument, while the keyword it is named for is a software-evaluation search, so the rewrite matches what the results page actually rewards: a direct definition of technician scheduling software above the fold, a section on what the software does, and a "what to look for" evaluation section built on category framing with no competitors named. The burnout narrative, the property-manager audience, and the Foresight positioning (balanced workload distribution, predictive scheduling, real-time rebalancing) all carry through. Two FAQs added that the body does not cover: how scheduling differs from route optimization, and how the software works alongside an existing PMS. Stat correction: the maintenance turnover figure the piece leaned on measured 2021, and the claim it supported (maintenance turnover well above the broader workforce) does not hold on current data, so both were replaced with 2025 and 2026 figures from the RCLCO compensation survey published by NAA and NAA's Q2 2026 apartment labor report. Next: Indexing requested in GSC 2026-08-07 to force a fresh crawl. First check is whether the page leaves crawled-not-indexed at all, since that is the gate on everything else here. 30-day measurement window 2026-09-06, re-pull positions, index status, and AI Overview presence. Two unclaimed cluster terms worth a roadmap slot: service scheduling software (800 volume, KD 4, the parent topic of this page's keyword) and property maintenance software (1,500 volume, KD 10).

• 2026-07-31: Extreme heat article drafted, second of the extreme weather set, and its publish window moved forward. Research changed the shape of this one. Rather than the freeze piece with the temperature inverted, heat is a duration story: cooling systems run at maximum output for weeks so failures accumulate across a season, the power grid has become part of the maintenance risk, and cooling is starting to be written into habitability law. LA County passed an indoor temperature mandate in August 2025 requiring rental units to be kept at 82°F or cooler, with enforcement beginning January 1, 2027 and a carve-out for owners of 10 or fewer units until 2032. That deadline is why the piece moved from an April/May 2027 publish to January 2027, so it lands while property managers are working the problem rather than after. The compliance shift is the trigger; the body stays in the maintenance-operations lane. Next: Gemma review, then Nate, with a specific legal read requested on the compliance section. Maryland and California cooling requirements were excluded from the draft because they could not be verified on source, and would strengthen it if Lula can confirm them.

• 2026-07-31: Freeze-event article drafted, first of a two-part extreme weather set. A seasonal piece on what happens to a rental portfolio when a freeze hits every unit on the same night: the call flood and triage problem, why the local vendor market saturates at exactly that moment, and why markets that freeze rarely (Texas, Tennessee, and the wider Sunbelt) take more damage per event than cold-climate markets. Built on verified 2025 and 2026 claims data from State Farm and Verisk rather than a seasonal checklist, since that ground is held by the Red Cross and Consumer Reports and is not winnable. Deliberately positioned as an answer-engine play: no rental-framed keyword in this space carries search volume, so it is graded on citation presence rather than sessions. Targeted at a September publish to land inside the freeze-prep window. The companion heat piece is scheduled for winter drafting and an April or May 2027 publish. Next: Gemma review, then Nate. The vendor-capacity section is currently carried by network scale alone and would improve materially if Lula can supply work-order volume data from a past freeze event.

• 2026-07-10: Flat-Rate Maintenance page reworked and a dedicated HVAC page drafted, off the ad learnings. Reworked the copy on the Flat-Rate Maintenance page to lead with "flat-rate maintenance" and the "the quote is the invoice" hook, with HVAC pulled to the front as the interest driver, after the paid ads showed that phrasing and the HVAC angle are what is converting (four ICP leads in a week, with the HVAC creative doing most of the work). Prices were deliberately kept off the page so the pricing form still does its job. Also drafted a new dedicated Flat-Rate HVAC landing page in the Flat-Rate Handyman style (hero quote card, a typical-vendor fee-stack against one flat rate, a three-step flow, and an FAQ), built from the winning ad copy, to ride the current heat-wave demand. Specific HVAC claims (replacement window, warranty terms, supplier buying power) are flagged for Nate to confirm against source-of-truth before publish. Next: Nate reviews the reworked page and the HVAC draft, confirms the flagged HVAC claims, then publish both.

• 2026-07-10: Resident-retention guide refreshed and republished. Updated and republished /articles/how-to-improve-resident-retention with seven proven retention strategies for property managers, from faster maintenance to a friction-free move-in, keeping the guidance and framing current. Next: 30-day measurement window 2026-08-09, re-pull positions and AI Overview presence.

• 2026-07-09: Foresight PropTech Breakthrough award announcement article drafted. An announcement for Foresight being named Property Management Solution of the Year in the 2026 PropTech Breakthrough Awards. Foresight is described accurately as software (a maintenance operating system for property managers who run in-house maintenance teams, sitting behind the PMS and adding AI coordination, smart scheduling and dispatch, predictive pricing, and work-order summaries), distinct from the Core service layer. Includes an award-credibility section and an FAQ block for AI-answer visibility, with a Bo quote drafted for approval. Next: Nate confirms the exact award title + year, the prior "Work Order Management Solution of the Year" win details, and any specific Foresight claims against the Foresight Master Copy Deck, then publish.

• 2026-07-09: Inc. 5000 2026 announcement article drafted. A fresh announcement for Lula's repeat appearance on the Inc. 5000, restructured from last year's post rather than cloned: a growth-as-substance angle, the full product and service sweep (coordination, make-readies, Flat-Rate Maintenance, Foresight, LuMi, and PMS integrations), and a dedicated team-growth section spanning Kansas City and Paraguay. Bo quote drafted for approval. Next: Nate supplies this year's rank + numbers, the consecutive-year count, and the KC + Paraguay headcount details, signs off the Bo quote, then publish.

• 2026-07-09: Tenant-damages guide refreshed and republished. Updated and republished /articles/tenant-caused-damages, ten common examples of tenant-caused damages, how to tell them from normal wear and tear, and how to document and bill each one back, kept current for property managers. Next: 30-day measurement window 2026-08-08, re-pull positions and AI Overview presence.

• 2026-07-08: Core, Core Boost, and the Services catalog consolidated into one Property Maintenance page (built, ready for review). Per the direction set with Nate, merged the three overlapping pages (/core, /core-boost, and the repair-and-maintenance services catalog) into a single Property Maintenance service page at /services, with /core and /core-boost set to 301 into it. The page speaks in customer language (Lula Pro Network + LuMi), retires the internal tier names, and pulls together the platform features, the full repair-and-maintenance services list, a "Works with Any Software" PMS integration strip matching the homepage, the 56-market coverage list, trust proof, and FAQ. Next: confirm three small facts before publish (Inc. 5000 count, current market number, gravityform id), run the pre-301 AEO citation check on /core and /core-boost, then publish and set the redirects; per-service programmatic pages can hang off /services next.

• 2026-07-08: Ingram's Fastest-Growing Companies (KC) 2026 announcement article drafted and sent to Nate. A fresh announcement for Lula's repeat appearance on Ingram's Fastest-Growing Companies in Kansas City, written from a distinct angle (a Kansas City company scaling residential maintenance nationwide, growth measured in work done) rather than a rerun of last year's post. Framing carefully drops the top-spot claim since this is a repeat listing, not #1. All scale numbers refreshed to current figures, and Bo's quote drafted for approval in a hometown-pride framing. Two facts are left as clear confirms for Nate: the exact list placement and this year's qualifying growth percentage (the single number that most strengthens a growth-award post). Next: Nate confirms placement + growth figure and signs off the Bo quote, then publish.

• 2026-07-08: PadSplit vendor-marketplace announcement article drafted and sent to Nate. An announcement article for Lula joining the PadSplit vendor marketplace, written to leverage PadSplit's brand search for AI-answer and organic visibility (PadSplit named in the title, opening line, and FAQ). Positioned carefully as Lula becoming a vendor available to PadSplit hosts, not a partnership, per Nate's steer. Founder quote lines are reserved for Bo Lais and Will Parrish, with an optional PadSplit spokesperson quote left as a clean gap to fill or cut. Two open questions flagged rather than guessed: exactly how a host activates Lula and how billing works. Stats held to approved proof points only; the flagged 80% first-trip figure was not used. Next: Nate reviews and supplies the Bo + Will quotes (and a PadSplit quote if he can get one), confirms the activation + billing mechanics, then publish at /articles/lula-padsplit-vendor-marketplace.

• 2026-07-08: AppFolio customer URL list delivered and refined for the vendor-application outreach run. Built Nate a pre-filtered list of AppFolio customer (property management company) websites to target, mined from AppFolio's backlink profile (each site linking to a branded resident portal is, with high confidence, a customer's own website), then stripped of spam, directories, review sites, and competing PMS vendors, and geo-matched against the 51-market / 11,780-ZIP coverage sheet. Refined per Nate's follow-ups: SEO / link-scheme domains pulled for review, a company-name field added (pulled live from each site), and Lula's existing customers filtered out against Nate's customer export. The list now holds 11,868 unique customer domains, 3,236 already matched to a Lula market to start from. Top matched markets: Los Angeles, San Diego, Seattle, Phoenix, and Dallas-Fort Worth. Every removal is itemized in a separate audit file. Next: Nate works the ICP-matched list first; the unknown-geo tier still needs an on-site geo check, and the softer name-based customer matches are worth a quick eyeball before outreach.

• 2026-07-08: Make-Ready Spoke 1 (Checklist) published, completing the Make-Ready cluster. Published /articles/apartment-make-ready-checklist, a room-by-room 67-item apartment make-ready checklist with a free toolkit (tracker plus priority matrix). This was the last remaining spoke, so all six Make-Ready spokes plus the hub are now live. Published ahead of the toolkit being embedded, so it may be pulled briefly if Nate prefers to wait for the embed. Next: confirm the toolkit/checklist embed with Nate, wire the make-ready lead-magnet load, and apply the hub light-optimization patch; 30-day measurement window 2026-08-07.

• 2026-07-07: Best Property Management Software comparison refreshed and republished. Updated /articles/best-property-management-software, the landlord-facing 2026 software comparison, with verified pricing across AppFolio, Buildium, Rent Manager, and top free tools. Next: 30-day measurement window 2026-08-06, re-pull positions and AI Overview presence.

• 2026-07-06: Make-Ready Spoke 6 (Reduce Days Vacant) published. Live at https://lula.life/articles/reduce-days-vacant. The highest-commercial-intent spoke in the Make-Ready cluster: what days vacant costs, single-family vs multifamily benchmarks, the five drivers of long vacancies, and eight tactics to compress days vacant, positioning Lula's 72-hour make-ready model as the highest-leverage operational lever. Coverage sentence lists all 17 metros; wired to the hub, cost, and timeline spokes plus the make-ready service page. Only Spoke 1 (Checklist) now remains to publish in the cluster. Next: 30-day measurement window 2026-08-05, re-pull positions and AI Overview presence on "days vacant"-family queries.

• 2026-07-06: Resident-satisfaction article refreshed around the 2026 Renter Preferences Report. Updated and republished /articles/critical-insights-for-property-managers-leveraging-tech-and-communication-to-boost-resident-satisfaction, retitled to lead with AppFolio's 2026 Renter Preferences Report (3,002 renters surveyed) and its finding that maintenance is the #1 driver of resident satisfaction. Reframes the tech-and-communication guidance around the fresh 2026 data (renewal, move-intent, and referral lift from maintenance and communication satisfaction) and closes on the Lula + AppFolio Smart Maintenance integration. Next: 30-day measurement window 2026-08-05, re-pull positions and AI Overview presence.

• 2026-07-02: Appliance-replacement-procedures guide refreshed and republished. Updated and republished /articles/why-property-managers-need-appliance-replacement-procedures, keeping the appliance repair-vs-replace guidance current for property managers. Next: 30-day measurement window 2026-08-01, re-pull positions and AI Overview presence.

• 2026-07-02: Centralized-maintenance article rescued from a hidden indexing miss. The 30-day check on /articles/centralized-maintenance (published 5/29) found it getting zero search exposure. Root cause: Google had discovered the page but never crawled or indexed it, because no other pages linked to it (an orphan page). Fixed it by adding three in-context internal links from high-authority, already-indexed pages: the make-ready guide, the "best property management maintenance software" comparison, and the deferred-maintenance article. Requested indexing in Search Console to trigger a fresh crawl. Next: confirm the page indexes over the next week or two, then re-run the 30-day measurement (rankings, impressions, AI Overview presence) once it is actually in the index. Also worth a quick orphan check on other recently published articles.

• 2026-07-02: 16 of 17 local make-ready market pages now live. Atlanta, Cincinnati, Cleveland, Columbus, Dallas-Fort Worth, Dayton, Houston, Indianapolis, Kansas City, Memphis, Minneapolis, Oklahoma City, Orlando, Phoenix, Tampa, and Tulsa are published, each with its local W-2 field manager, market-specific make-ready content, and a "Talk to a Field Manager" CTA. Next: Nate deploys the per-city JSON-LD schema via GTM; St. Louis follows once its field-manager details arrive; verify phone numbers and the few unconfirmed cost figures on the live pages; Yoast config per city.

• 2026-07-01: Preventive Maintenance Examples spoke live at https://lula.life/articles/preventive-maintenance-examples. Second published surface in the Maintenance Fundamentals cluster, sitting behind the property-maintenance pillar and written to verified Lula proof points. Next: Checklist and Strategies follow from Nate's editorial queue; Common Issues in draft.

• 2026-06-30: Maintenance Strategies spoke drafted (Maintenance Fundamentals cluster). Third spoke behind the live Property Maintenance pillar: a guide to the four maintenance strategies (reactive, preventive, predictive, routine) and how to weight the mix as a portfolio grows, targeting property maintenance strategies (/articles/property-maintenance-strategies). Built to verified Lula proof points only (9,000+ Pros, 50+ markets) and wired into the pillar's maturity model, the preventive-examples spoke, and the deferred-maintenance page. Leads with a direct-answer summary and a four-way comparison table for answer-engine pickup. Next: publish behind the pillar with the other two drafted spokes and wire internal links; one spoke (Common Issues) still to draft.

• 2026-06-29: Footer re-imagine produced and handed to Nate. Reworked the site footer information architecture at Nate's request. The current footer mixes products, services, and content in one undifferentiated "Resources" list; the new structure groups links by what they actually are: Software (Foresight, LuMi), Maintenance (Coordination, Services, Make-Readies, Flat-Rate Maintenance, Vendor Network), Integrations (AppFolio plus all integrations), For Pros (become a pro, pro app, pro login), Company, and Resources. Adds an Integrations group so AppFolio finally has footer presence, an inline newsletter email capture, a scale line, and keeps the AppFolio Stack and NARPM trust badges. Also removes the hidden dead app-badge block flagged in the June broken-link audit while the template is open. Delivered as a brand-styled mockup image plus a build spec. Next: Nate review, then Lula dev builds the new footer template.

• 2026-06-29: AppFolio integration content opportunity scoped; direction set on integration-page Q&A (AEO). Worked through whether the recent AppFolio Realm-X / Maintenance Performer news warranted a content push. Finding: these integration topics get very little classic search, so the value is answer-engine visibility, being the cited answer when property managers ask AI assistants about AppFolio maintenance (tracked in Brand Radar), not rankings. Landed with Nate on the sharper play: improve Lula's existing PMS integration pages, starting with a questions-and-answers block on each, beginning with AppFolio as the template before rolling out to Buildium, Rentvine, Rent Manager, and Property Meld. Gemma's FAQ sheet was forwarded to Nate to seed the question set. Positioning frame carried through: AppFolio's AI coordinates the work, Lula fulfills it through the vetted Pro network. Next: on Nate's go, draft the full AppFolio Q&A set as the template, then clone the structure to the other PMS pages with page-specific answers.

• 2026-06-26: Property Maintenance pillar guide published at https://lula.life/articles/property-maintenance-for-rentals. The hub of the new Maintenance Fundamentals cluster is live: a broad property-maintenance guide framed for rental owners and property managers, written to verified Lula proof points and wired into the existing software, deferred-maintenance, and make-ready pages. It targets a core informational head term where Lula previously had no ranking presence (a content gap surfaced in the Ahrefs competitor analysis) and where an AI Overview is already present, so it doubles as an answer-engine play. Next: publish the cluster spokes behind it (Checklist and Preventive Maintenance Examples are drafted; Strategies and Common Issues still to write), wiring internal links as each goes live; 30-day measurement window 2026-07-26.

• 2026-06-26: Resident and property-manager reviews page built and handed to Nate. A new reviews page produced in the Lula site style, pulling the strongest customer reviews from the public Google profile into a curated, on-brand wall grouped by service and audience. It leads with a featured customer story and a five-star summary, shows the range of work covered (HVAC, plumbing, electrical, appliances, remodels, general repairs), and keeps resident reviews and property-manager reviews separate so a PM / resident toggle can switch on later. Designed to refresh quarterly so it stays current. Page-matched JSON-LD schema (BreadcrumbList plus Review markup, tied to the existing Lula entity) built alongside it. Passed to Nate via Trello 2026-06-26 for review and publish. Next: Nate / dev to confirm the hero image and contact form, paste the schema block, and publish; gathering more property-manager reviews is the parallel priority, since PM proof is currently thin against strong resident volume.

• 2026-06-25: llms.txt is now live on lula.life. The curated llms.txt file is published and serving at lula.life/llms.txt, the emerging standard file that tells AI answer engines what a company is, what it offers, and which pages to trust. Confirmed loading correctly as plain text with every section and link intact. It gives AI assistants a clean, deliberate description of the platform (the 9,000+ Pro network, Foresight software, and the LuMi intelligence layer), how the pieces integrate and coordinate work, and a hand-picked map of the pages worth citing, rather than leaving them to piece it together from a raw crawl. Next: re-check the linked pages each quarter to keep the file current.

• 2026-06-24: Maintenance Fundamentals content cluster planned and three drafts produced. A new hub-and-spoke cluster targeting core property-maintenance search terms where Lula has no current ranking, a competitor gap surfaced in the Ahrefs analysis, framed for property managers and single-family rentals. The pillar guide ("Property Maintenance"), a recurring Property Maintenance Checklist, and a Preventive Maintenance Examples guide are drafted, written to verified Lula proof points only, and scoped so the new Checklist does not compete with the existing rental-inspection-checklist page. Next: draft the two remaining spokes (Maintenance Strategies, Common Maintenance Issues), confirm the demo CTA link, and publish the pillar first, then the spokes.

• 2026-06-24: AI answer-engine visibility tracking went live for Lula. Stood up monitoring in Ahrefs Brand Radar to measure how often Lula gets cited when property managers ask AI assistants for help, the new front door to discovery alongside Google. A focused starter set of five prompts is now tracked, spanning the highest-value buyer searches (best property maintenance software, how to manage work orders and vendors at scale), the core maintenance pain points Lula solves, and brand recognition (whether AI engines correctly identify Lula as the property-maintenance platform). This gives a baseline for AI share-of-voice we can grow against as more content lands. Next: first visibility read at the 30-day mark; expand the tracked prompt set as the plan allows.

• 2026-06-23: Apartment-turnover guide tuned for benchmark queries (quick win shipped). Made small on-page search edits to /articles/best-ways-to-cut-down-on-apartment-turnover-time to capture a cluster of low-difficulty benchmark queries sitting one position off page 1: "apartment turnover rate" (volume 200, position 9), "unit turnover" (position 6), and "average tenant turnover rate" (position 8), roughly 370 combined monthly searches at low difficulty. The page already ranks well on its core terms, so these were light surface-the-query edits, not a rewrite, and the published date was intentionally left unchanged. First of the three 2026-06-22 quick wins to land. Next: 30-day measurement window 2026-07-23, re-pull positions on the three benchmark queries; entity-disambiguation pass and /articles archive recovery still to come.

• 2026-06-23: llms.txt file drafted for lula.life and handed to Nate. Created a curated llms.txt for the site, the emerging standard file that tells AI answer engines what a company is, what it offers, and which pages to trust. It opens with a plain-language description of Lula (the maintenance platform: the 9,000+ Pro network, Foresight software, and the LuMi intelligence layer) and what Lula is not, then points to the key services, software, integration, guide, and company pages. Hand-written rather than auto-generated, so the positioning, page selection, and category framing are deliberate rather than a raw page dump. Every linked page was checked live. Came with a short implementation guide covering exactly where the file has to live and the cleanest way to publish it on WordPress. Next: Nate / dev to host it at lula.life/llms.txt, then confirm it loads.

• 2026-06-23: Integrations page structured-data error diagnosed, fix handed to Nate. A validation check flagged one remaining issue on the Integrations page: a parsing error in the page's structured data ("Missing '}' or object member name"), which makes the affected items invalid and ineligible for Google's rich results. Traced to a single malformed spot in the schema where one object was never closed before the next began. The fix is a one-line correction (close the open object and add the separating comma). Pinned the exact location and change in the Trello card. Next: apply the one-line schema fix, then re-validate to confirm the page is rich-results eligible.

• 2026-06-22: Maintenance Budget Calculator landing page built. A new interactive tool for property managers: enter your monthly work-order volume, average invoice, and how much a job's cost tends to swing, and see the annual maintenance budget range that variable pricing leaves you forecasting against, the spread you cannot plan around. It carries the Flat-Rate predictability story, with a plain-language readout of what the number means, a short note on how it is calculated, a clear disclaimer, and a book-a-demo path. Styled to the Lula site with a new hero illustration and supporting card icons. Next: publish at /flat-rate-maintenance-calculator, then connect the lead-capture form so each result becomes a qualified lead with its portfolio numbers attached.

• 2026-06-22: Three quick-win search optimizations surfaced and underway. A scan of pages sitting just off page 1 surfaced three low-effort, high-leverage moves. (1) Add a benchmark-rate block to the apartment-turnover guide to capture "apartment turnover rate" and "unit turnover," both one position off page 1 (about 370 combined monthly searches). (2) Resume the sitewide "Lula" brand-entity fix on the top pages, where the homepage still ranks only around 12th for the brand name itself. (3) Recover the /articles blog archive, which is slipping on "property management blog" and "property managers blog" (positions 5 and 7). Next: ship the turnover block, run the entity pass on the top five pages, and confirm the archive edit path.

• 2026-06-18: Flat-Rate Handyman launch content produced. A full content set for the Flat-Rate Handyman push: a content program brief that gives blog, social, and email one shared positioning and messaging foundation; a blog announcement; a conversion landing page built in the make-ready page style (hero catalog visual, a three-step walkthrough with custom step graphics, and the customer-success image in the closing call to action); and a press release. Grounded in fresh property-manager research, with the through-line that predictable, transparent, catalog-based pricing turns maintenance from a churn risk into a retention win. Next: finalize against Nate's edits, confirm the demo form and a couple of open product details, then publish to land with the launch.

• 2026-06-17: Broken-link audit reviewed and handed to Nate. A site audit flagged broken outbound links across ~36 pages. Diagnosed down to a single real issue: a dead Google Play app-badge link living in a footer block that is hidden from view, so no visitor ever sees or clicks it. Cleanest fix is removing that hidden block from the footer template, which clears every flagged page at once. The AppFolio badge links also flagged but are false positives (AppFolio blocks the audit crawler; the links return 200 for real visitors and for Google). Info passed to Nate. Next: Nate / dev to remove the hidden footer block, then re-run the audit to confirm the flags clear.

• 2026-06-16: Three on-page optimizations shipped across the article library. Surgical edits to three ranking articles to push high-intent queries sitting just off page 1. (1) /articles/deferred-maintenance gained three internal links from related maintenance articles to build topical authority behind "what is deferred maintenance in real estate" (position 7, already position 2 on the core term). (2) /articles/best-property-management-software had its intro, a section heading, and an FAQ reworded to capture "property management software ratings" and "most popular property management software" (positions 11-12, roughly 400 combined monthly searches). (3) /articles/rental-inspection-checklist had a section heading and a sentence updated to target the "routine" and "quarterly" rental inspection checklist queries (positions 7-10). Next: 30-day measurement window 2026-07-16.

• 2026-06-16: 16 of 17 local make-ready market pages built and loaded into WordPress, ready to publish. Atlanta, Cincinnati, Cleveland, Columbus, Dallas-Fort Worth, Dayton, Houston, Indianapolis, Kansas City, Memphis, Minneapolis, Oklahoma City, Orlando, Phoenix, Tampa, and Tulsa each have a full local market page: the market's W-2 field manager front and center (photo, bio, direct contact), make-ready content tailored to that metro (seasonality, climate, neighborhoods, county coverage, and ZIP service area), and a "Talk to a Field Manager" call to action. Every page's counties, neighborhoods, employers, climate, and ZIP codes were fact-checked against public sources and the master coverage sheet before load-in. Next: publish from preview to live, link them from the main /make-ready/ markets section, and build St. Louis once its field-manager details arrive (the only market still outstanding).

• 2026-06-09: Bing crawl throttle cleared. Bing Webmaster Tools flagged a High-severity "limited crawl capacity" recommendation. Root cause was a crawl-rate setting in Webmaster Tools held at the slow band across every hour of the day, capping how much Bing would crawl. Lifted it to full crawl rate around the clock. robots.txt and the sitemaps were already clean (no parameter sprawl or low-value URLs to exclude), so this was the only lever. The recommendation clears on Bing's next crawl pass. Next: confirm it drops off the Webmaster Tools recommendations within a week.

• 2026-06-08: Maintenance performance claims corrected across the content set. Removed the unverified "80% one-trip resolution rate" stat (an industry-benchmark figure from the Vendor Performance Scorecard lead magnet, not a Lula performance metric) along with the unsupported "3.8-day turnaround," "coordination within 10 minutes," and "60 to 65% reduction in coordination time" claims wherever they appeared in body copy. Each was reframed onto verified scale proof (9,000+ maintenance Pros, 350,000+ properties served) while keeping the original benefit framing intact: fewer repeat visits, less resident disruption, freed coordinator capacity for renewals. Affected the LuMi landing, the maintenance-scheduling, AI-work-order, AI-scheduling, and predictive-maintenance hub surfaces, plus the lease-renewal retention and downtime/repair-delay pieces. Next: the three performance metrics Nate is confirming (average turnaround, coordination-start time, maintenance time saved — see Pending) can drop back in once verified.

• 2026-06-05: Source7 partnership announcement article published at https://lula.life/articles/source7-foresight-integration. The partner-supportive piece for Source7 (the appliance-data company integrated into Lula) went live alongside Source7's PR Newswire press release. Predictive-maintenance / repair-vs-replace angle, dropping into the preventive-maintenance cluster and reinforcing the 200,000+ work orders data-volume story. Strengthens the Foresight narrative through the Source7 integration and gives Lula a citable asset on the partnership. Next: monitor for citation pickup; 30-day measurement window 2026-07-05.

• 2026-06-02: AI property management software comparison article drafted (competitive response to Vendoroo's organic surge). Nate flagged a competitor's sudden organic increase on AI-property-management queries; analyzed their ranking page + AEO visibility and built a sharper version, Best AI Property Management Software in 2026 (target keyword ai property management software), ranking Lula first for AI maintenance coordination (LuMi + Foresight) on the "automate your costliest workflow first" thesis. Ready for editing, not yet live. Next: editing pass, then publish.

• 2026-06-05: LuMi announcement article revised and aligned to the approved positioning. Reworked the product announcement article (/articles/lumi-ai-maintenance-intake) against the May 2026 LuMi Positioning Brief. LuMi now leads as Lula Maintenance Intelligence, the AI behind every maintenance experience, with intake framed as how it shows up here rather than as a standalone product. Added the approved data-credibility block (7 years, 500K+ work orders, 50+ markets, always learning) and swapped in approved proof points (70% fewer re-calls, 9,000+ Pros, 3.8-day turnaround). Removed the inaccurate "80% one-trip resolution" claim and tightened the voice (no contrast framing, no em dashes). Next: holds for the launch go/no-go; the 70-80% handle rate and the Brandywine/Truehold/Bridge customer references still need Nate's confirmation before publish.

• 2026-06-03: Property-maintenance-software listicle updated, Lula section reworked around LuMi. Surgical on-page edits to /articles/best-property-management-maintenance-software (the cluster's top organic workhorse, #1 on best property maintenance software-family queries) to firm up rankings after recent mixed tracking signals. The Lula entry was reworked to center LuMi as the AI layer running maintenance coordination end to end, with Foresight positioned for in-house teams. Section sent back to Nate for review. Next: confirm the flagged performance metrics with Nate (see Pending), then finalize; 30-day measurement window 2026-07-03.

• 2026-06-01: Make-Ready Spoke 4 (vs Apartment Turnover) drafted and in editing. Full spoke produced distinguishing the apartment-turnover lifecycle from the make-ready subset: a quick-answer summary, side-by-side comparison, the ten-stage turnover process, the KPIs that matter (days vacant, turnover rate, vacancy loss, cost per turn), and reduction levers, all on an owner-facing angle. Now in an editing pass before publish. Next: finalize edits and publish; remaining production order is Spoke 6 (Reduce Days Vacant), 2 (Cost), 3 (Timeline), then 5 (Technician).

• 2026-06-01: Make-Ready PDF partner prospect list extended to 87 verified PMs. Added two more PMS-vendor ecosystems (Yardi, Propertyware) to the earlier four, taking the sourcing pool to six. After individual verification, with brokerages, owner-operators, software vendors, and non-US firms screened out, the master tracker holds 87 confirmed US property-management companies: 18 with explicit make-ready language and 69 confirmed PMs. Referring-domain sourcing has reached diminishing returns (each added vendor now surfaces only a handful of new PMs), so the final stretch to 100 will come from vendor customer/case-study pages and the NARPM member directory. Next: source the remaining ~13, then hosting URL slug and Nate-voiced outreach email.

• 2026-06-01: Make-Ready owner-facing PDF drafted and designed. The brand-neutral 5-page research brief for the PM-partner backlink program is written and laid out (cover, what a managed make-ready is, the owner-facing case, the wealth angle, and a five-question checklist for owners to use on any manager). Sourcing was resolved cleanly: the 2025 US median single-family rent is cited from the Rentometer 2025 Annual SFR Report ($2,100/mo), the portfolio-wealth math is presented as illustrative on the owner's own turn numbers, and a planned Peter Lohmann citation was dropped after the latest edition turned out to be a 2024 report with no make-ready data. No CTA, light Lula attribution, reads as research. Next: Nate review for owner-audience tone and any factual corrections, then hosting URL and outreach.

• 2026-05-29: PM-partner PDF backlink program scoped end-to-end and 85 prospects sourced. Strategic call 2026-05-28 with Nate locked the campaign shape (brand-neutral owner-facing PDF distributed to PM companies as a lead-gen asset, link back to /articles/what-is-a-make-ready in exchange). Built the sourcing pipeline today: four PMS-vendor referring-domain CSVs (AppFolio, Buildium, Rentvine, DoorLoop) processed through a Python filter, 2,893 unique domains classified, top candidates WebFetch-verified via subagent runs. Master tracker live as a Google Sheet (lula-prospect-tracker-makeready-2026-05-29) with 85 prospects in 3 tiers: 18 Tier A (explicit make-ready signal on homepage, pitch first), 64 Tier B (confirmed PMs without explicit make-ready language), 3 Tier C (manual verification needed). Cross-vendor confirmed in 20 cases. Next: one more vendor CSV to clear 100, PDF design ownership decision, hosting URL slug, Nate-voiced outreach email.

• 2026-05-29: Cluster 6 centralized-maintenance spoke shipped live. Published at https://lula.life/articles/centralized-maintenance. First Cluster 6 surface area for Lula, targeting centralized maintenance (KD 0, vol 30, AI Overview present) with the vendor-network-centralization wedge no competitor in the SERP makes. Next: 30-day measurement window 2026-06-28; consider productizing the in-article "Centralization Gap" assessment as the Cluster 6 lead magnet.

• 2026-05-25: Make-Ready city-page expansion produced. Atlanta sample page built (full local-SEO city-page template with branded dark statement block, schema, NAP, embedded Google Map, county/state variation, 10 city-specific FAQs). 17-city data-collection spreadsheet built with 13 [LULA] columns for the team to fill and 11 [RESEARCH] columns pre-populated per city (avg SFR rent, daily vacancy cost, peak season, days to lease, counties, neighborhoods, ZIPs, climate factors, pre-1978 stock notes, employer/school patterns, Maps URL). Next: Lula team fills the team-side columns; templated rollout of remaining 16 city pages follows.

• 2026-05-25: Agentic-maintenance competitive intel + Foresight-light positioning produced. Three competitor deep-dives (Vendoroo, Mason, Haven) plus cross-cutting synthesis with a ranked like-for-like wedge stack led by vendor-network-included. Next: wedge-stack confirmation with Nate, pricing-model decision.

• 2026-05-21: Make-Ready hub patch produced. Generated the find-and-replace patch set for the live /articles/what-is-a-make-ready hub: 9 patches covering stale-stat swaps to NAA 2025 data, the 3-day vs 72-hour fix, 9 to 11 metros, voice fixes, and the Spoke 1 cluster-activation link. Next: apply the patches in WordPress.

• 2026-05-20: Make-Ready Spoke 1 (Checklist) brief and article produced, lead magnet and 2 content rules locked. Full Spoke 1 production pass via the Lula skill stack: a zero-ambiguity brief plus a verified ~2,650-word article draft, voice-clean, pending Gemma final read and publish. Lead magnet locked: Gemma's existing Google Sheet repositioned as "The Make-Ready Operations Toolkit," gated week 1, with a printable PDF mirror to design. Money-page rewrite done by Gemma and signed off. Two content rules locked for all future work: 2025-or-newer stats only, and no fabricated operational provenance. Next: hub patch, then Spokes 4, 6, 2, 3, 5.

• 2026-05-18: /buildium pre-Phase-2 diagnostic and hub-landing wiring verified. Confirmed all 3 Foresight hub landings live and all 12 Cluster 1, 2, and 4 spokes plus the buyer's guide linking correctly. The /buildium diagnostic found near-zero organic search demand, so the page should be reframed as a conversion landing for direct and branded traffic rather than an SEO play. Next: run the same diagnostic on /appfolio, /rentvine, /rentmanager, and /propertymeld before Phase 2 Week 5. Full spec at work/artifacts/2026-05-18-buildium-diagnostic.md.

• 2026-05-15: Make-Ready cluster execution kicked off. Strategic plan locked 2026-05-14: 6 spokes plus money-page rewrite plus hub optimization, projected ~1,300 net new visits per month at 12 months. 4 of 6 spoke drafts produced as Google Docs (Checklist, Cost, vs Apartment Turnover, Reduce Days Vacant). Next: Spokes 3 and 5, money page, and hub edits over the following weeks.

• 2026-05-15: Cluster and internal-link map shipped to lula.propsaasgrowth.com/map. New dashboard surface visualizing Lula's topical clusters and internal link graph: 244 indexable pages with URL rating, traffic, and inlink counts, plus orphan and authority-concentration findings. Refresh runbook at operations/cluster-map-refresh.md.

• 2026-05-15: property management work order system buyer's guide shipped live (Cluster 1). Published a 2,157-word buyer's guide at /blog/property-management-work-order-system, built with the full Lula skill stack, voice gates passed. Closes the Cluster 1 buyer's guide loop opened 2026-05-08. Next: 30-day measurement window 2026-06-14, and wire the reciprocal link from the Cluster 1 hub.

Open items pending Nate input

• LuMi launch go/no-go + customer-name permissions (Brandywine/Truehold/Bridge) + handle-rate confirmation (positioning now signed off)
• Core / Core Boost / Core Premium naming current state
• Attribution stack clarity for demo attribution — needed for lagging indicators
• Per-URL GSC data on 10 priority Foresight-cluster articles (Gemma can pull, but Nate access useful for some)
• Provider-recruitment geo page duplicate audit — flag and prioritize Q3 if needed

What we're explicitly NOT doing this quarter

(See strategy/icp-traffic-roadmap-2026-Q2-Q3.md for full list.)

• New blog content on Clusters 5-8 (After-Hours, Disconnected Systems, Inventory/CapEx, Training)
• More Foresight/predictive blog spokes (existing get title rewrites + link wiring; no new)
• AEO citation tracker build (defer to Q3)
• Wikipedia attempts (defer indefinitely)
• Tangential blog posts (lease renewals, fair housing, landlord-tenant disputes)
• Help center subdomain SEO

Standing meetings + reporting rhythm

• Weekly check-in (Fridays, ~30 min): Gemma + Nate. Shipped, blocked, next.
• Monthly check-in (last Friday of month, ~45 min): Phase vs plan; update this file.
• Quarterly revisit (2026-07-23, ~90 min): Full scope review; update audit + roadmap.

Tools / infrastructure in use

• Ahrefs MCP (via Claude) — domain + per-URL data
• GSC (Gemma access) — URL Inspection + queries
• Looker Studio — dashboards
• Surfer SEO — content optimization
• WordPress + Yoast — CMS
• Trello — editorial pipeline (Nate edits)
• Microsoft Clarity — page behavior
• 27+ Lula-specific Claude Skills — content production stack
• GitHub repo (nateatlula/Lula-mrktng-Claude-skills) — skills versioning
• Foresight Master Copy Deck 2026 — source-of-truth for positioning (Bo-approved)

Update cadence for this file

• Weekly: Update "Pending Nate verification," "Active delivery streams," and "Recently completed." Move any "Recently completed" entry past 7 days into active-work-archive.md so the section stays scannable.
• Monthly: Roll up and review delivery streams.
• Quarterly: Full review; update against roadmap; retire/add streams.