Stay-guide priority
low priority with 3 named anchors
Bangkok-adjacent purpose-stay inventory; not a leisure hotel guide
Accommodation research
Nonthaburi is modeled as Bangkok support lodging node. This page keeps the base logic, named stay anchors, rental-policy caution, and live-only fields visible without pretending room inventory is static truth.
Stay-guide priority
Bangkok-adjacent purpose-stay inventory; not a leisure hotel guide
This row is the fast product call for whether the city deserves a stand-alone stay guide, a merged guide, or research-only treatment.
| City | Status | Primary bases | Hotel model | Rental model | Confidence |
|---|---|---|---|---|---|
| Nonthaburi | Bangkok support lodging node | Ko Kret/river route / MRT/urban Nonthaburi | Bangkok-adjacent purpose-stay inventory; not a leisure hotel guide | condos/serviced apartments only as Bangkok-adjacent support | medium |
Use these rows to understand the city’s stay shapes. They are orientation anchors, not a substitute for live rates, room inventory, or cancellation terms.
| Stay anchor | Type | Area or base | Best for | Publishing rule |
|---|---|---|---|---|
| Nonthaburi Palace Hotel | hotel | Mueang Nonthaburi / MRT-purple-line support | Bangkok-adjacent business/support stay | static candidate with live validation |
| Kalanan Riverside Resort | resort | Chao Phraya / Pak Kret side | river resort, weddings/events, Ko Kret context | static candidate with live validation |
| Airbnb / vacation rental / serviced-apartment pattern | vacation rental pattern | city-specific; do not hardcode individual listing | business, medical, airport, event, family support stays | live-only inventory; static page may describe safe booking checks |
The package is deliberately strict about what can be written statically and what must remain a live check.
| Rule | How to use it |
|---|---|
| Safe to publish statically | base-area role / route role / official hotel identity/source URL / approximate area / stable history/opening notes only when sourced / caveats / stay-guide priority |
| Must stay live | room availability / nightly price / user rating score / individual review count / Airbnb listing legality / condo/building rules / host license / cancellation policy / ferry/weather/event disruption / exact shuttle/transfer times |
| Rental policy | Do not static-publish individual Airbnb or vacation-rental listings. Keep legality, building rules, host status, and cancellation terms as live checks. |
| Suggested widgets | Bangkok support stay decision widget |
Official hotel pages and public sources support stable identity; reviews and platform layers stay clearly marked as dynamic or catalog-only.
| Entry | Source role | Type | Supports |
|---|---|---|---|
| Nonthaburi Palace Hotel | primary/static candidate | public social/business page | support-node lodging example |
| Nonthaburi Palace Hotel | review/catalog signal candidate | public social/business page | support-node lodging example |
| Kalanan Riverside Resort | primary/static candidate | official hotel | Nonthaburi river support card |
| Airbnb / vacation rental / serviced-apartment pattern | primary/static candidate | commercial-catalog-only / generated platform search | future accommodation live-signal / legal-caveat widget |
| Airbnb / vacation rental / serviced-apartment pattern | review/catalog signal candidate | commercial-catalog-only / generated platform search | future accommodation live-signal / legal-caveat widget |
Vacation-rental rows are city-level patterns only.
The research brief explains what we know. These are the public pages where the lodging logic should actually change a traveler choice.
Use the raw package when you need the full row data, matrix, policy note, or original archive instead of the rendered lodging brief.