All resources

After a job posting closes, what should you do with your blog posts?

Good stories can outlast a hiring round. Learn how to audit outdated details and application links and decide whether to update a post or make it private, with a quarterly content checklist.

Two team members checking old posts and links with a magnifying glass and a checklist

The end of a hiring round doesn't make stories about the people you work with useless. But if a reader finishes a good interview and clicks a button that leads to a closed posting, they're left with no idea where to look next. Before you delete a post, separate the content worth keeping from the information that needs to change.

A job posting and a piece of content have different lifespans

An announcement for a specific position may have done its job once hiring ends. How a team solves problems and what its members have experienced, on the other hand, remain useful the next time you hire. For each post, check again what the reader gets from it.

For example, the point of “We're hiring designers this September” is whether the role is open now, while the point of “How a designer and a developer solved a problem together” is the collaboration itself. For the latter, keeping the body and changing the hiring information may be the better call. The criteria below are examples to support your judgment; confirm with your team what should actually stay public.

  • Posts that are still accurate and useful: Keep them, but check the links.
  • Posts where the story holds but the conditions or the contact have changed: Update those details and note the date they're accurate as of.
  • Posts announcing hiring that has closed: Say so in the title and the body, and link to current hiring information.
  • Posts whose public scope needs rethinking or whose key information is inaccurate: Make them private, then decide whether to verify and update.

Check the title and the apply link before the body

Readers may arrive having seen only a search result or a shared title. If the title says “Now hiring,” adding a closing notice at the very bottom of the body may not be enough. Make sure the title, the opening and the button copy all describe the same situation.

For links, don't just check that they open; check where they take the reader. A posting that only shows a closed notice, a page that now describes a different role, or a page that requires a login may not be what the reader expects. If a specific posting can no longer be found, choose a destination that actually helps, such as your current openings or a team introduction.

Also confirm with the person in charge which role details, working arrangements, hiring steps and contact details can be public. A recent review date doesn't make the information current. For conditions you couldn't verify, write down who will confirm them and by when rather than fixing them by guesswork.

Keep past experiences, and set current information apart

It's important not to let an experience from the time of the interview read as today's policy. If things have changed, give the time context, for example “This interview reflects how we worked at the time.” If a direct quote has to change, confirm the meaning with the interviewee again.

In Teamblog, you can edit a published post and apply the changes. For example, you can keep the collaboration story in the body and change the final button from “Apply as a designer” to “View open positions.” Check the button copy and the destination URL together. Owners, admins and editors edit published posts; contributors take part in draft work.

If what readers need to know has changed substantially, leave a brief note in the body with the date of the update and what changed. Rather than changing only the date to make an old interview look new, it's clearer to show when the experience is from and what you brought up to date. After editing, also confirm that the save and update actually went through.

Making a post private buys you time to review

If a post contains something that can't stay public right now, such as incorrect working conditions or customer information that needs checking, you can make it private while you review. There's no need to hide every useful team story simply because hiring has ended.

Teamblog's public/private setting for posts lets you change whether a post is visible. When you do, also check links from other public posts and URLs you've shared elsewhere. It's better to point readers to information that's currently public than to leave them clicking through to a private post.

Making a post private doesn't immediately remove screenshots already shared or content that remains in search services. In your records, note why it was made private, the date you'll review it again and who is responsible. When you make it public again, recheck not only the body but also the buttons, photos and role conditions.

Check shared information and already published posts separately

If the same hiring information appears in several posts, there are several places to update. First settle on the copy to use now, then go through the list of posts that contain it. Each post may serve a different purpose, so think about the next action for each one rather than pointing every button to the same place.

If you keep shared hiring information in Reusable blocks, a paid Teamblog feature, you can insert it again in your next draft. When hiring closes, update the copy and links in the saved block first so outdated information doesn't keep making its way into later posts.

An example of choosing hiring information from Reusable blocks and inserting it into a draft. Inserted content is managed separately from the source block.

The people, content and figures shown are fictional examples.

Editing a block doesn't automatically sync content already inserted into published posts. You have to open existing posts separately and check their links and copy. Recording the source block and the published posts separately in the checklist below makes it less likely you'll update one and stop there.

Run quarterly reviews alongside checks right after a change

Set a day each quarter to go back through every post. But when something happens that affects a reader's decision, such as hiring closing or a change to the organization or working conditions, don't wait for the next quarter: check the related posts first.

If you're short on time, start with posts that link to current hiring information, posts with recent traffic and FAQs whose conditions change often. A post with important information that's wrong should be fixed first, even if its views are low. Use statistics as a reference to help you prioritize.

At the end of the checklist, don't just write “Checked.” Note what you changed and who will look at it next. Content can only keep describing your team accurately if someone can take it over after publication.

Use the quarterly content checklist to hand over to the next owner

Copy one for each post and check the title, conditions, links and visibility. Use it for quarterly reviews and right after hiring closes.

No login needed. Use it right away.

Show the content checklist text