We keep /ch/gr broad enough to explain the canton context without stealing intent from the city pages.

Graubuenden hub for focused local landing pages
Graubuenden pages should feel flexible and commercially clear across tourism-adjacent, service, and regional business use cases. The canton hub gives every city page a clear parent and keeps the Swiss cluster easy to scale.
View city pagesGR
The Graubuenden hub sits between the Switzerland page and every local city page.
Graubuenden pages should feel flexible and commercially clear across tourism-adjacent, service, and regional business use cases.
We keep Graubuenden pages practical and structured so the city layer can support more than one acquisition channel.
GR
Canton code in the URL structure
Hub
Parent layer for focused city landing pages in the canton
The canton page acts as a linking hub so city pages can stay sharper and more commercial.
If a city starts showing deeper demand, the structure is ready for support-topic expansion later.
City Pages
City landing pages inside Graubuenden
These are the commercial destinations under the canton hub. Each city page is meant to carry the sharper local angle, problem framing, offer, proof, and CTA.
City page
Davos
hospitality-adjacent and premium local service offers
City page
Thusis
B2B teams that need custom code, scalable architecture, and a more capable digital platform for growth
FAQ
Why create a dedicated Graubuenden canton hub?
Because the canton hub at /ch/gr gives every city page a clear parent node. It also keeps the Swiss cluster easier to navigate, expand, and interlink.
FAQ
Do city pages in Graubuenden still work as money pages?
Yes. The canton hub handles the broader market context, while the city page can stay fully commercial with a sharper local angle, clearer problem framing, and stronger CTA placement.
FAQ
Can this structure support topic pages later?
Yes. Once a city proves demand, it can expand naturally into /ch/gr/city-slug/support-topic without rebuilding the whole architecture.