When a Writer Leaves: Old Posts and Author Pages

When a writer leaves, you keep their published posts, assign each one a maintainer, decide what happens to the author page, and make sure the bylines and the structured data still tell the truth. Nothing needs to be deleted by default. If you run a science newsletter with a web archive, a columnist's departure touches dozens of archive pages, tag listings and a profile page at once, and readers who arrive from search or from old emails should still find accurate, attributed work.

Setting up an author page from scratch is covered in the guide to building an author page for E-E-A-T. The question here is what happens to that page, and to the posts behind it, when the person is gone. Requests from the writer to erase personal data are outside this topic.

What a departure sets in motion

From the people side, a departure is an HR matter. From the content side, it changes ownership, links and attribution on every page the writer produced. If nobody plans for this, one of two things happens: pages stay untouched and slowly go stale, or somebody sweeps them away in a clean-up and the archive loses its most-read work.

Google's helpful, reliable, people-first content page (Opens in a new tab) says it helps readers when it is clear who created content, asks whether bylines lead to more information about the authors, and strongly encourages accurate authorship information. It also advises against deceptive authorship information. Those two expectations meet at a departure: a byline that is still true should stay, and a byline that stops being true must change.

What can go wrong in the first month

• Posts have no maintainer, so corrections wait for nobody.
• The author page remains in the active team list, implying the writer still works there.
• Structured data still names a person who is no longer shown on the page.
• Links to the author page break after a hurried deletion.
• Someone replaces the byline across many posts, crediting people who did not write them.

Who stands behind a post when its writer is gone

Separate two roles: the person who wrote the post and the person who maintains it. Maintenance can pass to an editor or a colleague. Authorship cannot, because a successor did not write the original. Google's page names made-up names and false credentials as examples of deceptive authorship information, so replacing a byline across the archive to hide a departure is the wrong move.

Table: Handover options and what each does to the byline.

The handover conversation

If you can, hold a short handover with the departing writer. Whatever sits in their head about a post will not be reachable later.

• Where are unpublished drafts, notes and interview recordings?
• Which posts depend on a particular source or on a promise to an interviewee?
• Is any correction or dispute pending?
• Which of the writer's pieces on other sites link to ours?
• Is the bio on the author page still accurate and what should change?

If the writer asks to be unlisted

A writer may ask for their name to be removed. That is an editorial decision to handle in writing: weigh who actually wrote the piece, what the writer wants and what the reader needs to be told. Do not make a byline false to satisfy a request. If the request is about erasing personal data, it follows a separate process and falls outside this topic.

Inventory the writer's footprint

Before you decide anything, list everything the writer touched. A spreadsheet is enough, and the structure in the content inventory decision matrix can serve as the base. For a newsletter, the footprint is wider than a blog's, because issues exist as emails and as archive pages.

Table: Where a departing writer's name and work appear.

Classifying each post

Current posts stay and only get a maintainer. Outdated ones follow the guide to updating old blog posts. Posts that cover the same question as another post follow the guide to merging overlapping articles with a 301 or canonical. Retiring is a decision per post, not a side effect of a departure.

Is the departure permanent

Leave of absence, a sabbatical or a move to another team can end with the writer coming back. Practical suggestion: label the departure as permanent or temporary in writing. For a temporary one, assign only a stand-in maintainer and leave the author page untouched.

The author page: keep, archive, redirect or remove

Deleting an author page throws away the links that point to it and leaves posts with a byline that goes nowhere. You have four options, and the choice depends on what else lives on the page.

1. Keep it with a note. Choose this when the writer has a body of work still on the site. Add a line such as "former contributor" and leave the post list in place.
2. Archive it. Choose this when the page should stay reachable but leave the active team listing.
3. Redirect it permanently. Choose this when the page merges into another page or has no value of its own and a related destination exists.
4. Remove it. Choose this when no sensible destination exists and the page has no remaining use.

Ask three questions in order: does the page still serve readers, does the byline still link to it, and does a fitting destination exist? The answers point to one of the four.

What a permanent redirect tells Google

The Google page on redirects (Opens in a new tab) says the 301 and 308 status codes mean a page has permanently moved to a new location. With a permanent redirect, Googlebot follows the redirect and the indexing system uses it as a signal that the target should be canonical, and the new target is shown in search results. With a temporary redirect, the source page continues to show in results. The page recommends a permanent server-side redirect when a page's address changes and says to use permanent redirects when you are sure the redirect will not be reverted.

