Skip to main content
Location-specific pages help candidates find roles and information relevant to where they want to work. There are two approaches in Studio, depending on how many locations you need and how often they change.

​
Approach 1 — A static page per location

Best for: a small number of fixed locations (fewer than 10–15), or when each location page needs significantly different content.
If the content structure is identical across all your location pages (same sections, same layout), consider building one page and saving the layout as a prefab. You can then start each new location page by inserting that prefab and updating only the location-specific details.

​
Approach 2 — A single dynamic page

Best for: a large number of locations that all share the same page structure. A dynamic page uses a slug with a wildcard segment — for example, /locations/:city. A single page then serves all location URLs, such as /locations/london, /locations/manchester, and /locations/birmingham. The value from the URL (the city) can be used in block conditions and to filter the Job Search block. You can create dynamic slugs yourself in the Pages list. Wiring up each block to respond to the URL value, and making sure all the location URLs appear in your sitemap, uses the same building blocks as a job detail page — Resources, dynamic parameters, interpolation, and conditions. See Resources and dynamic pages for how those work, and Creating a job detail page for a worked end-to-end example.
Dynamic pages are best suited to organisations with many locations that all follow the same content structure. For most careers sites, static pages per location are simpler to manage. If you’d like help setting one up, contact your inploi account manager.