Auto-Generated Author Archives Are Diluting Your Blog Authority

When a thin author or tag archive ranks for a query your article should own, “diluting authority” is the industry’s name for the problem. The measurable harm is narrower and easier to act on: a page of excerpts is taking the search result that belongs to the article it links to. Keep generic author and tag archives out of the index, keep purpose-built author pages in it, take the archives out of your sitemap, and confirm the result in Search Console.

Why archives compete with your articles

Two features can make an archive a candidate for your article’s query. It is well linked: if a writer has published 80 posts, their author archive receives a link from every byline, and a tag used on 40 posts collects 40 links from those posts. And it repeats the words: each archive shows excerpts from every post it lists, so it carries the same phrases the articles are written around.

For a query an article was written to answer, “all posts tagged marketing, newest first” is the weaker answer. When the listing appears instead of the article, the reader who wanted a guide lands on a list of links to guides.

Confirm it before you fix it

Don’t assume; check. In the Search Console Performance report, filter to the queries you expected an article to own and open the Pages tab. If an archive or tag URL is earning the impressions and clicks for those queries instead of the article, you have found the problem directly.

What the harm is, and what it isn’t

The harm is the one you just measured: a weaker page answering the query, and a lost landing for the article that should have answered it.

What it isn’t is a penalty. Google’s guide to its ranking systems records that its helpful content system became part of its core ranking systems in March 2024, so there is no separate penalty to appeal. The same guide says its systems work on the page level and also use site-wide signals, and it gives no ratio of thin pages to substantive ones. Keeping low-value listing pages out of the index is sound housekeeping; don’t promise a fixed ranking payoff from it.

The fix: noindex generic archives, keep real author pages

• Noindex author and tag archives. Use your SEO plugin’s or theme’s archive indexing settings, and check its current documentation for where they sit, since menus change between versions. The archives still work as navigation for readers.
• Don’t block them in robots.txt. Google’s Page indexing report help warns that a robots.txt rule will prevent noindex from being seen by Google.
• Take them out of the XML sitemap. Google’s guide to building a sitemap says to include the URLs you want to see in Google’s search results. A noindexed archive isn’t one of them.
• Judge categories one by one. A category page with a unique introduction and editorial framing can earn its place; a bare list of every post in a catch-all category can’t.

The distinction that matters is between an auto-generated archive and a real author page. A real author page is written by hand: a bio, stated credentials, relevant experience, links to external profiles, and a curated selection of the writer’s best work. Google’s guidance on creating helpful, reliable, people-first content asks whether bylines lead to further information about the author, and it says E-E-A-T itself isn’t a specific ranking factor. A good author page does that job for readers; it isn’t a ranking switch.

Control it author by author

You don’t have to choose between indexing every archive and none. If your plugin or theme allows per-author settings, index hand-built pages for the authors whose names people search for, such as a staff expert, and keep the generic archives for occasional contributors out of the index. A freelancer who wrote two posts doesn’t need a search-visible archive.

Measure: a falling indexed count is the goal

After the noindex rules are live, watch the Search Console Page indexing report. As Google recrawls the archives, they should move to the “URL marked ‘noindex'” reason. That is the correct end state, not an error: the report’s help says it’s fine for a URL not to be indexed for the right reasons, and names a noindex tag on the page as one of them. Your total indexed count will fall, and that fall is the point.

• Spot-check a sample with the URL Inspection tool to confirm the right URLs moved.
• Leave the navigation alone. Bylines, tag links and archive links can stay; noindex controls whether the archive appears in results, not whether readers can use it.
• Let recrawling happen on its own schedule. Google’s guide on asking Google to recrawl URLs notes a quota for individual URL requests, so requesting hundreds of archive URLs one by one isn’t practical.

Frequently asked questions

Should I delete author and tag archives instead of noindexing them?

No. Deleting them breaks navigation and “more from this author” modules, and any links pointing at them would need redirects. Noindex keeps the pages working for readers while keeping them out of search results.

Will removing archives from the index hurt the articles they link to?

The articles keep their other links from the site: bylines, related posts and category pages. The noindex only decides whether the archive itself appears in results, so the article is left to answer its own query.