Author and date archives on WordPress: index or not?
Open Search Console’s Pages report on a small WordPress blog and you’ll often find pages the owner has never visited. /author/admin/. /2021/06/. /2019/. /author/admin/page/4/.
WordPress creates these archives automatically. Every author gets one. Every year, month and day with a post gets one. Nobody asked for them, but there they are, crawlable and often indexed.
So: should you keep them in Google’s index or not? My answer is it depends on whether the page does a job a visitor would want, and for most small sites, author archives can stay only if there’s more than one author, while date archives can usually go. Here’s the reasoning.
What these archives are
- Author archives (
/author/name/) list every post by one author, newest first. - Date archives (
/2024/,/2024/03/,/2024/03/18/) list every post published in that year, month or day.
Both are generated by the theme’s archive template, so they usually look like your blog page: a title, a list of excerpts, pagination.
The problem with keeping everything
On their own, these pages aren’t harmful. Google is good at ignoring duplicate lists. But they can cause small, real problems:
- Duplication. On a single-author blog, the author archive is the same list as the main blog page. Two URLs, same content.
- Thin pages. A month with one post produces an archive page with one excerpt on it. There’s nothing there for a searcher.
- Crawl waste. Every archive paginates. A few hundred posts can produce hundreds of archive URLs. On a small site this isn’t a crisis (I covered when it matters in crawl budget: does a small site need to care?), but it’s noise.
- Messy reports. They clutter the Page indexing report, so the real problems are harder to spot.
- The username leak. On many sites, the author archive URL reveals the login username, especially if it’s still
admin. That’s a security point, not an SEO one, but worth knowing.
Author archives: when to keep them
Keep author archives indexable when:
- The site has several writers, and readers might want “everything by this person”.
- The author pages are real pages. A photo, a proper bio, credentials, links to social profiles, and a list of their work. That kind of page supports trust, and it gives the byline on each post somewhere meaningful to link. I made the case in author pages and bylines: showing who writes your content.
Set them to noindex (or switch them off) when:
- There’s one author, and the archive just repeats the blog page.
- The archive is a bare list with no bio, and you don’t plan to improve it.
- Authors are generic accounts like “admin” or “editor”.
A middle path for single-author sites: switch off the author archive and make a proper About page the place your byline links to. That keeps the trust signal without the duplicate list.
Date archives: usually noindex or off
Date archives make sense for a few kinds of site: news publishers, diaries, sites where “what happened in March 2019” is a genuine way to browse. For almost everything else, nobody searches by month, and the categories already organise the content better.
So on most business sites, blogs and stores, I switch date archives off or set them to noindex. Readers lose nothing, because categories and internal links do the job. If you’re unsure how your categories should be set up, see WordPress categories and tags: an SEO-friendly setup.
How to do it
Most SEO plugins handle this with a couple of toggles.
- Yoast SEO lets you disable author archives and date archives entirely, or keep them but hide them from search results. Look in its settings for the archives section.
- Rank Math has similar options under its Titles & Meta settings, for author and date archives.
- Other plugins usually have an equivalent; it’s one of the standard settings.
There’s a difference between the two options:
- Disabling the archive usually redirects its URLs to the homepage or another page. The archive stops existing.
- Noindexing keeps the page for visitors but asks search engines to leave it out of results. Links on it can still be followed.
For a single-author blog, disabling is cleaner. For a multi-author site where you want to keep the pages but they’re not good enough to rank yet, noindex is the gentler choice. And remember the rule from robots.txt and noindex: when to use which: don’t block these URLs in robots.txt as well, or Google can’t see the noindex.
Check your sitemap too
If an archive is noindexed or disabled, it shouldn’t be in your XML sitemap. Most SEO plugins remove it automatically when you change the setting, but check. A sitemap full of noindexed URLs sends mixed signals and fills the Page indexing report with “Excluded by noindex tag” entries that you put there yourself.
What happens after
Expect the archive URLs to drop out of the index over the following weeks as Google recrawls them. You won’t lose meaningful traffic. If you want to be sure, look at the Search Console Performance report filtered to URLs containing /author/ or a year, before you make the change. If those pages earn almost no clicks, which is usual, there’s nothing to lose.
FAQ
Will noindexing author archives hurt E-E-A-T?
Not if the byline still links somewhere useful. What signals experience is the information about the author, not the archive list itself. A good About page or author page does that job.
Should I noindex category archives too?
Usually not. Categories are often the most useful archive on a site and can rank well if they have a short introduction and a sensible set of posts. Tags are a different story; they tend to multiply thin pages.
Related reading
- WordPress categories and tags: an SEO-friendly setup
- Duplicate content on WordPress: common causes and fixes
- Author pages and bylines: showing who writes your content
- Robots.txt and noindex: when to use which
Type site:yourdomain.com/author/ into Google and see what comes back. Is that a page you’d want a new reader to land on?