In short: Once the page is reachable and readable, WordPress sites lose answers in four specific places, and all four come from how the platform is usually used rather than from the platform.
Builder markup that buries the sentence, archives that compete with the page you meant, plugin schema that disagrees with what a reader sees, and an author line that leads nowhere.
Each is an editing job rather than a development one, which is why they survive: nobody owns them.
The Sentence Is There And Nobody Can Find It
The most common failure on an otherwise healthy WordPress site.
Builder layouts put a hero, a feature grid and three testimonial cards above the paragraph that answers the question. Everything is in the HTML, so the fetch test passes, and the passage a system would lift is a testimonial.
The fix is the one from Optimizing for AI Discovery applied to a layout rather than to prose: under each heading, the first text in document order should be the answer to that heading. Design order and source order are set separately in most builders, and the second one is the one that counts.
Archives Competing With The Page You Meant
WordPress generates a page for every category, tag, author and date, and most of them are a list of excerpts with no answer on them.
These are not harmful by default. They become harmful when a tag archive covers the same ground as the page you actually want retrieved, because then two thin pages and one good page all describe the same thing and nothing marks which is the answer.
Look at your own site with fresh eyes: how many tags exist, how many have fewer than three posts, and how many duplicate a category. The count is usually the finding, and the answer is to remove the thin ones rather than to rewrite them.
Schema That Disagrees With The Page
Plugins generate structured data from fields, and fields drift from what the page says.
An Organization block naming the company one way while the footer names it another, an author entry for an account called "admin", a date in markup that does not match the date on the page: each of these documents an inconsistency in a machine-readable format, which is worse than having nothing, because it is the version a parser reads first.
Markup records consistency rather than creating it. Fix the name, the byline and the date on the page, then let the plugin describe what is now true. Done in that order it earns its keep. Done first it is a tidy description of a mess, which is the subject of The Mistakes Competence Causes.
An Author Line That Leads Nowhere
WordPress prints an author on every post by default, and on most sites that author is a shared account or a first name with an empty profile.
A byline exists to let a system judge whether a claim has somebody behind it. A name with no biography, no other work and no identity that resolves anywhere gives it nothing to judge, which is close to the same position as having no byline at all.
This is a twenty minute job per author: a real name, a biography that says what they do and why they would know, and a link to something outside the site that is recognisably the same person.
What To Do With Old Posts
A WordPress site accumulates, and most of the accumulation is not worth fixing.
Take the twenty pages that carry your commercial questions and fix those. For the rest, decide only whether each one is still true. An honest old date on a stable explainer is fine. A refreshed date on a page nobody changed is detectable, teaches systems that your dates are unreliable, and unreliable dates are worse than old ones.
Bulk updating modified dates is the one action to avoid entirely. It is offered by several plugins, it changes nothing about the content, and it costs you the ability to make a freshness claim that anybody believes later.
Key Takeaways
- Builder layouts routinely put the answer below three other blocks. Source order decides what gets lifted, and it is set separately from design order.
- Thin tag and category archives compete with the page you meant to be retrieved. Count them; the count is usually the finding.
- Plugin schema that disagrees with the visible page documents the inconsistency rather than fixing it.
- A byline with no biography and no traceable identity gives a system nothing to judge, which is nearly the same as no byline.
- Fix the twenty pages that carry commercial questions, and never bulk update modified dates.
Check yourself
Before you move on
Not scored, not recorded, and not part of the certificate. Both answers are settled by a sentence in this lesson, and the reasoning appears whichever option you pick.
- 01
A builder page has the answer in the HTML, below a hero, a feature grid and three testimonials. Why can it still lose?
- 02
A plugin generates Organization schema naming the company one way while the footer names it another. What has that achieved?