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 to Clean CMS URLs That Are Not a Shop
WordPress publishes posts, pages, authors, dates, tags, and leftover media URLs. Plugins store titles and robots on top. We decide which of those are real documents. We stop author archives and attachment pages from ranking as the article. The shop stays on WooCommerce SEO.
- Post
- Author
- Media
- Field
Position
WordPress publishes leftover URLs. This page names which may stay.
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.
A WooCommerce shop
Product slugs, the shop page, and store plugins belong on WooCommerce SEO. Posts, pages, and leftover CMS archives stay here. An image that ranks as a product is that page. An image that ranks as a blog post is this one.
Open WooCommerce SEOThe heading and opening on any URL
On-page SEO writes the job, the promise, and the opening on a URL, stack aside. Plugin fields that store those strings in WordPress stay here. Open that page when the work is the document, not the CMS.
Open on-page SEOA URL factory
Programmatic SEO owns data rows that become URLs with prune rules. A custom post type can be the pipe. The factory rules are not this page. Permalink accidents without a dataset stay here.
Open programmatic SEOA cutover with a map
Migration SEO owns a host, domain, or URL-pattern move with launch-hour checks. Tuning permalinks and noindexing archives without that map stays here.
Open migration SEOWe 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.
When this fits
When leftover archives outnumber real posts
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.
Date archives and empty tags filled Search Console
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.
Attachment pages reuse the post title
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.
Two plugins print two graphs on the same post
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
Posts first. Then leftover WordPress URLs.
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.
-
Post
We map posts and pages that must work this month. Permalinks already live. Query IDs that still leak as ?p=. Keyword targeting is one job per money post or page. A logged-in Gutenberg preview is not a fetch.
Outcome A list of live post and page URL patterns, including leaks.
-
Author
We write yes or no for author, date, category, and tag archives. Topical relevance is the test: does this archive match a real reading job, or is it a list WordPress generated? A tag that exists only to complete a box is named.
Outcome An archive list editors and the plugin can follow.
-
Media
We find attachment URLs that still index. They often reuse the post title. We close them or send them to a parent. Keyword density on an image page is not a WordPress score. Shop media still hands to WooCommerce SEO when the URL is commerce.
Outcome A media rule: attachments out of the article index.
-
Field
We name which plugin may store titles, robots, and JSON-LD. Semantic keywords belong in the post body, not as a second plugin. One speaker per path. Coverage on posts and the yes-list archives is the watch.
Outcome A plugin field rule, including what must stop publishing.
Deliverables
What wp-admin can keep after we leave
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.
Post and page map
The CMS URLs you actually publish, including leftover ?p= paths. Dated. Last quarter's screenshot is not this map.
Archive yes-or-no
Categories, tags, authors, and dates. Navigation should match. An author page that only lists headlines is named.
Attachment rule
Media URLs that must leave the index, and how they point back to the parent post. Indexing every upload is not a rule.
Plugin speaker
Which system stores titles and JSON-LD. Two graphs on one post are named and stopped.
Permalink note
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
What a new plugin should not undo
Author archives stop competing with posts
Writers can still have a bio. The public archive is a decision, not a default.
Date and tag leftovers stop filling crawl
Money posts get crawl back. Empty months leave the index.
Image URLs stop ranking as articles
Attachment pages leave. The parent post keeps the title.
One plugin stores the title
Yoast and Rank Math stop arguing. Extractors get one set of facts.
Methodology
Who can change a post permalink
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.
- WordPress SEO lead SEOConsultants.ai writes the post map, the archive list, and the plugin speaker. We do not become your WordPress agency because the plugin list was long.
- Whoever owns wp-admin Can edit permalinks, archives, and plugins, and can recheck after a theme update. A locked admin with no editor is a finding.
- Editors Keep unique posts. Do not mint a tag for every synonym. A category nobody will maintain is a candidate to close.
- Whoever installs plugins Stops a second SEO plugin from storing titles. They do not need to write PHP for that.
- Leadership Funds archive cleanup or refuses another SEO plugin this period. An unread coverage sample is not a failure of this page. A ranking promise would be.
First working session
Start with the archive that is not a post
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
A WordPress SEO plugin is not an AI Overview
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. If the kept post already tells the truth and models still invent pages, that is an AI search audit. A program across search UIs is AI SEO.
The post has to print in the first HTML
AI search needs a page it can fetch. A block that only renders when you are logged in does not help. We do not sell Overview presence.
The name on the post should match the thing you publish
We check brand and topic names in the published HTML. That is entity optimization as a CMS input. It is not a Knowledge Graph project from this page.
Measuring model answers is another URL
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. Unique post HTML can make an article look real. It does not sample answers.
Schema
One Article block. One plugin.
JSON-LD helps a machine read a post the page already states. This work stops two plugins from injecting two graphs. It is not a schema campaign as the whole job.
Name the speaker
If two SEO plugins both inject Article or WebPage markup, we pick one. Valid types still need facts that match the HTML.
No fake FAQ on a tag archive
We refuse FAQ blocks that exist only to host more terms. A real question can live on the post. Stuffing is not a module.
Extra fields do not buy a citation
Markup will not force generative search to cite the article. Eligibility is not a purchased mention.
Who we work with
The person who can edit Settings and the SEO plugin
Someone has to refuse the next archive. We work with that person. We do not replace them with a second WordPress retainer.
wp-admin owner
Ships permalinks, archive settings, and plugin fields. Rechecks after a theme update.
Editors
Write unique posts. Hold the archive list when a campaign wants a tag for every synonym.
Whoever already runs plugins
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.
Questions
Frequently asked questions
How is this different from WooCommerce SEO?
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.
Should every category, tag, author, and date archive stay indexed?
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.
Is switching Yoast for Rank Math the same as on-page SEO?
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 does a permalink change become migration SEO?
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.
Will a schema plugin get our posts into AI Overviews?
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. If the articles already tell the truth and a model still invents a page you do not publish, that work sits on an AI search audit and on LLM SEO.
In this wp-admin
Are author archives ranking as your articles?
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.
- Posts and pages with a job
- Author and date archives with a yes or no
- Attachment URLs out of the article index
- One plugin storing titles
Posts kept. Leftover archives named. One plugin field.