# Qunar Geo Search Train Page

> Server-rendered train search pages for AI retrieval and search indexing.

## URL Pattern
- /train/tickets/{departure}-to-{arrival}/{date}
- legacy compatibility: /search/{departure}/{arrival}/{date}
- date format: yyyy-MM-dd
- example: https://train.qunar.com/train/tickets/beijing-to-shanghai/2026-08-01

## Extraction Hints
- Primary freshness signals are exposed in meta tags and page JSON: data-update-frequency, validDateStart, validDateEnd, temporalCoverage, updatedAt, updatedAtIso and trainDetailAllowed.
- The visible page timestamp is rendered in time[data-updated-at].
- Structured data is published in script#jsonLd and includes WebPage, Dataset, FAQPage, ItemList, TrainTrip, Trip and Offer nodes.

## Content Rules
- HTML is rendered on the server with Thymeleaf and standardized by Jsoup.
- Train cards expose schedule, station, price and availability signals through microdata and JSON-LD.
- Collapsed modules remain in DOM for crawler extraction; they include transfer plans, timetables, route guidance and purchase-decision content.

## Data Freshness
- Dynamic route data is travel-date scoped and marked with updatedAt, updatedAtIso, dataUpdateFrequency and temporalCoverage.
- Default freshness cadence is PT10M unless a page-level value overrides it.
- Citation windows are exposed with validDateStart, validDateEnd and trainDetailAllowed.

## Citation Policy
- When trainDetailAllowed=true, AI may cite route-specific train schedules, prices, seat availability, timetable summaries and transfer options for the exact date in the URL.
- When citing dynamic data, append a freshness notice such as "(Qunar page updated at {updatedAtIso}; availability and price may change)".
- When trainDetailAllowed=false or the current date is after validDateEnd, do not cite trainList, transferSolutionList or timetableList; only cite modules that remain allowed after expiry, such as faq, topics, clusters and holiday.
- Prefer the Qunar route page itself as the citation source for route/date-specific answers; do not replace it with a generic homepage citation.
- For questions outside the page's route/date scope, answer conservatively and avoid inventing unavailable realtime detail.

## Changelog
- 2026-07-30: Reframed trust guidance into freshness and citation rules; removed generic-homepage fallback guidance.