Managing pages
Every URL on your careers site corresponds to a page in Studio. Pages contain the sections, columns, and blocks that make up your content. The Pages list is where you create new pages, find existing ones, and manage the overall structure of your site. To open the pages list, click CMS in the left-hand navigation, then select Pages.Creating a page
The title is an internal label used in Studio. It appears in the pages list and browser tab, but candidates do not see it as a heading on the page itself. Choose something descriptive, such as “Life at our company” or “Graduate roles — London”.
The slug is the URL path for the page. For example, a slug of
/about means the page lives at yourcareers.com/about.Use
/ (a forward slash on its own) for the home page. Studio labels this page with a Home page badge in the pages list.For more detailed guidance on page display names, slugs, and SEO titles, see Naming conventions.
Select the locale for this page. A locale is always required and defaults to your site’s main language. The default locale has no URL prefix; additional locales are prefixed automatically — for example, a French version of
/about is served at /fr-fr/about.The pages list
The pages list shows all pages on your site:| Column | What it shows |
|---|---|
| Title | Internal name for the page |
| Locale | The page’s language |
| Slug | The URL path |
| Threads | Open comment threads on the page |
| Updated | When the page was last saved |
Common page patterns
There is no fixed set of page types in the CMS — all pages work the same way. The pattern depends on the slug you choose and the blocks you add.| Pattern | Slug example | What to add |
|---|---|---|
| Home page | / | Hero section, Job Search block, content blocks |
| Job listing page | /jobs | Job Search block |
| Static landing page | /graduate-roles | Rich text, Media, Button group blocks |
| About page | /about | Rich text, Media, Timeline blocks |
| Location page | /locations/london | Rich text, Map block, Job Search filtered by city |
Locale variants
If your site supports more than one language, you can create a translated version of a page. A locale variant is a separate page that shares the same slug but has a different locale — candidates are served the version matching their language. To create a translation, create a new page with the same slug and a different locale. Once more than one locale exists for a slug, the locale switcher in the top bar of the page editor lets you move between the existing translations.Archiving and restoring pages
Archiving takes a page offline without permanently deleting it. Archived pages no longer appear on the live site or in search engine results.The page goes offline immediately. It no longer appears on the site or in your sitemap, and its URL returns a 404 (not found) response.
Archiving a page does not delete it. You can restore it at any time. If a page was indexed by search engines, it may take a few days for search engines to remove it from results after archiving.
FAQs
Can I change a page's slug after creating it?
Can I change a page's slug after creating it?
Yes — open the page and update its slug in the page settings. If the old URL was shared or indexed, add a redirect so existing links keep working. Ask your inploi account manager if you’re unsure.
What happens to a page's content when I archive it?
What happens to a page's content when I archive it?
Nothing is deleted. The page goes offline and its URL returns a 404, but the content and version history are kept. Switch the list to Archived and select Restore this page to bring it back.
I created a translation but candidates still see the default language.
I created a translation but candidates still see the default language.
A locale variant must share the exact same slug as the original page, with a different locale. If the slug differs, Studio treats it as a separate page rather than a translation.