# Phuket (ภูเก็ต)

Phuket is modeled as: island base, beaches, food, ferries, airport. Static copy should foreground traveler decisions and avoid live claims.

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

## Quick call

- Best for: island base, beaches, food, ferries, airport
- Avoid if: monsoon surf/boat risk and island traffic cannot be static
- Best months: December–March

## Best bases

| Area | Best for | Watch outs | Transport logic | Walkability or spread | Caveat |
| --- | --- | --- | --- | --- | --- |
| Old Town | food, culture, markets | not a beach base | road to beaches/piers | compact core | rain traffic |
| Patong | nightlife and hotel inventory | noise/crowds | road-heavy | compact beach strip | surf/rain/crowd |
| Kata / Karon | beach families, lower chaos | still road-dependent | road to airport/Old Town | linear | monsoon surf |

## Season windows

- Best: December–March
- Acceptable with caveats: November and April shoulder; May–October if flexible/non-boat
- High risk: southwest monsoon rough sea/red-flag periods; heavy-rain advisories

## Nearby pivots and route role

- Nearby pivots: Krabi, Khao Lak, Phang Nga, Trang
- Route roles: international airport, Andaman ferry node, food-route node
- Arrival modes: Phuket International Airport, road bridge, ferry/speedboat

## Keep static

- base-area distinctions
- monsoon risk band
- food identity
- airport/road role

## Do not hardcode

- ferry schedules
- sea state
- red flags
- room prices
- AQI

## 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: Very high; build Phuket food-route and Old Town dining widgets.
- Culture angle: Old Town, Sino-Portuguese context, shrines, festivals.
- Shopping / gold / gem angle: Gold-buying check viable as live-price/shop-directory support; not a primary static claim.

## Source candidates

| Source | Type | Why it matters | Supports |
| --- | --- | --- | --- |
| TAT Phuket | official | official destination identity | static copy |
| UNESCO Creative Cities Phuket | public | gastronomy vertical support | food-route |

## Product links

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

## 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/