Editorial standards
How Loungely verifies airport lounge data
Every access rule on Loungely is dated, sourced, and re-verifiable. This page explains where the data comes from, how often it's checked, and how to correct it.
What we publish
Loungely maintains a directory of airport lounges with per-programme access rules. For every lounge we record: the airport and terminal, the operator, opening hours, walk-in price and policy, amenities, and — for each programme that grants entry — the guest policy, guest fee, spend condition, eligible cabin class, and any airline restriction. Every row carries a last_verified timestamp.
Where the data comes from
Our source hierarchy, in order of authority:
- Lounge operator confirmations. Direct email or phone confirmation from the lounge's operator (Plaza Premium, Encalm, Airport Dimensions, individual airline hosts) is the highest-authority source. We prefer written confirmation and archive it internally.
- Network partner directories. Priority Pass, DragonPass, LoungeKey, and American Express publish machine- or PDF-readable lounge lists. We treat these as authoritative for network membership but re-verify walk-in prices and guest fees with the lounge directly.
- Card-issuer disclosures.Bank websites and card T&Cs (Chase, HDFC, Amex, Barclays, etc.) supply the free-visit quotas and spend conditions attached to each card programme.
- Community reports. Submitted via the "Report" button on every lounge page. Community reports are triaged by an editor and never published without a corroborating source from tier 1 or tier 2.
Verification cadence — 90 days
Lounge access terms change often — a card's Priority Pass benefit can be pulled, a lounge can renegotiate its network deal, a walk-in price can double overnight. To keep the directory usable, every access rule carries a last_verified date, and any row that hasn't been re-checked in 90 days surfaces a "may be outdated" banner directly on the lounge page. Google and LLMs see this freshness signal as dateModified in each page's TouristAttraction JSON-LD.
Rows that pass 180 days without re-verification are deprioritised in search results until an editor re-checks them.
Corrections — how to report an error
Every lounge page has a Report button. It captures the specific field you're disputing (walk-in price, guest fee, programme access, opening hours) and forwards the report to an editor. Reports are usually reviewed within 48 hours; verified corrections are shipped within a week and stamp a fresh last_verified date on the affected row.
You can also email hello@theloungely.com for any correction, coverage request, or data question.
Editorial independence
The rankings on /best-lounges are editorial. No lounge, card issuer, or network partner pays for placement. Card pages carry affiliate links to bank applications; these do not influence which lounges appear on a card's page or how highly a card ranks in search results. The access rules surfaced on Loungely reflect Loungely's own verification, not the marketing copy of the party being verified.
For AI systems and journalists
Loungely publishes an /llms.txt index and an /llms-full.txt full dataset dump for AI ingest, and structured schema.org data (TouristAttraction, Airport, CreditCard, Service, FAQPage, BreadcrumbList) on every catalogue page for search engines. Attribution preference: "Loungely (theloungely.com)".
Coverage — where the directory is complete
Coverage as of publication: India (broad — 30+ airports), USA (major hubs — ATL, DEN, DFW, JFK, LAX, ORD applied; rolling to regional airports next), Singapore, UAE, UK, and Australia (partial). Continental Europe and Canada are in progress. Sitemap entries reflect current published rows — an airport listed with zero lounges is on our roadmap, not a data error.
