Oct 17, 2025·6 min read

Remove old conference bios after you switch companies

Learn how to remove old conference bios with a simple outreach process for event pages that still show the wrong employer, title, or contact details.

Remove old conference bios after you switch companies

Why this happens after a job change

Conference pages stay online much longer than most people expect. A one-day event can leave behind a speaker page, an agenda page, a PDF program, and search result snippets that stick around for years. If you've changed jobs, those pages can still show your old company, title, headshot, and work email.

Most of the time, the reason is simple. Event teams reuse old material. The bio you submitted once may have been copied into a form, a spreadsheet, a PDF, and a website draft. Later, when the organizer runs another event or republishes past sessions, someone pastes the old version without checking whether your role changed.

Sometimes no one is actively maintaining the page anymore. The event is over, the marketing contact left, or the site was moved into an archive that rarely gets reviewed. The page doesn't disappear. It just sits there with outdated details.

Search engines make the problem more annoying. Even after a page is updated, search results can keep showing an older title or preview for a while. If the page is never updated, people searching your name, old company, or talk title can keep finding the wrong information.

That creates more confusion than people think. Recruiters, clients, and reporters may assume you still work at your previous company. An old work email can send messages to an inbox you no longer control, or back to a company you no longer work for. People may also tie your current views to an affiliation that is no longer yours.

The good news is that this is usually a cleanup issue, not a fight. Most organizers are not trying to misrepresent you. They're working from old copy, and no one has flagged it yet. Once you understand why it happens, the fix gets much easier.

What to collect before outreach

Before you send a request, put the facts in one place. A messy message slows everything down. A clear one often gets handled in a single reply.

Start by listing every page that still shows the old version. Don't stop at the main speaker page. Check session pages, archived event pages, PDF programs, author profiles, and anything else tied to the event.

Then pull out the exact text that needs to change. That saves the organizer from hunting through the page and guessing what you mean.

A simple prep list is enough:

  • The page title or page name where the old bio appears
  • The sentence or lines that are wrong
  • One current bio you can paste into every request
  • The email address you want listed now, if any
  • A screenshot of each page before anything changes

Your replacement bio should be short and easy to drop in. Two to four sentences is usually plenty. If you changed jobs recently, keep it current and neutral: your role, your company, and maybe one line about your work now. Extra detail only gives the editor more chances to get something wrong.

Be clear about contact details too. If an old work email is still on the page, say whether you want it replaced or removed with no substitute. That sounds minor, but it matters. Many teams will update the bio and miss the email line unless you call it out directly.

Screenshots are worth taking. Event pages change, and some sites use mirrored pages or cached copies. If the text disappears for a day and then comes back, you'll have a record of what was posted.

Good outreach starts here. If you do the prep well, the actual request can stay short.

Who to contact on the event site

Start with the people who can edit the page, not the people who appeared on it. The best contact is usually the event team or whoever manages the site.

The footer is often the fastest place to check. Many event pages list an organizer email, support address, or short contact note at the bottom. It may look generic, but that inbox often reaches the person who handles website fixes.

If the footer doesn't help, check the speaker page, agenda page, and about page for titles such as event manager, program team, conference coordinator, or webmaster. The title matters more than the department name. A program team may own the speaker page, while a webmaster may only make the edit after someone approves it.

A simple search order helps:

  1. Check the page footer for organizer or support details.
  2. Look on the speaker, agenda, and about pages for the event manager or program team.
  3. Use the contact form if no direct email appears.
  4. If you're still unsure, send one short note asking which inbox handles website edits.

A contact form is fine when there is no public email. It may feel slower, but many event sites route form messages into a support system that gets seen faster than a random personal inbox. Keep the note short so it doesn't look like spam.

Try not to start with ticketing, sponsors, or media contacts unless the event is very small. They may want to help, but they usually aren't the ones updating archived speaker pages.

If the event is older, the live page may now be owned by the organizer's parent company, trade group, or association. In that case, the parent team is often the right place to ask.

How to ask for the change

Keep the message short and easy to process. The person reading it may be an event assistant, a volunteer, or someone working through a crowded inbox. If they can understand the problem in 20 seconds, your odds go up.

Start with the event name and year in the first line. "Regarding my speaker bio on Tech Summit 2023" is much better than "Please update my profile." It tells them where to look before they even open the page.