The page says nothing about how long to keep a redirect in place. Practical suggestion: choose a destination that relates to the old page, for example a team archive, a topic page or the alumni listing, instead of sending every old address to the home page. Redirect behavior is documented by Google and can change, so check the current page.

Testing the redirect

After setting up a redirect, open the old address and confirm it reaches the new one in a single step. If a redirect already exists on the old address, collapse the chain so the old address goes straight to the final one. Confirm the response is the permanent status you intended. Add the redirect to your inventory and spot-check a sample each quarter, since site changes can break old rules.

Keeping bylines and markup in agreement

Author information lives in two places: the line readers see and the structured data. Google's Article structured data page (Opens in a new tab) says there are no required properties and that you add those that apply. For authors it asks for a link to a page that uniquely identifies the author, and for an internal profile page it recommends profile page structured data. Multiple authors go in separate author fields. Every author shown on the page should also appear in the markup, the name field should contain only the name, and Person is the type for people.

That leads to three jobs at a departure. If the author page is redirected, update the profile link in the markup. If a post passes to a new writer, change the visible byline and the markup together. If someone no longer appears on the page, they should not remain in the markup. Never put a note such as "former editor" in the name field.

Several people on one post

A post may have been written by the departed writer, edited by someone else and updated in part by a third person. Decide who counts as an author and who is a contributor, and show the other roles in a visible note. Keep the markup limited to the people presented as authors, one author field each.

Date fields

The Article page recommends ISO 8601 dates and a timezone for both the published and modified date. A change of byline alone does not change the content, so do not touch the modified date for it. Google's helpful content page asks whether you change the date of pages to make them seem fresh when the content has not substantially changed. Update the date only after a real content update.

Archive pages, tags and the sitemap

A writer's name may be built into the structure of the site without anyone noticing. Series pages, tag listings and archive filters can each carry the name as a heading or a URL fragment. After you decide about the author page, walk through each of these.

Internal links

Update internal links so that they point at the final address instead of leaning on a redirect. Readers and crawlers then skip an extra step, and your own link report stays clean.

External links you cannot edit

Other sites may link to the writer's author page or to a post. You cannot edit those links, but a permanent redirect from an old address keeps them useful by delivering readers to a related page. Where the old page stays alive, the links keep working without any redirect.

Telling readers what changed

Readers do not need to hear about every internal change. When a byline or a maintainer changes in a way that affects how much to trust a post, a one-line note builds confidence. Keep the note factual and short. It does not need to give the reason for a departure, since the reason is not information the reader needs to judge the post. Who wrote it, who updated it and when it was last checked are enough.

Emailed issues cannot be edited

Past emailed issues stay in inboxes as they were sent. Only the web archive version can change. That makes the archive page the place for a correction note or an updated byline. Practical suggestion: link emailed issues to their web version so changes reach readers who click through.

Maintaining what stays online

A handover is not a one-off decision. On the day of the departure every post has a maintainer, but a year later nobody may remember who that was. Three things keep maintenance alive: a named maintainer and a backup per post group, a review schedule, and a short list of questions to ask on each review.

Table: Maintainers by content group in a science newsletter.

Review questions

At each review ask: is the information still accurate, do the sources still open, do the links work, does the post meet today's standards, and does the byline reflect reality? The answers decide whether to leave, update, merge or retire the post.

The gaps a departure leaves

If the departing writer was the only person covering a field, the inventory shows a topic gap: how many posts exist there, which are current and which questions go unanswered. Fill the gap with a new hire, a guest expert or a widened lane for an existing writer, and check the new writer's evidence of knowledge before assigning ownership.

A decision rule for each post

Rule: if a post still answers a reader's question correctly, a departure alone is no reason to remove it. If it would have been retired anyway, retire it regardless. Apply the same logic to the author page: keep or archive it while it still connects readers to a body of work. Redirect only where a related destination exists and the page has no independent value.

Example scenario: a science newsletter's columnist leaves

Example scenario: A weekly science newsletter has five contributors and a web archive. A columnist who wrote a monthly explainer series leaves the publication.

