Vehicle Class Pages That Do Not Read Like Each Other

A vehicle class page earns its place when it answers a question the rest of the site cannot: what this class is for, what it is not for, and what hiring one actually involves. A set of class pages fails when they are the same page with the class name swapped, which is the outcome of building them from a template filled in by find and replace. This article is about the difference. It covers what level of detail a class page should sit at, the five things that genuinely vary between classes, how to write the shared material without it becoming filler, and how the set should link into the rest of a fleet site.

Pick the right level of detail

The first sentence answers it: the right level is the level your customers use when they call, because that is the level they search at too. If people ring and ask for a Luton with a tail lift, that is a page. If they ask for a specific manufacturer’s model designation, they are almost certainly an existing customer confirming a booking rather than a buyer choosing.

Going too granular is the more common error and it is expensive. A page per make and model produces a set that nobody searches for, that cannot be kept current as the fleet rotates, and that splits whatever authority the class had across several thin pages. Google’s guidance on organizing a site is about clear, well-labelled sections that people and search engines can navigate, and forty model pages is not that.

Going too broad fails differently. A single fleet page listing everything cannot answer a specific question specifically, so it competes for nothing and converts poorly.

The naming test

Name the page what a buyer would say out loud. Refrigerated vans. Box trucks. Tippers. Flatbeds. Crew cabs. Not internal category codes, not marketing coinages, and not a compound that tries to capture two classes at once because you did not want to write two pages.

Google’s documentation on title links is a useful reminder here: the title of the page is one of the strongest signals of what it is about, and a title that uses the buyer’s own words is doing the simplest version of that job.

When a class is genuinely marginal

If a class exists in the fleet but is rarely asked for, it does not need its own page. It needs a clearly labelled section on the nearest class page. A page that exists purely for completeness will always be the weakest in the set and it will drag the average.

The five things that actually differ

This is the core of it. Five facts vary genuinely between classes and none of them can be generated mechanically.

What it is suited for. The specific jobs this class is the right answer to. Not a list of adjectives, the actual use cases: a two-person crew moving a small office, a supplier delivering pallets into a site with no dock, a contractor moving aggregate between two yards.

What it cannot do. The single most useful paragraph on a class page and the one most often missing. Height restrictions that rule out certain car parks. Payload limits that surprise people who were thinking in volume. License categories required. Telling a buyer the class is wrong for their job is not losing a sale, it is avoiding a failed hire and a complaint.

What the terms are. Minimum hire period, what is included, what is charged separately, deposit arrangements, mileage allowances if they differ by class. These do vary by class in most operations and buyers assume they do not, which is where disputes start.

Which depots keep it. Named, linked, and current. This is the fact that converts a browsing reader into an enquiring one, because it moves the question from whether to where.

What buyers get wrong about it. Every class has a recurring misconception. Refrigerated vans and pre-cooling time. Tail lifts and what they will actually take. Tippers and where they can legally discharge. Addressing it on the page is the clearest possible demonstration that the page was written by someone who does this rather than by someone describing it.

Write those first

The technique is simply to write those five sections before anything else, for every class, before any shared material is added. A page that opens with genuine class-specific substance has already established what it is about. Shared material added afterwards cannot do much harm. Shared material written first crowds out the specifics and produces the set of near-identical pages this article exists to prevent.

Templates are fine, sameness is not

There is a persistent confusion between a shared layout and duplicate content, and it leads people to avoid templates entirely, which is worse.

A template is a layout: the same sections in the same order with the same styling. That is good. It means a returning buyer knows where to find the payload figure on every class page, and it means the set is maintainable. Google’s concern with duplicate and near-duplicate URLs is about substance, not about layout consistency.

The failure is when the substance is shared too. A set of pages whose differences amount to a class name and a photograph is one page published several times, and it will be treated accordingly.

The paragraph test

Take the second paragraph of three class pages and read them side by side. If swapping them between pages would go unnoticed, they are filler and should be rewritten or removed. This test takes two minutes and catches nearly everything.

The shared sections that are legitimate

Some sections should be identical across the set and that is correct. The hire process. The documentation a driver needs to bring. The general terms that genuinely do not vary. These are reference material and buyers want them consistent. Keep them, keep them short, and put them below the class-specific material rather than above it.

Pricing, and what to say when you cannot publish a rate

Most hire operations cannot publish a firm rate per class, because the rate depends on term, volume, season and account. That is a real constraint and it is not an excuse for saying nothing.

What a page can always do is publish the structure. What the rate depends on, in order of impact. What is included in it. What is charged separately, specifically, including the charges people are surprised by. What the minimum term is. Whether an account changes the answer.

A buyer reading that can estimate whether you are in their range and whether the arrangement suits them, which is all they need at the comparison stage. A buyer reading contact us for pricing learns only that finding out will cost them a phone call, and at that stage they have two other tabs open.

If you show an indicative figure

Label it unmistakably as indicative, state what it assumes, and state what would change it. An estimate a buyer mistakes for a quote is worse than no estimate, because the correction arrives after they have anchored on the number and it reads as a bait.

Photography, and the one rule that matters

Class pages are where stock photography does the most damage. A generic image of a van that is not one of yours, in a livery that is not yours, tells a buyer the page is decoration.

The rule is that the photograph should show the thing being described, in the condition it will actually arrive in, from the angle that answers a question. The inside of a load space with the dimensions visible answers a question. A three-quarter view of a clean vehicle against a sunset does not.

If real photography is not available for every class, use it for the classes that matter most and use a clear diagram or no image at all for the rest. An honest absence reads better than a stock image that a buyer recognises as stock.

The accessibility side

Load space dimensions, payload figures and license requirements should be in text, not baked into an image. Text can be read aloud, searched, copied into a specification and reflowed on a phone. WCAG 2.2 requires text alternatives for non-text content, and on a class page the simplest way to comply is for the important numbers to be text in the first place.

Linking the set into the site

A class page has exactly three things a reader does next, and there should be a link for each.

Locate. Every depot that keeps the class, named and linked. The reverse link belongs on the depot page, which should list the classes it stocks.

Compare. The one or two classes a buyer at this point might be choosing between, with a sentence saying what would push them one way or the other. This is genuinely useful and it is the kind of link that keeps a reader on the site rather than sending them back to a search results page to compare.

Act. An enquiry route with the class already selected, so the buyer does not re-specify what the page already knows.

What not to link to

Resist the reflex to link every class page to every other class page in a block at the foot. A list of nine links is a list nobody reads. Two relevant links inside the text outperform nine at the bottom, because they arrive at the moment the question occurs.

Keeping the set true as the fleet changes

The fleet rotates. Classes get added, retired, moved between depots. A class page set that was accurate at launch is the thing most likely to be quietly wrong a year later, and wrong specifications are worse than missing ones.

Two practices keep it honest. First, record the class-to-depot mapping and the key specifications as data that the pages read from, so a change is made once and appears everywhere it should. Second, review the set on a schedule rather than when someone notices, because nobody notices.

A retired class does not get deleted. It gets a redirect to the closest class you still run, for the same reason a closed depot does: the URL has accumulated links and visits, and throwing that away serves nobody.

If you are building or rebuilding this, the fleet operator website templates page covers how the class page layout is structured, and the multi-depot location pages page covers the other half of the cross-linking. The companion article on depot page structure covers what happens on the other end of every one of those links.