Google's LSA Algorithm Now Penalizes Underutilized Moving Crews

Google deployed a quiet but significant update to its Local Services Ads algorithm for moving companies in early October 2026. The new ranking factor: appointment density—the percentage of available technician hours actually booked with paid jobs.

Movers running lean crews with high utilization are seeing their cost-per-lead drop 30–50%. Companies with excess capacity, poor dispatch coordination, or scheduling slack are paying more for the same volume of leads.

This is not a marginal tweak. It is a structural shift that rewards operational infrastructure over marketing budget.

Why Google Introduced It

Local Services Ads were designed to surface providers who can actually fulfill customer demand. Google loses when a homeowner books through LSA and then gets pushed out three weeks because the mover overcommitted or the crew scheduler didn't sync capacity with ad spend.

Appointment density is a proxy for operational reliability. A moving company with 85% crew utilization has built infrastructure to forecast demand, route crews efficiently, and eliminate scheduling slack. A company with 40% utilization is either overstaffed, underbooked, or managing dispatch with a spreadsheet and prayer.

Google's incentive aligns with the customer's: they want providers who can book fast, show up on time, and execute without operational friction.

The mechanic is simple. Google already tracks booking rate, cancellation rate, and review velocity through the LSA dashboard. Now they are layering in crew utilization data—pulled from integrations with scheduling platforms or inferred from booking patterns relative to stated availability.

If you tell Google you have four crews available Monday through Saturday, 8 AM to 6 PM, and only 40% of those hours convert to booked jobs, your ad rank drops and your cost-per-lead climbs. If you run the same crew capacity at 80% density, you pay less for better placement.

How Appointment Density Is Calculated

Google does not publish the exact formula, but operators who have seen cost-per-lead changes can reverse-engineer the mechanic.

Appointment density = booked hours ÷ available hours.

Booked hours are the sum of all scheduled job durations. For a moving company, that is the estimated time per job—typically a range entered at booking, not actual clock time. A three-bedroom house might book a four-hour window. A studio apartment books two hours. A commercial office move books eight.

Available hours are the hours you signal to Google as open for booking. This includes crew capacity multiplied by shift length, minus any blocked time for maintenance, travel between jobs, or internal tasks.

If you run three crews, six days a week, eight-hour shifts, you have 144 available hours per week. If those crews complete 115 hours of booked jobs, your appointment density is 80%.

The threshold appears to be around 70%. Operators consistently above that mark are seeing lower cost-per-lead. Operators below 50% are seeing increases of 20–40%.

Google is not penalizing small operators. A one-truck moving company running at 75% utilization will outrank a ten-truck fleet at 45%, all else equal. The signal is efficiency, not scale.

Why This Hurts Traditional Movers

Most moving companies manage scheduling with a combination of phone calls, text threads, and a wall calendar. The owner or dispatcher juggles inbound lead volume, crew availability, truck maintenance, and customer reschedules in real time.

This model produces three structural problems that torpedo appointment density.

First: overstated availability. Many movers list all crews as available seven days a week to maximize lead volume, then scramble to fill the calendar. Google interprets this as low utilization because the stated capacity far exceeds actual bookings.

Second: scheduling slack. Jobs are padded with buffer time to account for traffic, customer delays, or crew inefficiency. A four-hour move gets booked as a six-hour window. That two-hour gap counts as unutilized capacity in Google's calculation, even though it is operationally necessary.

Third: poor demand forecasting. Moving demand is volatile and seasonal. A company might staff for peak summer volume but run those same crews through the winter, producing 30% utilization from November to February. Google averages this over time, dragging down ad rank even during high season.

These are not operational failures. They are the predictable outcome of managing a complex scheduling problem without infrastructure.

What High-Density Operators Build

The moving companies seeing cost-per-lead improvements built three interconnected systems.

Dynamic Capacity Signaling

They do not advertise static availability. They adjust crew capacity in real time based on actual bookings, job pipeline, and forecast demand.

A moving company with four crews does not tell Google all four are available every day. Instead, they signal availability based on rolling seven-day utilization. If three crews are booked at 80% for the next week, they throttle LSA availability to match actual open capacity—perhaps two crews, four days. This keeps appointment density high and prevents overbooking.

This requires integration between scheduling software and LSA settings. Manual updates lag too far behind actual bookings to maintain density.

Tighter Job Duration Estimates

High-density operators use historical data to shrink the gap between estimated job duration and actual completion time. Instead of booking every three-bedroom move as a six-hour window, they analyze past jobs by home size, floor plan, and distance to calculate a tighter range—say 4.5 hours with a 15% buffer.

This reduces scheduling slack and raises utilization without cramming crews or cutting corners. The mechanic is better data, not faster work.

Some operators build custom estimation models inside their CRM. Others use scheduling platforms that learn from completed jobs and auto-adjust duration forecasts. Either way, the infrastructure turns guesswork into measurement.

Demand-Responsive Crew Scheduling

Traditional moving companies staff for peak capacity and accept low utilization during slow periods. High-density operators flex crew size and shift length based on forward bookings.

If next week shows 60% utilization across four crews, they consolidate to three crews and block the fourth. If demand spikes, they bring the fourth crew back online and adjust LSA availability to match.

