Most advice about a logistics website reads like a shopfront audit: better photos, tighter copy, a testimonial near the top. None of that is wrong, and none of it is the actual problem. It treats the site as something a person looks at and judges, the way a shopper sizes up a storefront before deciding whether to walk in. That was a fair model in 2015. It’s a poor model now, because a growing share of what visits a website today isn’t a person browsing at all. It’s a thumb on a phone screen filling in a form between two other tasks, or a system reading the page in one pass to decide whether the business belongs on a shortlist nobody at the business will ever see assembled.

Judged as a shopfront, most operator websites look fine. Judged as the infrastructure a modern demand channel runs on, the same site is often losing work nobody notices. Nothing tells an owner when a visitor gave up, or when a reading system decided there was nothing worth reading.
The site was built for a visitor who doesn’t behave that way anymore
A website’s design brief usually gets set once, early, and rarely gets revisited: convince a person to trust the business enough to contact it. Every choice downstream of that brief makes sense against it: a hero photo of the truck, three testimonials, a button that says “Request a Quote.” The brief assumes a patient reader who scrolls, forms an impression, and picks up the phone if the impression lands.
That assumption is the gap. It’s the same gap in every failure mode below. Google’s AI can already call a business directly and ask for a price on a customer’s behalf. It reports back whatever it gets in that one attempt: no patience, no follow-up call, no benefit of the doubt. The same logic applies when nobody calls at all. An AI agent reads the page instead, extracts whatever structured information a business makes available, and moves on if there’s nothing to find. Neither behaves anything like the visitor most operator websites were designed to win over.
The mistakes that follow aren’t a random list of bugs. Each mistake applies the same design brief to a form, a price, or a listed phone number.
The quote that dies in the form
The most common brochure-era holdover is a page with no price on it at all: a “Request a Quote” button that opens a form asking for a name, an inventory, two addresses and a callback window. In exchange for all that, the visitor receives nothing. No number, no range, no timeline. A business that asks a stranger for ten minutes of data entry and offers silence in return isn’t running a sales channel. It’s running an unpaid internship for its own admin team. That design fails for a different reason than looking old-fashioned. It fails because every field between “I want a price” and “I have a price” is a place a comparison shopper can leave for a competitor whose form gives something back faster.
The gap is measurable even before judging whether a specific form is well built. Zuko, a form-analytics company, tracked more than 93 million form sessions across industries. It found desktop forms convert starters to completions at 55.5% on average, against 47.5% on mobile. That’s an eight-point tax paid purely for opening the form on a phone, before counting field count, layout or copy. Baymard Institute’s long-running checkout research, built from more than a decade of usability testing, found the average checkout still asks for close to double the form elements of an ideal flow (23.48 versus 12 to 14). The same research found that a process feeling longer or more complicated than expected is one of the largest reported reasons people abandon it. That’s checkout research, not moving-industry research, but the mechanism travels: a moving-company quote form asking for a full inventory, two addresses and a preferred callback time before showing a number is a worse offender than the average online checkout it was benchmarked against, not a better one.
The arithmetic on one route page makes the gap concrete. A page that gets 60 mobile visitors a week who start the quote form would see roughly 33 finished submissions at the desktop completion rate, and roughly 28 at the mobile rate. Five completed quote requests disappear every week, from one page, purely on the device penalty, before anyone asks whether the form itself is any good. Over a quarter, that’s more than 60 quote requests that simply never happened. Nothing about that shows up as a lost deal, because there was never a deal on record to lose. It shows up as a route page with respectable traffic and forgettable enquiry numbers, which reads as “this page is fine.” It isn’t fine. It’s quietly bleeding five quote requests a week while the dashboard reports steady vitals.
The fix isn’t a shorter form for its own sake. It gives a visitor, human or otherwise, a usable number without making either of them wait on a person. An operator who publishes even a rough calculated range keeps both audiences a contact-only button loses: two movers and a truck at a stated hourly rate, plus a flat travel fee inside a stated radius.
A price a person can read and a system can’t
The second mistake sits one layer deeper: a price exists on the page, but only in a form nothing automated can parse. Google’s own structured-data documentation for local businesses lists exactly two required properties, name and address. That’s enough to earn a knowledge panel. The properties that let a reading system extract a usable number sit in the merely recommended column instead: price range, opening hours, phone number. These are fields most site templates and SEO plugins never fill in unless someone deliberately goes looking for them. A site can pass a basic “is my schema set up” check and still hand a reading system nothing to price a job with.
That’s the same category error as the quote form, one level down. An audit that checks whether a box is ticked isn’t the same as checking whether the output actually answers the question being asked. When a rate is posted only as a photographed infographic or a PDF behind a download link, it reads to a person as a business that publishes its pricing. It reads to a reading system as nothing at all. Being half-legible produces the identical outcome to not being legible.
Fixing this doesn’t require a site rebuild. A structured price block is a small piece of code that sits next to a pricing page without changing how the page looks to a visitor. The fix requires a decision an operator has to make anyway: a real, current number for each service, published somewhere plain enough for a program to read, not filed away in a salesperson’s head or a PDF nobody re-uploads when the rate changes.
One business, three phone numbers
The third mistake is the quietest of the three, because nothing about the website itself looks broken. The website’s footer says one phone number. The Google Business Profile, untouched since setup, says another, because nobody logged back in after the office moved two years ago. A marketplace listing on a site like Sirelo or Relocately carries a third number, whatever was supplied at onboarding and never updated since. Three true-sounding answers exist for the same question, and the business is effectively running a game show where the prize for guessing wrong goes to a competitor. Nothing on the operator’s own site tells anyone which one is current.
A human caller who dials the wrong number usually just tries the next listing. A system trying to decide which of three conflicting values to trust has no equivalent shortcut. Google’s own documentation is explicit that a listing needs a consistent name and address before it’s treated as reliable enough to feature prominently at all. BrightLocal’s Local Citations Trust Report found that 93% of consumers say they’re frustrated by incorrect information on online directories, and 80% say inconsistent contact details cost a business their trust before any service has even been delivered. In BrightLocal’s own Local Search Ranking Factors survey, citation consistency ranks among the more heavily weighted local ranking signals, not a footnote beneath reviews and links. Citation consistency means whether a business’s name, address and phone number agree everywhere it’s listed.
Nobody made a typo. The business’s identity lives in three places at once: the website, the Google profile and the marketplace listing. Nothing keeps them synced when one of them changes.
“We’re not a software company”
The objection that fixing any of this needs an internal engineering team is a reasonable one to raise, not a reason to skip the fix.
None of the three fixes above needs a rebuild. A calculated price range on a page is a content decision, not an engineering project. The structured-data block that makes that price readable by a system is a small, self-contained addition most SEO plugins already know how to write once a real number is supplied, not a custom build. NAP consistency is a spreadsheet exercise: listing every place the business’s name, address and phone number appear, then correcting the ones that disagree, starting with the Google Business Profile and the two or three marketplace listings that generate the most calls.
The actual obstacle isn’t difficulty. It’s invisibility. These three gaps never show up on a rankings dashboard or a monthly traffic report, because none of them is a ranking problem in the conventional sense. A business only finds the gap by testing it directly: opening its own quote form on a phone with the sound off, checking what a structured-data testing tool extracts from its pricing page, or searching its own name to see whether the number that comes back matches the one printed on the truck.
What the site is for now
This isn’t a checklist to bolt onto an existing brochure. Adding one more testimonial or a faster-loading photo is still shopfront thinking, aimed at a visitor’s patience and taste. A different job description for the site changes how much work a business wins. The job is to produce a current, usable, machine-parseable answer to whoever or whatever is asking, on the first attempt, with nobody standing next to it to fill the gap.
For most of history, trust between a business and a customer formed the way it always had: one person looked at another, or at a place, and decided whether to believe what they saw. That is quietly becoming the exception. A growing share of those judgments are now made by systems that read a page in milliseconds, extract a fact or find nothing, and move on. The mistakes above were never really about websites. They are the oldest human relationship quietly handing itself to something that reads instead of looks.
The bar isn’t hypothetical, and it isn’t arriving later. A caller and a reading system are already testing a business against it today, whether or not the business has noticed. Building on shared demand infrastructure starts from that job description, not a nicer photo of the truck: a business whose pricing, quote path and listed identity are already built the way the thing asking now expects them.









