# Sukhothai (สุโขทัย)

Sukhothai is modeled as: UNESCO heritage, old-city stay, cycling. Static copy should foreground traveler decisions and avoid live claims.

- Province: Sukhothai
- Recommended page status: first-class destination
- Merge recommendation: No merge
- Data confidence: high

## Quick call

- Best for: UNESCO heritage, old-city stay, cycling
- Avoid if: heat and festival crowding
- Best months: November–February unless the page-specific season window states otherwise.

## Best bases

| Area | Best for | Watch outs | Transport logic | Walkability or spread | Caveat |
| --- | --- | --- | --- | --- | --- |
| Old City / Historical Park | heritage and cycling | less nightlife/transit | bike/road | compact park, hotels spread | heat/rain |
| New Sukhothai | bus, food, cheaper stays | farther from park | bus/road | compact town | heat |
| Si Satchanalai route | heritage extension | needs road time | road | spread | heat/rain |

## Season windows

- Best: November–February
- Acceptable with caveats: March–May heat, May–October rain-aware travel
- High risk: heat and festival crowding

## Nearby pivots and route role

- Nearby pivots: Ayutthaya, Chiang Mai, Phitsanulok, Lopburi
- Route roles: UNESCO heritage, old-city stay, cycling
- Arrival modes: Sukhothai Airport, bus/road, nearby rail via Phitsanulok

## Keep static

- page status
- merge/split logic
- seasonal caveats
- base-area logic

## Do not hardcode

- daily weather
- AQI
- transport schedules
- event dates
- prices

## Static decision signals

- today signal: Do not hardcode; use TMD, Air4Thai/PCD, transport and event feeds where relevant.
- weather risk: Use seasonal static framing only; daily weather is a future live signal.
- aqi risk: Live-check via Air4Thai/PCD where station coverage exists; especially relevant in dry/smoke season.
- transport friction: Treat route timing, transfer spread and public transport schedules as live or semi-live.
- food signal: Use as static food-route positioning only when supported by official/local source candidates.
- crowd level: Do not hardcode current crowding; express event/weekend sensitivity as static risk.
- comfort penalties: heat, rain, AQI where relevant, event/crowd pressure, route spread

## Specialist angles

- Food angle: Support food-route only if official/local market/food sources are added.
- Culture angle: Use official TAT/provincial/heritage sources; avoid attraction listicles.
- Shopping / gold / gem angle: No primary static vertical unless separately listed.

## Source candidates

| Source | Type | Why it matters | Supports |
| --- | --- | --- | --- |
| TAT Sukhothai | official | official heritage identity | static copy |
| UNESCO Sukhothai | public | World Heritage basis | static copy |
| TAT Sukhothai Loi Krathong Festival | official | event crowd signal | future signal |

## Product links

- [Open current traveler page](https://enjoythai.land/where-to-go/sukhothai/)
- [Open stay guide](https://enjoythai.land/accommodation/sukhothai/)

## Raw package links

- https://enjoythai.land/research/cities/files/city_research_packets.json
- https://enjoythai.land/research/cities/files/city_strategy_matrix.csv
- https://enjoythai.land/research/cities/files/source_appendix.csv
- https://enjoythai.land/research/cities/