THEO: The vet clinic read that long content ranks better and turned it into a rule, every page padded to two thousand words, and they’re asking why it isn’t working. The premise is a misread of a correlation. Longer content often ranks well, but not because length is a ranking factor, because thorough answers to complex questions tend to be long. The clinic optimized the symptom, word count, instead of the cause, completeness.
ELENA: And padding to hit a number does structural damage, which is the part the rule ignores. A page that answers “what are clinic hours” in fifty words is a good page. Stretched to two thousand, it buries the answer under filler, and now the reader scrolls through padding to find one line. So the word-count rule doesn’t just fail to help short-answer pages, it makes them worse, the completeness that long content signals is the opposite of what padding produces.
HANNAH: Let me ground what the correlation actually is, because it’s easy to flip into “length is irrelevant,” which is also wrong. For a genuinely complex query, “what to do if your dog ate chocolate,” a complete answer really is long, symptoms, amounts, timing, when to call, what not to do. A fifty-word answer to that would be dangerously incomplete. So length isn’t worthless as a clue, it’s a side effect of matching the depth a question demands. What actually distinguishes strong content isn’t word count but information gain, whether the page adds something the already-ranking pages don’t, a fresh detail, a clearer breakdown, a piece of real experience, rather than restating the same hundred words everyone else has. The error is making length a target instead of letting it be a result of genuine completeness.
MARCUS: Hold on, I want to push on the YMYL angle here specifically, because this is a vet clinic and some of these queries are health-critical.
HANNAH: Meaning the depth isn’t just an SEO nicety on those pages.
MARCUS: Right. On a “my pet ate something toxic” page, completeness is a safety matter, not a ranking one, and that page genuinely should be thorough and careful. But padding a clinic-hours page to match it is the inverse error, length where it’s harmful. So the clinic has two opposite problems from one rule, critical pages that need real depth getting the same treatment as simple pages that need brevity, and the uniform two-thousand-word target serves neither.
THEO: Which is the correction, length should match what the query demands, long where the question is complex, short where it’s simple.
NOAH: The pattern is turning a correlation into a target, the classic version of optimizing a measurable proxy instead of the real quality it correlates with. Length was visible and easy to mandate, completeness is a judgment, so the team mandated the number. The tell is a uniform word count across pages that answer wildly different questions, every page the same length regardless of what it’s for.
SOFIA: And the reader bounces off padding fast, which feeds back into the ranking. Someone wants the clinic’s hours or whether it takes a certain insurance, and a padded page makes them hunt for one fact through paragraphs of filler. They leave frustrated. The page that answers immediately keeps them and converts them, books the appointment, gets the call. Padding costs the conversion the page existed to make.
AIKO: Operationally the fix is to set the target as completeness for the specific intent, not a word count, page by page. Each page asks what a complete answer to this exact query requires, the toxic-ingestion page needs depth and care, the hours page needs one clear answer fast, and the length falls out of that. A useful sanity-check is the length of the pages already ranking for a query, a rough signal of the depth that query rewards, used as a benchmark to test against rather than a number to copy. The content brief should specify the questions a page must answer, not a word minimum, so writers aim at covering the intent rather than hitting a count. Length becomes an output of completeness, never an input.
THEO: Which closes back to the misread, they targeted the byproduct and got pages that are long without being complete, and short answers buried instead of served.
DANA: So where we land is completeness per intent, not a word count. Long content correlates with ranking because thorough answers to complex questions are naturally long, not because length is a factor, so a uniform two-thousand-word rule optimizes the symptom and buries simple answers under filler. Per Marcus, this clinic has both errors at once, health-critical pages like toxic-ingestion genuinely need depth, where completeness is a safety matter, while a clinic-hours page needs one fast answer, and the uniform target harms both. So we set each page’s target as completeness for its specific query, depth where the question is complex, brevity where it’s simple, and write to the questions a page must answer rather than a word minimum. The instinct that thorough content does well was right. Chasing length as the goal, instead of the completeness it comes from, is what produced long pages that don’t satisfy.
SOFIA: Answer the question as fully as it needs and no more. A reader wants the answer, not the word count.
DANA: Length is what completeness sometimes costs, not a target to hit. Match the depth to the question, and let short answers be short.