Editorial standards
Trust is our only currency. Airport travel costs are notoriously opaque, so our editorial guidelines are built entirely around transparency and verification.
AirportCosts gives priority to official airport pages, transport operator pages, government or regulator information, and published fare material. Third-party articles, forums and social posts may highlight a possible change, but they should not be used as the only source for a fee, deadline, exemption or rule that affects traveller cost.
A published drop-off fee, such as a terminal charge, can often be treated as a fixed current rule once verified. A transfer fare, taxi range, coach fare or rail cost may change by date, time, booking window, disruption, passenger count or pickup point. Pages should make that difference clear so users know which figures need live checking.
Airport pages are checked for drop-off fees, public transport options, free alternatives, airport-specific friction, terminal issues, source links and calculator assumptions. We look for details that change real journeys: payment deadlines, DART charges, Oyster boundaries, shuttle buses, early or late service gaps and road routes affected by congestion.
Readers can send corrections to info@airportcosts.com with the page URL, proposed change and official source. A correction is reviewed against the source before the page is changed. If a fee change affects multiple pages, the relevant airport guide, route pages, calculator data and sitemap date may all need updating.
Advertising, affiliate links and commercial partnerships must not control editorial conclusions. If a public transport route is awkward with luggage, the page should say so. If a private transfer is poor value for one passenger, the page should not hide that. Users need the trade-off, not a sales pitch.
AirportCosts avoids copied filler and repeated generic FAQs. Route pages should include real route context, such as the M25, M1, M11, DART connection, terminal split, London rail stop or local pickup geography where relevant. Thin summaries are not enough for pages that ask travellers to make a cost decision.
Pages should be reviewed when an airport changes drop-off charges, a transport operator changes fares, an official source URL moves, a new airport access rule appears, or users report a repeated issue. Major content updates should be reflected in the sitemap lastmod date so search engines can recrawl the changed pages.
