Commercial planning content
Service and quote-related content explains the facts required to evaluate a shipment. It must distinguish screening guidance from a confirmed trailer, route, permit, schedule or price.
Trust and editorial controls
Heavy Haul Editorial Methodology
Heavy Haul Now publishes planning content only after defining the canonical entity, matching material claims to appropriate sources, separating verified facts from guidance and scenarios, checking visible content against structured data, and applying a publication gate. Regulatory information prioritizes controlling agencies; equipment specifications prioritize exact manufacturer records. Review dates identify when a page was assessed, but shipment-specific permits, routes, equipment and facility access must still be reconfirmed.
- Last reviewed
- August 2, 2026
- Review responsibility
- Heavy haul planning and technical content team
Editorial scope
What This Methodology Covers
The methodology applies to indexable service, equipment, trailer, industry, permit, route, state, city, hub, FAQ, comparison and case-study content. Each page must have one canonical subject and must direct supporting details to the page that owns that entity.
Equipment and trailer intelligence
Machine and trailer pages identify configuration variables, loading methods and decision factors. Manufacturer specifications are treated as model-specific references, not universal transport promises.
Geographic and route intelligence
Location and route pages require named infrastructure, jurisdiction, facility, industry and operating-condition evidence. Generic city or corridor substitutions do not satisfy the publication standard.
Regulatory information
Permit, escort, dimensional and travel-condition content prioritizes the controlling public agency. Published information remains planning guidance until the applicable authority issues shipment-specific approval.
Evidence hierarchy
Sources Are Selected by the Claim They Must Support
Source quality depends on the statement being made. A manufacturer document may support machine specifications but not a current permit rule; a transportation agency may support a legal requirement but not a private facility’s appointment process.
Primary public authorities
Departments of transportation, permit offices, ports, toll agencies, bridge authorities, municipalities and other controlling bodies are preferred for rules, restrictions and public infrastructure.
Manufacturer documentation
Current specification sheets, manuals and official product records support model dimensions, operating weights, components and configuration details when the exact variant is identified.
Facility and infrastructure owners
Official terminal, port, rail, industrial-park, bridge and facility material supports access procedures, ownership, appointments and operating constraints within its stated scope.
Approved first-party records
A project record can support a case study only when cargo, route, equipment, permits, timeline, outcome, publication rights and any customer attribution have been verified.
Research workflow
Seven Controls From Topic Selection to Publication
1. Establish canonical ownership
Identify the real entity, search intent and parent-child relationship before drafting. Weak city-by-equipment combinations are rejected rather than manufactured.
2. Define the decision questions
Map the questions a shipper, dispatcher, permit coordinator or receiving facility must answer for the subject.
3. Collect claim-level sources
Match every material specification, authority, corridor, facility or restriction to a source suitable for that exact statement.
4. Draft the direct answer
Open with a concise answer that defines the subject, controlling variables and appropriate next step without unsupported certainty.
5. Build decision support
Add tables, comparisons, FAQs and contextual links that help a user choose or verify an action rather than merely repeat keywords.
6. Run the publication gate
Check editorial leakage, placeholders, canonical URL, sources, schema parity, links, local evidence, claim boundaries and conversion functionality.
7. Review and maintain
Record the review date and recheck material changes to authorities, specifications, infrastructure or editorial evidence.
Claim boundaries
Facts, Guidance, Scenarios and Company Proof Are Kept Separate
| Content class | Required evidence | How it is presented |
|---|---|---|
| Verified public fact | Suitable authority or official owner source | Cited with scope and review date |
| Manufacturer specification | Exact official model or configuration record | Qualified for model, variant and included components |
| Planning guidance | Industry practice plus applicable authoritative context | Presented as a decision factor, not guaranteed approval |
| Illustrative scenario | No experience claim required | Clearly labeled as hypothetical and never described as completed work |
| Company performance claim | Auditable first-party record | With period, definition and qualification |
| Case study | Approved project file and publication rights | Published only after the case-study evidence gate |
SEO, AEO and AI retrieval
Visible Content and Machine-Readable Data Must Agree
Structured data is generated only for information visible on the page. FAQ answers, breadcrumbs, canonical URLs, entity names and review dates must match their rendered counterparts. Schema is not used to introduce ratings, reviews, prices, locations or credentials that users cannot verify on the page.
Direct-answer discipline
Answers use plain language, define the controlling variables and avoid unsupported absolutes. Longer analysis follows after the concise response.
Entity consistency
Equipment, trailer, industry, location, route, permit and service pages use stable names, canonical URLs and contextual relationships.
Citation readiness
Material public facts retain visible source labels and review dates so users and retrieval systems can understand their basis.
No hidden authority claims
FAQPage, Service, Organization, Dataset and other schema types must not claim evidence, ratings or capabilities absent from the page.
Maintenance and corrections
Review Timing Follows the Volatility of the Information
| Information class | Review trigger | Required action |
|---|---|---|
| Permit and regulatory information | Scheduled review and material agency change | Recheck the controlling authority and update affected pages |
| Manufacturer specifications | New model, revision or configuration conflict | Reconcile the exact model record and qualify inclusions |
| Routes and infrastructure | Closure, construction, ownership or access change | Update the corridor record and linked location pages |
| Local industry and facility context | Facility opening, closure or material role change | Revalidate the entity relationship before retaining it |
| Company proof and case studies | Before publication and after any correction request | Verify evidence, rights, wording and attribution |
Policy answers
Heavy Haul Editorial Methodology FAQ
Does editorial review guarantee that a proposed heavy haul route is authorized?
No. Published route and permit information supports planning. The controlling agencies, issued permits, current route conditions and private facilities determine whether a specific loaded configuration may move.
Can AI-generated text be published without human review?
No indexable page should rely on unreviewed generated copy. Automation may support organization and drafting, but canonical ownership, sources, claims, links, schema and customer-facing language must pass the publication gate.
How are corrections submitted?
Use the contact page and provide the affected URL, disputed statement, proposed correction and supporting source. Material corrections are evaluated against the most authoritative available evidence.
Why are hypothetical planning scenarios used?
They can explain trailer, loading, route or permit decisions without claiming that Heavy Haul Now completed a shipment. They must remain clearly labeled and cannot include invented customers, outcomes, prices or performance claims.
Why might a page remain unpublished?
A page remains unpublished when it lacks a defensible entity relationship, unique answer, suitable evidence, useful decision support, correct canonical structure, working links or another required publication control.
Questions, corrections or supporting evidence?
Send the URL, disputed statement and supporting source. Material corrections are reviewed against the evidence and reflected in the affected page.