We stopped trusting our own judgement on this a while back, after a page we were genuinely proud of in Epping sat flat for months despite ticking every box on the usual SEO checklist. The content was well-written. It just didn't actually answer the question someone typed into Google.
What stung slightly was that two of our own writers had each proofread that page separately before it went live, checking grammar, tone, and factual accuracy. Neither of them had thought to ask the one question that actually mattered: if you only had ten seconds, would you find what you came for? That gap in our own process is exactly what prompted us to build a proper test for it rather than relying on good proofreading alone.
The Test, Explained Simply
Before publishing anything now, we read the page cold, pretending we are the person who typed the exact search term in, and time how long it takes to find a direct, specific answer to that exact question. Not a related answer. Not context leading up to an answer eventually. The actual thing they searched for, stated plainly, as early as it reasonably can be.
If that takes longer than roughly the first third of the page, something's wrong with the structure, regardless of how good the writing itself is further down. We've failed this test on our own content more times than we'd like to admit, which is exactly why we built it into our process as a required step rather than an optional nicety.
The Epping Page That Failed Its Own Test
The page targeted "how long does a loft conversion take in Epping," a specific, practical question with a specific, practical answer someone wants quickly. Our original draft spent four paragraphs discussing the general benefits of loft conversions, planning permission considerations, and the company's experience in the area before finally stating a typical timeframe in paragraph five. A reader skimming for the actual answer would reasonably give up before getting there.
The page had been live for four months before we ran the test on it, and in that time it had earned a handful of decent backlinks from local trade directories, which made the underperformance even more frustrating once we realised the cause. External signals were doing their job. The page itself simply wasn't holding up its end of the deal once someone actually clicked through to read it.
We rewrote the opening to state the typical timeframe directly in the second sentence, six to ten weeks for a standard conversion depending on roof type and planning requirements, then used the rest of the page to add the context and nuance that had previously been blocking the answer entirely. Time on page actually increased after the rewrite, not decreased, because people who got their answer quickly then stuck around to read the supporting detail, rather than leaving before reaching it at all.
Why This Catches Problems Other Checks Miss
A keyword density checker will happily confirm a page is "optimised" while the actual answer sits buried under six paragraphs the searcher never reaches. A readability score can come back excellent on a page that still fails to address the question directly. Neither tool asks the one question that actually matters: did this person find what they came looking for, reasonably quickly, without having to work for it?
That's a genuinely different test from most SEO checklists, which tend to focus on whether the right elements exist somewhere on the page rather than whether they exist where and when the reader needs them.
Running This Test on Existing Content, Not Just New Pages
We applied the same test retroactively to a Witham plumber's existing site, working through his twelve highest-traffic pages one at a time. Four failed outright, burying their answer somewhere past the halfway point. Two of those four were pages he'd specifically told us he was proud of, which says something honest about how differently a page reads to the person who wrote it compared with the person searching for an answer under time pressure.
We shared those results with him directly rather than softening them, because a client who doesn't understand why a page is underperforming can't make a properly informed decision about fixing it. He took it reasonably well, mostly because the fix itself was quick and didn't require rewriting the pages from scratch, just reordering what was already there.
- Read the page as if you are the searcher, not the writer
- Time how long it takes to reach a direct answer
- Flag anything where the answer sits past the first third of the page
What This Looks Like for More Complex Questions
Not every question has a one-sentence answer, and forcing one where genuine nuance exists creates its own problem. "What does a kitchen extension cost" genuinely depends on size, materials, and specification, and a single number would mislead more than it helps. In those cases the test shifts slightly: does the page acknowledge the variables honestly and quickly, before diving into detail, rather than making the reader wade through unrelated content first to even understand why there isn't a simple number? A page that says plainly, within the first few lines, "costs typically range from X to Y depending on size and finish, here's why" passes the test just as well as a page with one clean figure.
A Mild Confession About Why We Built This Test
We built this test partly because we'd been writing content the wrong way round ourselves for longer than we'd like to admit, structuring pages the way we'd naturally explain something in conversation, building up context before reaching the point. That's a perfectly normal way to talk. It's a poor way to write for someone who typed a specific question into a search box and wants the answer now, not after a run-up.
Realising that gap existed in our own work, not just clients', changed how we approach writing from the first draft onward rather than treating structure as something to fix in editing after the fact.
How to Try This on Your Own Site Today
Pick your three highest-traffic pages, pull up the search term each one targets, and genuinely time yourself finding the answer as a first-time reader would. It takes fifteen minutes and tends to surface at least one page quietly failing its own purpose, buried under content that reads well but doesn't actually serve the person it was written for. We run this exact check as a standard part of our content audits for Essex clients, usually before touching anything else, because fixing structure first tends to make every other optimisation more effective afterward rather than less.
It's a cheap, fast diagnostic, and it's one of the more useful additions we've made to our own on-page SEO process precisely because it doesn't require any tool beyond a stopwatch and a willingness to read your own work honestly.
We'd recommend running this test again whenever a page gets edited substantially, not just once at launch. A page that passed the test cleanly a year ago can quietly fail it after three separate edits have each added another paragraph near the top, none of them individually a problem, but together pushing the actual answer further down the page than anyone intended.
The Bottom Line
Most content problems aren't really keyword problems, they're structure problems disguised as something more complicated. The Epping page didn't need new information, just the information it already had, moved to where a searcher could actually find it. Before publishing anything else, read it as the person who typed the question, time how long the answer takes to arrive, and fix the structure if it takes too long. It's the simplest test we use, and it still catches more than almost anything else in our process.
Looking for SEO agency in Essex?
Let's talk about what your business actually needs
Digital Impact Ventures provides SEO, AI visibility and digital marketing support for businesses across Colchester and Essex. Get in touch and we will talk through where your business is now and where it needs to go.