When does following SEO best practice produce a worse page?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 6
When a default meant for the typical case is applied to a page it does not fit. Best practices summarize what helps on average; a real page has its own question, reader and answer. Following a rule that contradicts what that page needs, a target length for a question that needs three sentences, or a list format for an argument that needs prose, makes the page worse in order to satisfy a checklist.
Defaults that backfire when misapplied
| Best practice | When it makes the page worse |
|---|---|
| Aim for a certain word count | The question is answered fully in a few hundred words, and padding buries the answer |
| Include the keyword in headings and early text | The keyword reads awkwardly and the sentence bends around it |
| Add an FAQ section | The questions repeat what the page already said |
| Use lists and tables for scannability | The answer is a chain of reasoning that bullets break apart |
| Put a number in the title | The page does not deliver a count, and the number is decoration |
| Add schema to everything | The markup describes content that is not visible, or no rich result exists for that type |
Each default is sensible for some pages. The failure is treating it as a rule rather than a starting point. Google’s guidance on creating helpful content poses its advice as questions for the writer to answer about each page, not as steps to apply everywhere, and some of its questions are pointed warnings against writing to a formula, such as writing to a particular word count because you heard Google prefers it.
A check before applying any practice
Ask whether it serves this question and this reader. If the answer is yes, apply it. If it is “the checklist says so”, look at what the page needs instead: the length the answer takes, the format the answer has, the words a reader would use. Where the format question comes up, whether an answer should be a list to win a snippet works through one such case.
Keep the defaults, drop the rigidity
Best practices remain useful for spotting what a page might be missing. Read each as a question (“would this page benefit from a table?”), not an instruction, and the page will follow its own needs rather than an average it does not belong to.
Add a comment