Anyone who has run a directory or a job board for a while knows the moment. You open an old category page and half of it is out of date. A tool that shut down. A business that moved. A job that was filled long ago, or was never really open.

Across the communities we follow, this keeps coming up from very different angles. Directory owners who went back and link-checked their own listings found a big share of them failing. One found that a large chunk of the entries an AI assistant had added for them were dead within a year. Another noticed that "failed" wasn't one thing: some sites were genuinely gone, while others were just blocking automated checkers and worked fine in a browser. On the hiring side, people tracking job posts keep pointing at "ghost jobs": roles that stay up for months with no intention of filling them. When a big job platform pulled a large batch of fake postings, the discussion quickly turned to why listings were allowed to sit there in the first place. People starting niche job boards ask a related question from the other end: how do you make sure employers who post actually get applicants, so they come back?

And not everyone wants things to expire. One launch-site builder made "launches don't expire" a selling point, arguing that a permanent page keeps sending visitors long after launch day.

So here's the question: should listings expire by default?

Side A: yes, everything should have a shelf life

The case for expiry:

  • Stale listings cost trust. A visitor who clicks three dead entries in a row stops trusting the other forty. For job seekers, applying to a role that doesn't exist is worse than a broken link. It wastes real hours and hope.
  • Old pages make the site look abandoned, to visitors and to search engines. A directory full of dead links reads like a site nobody maintains.
  • Expiry forces a heartbeat. If owners have to renew or re-confirm, you learn who is still around. Silence is information.
  • It creates a natural paid moment. Renewal is the obvious place for a featured upgrade or a paid repost, without punishing anyone who stays free.
  • It's honest to the people listed. Businesses that closed, or employers who filled the role, don't want inquiries they can't answer.

Side B: no, permanence is part of the value

The case against default expiry:

  • Owners forget to renew. Plenty of good listings vanish because an email went to an inbox nobody reads. You end up deleting the real ones and keeping the spammers, who are very diligent about renewals.
  • Old pages still earn. A permanent profile or launch page can keep sending visitors and search traffic for years. Removing it throws that away.
  • Some content is meant to be historical. A record of past launches, past events or closed businesses can be useful as an archive.
  • Expiry adds admin work. Renewal reminders, grace periods, support emails from people whose listing disappeared. For a one-person directory, that adds up.
  • Dead isn't always dead. If your checker can't tell "gone" from "blocks bots", automatic removal will take down perfectly good entries.

The grey areas

  • Jobs vs everything else. Most people who argue for permanence are talking about tools, businesses or launches. Very few defend a job post that never expires. Roles get filled; tools mostly don't.
  • Remove, hide or mark. Expiry doesn't have to mean deletion. A listing can move to an "unconfirmed" state, drop out of search on your site, or show a visible "last confirmed" date while staying online.
  • Who confirms. The owner clicking a link, your own checker, or visitors reporting problems all give different signals, with different false alarms.
  • Free vs paid. Should paid listings be held to the same standard? If someone paid for a year, does their listing stay even when the link breaks?
  • AI-added entries. Listings created in bulk by a script or an assistant often have no owner to ask. They may need a stricter rule than ones a real person submitted.

A middle path we keep coming back to

We build directories and job boards for a living, and where we've landed is somewhere in between. Job posts should expire by default, with a short, clear window and an easy one-click repost for employers who are still hiring. For directory listings, we prefer a visible "last confirmed" date over hard deletion. Run a regular link check that treats "blocked" differently from "gone", send owners a re-confirm request, and move unconfirmed entries out of the main listings after a grace period instead of deleting them. Claimed listings with an active owner get the benefit of the doubt. Unclaimed, bulk-added ones don't.

None of this is complicated technically. The hard part is deciding the policy, writing it down where listers can see it, and actually running the check.

Your turn

  • If you run a directory or job board, do listings expire on your site? What made you choose that?
  • Have you link-checked your own listings? How much was actually dead, and how much was just blocking checkers?
  • For job boards: what expiry window feels fair to employers without leaving ghost jobs online?
  • Would you trust a "last confirmed" date on a listing, or does it only matter if the site removes what fails?