How should a careers page handle open and closed jobs?
A careers page containing only “Join our team” and an email address may leave visitors unsure which role is available. Old vacancies that continue collecting applications create a different kind of uncertainty. Treat the area as a lifecycle: opening, maintaining and closing each listing. This guide covers page structure and editorial responsibility. It does not advertise a real vacancy or make decisions about candidates.
Separate the company introduction from each role
In our original teaching scenario, a manufacturer has an illustrative project coordinator role. The careers landing page can explain the working environment; the individual role page should describe responsibilities, location and the application route. Linking every job to one generic paragraph makes it harder to identify the purpose of an application. If no positions are open, say so. A general expression-of-interest channel should be clearly distinguished from a specific advertised vacancy.
Lead with information that changes the decision
Make the role name, team, location, remote or on-site arrangement and current application status easy to find. Then explain actual responsibilities and relevant experience. Do not invent compensation, benefits or working conditions to fill empty spaces in a mockup. Separating essential requirements from preferences can also clarify the description. Assign an approver for these details so that the designer does not have to guess employment conditions while constructing the page.
Test the actual application route
A role card should lead to that role’s details and then to the relevant application destination. If an external recruitment tool is used, check that it opens the same position. For an email route, instructions about identifying the role in the subject can help. If files are uploaded, explain accepted formats and sizes before submission. Our file-upload experience guide covers those interface decisions; the business’s authorised owner should separately verify its personal-data processing information.
Associate search markup with the correct page
Google’s JobPosting documentation requires markup on a page describing a single real vacancy and alignment with the visible content. Do not mark up a general careers list as though it were one role. Structured data does not guarantee a search appearance. Establish accurate, current content before adding the relevant technical representation. The illustrative role in this article is not an employment opportunity and must not receive JobPosting markup. Keep a teaching design distinct from an actual opening.
Define closure before publishing
Do not leave the end of the lifecycle undecided. When a role is filled, the application control can be removed, a clear closed status shown and visitors directed to current opportunities. Search markup also needs to reflect closure; Google documents expiry dates, markup removal and page removal as ways to handle expired postings. If the company retains an archive, closed roles must not look open. Record who performs the review and when it should happen.
Review three states at handover
Test one open role, one closed role and a list with no current vacancies. Can someone on a phone read the title and status? Does the detail link open the correct role? Is there a clear route back to the list? Does the team know where submitted applications arrive? Record the answers as observations. Our editorial approval and publishing guide and business website design service can help include careers content in ongoing maintenance rather than treating it as a one-off launch feature.
Frequently asked questions
Should the careers page disappear when there are no openings?
Not necessarily. Explain the current situation clearly and distinguish any general interest channel from an open vacancy.
Does JobPosting guarantee visibility on Google?
No. Correct markup is only part of eligibility and does not guarantee crawling, indexing or a special search appearance.