/job/79000019 and /job/79000020 are served by the same page, each showing its own role. Rather than building a page per job, you build one template and bind it to a Job resource.
This guide assumes you’re comfortable with the page editor. The concepts used here — Resources, dynamic slugs, interpolation, and conditions — are explained in Resources and dynamic pages.
Building a job detail page needs full page update access, because it uses the Resources and Sitemap settings. If you can’t see those sections in a page’s Settings, ask an administrator (see Users and permissions).
Create the page
Add and bind the Job resource
Build the page content
Use interpolation to drop the job’s data into your blocks. In a Rich text block, reference job fields with double curly braces:Set the SEO metadata
In Settings → SEO, you can use the same interpolation so each job gets tailored search results:- Page title — e.g.
{{resources.job.title}} | Your Company - Meta description — e.g.
{{resources.job.meta_description}}
JobPosting structured data automatically from the bound job, which is what makes them eligible for Google for Jobs. See SEO and discoverability.
Configure the sitemap
A dynamic page template needs to know which URLs actually exist so they can be listed in your sitemap for search engines.The Company slug here is the company slug in the underlying system, which may differ from the CMS company slug. If you’re unsure which value to use, ask your inploi account manager.
Preview and publish
If the page doesn’t render
See Why isn’t my job page showing? for the full list of causes — missing preview parameter, unpublished page, wrong job ID, a job that belongs to a different company, or content that references{{resources.job.*}} without a Job resource configured.