WordPress author archive pages in Google: keep or kill?

WordPress author archive pages are the pages at /author/yourname/, and every WordPress site has them whether you asked for them or not. On a single author blog they are an exact duplicate of your blog index with a different URL. On a multi author site they can be genuinely useful. The advice online treats these two situations as one, which is why so many people end up with the wrong setting.

There is a second thing going on here too, which is that “disable author archives” in both major SEO plugins does not do what the phrase suggests. I will get to that, because it is the part that trips people up in an audit.

What is an author archive page?

WordPress generates one automatically for every user who has published a post. The URL is your author base plus the user’s slug, so /author/shahid/ by default. It lists that author’s posts, newest first, paginated.

On a one person site, that list is the same list as /blog/. Same posts, same order, different URL. Google sees two URLs with near-identical content, picks one, and reports the other under a duplicate status. That is textbook index bloat, just with a friendlier name attached.

So should I remove them?

It depends on one thing only: does the author page carry information the blog index does not?

What “disable author archives” actually does

This is the bit worth knowing before you flip the switch in an audit.

Neither plugin deletes the page. Neither returns a 404. Both issue a 301 redirect from the author archive URL to your homepage. Yoast additionally removes author URLs from the XML sitemap. Rank Math offers a separate option to rename the author base from /author/ to something else, which is a different feature and does not remove anything.

So after you disable, the URL still resolves, it just resolves somewhere else. That has three consequences people miss:

• Existing links to the author page still work, which is good, and they now pass to the homepage rather than nowhere.
• Search Console will report those URLs as “Page with redirect”, not as removed. If you are watching the page indexing report expecting a drop in errors, you will see a shuffle between statuses instead.
• Anything in your theme that links to the author archive now links to a redirect. Most themes put the byline link there. That is a permanent internal 301, which works, but it is untidy. If you are already thinking about 301 versus 308 redirects, this is the same family of decision.

If you would rather keep the URL live and simply keep it out of the index, use noindex instead of disable. That is the right answer for a guest author with one article, where the byline needs a destination but the page itself has nothing to offer a searcher.

The REST API thing nobody gets right

You will read, repeatedly, that author archives leak your WordPress usernames and that the REST API at /wp-json/wp/v2/users makes it worse by exposing login names to anyone. The second half of that is wrong, and I checked the documentation directly rather than repeat it.

In the WordPress REST API user schema, the username field is listed as Context: edit. So is email. So are first_name and last_name. Edit context requires authentication. An anonymous request does not get any of them.

What an anonymous request does get is id, name, which is the display name, and url. Those are the same things a visitor can read off the byline of any post. The endpoint is a convenience, not a leak.

The real hardening question is separate and older: if your display name is identical to your login name, then your login name is on every post, archive page or not. Change the display name. Disabling author archives does nothing for that.

What a good author archive looks like

If you are keeping them, they need to earn the index slot. A page that is a list of post titles and nothing else will sit in “Crawled, currently not indexed” and stay there, and no amount of requesting indexing will change that.

What makes the difference is the author biography field, which almost every WordPress install leaves empty. Fill it with something a reader would actually use: what this person does, how long they have done it, where else they publish, their credentials. Then make sure the theme renders it on the archive page, because some themes do not.

That is also the only version of this page that helps with experience and expertise signals. An empty author archive is a duplicate. A real one is a credential page.

The order I do this in

On a WordPress audit, author archives take about five minutes and the sequence matters.

1. Count the author accounts that have published. One means disable, and the decision is made.
2. If it is more than one, open two of the archives. Empty bio, no photo, nothing but a list of titles? Disable, or fill the bios, but do not leave them as they are.
3. Check the sitemap after changing anything. Yoast strips author URLs on disable, Rank Math handles it separately.
4. Check the byline links in the theme. If they now point at a redirect, point them somewhere real or leave them and accept the hop.

None of this is a big lever. It is worth doing because it is quick and it removes a whole class of duplicate from the index, in the same way that tidying faceted navigation does. On a small site it will not move crawl budget at all, and anyone telling you otherwise is selling something.

Sources

• Users, REST API Handbook, WordPress Developer Resources. The user schema showing username, email, first_name and last_name as edit context only, and id, name and url as publicly readable.
• Author archives, Yoast SEO, Yoast. The disable setting’s redirect behaviour and the removal of author URLs from the sitemap.
• Titles and Meta settings, Rank Math, Rank Math. The author archive disable option, its redirect to the homepage, and the separate author base rename option.
• Page indexing report, Google Search Console Help. The “Page with redirect” status these URLs move into.