This requires visibility into the job pipeline—not just what is booked today, but what is likely to book in the next 7–14 days based on lead velocity, seasonal patterns, and conversion rate.

The operators doing this well treat crew scheduling as a dynamic system, not a fixed roster. They track utilization daily, forecast weekly, and adjust capacity in real time.

The Operational Trade-Off

Optimizing for appointment density introduces tension with other operational goals.

Capacity flexibility vs. utilization. Maintaining spare capacity lets you capture last-minute moves, upsell weekend slots, and handle customer reschedules. But spare capacity tanks appointment density. High-density operators sacrifice some flexibility to keep utilization high.

Job padding vs. efficiency. Adding buffer time to each job reduces crew stress, accounts for traffic, and improves on-time performance. But Google counts that buffer as unutilized hours. High-density operators shrink padding and rely on tighter routing and dispatch coordination to maintain service quality.

Seasonal staffing vs. year-round density. Moving demand peaks in summer and collapses in winter. Operators who staff for summer volume run low utilization half the year. Operators who optimize for density either scale crews seasonally or throttle LSA spend during slow months to match reduced capacity.

None of these trade-offs have a universal answer. The right balance depends on market density, competitive intensity, and whether the operator prioritizes growth or margin.

But the decision is no longer just operational. It now directly impacts acquisition cost.

How to Operationalize Density Optimization

Most moving companies cannot flip a switch and hit 75% appointment density. The infrastructure has to be built in sequence.

Step one: measure current utilization. Calculate booked hours divided by available hours over the past 30 days. Break it down by crew, by day of week, and by season. Identify where utilization is strong and where it collapses.

If you do not have this data in a system, reconstruct it manually. Pull completed jobs from your CRM or invoicing tool, estimate duration, and compare against crew schedules. The number does not need to be precise. It needs to be directionally accurate.

Step two: align LSA availability with actual capacity. Stop advertising availability you cannot fill. If you run three crews and historical data shows 60% utilization, signal two crews to Google until utilization climbs. This immediately raises appointment density and lowers cost-per-lead.

Step three: tighten job duration estimates. Analyze past jobs to calculate average completion time by job type. Replace generic time windows with data-driven estimates. Build in buffer, but make it deliberate—15% is defensible, 50% is waste.

Step four: build a demand forecast. Track lead volume, conversion rate, and booking velocity by week. Use this to project how many jobs will land in the next 7–14 days. Adjust crew schedules and LSA availability to match.

This does not require a data science team. A spreadsheet with four columns—week, leads, conversion rate, booked hours—is enough to start making forward-looking capacity decisions.

Step five: integrate scheduling and acquisition. The operators seeing the largest cost-per-lead improvements have eliminated the gap between when a lead arrives and when crew capacity updates. They use scheduling platforms that sync directly with LSA settings, adjusting availability in real time as jobs book or cancel.

This requires moving from manual dispatch to API-driven scheduling infrastructure. It is a non-trivial systems build, but it is also the only way to sustain high appointment density at scale.

Why This Rewards Systems Thinking

Google's appointment density algorithm does not reward marketing tactics. It rewards operational infrastructure.

You cannot game this with ad copy, bid strategy, or review solicitation. The only path to lower cost-per-lead is tighter scheduling coordination, better demand forecasting, and dynamic capacity management.

This is a structural advantage for operators who have already built Revenue & Operations Infrastructure. They have real-time visibility into crew utilization, data-driven job duration models, and integrated scheduling systems. Optimizing for appointment density is a configuration change, not a rebuild.

For operators still managing dispatch with spreadsheets and phone calls, this update creates a compounding penalty. They pay more per lead, book fewer jobs, run lower utilization, and pay even more next month.

The gap widens every cycle.

The Broader Signal

Google's move reflects a broader shift in how platforms evaluate service providers. Ranking algorithms are moving beyond reputation signals—reviews, response time, tenure—and incorporating operational performance.

Appointment density is just one mechanic. Expect similar signals to emerge for other appointment-based verticals. Cancellation rate, reschedule frequency, job completion speed, repeat booking rate—all of these are measurable proxies for operational reliability.

The operators who build infrastructure to measure, forecast, and optimize these mechanics will compound advantages across every acquisition channel. The operators who treat them as peripheral metrics will pay progressively more for the same volume of work.

This is not a marketing problem. It is a systems problem.

Building for Density

Moving companies epitomize the appointment-based service model. Every job is a scheduled event with known duration, crew size, travel time, and resource constraints. Demand is volatile. Job windows are long. Crews are expensive to carry but catastrophic to shortage.

Optimizing appointment density requires infrastructure that most movers have not built: real-time utilization tracking, dynamic capacity signaling, demand forecasting, and integrated scheduling.

The companies that build this infrastructure do not just lower their cost-per-lead. They compress the time between lead and booking, reduce scheduling errors, eliminate crew downtime, and improve gross margin per job.

Google's algorithm update does not create the value. It surfaces it.

Operators who have already invested in scheduling coordination and crew utilization measurement are now seeing that investment pay dividends in acquisition cost. Operators who have deferred those builds are now paying a tax.

The mechanic is clear. High appointment density lowers cost-per-lead. High appointment density requires operational infrastructure. Operational infrastructure compounds across growth and margin.

This is not a short-term optimization. It is a structural advantage that widens with every booking cycle.