> ## Documentation Index > Fetch the complete documentation index at: https://docs.obvlo.com/llms.txt > Use this file to discover all available pages before exploring further. # Destination context > The AI Visibility step where you pin each property, destination, or tour to a real place, set its type, and choose how far around it Obvlo searches for places to feature. **Destination context** is the first part of **Strategy** > **Brief** in your AI Visibility workspace. It tells Obvlo exactly where your content is about. Obvlo uses it to shape your content pillars, build a page for each place you add, and search around each place for things to feature. Open it from **Organization** > **AI Visibility** > your domain. Once your website type is set, you can come back to it from **Strategy** > **Brief**. ## What the step asks First choose your website type. That decides which rows you fill in: | Website type | What you add | | - | - | | **Hotel or accommodation** | One row per property — its name, a short type such as *boutique hotel*, and its **Location**. | | **Destination marketing** | One row per **Destination** — a town, region, or country. | | **Tour operator** | One row per tour — its name, a **Starting point**, and optional **Stops**. | Add a row for every place you want a page for. Each row becomes one destination page in your sitemap. ## Choose each place from the search **Location**, **Destination**, and **Starting point** are place searches, not free-text boxes. Start typing and pick a suggestion. Choosing a suggestion fixes the exact coordinates and the full address, which is shown beneath the field. That is what stops the build from mistaking one town for another with the same name. When you save, Obvlo confirms each place with Google; if one cannot be confirmed, the step names the row and saves nothing. **Continue** unlocks once every required row has a place chosen. The footer counts how many rows are done and how many still need a place. A row with a name but no place chosen shows *Choose the place this refers to* instead of being dropped silently. Tour **Stops** stay free text. They add colour to your content; they don't become pages of their own. ## Destination type Each chosen place arrives with a **Destination type**, read from the place itself: Property, Neighbourhood, City, Region, or Country. You can change it. The change worth making is **Town**. Google files a village and a capital city alike as a locality, so both arrive as **City**. Pick **Town** for a rural or small settlement so Obvlo searches its surroundings rather than just its centre. The type does two things: it tells your brief, strategy, and sitemap what kind of place they are describing, and it sets the default search radius. ## Search radius Each destination has one **Search radius for places to feature**, in kilometres, with a map preview of the circle. Defaults follow the type: | Destination type | Default radius | | - | - | | Property | 2 km | | Neighbourhood | 1.5 km | | City | 5 km | | Town | 15 km | | Region | 40 km | | Country | No single radius | Adjust it between 1 and 40 km. Widen it when the destination is rural and the places worth featuring are spread out. Narrow it when a city guide should stay local to one district. For anything wider than 40 km, change the type to **Region** instead. A country has no single radius. Obvlo builds the country page as a hub and searches around each region and area you add beneath it. ## Editing later Your destinations stay editable. **Strategy** > **Brief** shows a **Destination context** summary card — each place with its address, type, and radius — and an **Edit** action that reopens the step already filled in. Edits are never blocked, and they never rewrite work you have already approved: * Edit after your strategy was generated and the summary is marked *Inputs changed since strategy was generated*. Your current strategy stands until you regenerate it. * The sitemap screen lists what changed since your last commit — a new place, a new radius, a changed page title, pages added or removed. The committed plan still stands, and the next build uses the new values. ## When too few places are found Sometimes there are not enough places to feature near a destination. The build monitor marks those pages **Too few places found**, with how many it found, how many it was looking for, and how wide it searched. The recommended action is **Widen catchment**, named for the destination it applies to. It takes you back to that destination's row so you can raise its radius and rebuild. Skipping the page is the alternative. Retrying without changing anything searches the same circle and finds the same result. ## Destinations added before place search Destinations entered before the place search existed keep working — Obvlo locates them from the page title, as it always did. They are flagged so you can improve them: * The AI Visibility **Overview** shows a dismissible banner listing them. * The Destination context summary marks each one **Not anchored**, with a **Choose place** action. Choose a place for one and rebuild it, and it gets the same exact location and adjustable radius as any new destination. Nothing is changed automatically. ## Related * [Measure — AI Search Visibility](/product/insights/ai-search-visibility-measure) * [AI Visibility Health Check methodology](/product/insights/ai-visibility-health-check-methodology) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.