Then point to the exact page and the exact text that needs to change. Don't make them search the whole site. If the page says you still work at your old company, quote that line in your email. Do the same for an old work email, phone number, or job title.

A good request includes five things: the event name and year, the page where the bio appears, the outdated text copied exactly as it appears now, the full replacement text, and a short ask to confirm once the edit is live.

Be plain about what is wrong. You do not need to tell the whole story of your job change. One sentence is enough: "My affiliation and contact details on this page are no longer current."

Make the fix easy to copy. Paste the new bio directly into the message, even if the edit feels small. If they only need to replace one line, give them that line. If the whole bio needs to change, send the full replacement version so they don't have to piece it together.

Close with a light, direct ask. "Please reply when the update is live" works well. It's polite, specific, and gives you a clear next step if nothing changes after a few days.

A simple message you can adapt

Keep relistings from returning
Ongoing monitoring catches your data if it shows up again later.

A short, copy-ready note usually gets the fastest result. Point to the exact page, paste the outdated line, and put the corrected text right below it. If the page still shows an old work email or other contact details, ask for those to be removed too. Don't assume they'll catch that part on their own.

Subject: Speaker bio update request for [Event name] [Year]

My speaker bio on your site is out of date.

The page title is: [Exact page title]
Year: [Year]

Old text:
"[Paste the line exactly as it appears now]"

Please change it to:
"[Paste the corrected line]"

Please also remove these old contact details if they appear on the page:
- [Old work email]
- [Old company phone number]
- [Any old company contact form or profile reference]

My name: [Your full name]
Current role: [Your current role]
Current company: [Your current company]

Thank you,
[Your full name]

A few small choices make this work better. Paste the old line exactly, even if it is wrong in more than one place. That saves the editor from hunting through the page. If you changed companies recently, keep the correction tight. One sentence is often enough.

If you don't want any public contact info on the page, say that plainly. For example: "Please remove the old work email and do not replace it with a new public email." That's much better than leaving room for guesswork.

A realistic example

Maya spoke at a 2022 conference while she worked at North Peak Health. Two years later, her speaker page was still live. It showed her old company, old title, and old work email.

That sounds minor until people start using it. Old event pages still rank in search, and many people will use whatever contact details they find first. In Maya's case, messages were still going to an inbox she no longer used.

She kept the fix small. First, she saved the page address and copied the outdated text into a note. Then she wrote a replacement bio that was only two sentences long.

Her replacement text looked like this:

"Maya Chen is a product leader focused on patient experience and digital care. She now works at Riverbend Labs and speaks about practical ways teams can improve online care services."

She emailed the program team because they were the people most likely to own the speaker pages. Her note was short: she pointed out the old affiliation, asked them to remove the old work email, and pasted the new bio under the request. She did not ask them to add a new public email. That was a good call. Event pages get scraped all the time.

No one replied that day. That's normal with older conference sites. A week later, Maya sent one follow-up in the same thread: "Checking in on this request in case it got buried. Thanks for your help."

Two days later, the page was fixed. Her old company was gone, the old work email was removed, and the updated bio was live.

That's how most of these requests work when you make them easy to act on. Keep it short, give them the exact text to paste, and follow up once after a week if nothing happens.

Mistakes that slow things down

Skip manual broker requests
Let Remove.dev send removal requests so you do not chase sites one by one.

Most delays start with the request itself. Event teams are busy, and many archived pages sit on old website systems. If your note makes them guess what to change, it drops to the bottom of the pile.

The biggest problem is vagueness. "Please update my info" sounds simple, but it creates extra work. Now the other person has to find the page, decide what is outdated, figure out what should replace it, and wonder whether they're allowed to edit all of it.

Missing replacement text is another common mistake. If the page lists your former company and an old email, paste the exact wording you want instead. Don't make the editor assemble a new bio from scraps.

People also lose time by contacting the wrong team. Your former employer usually doesn't control the event page. The organizer or site manager does.

Another slowdown is bundling too much into one message. If your real issue is one paragraph and one email address, don't turn the request into a full page redesign. A new headshot, session title change, and logo swap can wait unless they belong to the same quick fix.

Using more than one bio version causes its own mess. If you send three options in the same thread, the wrong one often goes live. Pick one final version and stick to it.

