SEO for logistics companies, built one freight lane at a time

Shippers search lanes. Your website sells services.

Open almost any Indian freight forwarder's site and you'll find the same seven pages: ocean freight, air freight, customs clearance, warehousing, project cargo, contact. Every competitor has the identical seven. None of them match how a shipper actually types.

A merchandiser with 40 tonnes of textiles moving next month doesn't search "ocean freight services". They search a lane, and often an abbreviation: nhava sheva to jebel ali lcl, delhi to guwahati ftl rates, mundra to rotterdam transit time. The service is assumed. The route is the question.

That gap is the whole opportunity. The lane is a natural content unit — it repeats across hundreds of combinations, each one has genuinely different facts attached, and almost nobody in the Indian market has built the pages properly. It's also the fastest way to publish 300 thin pages and get the domain suppressed, so the rule for which lanes qualify matters more than the template.

The three-question test before a lane gets a URL

This is the part that separates a defensible lane library from scaled content abuse, which is a term in Google's own spam policies and applies exactly to what most logistics sites do with route pages. Run every proposed lane through three questions. Two noes and it doesn't get published.

• Start with 15 to 30 lanes, not 300. Publish your busiest corridors, wait eight weeks, and check indexation. If 25 of 30 are indexed and picking up impressions, the template works and you can extend. If 10 are indexed, the template is thin and publishing 300 more makes it worse.
• One lane, one direction, one URL. Mundra to Rotterdam and Rotterdam to Mundra are different rates, different equipment availability and different documentation. If you can't write them differently, you only have one page.

What has to be on a lane page so it isn't thin

A lane page that ranks and converts carries information a shipper would otherwise have to email three forwarders to get. That's the test — would somebody bookmark this, or is it a paragraph of adjectives around a route name?

1. Ports or terminals, named. Nhava Sheva (JNPT) and Mundra are not interchangeable, and a shipper in Ludhiana routing through ICD Tughlakabad needs to see their ICD on the page.
2. Transit time as a range, with the reason. "18–24 days port to port, longer on transhipment routings via Colombo or Jebel Ali." A single number is a promise you'll break.
3. Cut-off and frequency. Weekly sailing, Wednesday documentation cut-off, gate-in by Monday. This is the detail that makes a page feel operated rather than written.
4. Documentation and compliance for that lane. Certificate of origin requirements, fumigation, IIP-certified packing for hazardous, e-way bill thresholds on domestic FTL. These change per destination, which is precisely why the pages aren't duplicates.
5. Equipment and load types. 20ft, 40ft HC, reefer, flat rack, over-dimensional. Or for road: 32ft SXL, multi-axle, PTL slabs.
6. One honest limitation. "We don't do reefer on this lane" builds more trust than a page claiming everything. It also stops the enquiries you don't want.

Service clusters: 3PL, warehousing and last mile

Lanes handle freight movement. The rest of the revenue sits in three clusters that are searched completely differently, and each needs its own architecture rather than one paragraph on a services page.

3PL is searched by category and vertical: 3pl company for fmcg india, third party logistics for ecommerce. The buyer is comparing capability, not price, and the winning page describes systems — WMS, integration with the client's ERP or marketplace, SLA structure, how returns are handled.

Warehousing is searched by location, and Indian warehousing search is genuinely geographic: Bhiwandi for the Mumbai belt, the Bhiwadi–Farukhnagar corridor for NCR, Hoskote and Nelamangala for Bengaluru, Sriperumbudur for Chennai. A page per facility with square footage, racking type, dock count, temperature capability and distance to the nearest highway beats a generic warehousing page in every one of those markets.

Last mile splits again into B2B distribution and D2C delivery, and the D2C side overlaps heavily with the queries D2C brands run when they're choosing a fulfilment partner. Pincode coverage, COD handling, RTO rates and NDR management are the things people actually search and compare.

Rates and transit times: the query you're afraid to answer

Rate queries carry the most intent in the entire category and almost every forwarder handles them by saying "contact us for a quote". Which is the correct commercial answer and a terrible page, because there's nothing on it to rank.

Freight rates move weekly — bunker adjustments, peak season surcharges, capacity swings, Red Sea routing. You can't publish a fixed number and you shouldn't try. You can publish the structure of the rate, which is more useful to a first-time shipper than the number anyway.

• Break down what's in the price. Ocean or line haul, THC at both ends, bill of lading charges, customs clearance, documentation, haulage to the ICD, destination charges. Most SME exporters have been surprised by at least three of these.
• Give a band, with an "as of" date and a note that it moves. A stated range with a timestamp reads as honest. A precise number that's stale reads as a bait-and-switch.
• Name what changes it. Volume, equipment availability, season, whether it's direct or transhipment, whether the consignee wants DDP.
• Put the quote form on the lane page, prefilled with the lane. Not a link to a global contact page. The friction between a rate query and a quote request should be one field.

Your tracking page is eating the crawl budget

Almost every logistics site has a tracking function, and almost every one of them is quietly generating an indexable URL per consignment — /track?awb=123456789. Two problems follow, and the second one is serious.

The first is crawl budget. Googlebot spends its allocation on millions of parameterised tracking URLs and gets to your new lane pages weeks late, if at all. On a large forwarder's site this can be the single biggest technical constraint on indexation, and no amount of content fixes it.

The second is that if those pages render a result — consignee name, delivery address, phone number — you've published your customers' shipment data to a search index. It happens more often than the industry admits. Fix is straightforward: disallow the tracking parameter in robots.txt, add noindex on the result template, and keep exactly one indexable tracking landing page targeting track [your brand] shipment, which is a real branded query worth owning.

Two buyers, one website

The same site serves an SME exporter who wants a rate this afternoon and a procurement committee that will run a six-week RFP. Build for one and you lose the other.

• Report by lane, not by session. The only report worth reading maps query → lane page → enquiry → quoted → booked. Traffic on a logistics site is a vanity number; quoted volume by lane tells you which corridors to publish next.
• Tag enquiries by mode at the form. An SME rate request and an RFP invitation are different sales motions and blending them into one "leads" line hides both.