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.
1
Create a new page for the location
2
Go to CMS → Pages and click Create. Set a title (e.g. “London careers”), a slug (e.g. /locations/london), and a locale.
3
Add location-specific content
4
Open the page editor and build the page. Common content for location pages includes:
5
  • A hero section with an image of the city or office
  • A Rich text block describing the location, team, and culture
  • A Map block marking the office
  • A Job Search block filtered to show only roles in that city
    • 6
    Pre-filter the Job Search block
    7
    Add a Job Search block to the page. Open its Filters, add a filter with the Field set to City (or Town/Country), enter the location as the Default value, and mark it Hidden so candidates always see only that location’s roles.
    8
    Position the Map block
    9
    The Map block is placed using a latitude and longitude rather than a typed address. Look up the office’s coordinates (for example, from Google Maps) and enter them in the block settings.
    10
    Repeat for each location
    11
    Create a separate page for each location following the same steps.
    12
    Add each location page to the navigation
    13
    Add a dropdown in your Navbar block (see Adding a Navigation Item) and link to each location page from within it.
    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.