Author archives rank as if they were the blog
Each writer has a public URL. It lists headlines and little else. It competes with the real posts. We give authors a job, or we noindex them.
WordPress SEO
WordPress SEO from senior consultants who turn search demand into rankings, traffic and revenue for your business. We start with a free audit and a 90-day plan built around your goals.
Our process
We map the posts and pages that matter this month, and fix old ?p= URLs that still leak.
We decide which author, date, category and tag archives should be indexed, and retire tags with no purpose.
We find attachment pages still in the index and close them or redirect them to their parent.
We pick one plugin to manage titles, robots settings and structured data, so nothing conflicts.
Position
A WordPress site is not one homepage and a blog. It is posts, pages, categories, tags, authors, dates, attachments, and sometimes custom types that are not products. Search intent has to show in the HTML a crawler gets. The block editor while you are logged in is not that HTML.
We start with posts and pages. Then leftover archives. Then media URLs. Then the plugin that stores titles and robots. WooCommerce stays on its own page. On-page SEO writes the heading and opening when that work is not WordPress-specific. A data factory stays on programmatic SEO. A host or domain move stays on migration SEO.
We will not index every tag because the box exists in wp-admin. We will not treat Yoast versus Rank Math as the whole program. We will not change the whole permalink pattern to chase a prettier slug. If the site is a Woo shop, open that page for the cart. Stay here for the CMS.
Compare packages if a published retainer already fits. Use WooCommerce SEO when a related service is the real job. If this page is still a guess, start with a free AI + SEO audit.
When this fits
This page fits when WordPress itself is publishing extra URLs: authors, dates, tags, attachments, or two SEO plugins. If you needed a shop pass, a title-and-opening pass, or a cutover map, start there instead.
Each writer has a public URL. It lists headlines and little else. It competes with the real posts. We give authors a job, or we noindex them.
WordPress made a page for every month and every leftover tag. Crawl is busy. The money posts are not. We write which archives may stay. The rest stay tools or stay closed.
The media library left image URLs in the index. They steal the article name. We close those paths. Shop images that rank as products still belong on WooCommerce SEO.
Yoast and Rank Math, or a second schema add-on, both speak. Titles disagree. We pick one plugin to store fields. Installing a third is not the fix.
Process
Four CMS jobs in order. Each one ends with a note you can keep in wp-admin. We do not start a Woo product map in the last step. The point is a site whose real posts stay documents, and whose leftover archives are named.
Outcome A list of live post and page URL patterns, including leaks.
Outcome An archive list editors and the plugin can follow.
Outcome A media rule: attachments out of the article index.
Outcome A plugin field rule, including what must stop publishing.
Deliverables
You leave with a post map, an archive yes-or-no, a media rule, and one plugin to store fields. You do not leave with a Woo shop pass, a programmatic factory, or a ranking date.
The CMS URLs you actually publish, including leftover ?p= paths. Dated. Last quarter's screenshot is not this map.
Categories, tags, authors, and dates. Navigation should match. An author page that only lists headlines is named.
Media URLs that must leave the index, and how they point back to the parent post. Indexing every upload is not a rule.
Which system stores titles and JSON-LD. Two graphs on one post are named and stopped.
The post pattern you will keep. A title tidy is not a reason to rewrite every slug. If a move needs a launch map, that note is a handoff to migration SEO.
Benefits
Writers can still have a bio. The public archive is a decision, not a default.
Money posts get crawl back. Empty months leave the index.
Attachment pages leave. The parent post keeps the title.
Yoast and Rank Math stop arguing. Extractors get one set of facts.
Methodology
This works when one person can edit Settings and the SEO plugin, and one person can refuse a new archive. If both are missing, we are touring the plugin directory. We are not holding a CMS.
We start with the posts that must work this month, the archives already live, and the person who can edit a permalink. If any of those is missing, we name it first.
We fetch published HTML. We do not trust the editor while you are logged in. Does this category match a real reading job? Is an author archive worth keeping?
You may rename the roles below. You may not leave plugin installs implied. An implied SEO plugin is how a site grows two title graphs overnight.
First working session
The first hour is one leftover URL that is ranking as if it were an article: an author, a date, a tag, or an attachment. It is not a tour of the WordPress plugin directory.
We pick a money post. We list every WordPress URL that reuses its title or sits next to it. Author. Date. Tag. Attachment. If two of those share one unique paragraph, we keep the post before we touch titles. If the real question is a shop, that is WooCommerce SEO. If the real question is a factory, that is programmatic SEO. If the site is mid-move, that is migration SEO.
Then we fetch published HTML, robots, and a sample of archive URLs. We compare that to Search Console. The extra rows are usually the job. A block editor that looks finished while you are logged in is not evidence.
We leave with a first list or a stop. A list names the post pattern, the archives that may stay, and who may install the next SEO plugin. A stop names what is missing: wp-admin, an editor owner, or a stack that is actually Woo. Both are outcomes. A plugin roundup is not.
AI search
Honest post HTML can help later extraction. This page cannot sell AI Overviews, a chat mention, or LLM visibility as a score.
People ask whether Yoast, Rank Math, or another add-on will land articles in Google AI Overviews (AIO). If author archives and attachments have exploded, generative search has too many near copies, or nothing honest to lift. That is ours to tidy. A program across search UIs is AI SEO.
AI search needs a page it can fetch. A block that only renders when you are logged in does not help. Nobody can guarantee a spot in AI Overviews, but clear pages improve your chances.
We check brand and topic names in the published HTML. That is entity optimization as a CMS input.
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. Unique post HTML can make an article look real.
Schema
JSON-LD helps a machine read a post the page already states. This work stops two plugins from injecting two graphs. Schema supports the work; it is not the whole job.
If two SEO plugins both inject Article or WebPage markup, we pick one. Valid types still need facts that match the HTML.
We refuse FAQ blocks that exist only to host more terms. A real question can live on the post.
Markup will not force generative search to cite the article. Good markup makes you eligible; it cannot buy a mention.
Who we work with
Someone has to refuse the next archive. We work with that person. We do not replace them with a second WordPress retainer.
Ships permalinks, archive settings, and plugin fields. Rechecks after a theme update.
Write unique posts. Hold the archive list when a campaign wants a tag for every synonym.
Can keep going once one plugin stores titles. If they try to run this as a shop, two jobs collide. The cart belongs on WooCommerce SEO.
FAQ
WooCommerce SEO owns the shop: product slugs, the shop page, and plugins that publish store URLs. This page owns the CMS: posts, pages, author and date archives, leftover attachments, and plugin fields that store titles. A product permalink is that buy. A blog permalink lecture is this one.
No. A category people actually read can be a page. An author archive that only lists headlines usually should not. Date archives and empty tags are leftovers. We write a yes or no list. We do not index every archive WordPress can make.
No. Plugin fields that store title and robots are WordPress objects. What the live heading and opening should say is on-page SEO. We will not force a plugin move as a ranking product. We will name which plugin may speak for posts and pages.
When you are moving hosts, domains, or the whole URL pattern with an old-to-new map and a launch hour, that is migration SEO. Tuning post permalinks and noindexing tag archives without a cutover stays here. Do not mix those jobs.
No. Honest post HTML can help AI search later. It does not buy a place in Google AI Overviews (AIO), a generative-search mention, or an LLM visibility score.
In this wp-admin
Send the site URL, a wp-admin login we can use, and the SEO plugin already on. We will say if the leak is authors, dates, tags, leftover media, or two plugins speaking at once. Then we name the next setting to change.