Most general SEO advice assumes a product catalogue, and freight does not have one. A forwarder’s inventory is a set of lanes, modes and clearance capabilities that shift with capacity and season. A 3PL sells a contract, not a cart. A warehouse operator’s most valuable search asset is a physical facility with a postcode, a dock count, a clear height and a set of certifications. Those attributes are the page.
This page sets out how we approach search for freight forwarders, 3PL and 4PL providers, warehousing and fulfilment operators, carriers, customs brokers and last-mile networks: what the real search surfaces are, where the standard playbook breaks, and which constraints are worth naming before anyone writes a word of copy.
What search demand in freight actually looks like
The first job on a logistics domain is not keyword research. It is separating three populations of searcher who use overlapping language and want completely different things. Treat them as one audience and the commercial pages end up shaped by demand that has nothing to do with buying freight.
Shipper-side intent
These are the queries that turn into RFQs: a category manager searching for a 3PL that handles ecommerce returns, an importer looking for a bonded warehouse near a specific inland container depot, a manufacturer pricing air freight out of a named origin, a brand owner looking for a customs broker who has cleared their commodity before. The pattern is nearly always capability plus geography, or mode plus origin plus destination. The phrasing is narrow, the intent is unambiguous, and the searcher is generally building a shortlist rather than browsing. This is the demand worth architecting the entire site around.
Carrier, agent and partner-side intent
The second population wants to sell you capacity or buy your network access: owner-operators looking for a carrier setup packet, drayage firms near a port, overseas agents looking for a partner in your market, forwarders looking for co-loading. The vocabulary is almost identical to shipper vocabulary — both sides say “freight”, “lane”, “capacity”, “partner” — so these pages compete with commercial pages for the same URLs and the same internal links. Partner recruitment is a legitimate business need, but it belongs in a clearly separated section with its own entry points and its own conversion path, not blended into service pages that procurement teams are reading.
Jobs traffic, and why it quietly distorts logistics sites
The third population is the least useful for a sales-led site, and the hardest to keep out of the commercial pages. Job-seeker queries use the same nouns as shipper queries — warehouse, driver, dispatch — and they land on exactly the pages built for shippers: city pages, facility pages, anything pairing “warehouse” with a location. Left unmanaged, a careers section can end up carrying more traffic than the commercial pages while contributing nothing to pipeline, absorbing internal link equity and pulling the topical profile toward employment rather than freight services.
The fix is architectural rather than editorial: keep one canonical careers hub, run individual requisitions through an applicant tracking system on a subdomain instead of templating hundreds of thin job pages onto the main domain, and keep the careers section out of the primary navigation link graph. Then segment jobs queries out of reporting before anyone reads a traffic chart — otherwise a hiring push looks like an SEO win. That separation is technical SEO work: index control, link graph shape, honest measurement.
Lane and corridor pages: freight’s natural programmatic surface
Lanes are the one place where a freight site genuinely has a large, legitimate, structured page inventory. An origin–destination pair, crossed with mode, crossed with commodity or equipment type, produces a matrix that maps almost perfectly onto how shippers search. Someone sourcing ocean freight from Nhava Sheva to Rotterdam, or moving temperature-sensitive pharma by air out of Hyderabad, types close to that phrase.
The honest constraint — and the one that decides whether a lane build works at all — is that a lane page built from a template with an origin, a destination and a quote form is a doorway page. It carries nothing the reader could not have guessed, and Google’s search spam policies describe pages generated in bulk to funnel users to the same destination as doorway pages. Publishing that inventory does not produce a network of lane pages; it produces a thin-content problem spread across thousands of URLs, and it can drag down the pages that were already working.
What a lane page has to carry to be worth publishing
- Real transit expectations by service level — port-to-port versus door-to-door, direct versus transhipment, and which transhipment hubs the routing actually uses.
- The terminals in play — the specific seaports, airports, ICDs, rail ramps or border crossings, because shippers with existing operations care which gate their cargo goes through.
- Customs reality at both ends — documentation set, typical clearance steps, licensing or permits for restricted commodities, who acts as importer of record and which broker files the entry.
- Commodity constraints — what cannot move on that lane, what needs pre-approval, what triggers dangerous goods handling.
- Seasonality and known disruption patterns — the periods when that specific corridor tightens, and why.
- Equipment and capacity notes — container types available, reefer plug availability, LTL versus FTL economics, air uplift constraints on specific routings.
- What actually moves the price — chargeable weight, accessorials, demurrage and detention exposure, fuel and currency mechanisms.
The practical test is simple: publish a lane only when someone in operations can answer follow-up questions about it, then expand the inventory as coverage expands. That evidence-gated build is what programmatic SEO should look like in freight — a controlled expansion, not a page generator.
How lane architecture fails
Beyond thin content, three structural mistakes are worth naming. Lane pages get linked alphabetically from one giant index instead of hierarchically from corridor and trade-lane hubs, so crawlers see a flat wall rather than a network that mirrors the business. Reverse lanes get auto-generated with mirrored copy, doubling the inventory and halving the substance. And lane URLs get built on parameters or search results rather than clean paths, so the pretty URL and the working URL diverge and neither is canonical. Corridor hubs, clean paths, one self-canonical page per real lane, and sitemap coverage matching what is genuinely published — that is the shape that holds.
Capability pages are separate search surfaces
Capability is how logistics buyers search, and each capability carries its own qualification signals. Bonded warehousing, temperature-controlled storage and distribution, dangerous goods handling, cross-docking, reverse logistics and returns processing, project and out-of-gauge cargo, customs brokerage, bonded trucking, FTWZ or free-trade-zone operations, and ecommerce fulfilment with marketplace integrations are not bullet points on a services page. They are distinct pages with distinct readers.
A capability page earns its place when it proves handling competence to someone who already knows the subject. A pharmaceutical shipper reading about temperature-controlled distribution wants mapping and validation of the storage envelope, calibrated data loggers, documented excursion procedures, qualified packouts and Good Distribution Practice alignment. A chemicals shipper reading about dangerous goods wants UN numbers, packing groups, segregation rules and named handling capability, not reassurance. A retailer reading about returns wants disposition logic, grading, refurbishment and restock cycle times. Write for the reader who already knows the vocabulary. Copy pitched below that level tells a specialist buyer nothing they can evaluate, while copy pitched at it stays readable to a generalist. Building that library in the right order and maintaining it as capabilities change is content strategy work, not a one-off copy project.
Warehousing: build pages around facilities, not city keywords
Publishing a page per target city regardless of whether a building exists there fails twice. It fails commercially — a shipper arriving to evaluate a building finds marketing copy instead — and it fails structurally, because there is no address, no local entity and nothing verifiable behind the page.
A facility page should be built the way a site-selection team would read it: address and precise location relative to port, airport, rail ramp and highway access; dock doors and levellers; clear height; pallet positions and racking type; floor loading; sprinkler and fire classification; power, yard and trailer parking; gate and receiving hours; the WMS in use and the EDI or API integrations supported; and the certifications actually held for that site. Multi-site operators should treat each facility as its own entity with its own page, its own address data and its own local presence, then roll them up through a network page that explains coverage. That is what gives each market its own local SEO entity to work with, instead of one national page carrying every location.
Compliance and standards content you can stand behind
Freight is a vertical where genuinely technical, publicly checkable reference content is both useful to buyers and safe to publish. Incoterms 2020, published by the International Chamber of Commerce, defines eleven rules governing where risk and cost transfer, and an accurate explainer of each term is read by real shippers. Air dangerous goods sit under the IATA Dangerous Goods Regulations, reissued annually; ocean dangerous goods sit under the IMO’s IMDG Code, amended on a two-year cycle. Authorised Economic Operator status, built on the World Customs Organization’s SAFE Framework, is worth explaining because the benefits it confers are not obvious from the name. In India, the e-way bill requirement under Rule 138 of the CGST Rules governs the movement of consignments above the prescribed value threshold, and the documentation rules around it are worth an explainer of their own.
There is a hard line here. Reference content explaining a standard is always publishable. Claiming a status is only publishable if it is held. AEO authorisation, ISO 9001 or ISO 28000 certification, C-TPAT membership, FMC licensing, an IATA cargo agent code — every one of these is checkable by a buyer, some through open registers such as the FMC’s licensed-OTI search and published AEO lists, and some only through the issuing body: a certification body’s own directory, or CTPAT’s Status Verification Interface, which is visible to other partners rather than to the public. Asserting a status that has lapsed or was never granted is a commercial and legal exposure long before it is a search problem. Certifications go on the site with the issuing body, the scope and the reference number, or they do not go on the site.
Structured data for carriers, forwarders and warehouse networks
Structured data in logistics is less about rich results and more about making an entity legible. For a multi-facility operator, each site is marked up as a LocalBusiness — the type that inherits from both Organization and Place, and therefore the only one that can carry its own PostalAddress, geo coordinates and openingHoursSpecification for gate hours — tied back to the parent company through parentOrganization. Capability pages map to Service with serviceType and areaServed, which is the correct way to express that bonded warehousing is offered in one region and cross-docking in another. Tracking and shipment pages can use ParcelDelivery with deliveryAddress, provider — which supersedes the older carrier property — and trackingNumber or trackingUrl. Regulatory and trade identifiers — an FMC licence number, a USDOT or MC number, a SCAC code issued by the NMFTA, an IATA cargo agent code — belong in identifier and sameAs properties, because they are the strongest unambiguous signals a freight business has.
Worth stating plainly: schema.org has no type for a freight lane. Lane pages get standard page-level markup and a Service reference, not an invented type. Nor should Review or AggregateRating markup ever appear on pages without real, collected reviews behind them. Structured data describes what exists; it does not manufacture it.
Seasonality and capacity cycles as a publishing calendar
Freight demand is cyclical in ways that are predictable enough to plan editorial around. Transpacific and transatlantic peak season builds ahead of holiday retail. Chinese New Year and Golden Week produce pre-shipment surges followed by blank sailings as carriers withdraw capacity. India’s festive season reshapes domestic road and warehousing demand. Ramadan, harvest cycles, monsoon windows and hurricane season each move specific corridors. Rate negotiations, contract renewals and budget cycles cluster at particular points in the year.
That gives a logistics content calendar something rare: known dates when specific questions surface. Capacity outlooks, contingency guides, cut-off calendars and rate-environment explainers published weeks ahead of the cycle they address arrive while the question is being asked. Published after, they are archive.
The RFQ funnel has three readers, not one
Logistics does not convert through a checkout. It converts through an RFQ, a tender or a discovery call, usually after a long evaluation with three sets of eyes on the same page. Procurement is comparing scope, terms and commercial structure and wants something that can be laid alongside two competitors. Operations is checking transit reliability, exception handling, EDI and API integration, onboarding time and whether the account will actually be staffed. Finance is looking at payment terms, currency exposure, insurance and the liability regime — cargo liability under the Montreal Convention for air, and the Hague-Visby Rules or US COGSA, which enacts the earlier Hague Rules, for ocean, is materially different from a commercial guarantee, and finance teams know it.
A service page written for only one of the three leaves the other two without the answers they need to sign off. The response is to answer all three without becoming a wall of text: scope and commercial structure up front, operational detail in a clearly labelled section, and terms, insurance and liability addressed rather than deferred to a PDF. Then keep the RFQ form proportionate to what actually qualifies a lead — lane, mode, volume, commodity and timeframe — rather than collecting the full account-opening pack before anyone has spoken.
Multi-country freight sites
Freight is international by definition, and the failure mode on multi-country sites is predictable: one English page targeted at every market, a country selector in the header, and hreflang either absent or self-contradictory. The result is that the same page competes with itself across markets while none of the local entities gets clear standing.
The correct structure follows the operation. Markets where the business has a legal entity, a facility or a licence get their own section with its own service scope, contact and compliance details and correct hreflang annotation, including a sensible default for unmatched regions. Markets served remotely through an agent network are described honestly as such. Language versions are translated by people who know the freight vocabulary of that market, because customs and mode terminology is exactly where untested machine translation goes wrong, in front of the exact reader you want. That market architecture is the substance of international SEO for a freight network.
How we scope work on a logistics site
The work starts with the separation exercise: split shipper, partner and jobs demand in the existing data so everyone is looking at the same reality. From there we map the capability and facility inventory that actually exists, decide which lanes have enough operational substance to justify a page, fix the crawl and index architecture so the commercial section is the strongest part of the link graph, deploy entity and service structured data across facilities, and build the editorial calendar against the cycles the business already plans around. The sequence is deliberate — architecture before inventory, inventory before volume — because publishing at scale on a broken structure makes the structure harder to fix.
Frequently asked questions
Are lane pages worth building, or will search engines treat them as doorway pages?
Both outcomes come from the same idea, and the difference is substance rather than quantity. A lane page carrying real routing, transit expectations by service level, customs steps and documentation at both ends, commodity restrictions, seasonality and the factors that move price is genuinely useful. A lane page assembled from a template with an origin, a destination and a quote form matches how Google’s search spam policies describe a doorway page, and generating thousands of them creates a site-wide thin-content problem rather than coverage. Publish lanes the operations team can actually speak to, link them from corridor hubs rather than one alphabetical index, avoid mirrored reverse-lane duplicates, and expand only as real coverage expands.
Our warehouse pages attract mostly job seekers. How do we stop that swamping the site?
Job-seeker queries use the same vocabulary as shipper queries, and they land on exactly the pages built for shippers — city pages, facility pages, anything pairing “warehouse” with a location. Handle it structurally: keep one canonical careers hub instead of templating hundreds of thin requisition pages onto the main domain, run individual openings through an applicant tracking system on a subdomain, and keep careers out of the primary navigation link graph so it does not compete with service pages for internal link equity. Then segment jobs queries out of reporting, so a hiring push is never mistaken for commercial performance.
What structured data actually applies to a freight or warehousing business?
Each facility is marked up as a LocalBusiness, which inherits from both Organization and Place and so can carry its own postal address, geo coordinates and opening hours for gate times, tied to the parent company through parentOrganization. Capability pages use Service with serviceType and areaServed, which correctly expresses that a capability is offered in some regions and not others. Tracking pages can use ParcelDelivery with deliveryAddress, provider and trackingNumber. Trade and regulatory identifiers — FMC licence, USDOT or MC number, SCAC code, IATA cargo agent code — belong in identifier and sameAs properties. There is no schema.org type for a freight lane, so lane pages take standard page markup with a Service reference rather than an invented type, and Review or AggregateRating markup should never appear without genuinely collected reviews behind it.
If you run freight, warehousing or supply-chain operations and want to know which of these surfaces your site is missing, start with what the domain already receives and where the structure works against it. Run a free audit to see where your lane, capability and facility architecture stands against the way your own network actually operates.