02 / WORDPRESS SEO
Make the publishing system answer to the site architecture.
WordPress can publish pages, posts, archives, taxonomies and custom content types through several layers of theme and plugin logic. SEO management decides which outputs belong in the search system and which implementation layer should control them.
The visible page is the product of several authorities.
Editors see a title and body field. Search engines may see output assembled by a content type, taxonomy, template hierarchy, theme component, SEO plugin and cache. A correct change in the editor can be overwritten or contradicted elsewhere in that chain.
The first management decision is therefore not “which plugin setting should change?” It is which public page should exist, what job it owns, and which layer has durable control over the required output. Plugin configuration follows that model; it cannot substitute for it.
Sought is independent and is not affiliated with or endorsed by WordPress.
PUBLIC OUTPUT INVENTORY
Inspect what WordPress can publish before deciding what it should publish.
| Layer | What it can change | Management decision |
|---|---|---|
| Content types | Single URLs, archives, fields, editing workflows and rewrite rules. | Which types represent real reader jobs and which are implementation conveniences only? |
| Taxonomies | Category, tag and custom-term archives with their own crawl paths. | Which classifications help discovery enough to justify public landing pages? |
| Templates | Rendered headings, navigation, content order, metadata hooks and structured data. | Which decisions belong globally to a page type, and which require editorial control? |
| Plugins | Canonicals, robots directives, sitemap providers, redirects and schema output. | Which plugin owns each signal, and where are duplicate or conflicting outputs produced? |
| Delivery stack | Caching, rendering, headers and deployment timing. | Does the public response contain the change that the editor or plugin claims to have made? |
Control follows the page job.
- Inventory the rendered routes
Include singular content, archives, search paths, feeds, attachments and plugin-generated surfaces that can be discovered.
- Assign or remove public jobs
Keep an output only when a reader or search system needs it and its role does not duplicate a stronger page.
- Name the producing layer
Trace the template, hook, plugin or server behaviour that controls the live response.
- Change the causal layer
Correct the source of the output so an editor action or later update does not silently recreate the problem.
- Verify the response
Inspect HTML, status, canonical, robots instruction, sitemap membership and internal links after release.
Architecture still has to become a useful page.
A clean template hierarchy cannot decide whether a page satisfies a real search intent. The on-page SEO process establishes page ownership and the visible evidence needed to support it.
Sites with continuing editorial, plugin and deployment change may need ongoing SEO management so those layers remain reconciled after the initial correction.
Primary reference points
NEXT STEP
Bring the WordPress surface, not a plugin shopping list.
Share the site, the business priority and the routes or publishing behaviour that need one coherent decision.