← All weekly rollups

Lula Weekly Status, Week of September 21, 2026

From: Gemma Period: 2026-09-21 to 2026-09-27

Executive summary

Three pages were refreshed and are live. The make-ready city pages are moving up as a group, which is the cluster working as designed, and one finding this week says to slow down and fix something first.

The make-ready service area does not reconcile. Make-ready is gated to 11 staffed metros, each requiring a W-2 field manager in market. Three cities with live indexable pages are not on that list: Cleveland, Dayton and Tulsa. Their H1s read "run by a local Lula W-2." This week Dayton entered the rankings at position 1. Phoenix, which is a staffed metro, has no page at all.

So the cluster is gaining position fastest on a page Lula cannot currently deliver against, while a market it can deliver in has nothing to rank. That is the first thing to fix, and it is a decision rather than a build.

The second pattern is where the cluster is winning and where it is losing. City pages gained across the board. The article that has been absorbing the generic searches lost ground on the terms with real search volume behind them.

Delivered this week

Refreshed and live

/predictive-maintenance-software, refreshed Tuesday after the refresh brief was checked against the live page and rewritten. Four of the brief's five premises did not survive that check. Schema was already present, the FAQ already had six populated answers, the date fields were already being emitted, and the two broken app store links are in the site-wide footer rather than on this page. Only the thin word count held.

The page-one framing was also wrong. Roughly 90 percent of the impressions on that page are site-operator queries at zero clicks, the same automated pattern logged on the NARPM page the week before, so there was no human position to push. Real human queries over 90 days came to under 40 impressions.

The more useful finding underneath it: the head term is the wrong search result page. Predictive maintenance software carries 2,000 monthly searches at low difficulty, and the top ten is C3 AI, AspenTech, Rockwell Automation and Prometheus Group, every result industrial and assuming condition-monitoring hardware. Where the demand actually sits, with Lula's real competitive set on page one, is property maintenance software at 1,600, property management maintenance software at 600 and property management work order software at 150. No Lula product landing page targets any of them. Property maintenance software is currently answered by a Denver recruiting page at position 9 on 360 impressions and zero clicks, which is a provider page ranking for a buyer term.

/articles/best-property-management-software, refreshed Tuesday with the priority internal link fix applied.

/articles/maintenance-automation, refreshed Sunday.

Fixed

Make-ready city page images, 7.6MB down to 124KB across the set. The Pro portraits were shipping at full camera resolution, which was the largest payload on those templates and the clearest of the Core Web Vitals findings in the audit. It lands on exactly the city pages that are gaining position.

Audited

The full site audit was rebuilt on a corrected crawl, with Core Web Vitals findings added. The make-ready service area mismatch came out of that pass.

In flight

  • Flat Rate hub page rebuild. Mockup v8 and the copy document went to Nate on September 17 and are waiting on review. Also needs the full resolution Pro portraits, three subject photos, and four decisions from the master strategy.
  • Make-ready city pages. Gaining. Held on the service area decision below before any further expansion.
  • Help center migration. Half finished. The navigation and footer still link to 54 redirectors, and 25 pages are still live on the main domain.
  • Site-wide soft 404. Any nonexistent single-segment URL returns a 200 and renders an article. Search Console already flags it.

Measurement highlights

Make-ready cluster rankings. The city pages moved as a group, week over week:

  • Dayton, new at position 1
  • St. Louis, 9 to 4
  • Indianapolis, 12 to 5
  • Kansas City, 5 to 3
  • Atlanta, new at 6

Of those five, three are staffed metros, and Dayton is not. Indianapolis is gaining on the hub rather than on its own city page, which is worth correcting because the city page is the one built to convert.

Most of these city terms carry little or no measured search volume, so treat them as evidence the cluster structure is being understood rather than as traffic. The terms that do carry volume tell a sharper story, and it is mixed:

  • Make ready maintenance, 150 monthly searches, improved 7 to 5
  • Make ready services, 100 monthly searches, slipped 3 to 7
  • Apartment make readies, 80 monthly searches, was position 1 and is now outside the tracked range
  • Make ready service, 50 monthly searches, was position 4 and is now outside the tracked range

All four of those sit on the make-ready article rather than on a city page. The city pages are gaining and the article is losing the head terms. That is the thing to look at next week, and the first question is whether the article and the hub are now competing for the same searches after the recent refreshes.

Cleveland also dropped out of the tracked range, from 16, and Cincinnati from 11. Cleveland is one of the three unstaffed cities, so that particular loss is not a problem to solve.

Traffic, citations and backlinks. No material change to report this week.

Blockers and open items

  • The make-ready service area, and it is the priority. Cleveland, Dayton and Tulsa have live indexable pages promising a local W-2 field manager in markets that are not on the staffed list. Dayton is now ranking first. Either those markets get staffed, or the pages come down or change what they promise. This is a decision only Lula can make, and it is currently a live claim on the site.
  • Phoenix has no make-ready page, and it is a staffed metro. The inverse of the problem above, and a straightforward build once confirmed.
  • Flat Rate hub rebuild, waiting on Nate: mockup and copy review, the full resolution portraits, three subject photos, and four strategy decisions.
  • Product claims on /predictive-maintenance-software. Predictive maintenance and failure forecasting are listed as roadmap rather than shipped, and one claim is still live in the meta description. An unsourced "up to 80 percent" line is also still above the fold in section 6.
  • Footer app store links. Both 404 site-wide.
  • No product landing page targets the terms where the demand actually is. Property maintenance software, property management maintenance software and property management work order software are all unclaimed. Needs a decision on whether to build.

Next week's priorities

  1. Resolve the make-ready service area: confirm staffed markets, then fix Cleveland, Dayton and Tulsa, and build Phoenix.
  2. Check whether the make-ready article and hub are competing for the head terms that slipped this week, and repoint Indianapolis at its city page.
  3. Pull the retired product claims off /predictive-maintenance-software, including the meta description and the unsourced 80 percent line.