1. The editor lists every archive page with the columnist's byline and notes its status. Some explainers are still accurate, some describe a field that has moved on, and two cover the same topic.
2. The still-accurate explainers get a maintainer: the senior editor. The columnist remains the named author on each.
3. An explainer on a fast-moving topic is updated by a staff writer. The byline remains the columnist's, with a note crediting the staff writer for the update, and the modified date changes because the content did.
4. The two overlapping explainers are compared. The weaker one is permanently redirected to the stronger one, and internal links are pointed at the final address.
5. The columnist's author page stays, now marked "former contributor" and moved from the team page to an alumni section.
6. The newsletter's structured data still names the columnist on those posts, matching the visible bylines. Nothing changes there.
7. The editor adds the departure routine to the editorial handbook.

The archive keeps its work, no byline becomes false, and no address is lost without a destination.

Announcing a departure

Tell the team first and cover ownership: which posts passed to whom, and who to ask about them. Telling readers is optional. For a widely recognized columnist, a short farewell note can be appropriate, written with the person's consent and factual.

Keeping a decision log

Record each decision with its date, reason and owner: why a redirect exists, why a page was archived, why a byline stayed. A year later, when someone asks why an old address behaves as it does, the answer sits in the log, not in somebody's memory.

Departure checklist

Checklist: work through these in order.

Day one

• Inventory of the writer's posts created.
• Interim maintainer assigned to each post.
• System access closed and drafts saved.

Week one

• Posts classified as keep, update, merge or retire.
• Author page decision made and written down.
• Byline and markup decisions recorded.

Month one

• Redirects set up and tested.
• Internal links, team pages and sitemap updated.
• Updates scheduled for posts that need them.
• Page-level trust signals reviewed with the E-E-A-T implementation checklist.

Turning the departure routine into a habit

Write the routine down: inventory, maintainer assignment, author page decision, byline and markup check, redirect test. Share it with contributors when they join, so the process is not a surprise on their last day. The editor owning that routine fits naturally within the workflow described in the writer-editor workflow guide.

Once a quarter, run a check for orphaned posts: any post whose writer is inactive and whose maintainer field is empty goes on a list. A routine like this prevents a year's worth of ownerless posts from piling up. After a real departure, review the routine itself and note which step took too long or lacked information, then fold the lessons into the next version.

Mistakes to avoid

Closing system access before the handover talk

Drafts, notes and interview recordings can vanish with the account. Hold the handover conversation first, save the material, then cut access.

Treating a temporary absence as a departure

Swapped bylines and removed author pages have to be undone when the writer returns. Label the absence in writing and assign only a stand-in maintainer.

Retiring posts only because the writer left

A departure says nothing about a post's value. Judge each post on whether it still answers a reader's question.

Skipping the decision log

Without dates, reasons and owners, nobody can explain a redirect or an archived page a year later. Write each decision down when you make it.

Frequently Asked Questions

Do a departing writer's posts have to come down?

Not automatically. A post that still helps readers stays, with a maintainer. Retiring and redirecting a post is a separate decision based on its own value.

When does a changed byline become misleading?

When the new name belongs to someone who did not write the post. Only if the new person substantially rewrote it does a change make sense. Google's helpful content page advises against deceptive authorship information.

Which status code suits a retired author page?

Google's redirect page says 301 and 308 mean a permanent move. If you are sure the page is permanently gone to another destination, use a permanent server-side redirect. With a temporary redirect, the source page continues to show in results.

Should structured data still list a writer who has left?

If the writer remains the author shown on the page, yes. Everyone presented as an author on the page should be in the markup, and only the name belongs in the name field.

Does a byline change justify a new modified date?

Only if the content changed. Google's page asks whether dates are changed to make pages seem fresh without substantial content change.

For how long should a redirect remain?

Google's redirect page makes no statement about duration. It advises using permanent redirects when you are sure they will not be reverted.

Conclusion

When a writer leaves, keep the work that still helps readers, give every post a maintainer, keep bylines truthful, decide the author page's fate on purpose and keep the markup in line with what readers see. Google's helpful content page asks for accurate authorship information, the Article page asks for each author to be entered separately, and the redirect page describes permanent moves with server-side redirects. A written routine means the next departure takes an afternoon rather than a crisis.

If you would like support with handovers and editorial processes, take a look at our content writing service.