# What happens to WordPress author pages after migration? > When you migrate off WordPress, you decide about author pages based on whether real, named authors matter to your site, because author archives can carry genuine E-E-A-T value or can be redundant clutter, depending on the site. If you publish under real experts, keep the author pages: rebuild them on the new site with the byline, a real bio, and Person schema, and 301 the old /author/ URLs to the new ones so the authority and any links transfer. If you are effectively a single-author or brand blog where the author archive just duplicates the blog index, it is cleaner to 301 those /author/ URLs to your about page or blog index rather than maintain a thin archive. Either way you handle the URLs deliberately so nothing 404s. WPBuildAI rebuilds author pages with bylines and Person schema where they add authority, and maps every old /author/ URL to a verified 301, so your author signals and links survive the move. Source: https://wpbuildai.com/what-happens-to-author-pages-after-migration/ By lawrence-arya ยท 2026-06-07 --- When you migrate off WordPress, you decide about author pages based on whether real, named authors matter to your site, because author archives can carry genuine E-E-A-T value or can be redundant clutter, depending on the site. If you publish under real experts, keep the author pages: rebuild them on the new site with the byline, a real bio, and Person schema, and 301 the old /author/ URLs to the new ones so the authority and any links transfer. If you are effectively a single-author or brand blog where the author archive just duplicates the blog index, it is cleaner to 301 those /author/ URLs to your about page or blog index rather than maintain a thin archive. Either way you handle the URLs deliberately so nothing 404s. WPBuildAI rebuilds author pages with bylines and Person schema where they add authority, and maps every old /author/ URL to a verified 301, so your author signals and links survive the move. ## Author pages are an E-E-A-T signal, when the author is real The reason author pages are worth a decision is that they can carry authority. When your content is published under a named expert, the author page, with a real bio, credentials, and links, is part of how Google reads the experience and expertise behind the content, which is why author markup features in Google's [Article structured data](https://developers.google.com/search/docs/appearance/structured-data/article) and why [people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) emphasizes who is behind it. That value is real only when the author is real and meaningful to the topic. So the first question in a migration is not how to move the page, but whether the author is a signal worth preserving for your site, which decides everything that follows. ## When the author archive is just clutter Honesty cuts the other way too. On many sites the author archive adds nothing: a single-author blog where /author/jane/ lists exactly the same posts as the blog index, or a brand site where posts are effectively anonymous and the "author" is an admin account. In those cases the author page is a thin, duplicate archive, much like a low-value tag page, and maintaining it on the new site is not worth the effort. The platform itself is not a ranking factor, as the [Backlinko analysis](https://backlinko.com/search-engine-ranking) shows, and neither is a redundant archive; what matters is whether the page carries a genuine signal. So for these sites the right move is to retire the archive and redirect its URLs, not to lovingly rebuild an empty page. ## Keep and rebuild the pages that carry authority For sites with real authors, rebuild the author pages properly rather than as stubs. Give each author a proper bio that states their expertise, links to their profiles, and reads like a real person, and emit Person schema tying that author to the articles they wrote, as covered in [which structured data types matter](/which-structured-data-types-matter-for-seo-and-ai). Keep the byline visible on every article, since the visible attribution is part of the signal, not just the markup. Preserve the author URLs where you can, so any authority and links transfer directly. The author data itself, names and post mappings, comes across in the content export, which overlaps with [exporting authors and posts](/export-wordpress-authors-posts-excel) and the wider [Yoast metadata export](/export-yoast-seo-data-leaving-wordpress). ## Redirect the old /author/ URLs either way Whichever path you take, the /author/ URLs need handling so none breaks. If you keep author pages, 301 each old author URL to its rebuilt page, so accumulated authority and inbound links flow to the new one, exactly as any [URL change](https://developers.google.com/search/docs/crawling-indexing/301-redirects) should be handled. If you retire the archive, 301 the /author/ URLs to your about page, which is the natural home for who-we-are context, or to the blog index. The mistake to avoid is deleting the archive and leaving the URLs to 404, since even a thin author page may have been indexed or linked. Handling the redirects deliberately, guided by [preserving your internal linking](/how-to-preserve-internal-links-when-migrating), keeps the transition clean. ## Do not collapse to an anonymous voice by accident A subtle migration risk is losing authorship without deciding to. It is easy, in a rebuild, to drop bylines and let everything become an unattributed brand voice, quietly discarding the E-E-A-T you built under named experts. If your authors are a real signal, that is a loss you would not choose on purpose, so make preserving bylines and author pages an explicit requirement of the rebuild rather than an afterthought. Conversely, if you were always effectively anonymous, do not invent authors to seem authoritative; keep it honest. The point is to decide your authorship model deliberately in the migration, not to let the rebuild default silently change who appears to have written your content. ## Steps to handle author pages in a migration 1. **Decide whether authors are a real signal** for your content, or redundant. 2. **If real:** rebuild each author page with a genuine bio and Person schema. 3. **Keep bylines visible** on every article, not just in the markup. 4. **Preserve author URLs** where possible; 301 them to the rebuilt pages if they change. 5. **If redundant:** 301 the /author/ URLs to your about page or blog index. 6. **Confirm no /author/ URL 404s** after launch. ## Worked example: preserving an expert byline Consider a health site that published under three named clinicians, whose author pages carried bios, credentials, and a handful of inbound links from professional directories. Migrating off WordPress, the team treated authorship as a real signal: each author page was rebuilt with a full bio and Person schema, the bylines stayed on every article, and the original /author/ URLs were preserved so the links and authority carried straight over. Nothing collapsed to an anonymous brand voice. The result was that the expertise signals Google had been reading, and the professional links pointing at the author pages, survived the move intact, which mattered more for a health site than almost any layout decision. ## Limitation: author pages help only genuine expertise It is honest to bound this. Author pages support E-E-A-T only when the authorship is genuine and relevant; they are not a trick that lifts thin content, and inventing authors or padding bios does nothing real and risks looking manufactured. So preserve author signals where they reflect actual expertise, and retire the archive cleanly where it does not, rather than manufacturing authority you do not have. Redirected author URLs also consolidate over several crawls rather than instantly, so give Search Console time to settle. The deciding question is always whether the author is a real signal for your content. ## Key points When you migrate off WordPress, you decide about author pages by whether real, named authors are a meaningful signal for your content. If they are, rebuild the author pages with genuine bios and Person schema, keep bylines visible on every article, preserve the URLs or 301 them to the rebuilt pages, so the E-E-A-T and links you built survive. If the archive is redundant, as on many single-author or brand sites, 301 the /author/ URLs to your about page or blog index rather than maintaining a thin duplicate. Either way, handle every /author/ URL deliberately so none 404s, and do not let the rebuild quietly collapse named authorship into an anonymous voice. Author pages help only where the expertise is real, so keep it honest. WPBuildAI rebuilds author pages with Person schema where they add authority and maps every old /author/ URL to a verified 301. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.