Do I need to update the team page immediately when someone leaves?

At the latest, on their last working day. The simplest fix is adding the website to the offboarding checklist so it doesn't depend on chance.

What should I do with the departing person's email address?

Forward it to a shared address for a transition period, then shut it down. An address that quietly leads nowhere costs you enquiries.

Should names appear on the website at all?

Yes for direct contacts — that builds trust. Everywhere else, roles and function addresses are easier to maintain.

What about old team photos?

Review them once a year, separately from the text. A photo with people who've left is just as outdated as a wrong name, just harder to spot.

How do I handle a vacant role while hiring for it?

Name the function instead of a person, with a shared address. It reads as accurate today and won't need changing again once someone starts.

What about photos of offices or vehicles after a move?

Treat them the same as a team photo. A picture of the old location or an old vehicle confuses visitors who show up expecting to recognise the place.

Who should be told when a team page needs updating?

Whoever owns editing access, named specifically — not "the office" in general. A named owner is the difference between a same-day fix and a months-long gap.

Team and contact pages: when someone leaves

When someone leaves the company, the team page, contact page, named contacts on service pages and personalised email addresses should all be updated in one go. Otherwise prospects write to an address nobody reads, or ask for a person who's no longer there.

August 5, 2026

Is your team page still accurate?

Enter your address — DustOff reports spots that no longer match who's actually on the team today.

No account, no credit card. Takes a minute.

The phone call nobody wants to have

"Could I speak to Ms. Berger, please?" — "She left two years ago." That exchange is awkward for everyone, and it only happens because one page never got touched.

Quieter still is the case where someone emails a personalised address nobody reads anymore. That enquiry never shows up in any statistic. It simply vanishes.

The list for someone's last day

When someone leaves, people remember keys, access and account closures. The website rarely makes that list. Put it there:

Team page: remove or replace the entry
Contact page: named contacts and extensions
Service pages with a named contact person
Personalised email address: forward it or shut it down
Quotes, testimonials and blog posts with a name attached
Photo captions

Every place a person shows up

A staff change reaches further than the team page. These spots get missed regularly:

Team page with photo, role and contact details
Named contacts on service and location pages
Legal or imprint pages, where a responsible person is named
Alt text and image captions
Author bylines on posts

Between a gap and a lie

Some leave the entry up because the team looks smaller without it. That's understandable and still the wrong call: an honest, small team is more convincing than a large one where two people don't actually exist.

If a replacement hasn't started yet, name the role instead of the person: "Contact for quotes" with a shared address works, and it doesn't age.

Roles instead of names, where you can

The more names on a website, the more often you have to touch it. Trust usually needs only a few faces — leadership, direct contacts — and everything else can run on function-based addresses.

That's not anonymity. It's maintenance work you don't have to do again. Set aside one review a year for photos too: a team photo with people who've since left is just as outdated as a wrong name, only harder to notice because nobody reads images.

How DustOff catches a stale team page

DustOff reads team and contact pages and flags text that reads as tied to a specific person, so an outdated name is more likely to surface at your next check instead of a customer's phone call.

It can't know someone left unless the page still names them somewhere unexpected — which is often exactly where teams forget to look.

Reads team, contact and about pages together
Flags named contacts that appear only once, in an easy-to-miss spot
Reminds you on a schedule, not just after a complaint

Häufige Fragen

Do I need to update the team page immediately when someone leaves?: At the latest, on their last working day. The simplest fix is adding the website to the offboarding checklist so it doesn't depend on chance.
What should I do with the departing person's email address?: Forward it to a shared address for a transition period, then shut it down. An address that quietly leads nowhere costs you enquiries.
Should names appear on the website at all?: Yes for direct contacts — that builds trust. Everywhere else, roles and function addresses are easier to maintain.
What about old team photos?: Review them once a year, separately from the text. A photo with people who've left is just as outdated as a wrong name, just harder to spot.
How do I handle a vacant role while hiring for it?: Name the function instead of a person, with a shared address. It reads as accurate today and won't need changing again once someone starts.
What about photos of offices or vehicles after a move?: Treat them the same as a team photo. A picture of the old location or an old vehicle confuses visitors who show up expecting to recognise the place.
Who should be told when a team page needs updating?: Whoever owns editing access, named specifically — not "the office" in general. A named owner is the difference between a same-day fix and a months-long gap.