A small example shows the difference. "My speaker page is outdated" leaves all the work to the editor. "Please replace 'Head of Product at Northpeak' with 'Independent consultant' and remove '[email protected]'" is a two-minute task.

Polite is good. Clear is better. One page, one change set, one final bio version.

A quick check after the update

See what still appears
Find exposed personal details across broker sites before they keep spreading.

A page can look fixed at first glance and still leave old details behind. Before you mark the job done, check it the way a stranger would.

Run through these four checks:

  • Make sure your old company name is gone everywhere, not just in the main bio. It often survives in the page headline, image caption, or browser title.
  • Check that old email addresses and phone numbers are gone from sidebars, speaker cards, and contact sections.
  • Open any PDF agenda, brochure, speaker packet, or media kit tied to the event. These files are easy to miss and can still appear in search.
  • Search your name again after a few days with the old company, the event name, and the old work email.

This matters because search results don't refresh at the same speed. Sometimes the live page is clean, but the search snippet still shows an old line for a while.

PDFs are a common miss. An event team may update your speaker page and forget the downloadable agenda. If someone searches your name and finds the PDF first, the bad information is still doing its job.

If something is still wrong, reply in the same thread and keep the follow-up narrow. Mention the exact page or file name, paste the outdated line, and ask for that item only. A specific follow-up gets handled faster than a broad "it still looks wrong" message.

Once each page is confirmed, note the date. If the same site brings the old bio back later, you'll know exactly what changed.

What to do next

Once one page is fixed, don't assume the problem is over. Old speaker pages stay online for years, and the same outdated bio often gets copied from one event site to another.

A simple tracker helps. A note, spreadsheet, or task app is enough if it records the event name, page title, what is outdated, who you contacted, when you contacted them, and when to follow up.

That makes patterns easier to spot. If the same old work email keeps showing up, you'll catch it quickly instead of finding it again by accident months later.

For future events, ask one direct question before your talk page goes live: "Which bio, title, company, and contact details are you planning to publish?" Many mistakes happen because someone pastes an older version without checking. A short note before publication can save a lot of cleanup later.

It's also worth rechecking older event pages every few months. You don't need a huge audit. Just review the events that rank well for your name and see whether anything has been copied, relisted, or left behind.

Conference pages are only part of the problem. If your old work email, phone number, or employer history also appears on data broker sites, Remove.dev can help by finding those listings, sending removal requests across more than 500 brokers, and monitoring for relistings after your data is removed.

The real goal isn't to chase every page forever. It's to keep one clean record, check it on a schedule you'll actually keep, and stop old details from spreading again.

FAQ

Why is my old conference bio still online after I changed jobs?

Because event pages often outlive the event itself. Your bio may have been copied into a speaker page, agenda page, PDF, or archive, and no one went back to check it after you changed jobs.

What should I collect before I contact the event team?

Pull together the exact page URLs, the outdated lines, one final replacement bio, and any old contact details you want removed. Screenshots help too, especially if the page changes and then reappears later.

Who should I contact first on the event site?

Start with the organizer, program team, or site contact listed in the footer, speaker page, or about page. If there is no direct email, the contact form is usually fine.

What should I say in my update request?

Keep it brief and specific. Name the event and year, point to the exact page, quote the wrong text, paste the corrected text, and ask them to confirm when the update is live.

Should I replace my old work email with a new public email?

Usually no. If you do not want a new public email on the page, say that clearly and ask them to remove the old one without replacing it.

What if no one replies to my first message?

Wait about a week, then send one short follow-up in the same thread. A polite check-in is often enough for older event sites that are not watched every day.

Do I need to check PDFs and archived event pages too?

Yes, if they exist. Old details often stay in downloadable agendas, brochures, or archived session pages even after the main speaker page is fixed.

Why does Google still show my old company after the page was updated?

Search results can lag behind the live page. Even after the site is corrected, the old title or preview may stick around for a while until search engines refresh it.

What mistakes make these requests take longer?

Vague messages are the biggest problem. If you do not paste the exact text to remove and the exact text to use instead, the editor has to guess, and that slows everything down.

Can Remove.dev help if my old work details also show up on data broker sites?

Yes, for the broker side of the problem. Remove.dev finds your personal data on more than 500 data brokers, sends removal requests automatically, and keeps checking for re-listings so the same details do not keep coming back.