Google publishes the questions it wants content creators to ask about their own work, and running a page through them honestly catches most of what separates a genuinely useful page from one that just exists.
The questions Google actually suggests
Google's own guidance on helpful, people-first content offers a specific set of self-assessment questions, including:
- "Does the content provide original information, reporting, research, or analysis?"
- "Is this the sort of page you'd want to bookmark, share with a friend, or recommend?"
- "Does your content clearly demonstrate first-hand expertise and a depth of knowledge?"
- "After reading your content, will someone leave feeling they've learned enough about a topic to help achieve their goal?"
The pattern underneath all four is the same: does this page exist because something real needed to be said, or because a page needed to exist? Google frames the core distinction directly, that the real test is why the content exists, to genuinely help a reader or primarily to attract search traffic.
Turning this into a writing process
- Start with the actual question, the one a customer would type or ask on the phone, word for word if possible.
- Answer it in the first two or three sentences. Don't build up to the answer; give it immediately, then explain.
- Add the detail only you would know. A generic answer to "how much does X cost" is available on fifty other sites. What you've actually seen go wrong, what customers are usually surprised by, what changes the price, that's the part only you can write.
- Cut anything that doesn't serve the question. A page padded with unrelated background information dilutes the part that actually answers what someone came for.
- End with what to do next, whether that's a related question, a service page, or a way to contact you.
What this looks like against a weak version of the same page
A weak page: "At [Business], we believe every customer deserves the best service. We've been serving the community for years with pride and dedication to quality..." three paragraphs in, and the actual question still hasn't been touched.
A strong page: states the answer to the actual question in the opening lines, then explains the reasoning, the exceptions, and what a reader should do with that information. See what should be in a website proposal? as one example of this Bulletin's own articles opening directly with the answer before expanding on it.
Why this matters beyond ranking
Content that genuinely helps a reader also happens to be what search engines and AI assistants are built to reward, but that's a byproduct, not the goal to write toward directly. Writing for the score tends to produce hedged, padded, forgettable pages. Writing to actually answer the question tends to produce both a better page and, as a side effect, one that performs better. See do contractors need a blog? for how this applies specifically to a trades business deciding what to write about at all.
A short test before you publish anything
Read the page back and ask: if a customer asked me this exact question on the phone, is this what I'd actually say? If the page sounds like something else, marketing copy, a template, a list assembled to look thorough, that's the signal to rewrite it closer to how you'd really answer.
Questions
Does length matter for this kind of content?
Only as much as it takes to actually answer the question well. A short, complete answer beats a long, padded one every time.
Should I write in a formal or conversational tone?
Whichever matches how you'd actually talk to a customer. Content that sounds like a real person answering a real question tends to read as more trustworthy than content that sounds like it was written to satisfy a template.
How do I know what questions to write about in the first place?
See how to find the questions your customers are asking for the practical methods, including one that uses data your own site is already generating.