Almost every moving company I look at has been told the same thing: build a page for every route you serve, and the rankings will follow. So they spin up forty near-identical pages, swap two city names on each, and wait. The pages either never rank or quietly disappear from the index, and nobody explains why.
Route pages absolutely can rank, and for city-to-city movers they are one of the better plays going. But the tactic only works when each page earns its own existence. This is the part the guides selling you the tactic leave out, so let me give you the spec, the selection method, and the honest line on where Google’s doorway policy sits.
Principaux enseignements
- A moving company route page is a page built for one specific city-to-city corridor you actually serve, like Austin to Denver, not a generic service-area page.
- A route page ranks only when it carries corridor-specific substance: a real transit time, a real price band for that lane, the licensing and logistics quirks of the route, and detail about both the origin and the destination.
- Use the deletion test before you publish: strip the two city names, and if nothing distinguishing is left on the page, it is a doorway page.
- Google’s doorway abuse policy explicitly names pages targeted at specific regions or cities that funnel users to one page, so thin route pages are a documented risk, not a hypothetical one.
- Build route pages for the lanes you already run and quote often, not a page for every possible city pair. Eight real pages beat eighty thin ones.
- Near-identical route pages usually end up marked “Crawled, currently not indexed” as Google consolidates the duplicates down to one.
What a route page is for a moving company
A route page is a page dedicated to one moving corridor you serve, a specific origin-to-destination lane such as Austin to Denver or Chicago to Phoenix. It targets long-distance and interstate searches for that exact pair, and it answers the questions someone planning that specific move actually has: how long the drive takes, roughly what the lane costs, and what is different about moving across those particular states.
That is different from a city or service-area page, which targets one location (“movers in Austin”). A route page targets the relationship between two places, which is why it can rank for the higher-intent “moving from Austin to Denver” style searches where the buyer has already decided on the move.
Here is the interesting part I saw when I checked what Google actually cites for these queries. On a city-to-city route search, the AI Overview’s sources are almost entirely movers’ own route pages and route directories, not SEO agency guides. In other words, a well-built route page can be the cited source for its corridor. The opportunity is real; the execution is where it falls apart.
What should be on a moving company route page
A route page earns its ranking when it carries substance that is true for that corridor and nothing else. If the only thing separating your Austin-to-Denver page from your Austin-to-Seattle page is the two city names, you have not built two pages, you have built one page and published it twice.
So here is the spec I would hold every route page to before it goes live. Each of these has to be genuinely specific to the lane, not a template field with the numbers guessed.
| What goes on the page | Why it has to be corridor-specific |
|---|---|
| Real transit time for the lane | Austin to Denver is a different drive from Austin to Miami. A real estimate (and what changes it, like winter passes) is something only this route can say. |
| A real price band for that corridor | Long-distance pricing tracks distance and season. A genuine range for this lane, even a wide one, is more useful and more unique than “get a quote”. |
| The licensing and logistics of the route | Interstate moves need a USDOT number and fall under FMCSA rules; some lanes have tolls, weigh stations, or seasonal road closures worth naming. |
| Origin and destination detail | Parking rules, building access, and neighborhood quirks at both ends. This is local knowledge a template cannot fake. |
| Proof you actually run this lane | A real job you have done on the route, a review from that move, or your schedule for it. This is what turns a doorway into a page worth citing. |
The deletion test is the quickest way to check a page against this spec. Cover the two city names on the page and read what is left. If the remaining text would sit just as happily on any other route, the page is a doorway and Google will treat it as one. If what is left still clearly describes a real, specific move, you have a page worth publishing.
To show you what fails that test, here are two route pages I pulled from a directory that ranks for these queries. Notice the description is byte-for-byte identical; only the ZIP code and the city names change.
Both of those pages fail the deletion test in one read. Strip “Eagle Mountain, UT to Monroe, NC” and “Layton, UT to Gering, NE” and you are left with the exact same sentence. That is the pattern that gets a whole folder of route pages consolidated or ignored.
How many route pages should a moving company build
Build route pages for the lanes you genuinely run and quote often, not a page for every city pair a keyword tool can list. For most movers that means somewhere around five to fifteen strong pages, not the fifty to a hundred a template makes easy. Eight real pages will out-earn eighty thin ones every time, because only the eight have anything to say.
The selection mistake I see most is picking routes off search volume. Volume tells you what people search, not which lanes you can actually write a substantive page about. A better source is your own job data, which is also the only place your corridor-specific detail comes from.
How to pick which route pages to build
- Pull the lanes you already win: routes you have completed jobs on, with real transit times and reviews to draw from.
- Add the lanes you keep quoting but losing: there is demand, and a strong page can start closing it.
- Drop any lane where you cannot honestly fill the spec: no real detail means no page, for now.
- Publish that shortlist, and only expand once each page is genuinely specific.
This is the same discipline I push in any stratégie de référencement local: fewer pages that each carry real intent and real proof, rather than a wide net of near-empty ones. A moving company competing on a handful of well-built corridors will beat a competitor with a hundred doorways nearly every time.
Are moving company city pages doorway pages?
They are doorway pages when they are substantially similar and exist mainly to funnel every visitor to the same quote form. They are not doorway pages when each one is genuinely useful for its specific route. The line is exactly the deletion test above, and it is worth reading Google’s own words on it rather than trusting a vendor’s summary.
Google’s spam policies define doorway abuse (its current term for what people still call doorway pages) as sites or pages created to rank for specific, similar queries that lead users to intermediate pages less useful than the final destination. One of the listed examples is almost a description of a thin route-page setup:
Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page.
Google Search, Spam policies for Google web search (doorway abuse)
Now here is the part I find genuinely odd, and it is the reason so many movers walk into this. Search Google for “seo for moving companies” and Google’s own AI Overview tells you to build unique pages for every single town you service, with no mention of the doorway policy sitting right next door. The word doing all the work in that advice is “unique”, and nothing around it explains what unique has to mean.
So both things are true at once. The pages are a legitimate, cited format when they are real, and the exact same format is named as abuse when it is thin. The advice everyone repeats stops at “make a page for every route” and never tells you which side of that line you are on. The deletion test is how you stay on the right side of it, and I would run every route page through it before it ships. For the AI-search angle specifically, I go deeper in my piece on local SEO and AI Overviews.
Why route pages end up “crawled, currently not indexed”
When a batch of route pages is near-identical, Google often crawls them, decides they are duplicates of each other, and keeps only one, leaving the rest marked “Crawled, currently not indexed” in Search Console. This is the failure state almost nobody in the route-page advice names, and it is the single clearest signal that your pages are too thin.
It is not a penalty, and there is usually no error to fix. Google is just declining to spend an index slot on a page that repeats what it already holds. If you open the Pages report and see your route folder sitting in that bucket, the answer is not more pages or more internal links, it is more distinct substance on the pages you have, exactly the spec above.
I walk through how to read and act on that status in detail in crawled, currently not indexed. For route pages specifically, treat it as your scoreboard: as pages move from that bucket into “Indexed”, you know the distinct-content work is landing.
So, should a moving company build route pages?
Honestly, yes, but far fewer than you have been told, and each one built with real substance. Route pages are one of the strongest plays a city-to-city mover has, because they match a high-intent search and Google is actively citing movers’ own pages for those queries. That opportunity is genuine.
What I would not do is treat them as a volume game. The template approach, a page for every city pair, is the fastest route to a folder of doorways that never index and do nothing for you. If this were my moving company, I would build a tight set of pages for the lanes I actually run, pass every one through the deletion test, and only add more once each earns its place. That is slower, and it is the version that works. This piece sits alongside my broader guide to SEO for moving companies, which covers the rest of the local picture.
Want your route pages built to rank, not to bloat?
If you run a moving company and want a route-page setup that earns rankings instead of doorways, travailler avec nous ou m'envoyer un courriel. I will help you pick the right lanes and give each page a real reason to exist.
Want our posts to show up more often on Google?
One step & Google will surface this site in your Top Stories.
