Publishing a hire page

Every hire page has one of four statuses, and each one controls who can see the page and whether the form is accepting new applications. This guide walks through the lifecycle: how to publish, what happens on each transition, and how to wind a page down without losing the applicants you've already collected.

The four statuses

• Draft — Private to your team. The public URL returns 404. The form does not accept submissions. Use while you're writing the role.
• Published — Live and indexable. The form accepts submissions. Counts against your plan's active-pages limit.
• Closed — Public URL stays live with a "no longer accepting applications" message. The role body remains visible; the form is disabled. Frees a slot in your active-pages count.
• Archived — Public URL returns 404. Hidden from the dashboard by default. All applicants, notes, and messages are preserved.

Only published pages count against your plan's active-pages limit (1 on Free, 3 on Starter, 10 on Growth, 30 on Scale, unlimited on Enterprise). Drafts, closed, and archived pages are unlimited on every plan.

Draft → Published

A page starts as a draft. Click Publish in the top-right of the editor. We:

1. Generate the public URL and the SEO/OG metadata
2. Add the page to your JobPosting JSON-LD schema and to the sitemap
3. Start accepting applications immediately

If you've hit your plan's active-pages limit, Publish is disabled and we'll prompt you to upgrade or close another page first.

You can edit a published page at any time. Changes go live on save — no re-publish needed.

Published → Closed

Use Close when you've finished hiring for this role but want to keep the page visible.

What happens:

1. The form is replaced with a "no longer accepting applications" message
2. The role body stays visible at the same URL
3. A slot frees in your active-pages count (so you can publish another page)
4. Every applicant and stage in your kanban stays exactly as it was

Closed pages are useful for keeping a record of past roles, for SEO continuity, and for letting candidates who find an old link know what happened.

You can re-open a closed page (publish it again) any time — applications resume where they left off.

Closed → Archived (or Published → Archived)

Use Archive when the role is fully retired and you don't want it visible anywhere.

What happens:

1. The public URL returns 404
2. The page is hidden from your dashboard's default view (toggle "Show archived" to see it)
3. All applicants, stages, notes, and messages are preserved — they're not deleted, just no longer indexed

Archive is reversible. You can un-archive a page back to draft and re-publish if needed.

Deleting a hire page

Delete is permanent. It cascades to every applicant, every note, every message, and every uploaded file for that page. Use Archive instead unless you have a specific reason to permanently delete.

Only the workspace owner can delete a page.

What happens to applicants on each transition

Applicants are bound to the hire page they applied to, regardless of the page's status:

• Closing a page does not move applicants out of your kanban
• Archiving a page does not delete applicants
• Deleting a page does delete applicants — permanently

If you're winding a role down and want the data to live on, close then archive, in that order. Don't delete unless you actually want the data gone.

Frequently asked

What's the difference between Closed and Archived?

Closed is still public with no apps; Archived is not public at all. Use Closed for "this role is filled but I want the URL alive"; use Archive for "this role is done, hide it."

Will a closed page still rank in Google Jobs?

We mark closed pages with JobPosting.validThrough set to the closing date, which tells Google Jobs to deprioritize but not de-index.

Can I schedule a publish or auto-close?

Not in v2. Status changes are manual.

Does closing a page send candidates an email?

No automatic email fires on close. If you want to email everyone still in early stages, move them to a "Rejected" stage and let the stage-triggered email do the work.