Write for people first

You will be able to check a post against Google's guidance on helpful, people-first content before you publish.

Search for almost any common question and you will find pages that look helpful and say nothing. They repeat the question in the first paragraph, list obvious points under headings stuffed with search phrases, and end with a call to action. Nobody who wrote them had done the thing they describe. They were written to be found, and readers can tell.

Google has published guidance on this kind of content, and it is worth reading even if you never think about search rankings. It is a useful checklist for whether a post is actually good for the person reading it.

What Google's guidance asks

Google Search Central, the part of Google's website for people who publish online, has a page on creating helpful, reliable, people-first content. It describes content made mainly to help people, as opposed to content made mainly to rank in search, and it offers a set of questions you can ask about your own work.

The questions cover several areas. Some ask about the content itself: does it provide original information or analysis, and does it go beyond the obvious? Some ask about expertise: does the content clearly show first-hand experience, such as having used the product, visited the place or done the work? And some ask about the reader's experience afterwards: would someone leave feeling they had learned enough to reach their goal, and feel satisfied with what they read?

Read the current version of the page yourself before you publish, because Google updates its guidance and the exact wording matters. The point for a writer is that these are the same questions a good editor would ask, whether or not search engines existed.

What the guidance warns against

The same page also describes content written mainly to attract search visits. Its warning signs include writing about a topic only because it seems to be trending, entering a subject with no real expertise because you expect search traffic from it, and producing lots of content on many topics in the hope that some of it ranks. It also warns against content that leaves readers needing to search again to get a better answer.

For a small business, the most common version of this is the post written to fill a calendar. "Ten tips for exam success" with tips anyone could write, no examples from the business's own work, and a sales pitch at the end. It is not dishonest, but it is not helpful either, and it does nothing for the business's reputation.

The fix is the work you have already done in this module. A post that answers a question real customers asked, gives the answer early, and includes examples from your own work is people-first content almost by definition.

Name the author and their experience

Readers want to know who wrote what they are reading, and why that person knows. Google's guidance asks whether it is clear who created the content, for example through a byline where one would be expected, and whether there is information about the author's background.

For a small business blog this is easy and often skipped. Put the writer's name on the post and add a line or two about their relevant experience. "Priya has taught upper primary maths for twelve years and runs the centre's P5 and P6 classes." That line tells a parent why this person's opinion on tuition is worth reading.

This matters most on topics that affect people's money, health or safety. Google's guidance gives more weight to experience, expertise and trustworthiness on those topics, and so do readers. If you write about insurance, investments, medical conditions or legal questions, the author's qualifications and experience should be visible, and the post should be accurate and current. A financial adviser writing about CPF should say who they are and check every figure against the CPF Board's website on the day of publishing.

Easy for every reader

People-first content is also content that is easy to read. That means short paragraphs, concrete examples, and plain words a reader would use themselves. These choices help everyone: the busy parent reading on a phone during her lunch break, the reader whose first language is not English, and the reader who is simply tired.

Many of your readers will be on a phone. A paragraph of seven lines on a laptop can fill a whole phone screen, and a wall of text on a small screen is where people stop. Keep most paragraphs to three or four sentences. Use a list where the content really is a list, such as steps or items to bring, and prose where ideas connect.

Module 7 covers editing for clarity in detail. For now, read your post on your own phone before you publish and notice where you would lose patience.

Checking your outline

Take the outline you wrote in lesson 6.2 and go through the people-first questions from Google's page. Be honest. Where a section would not leave a reader better informed than a general article would, it is weak.

The usual cure is a first-hand detail: something you have seen, done, measured or got wrong. Priya found that her section on "When practice at home is enough" was generic. She added a short example of a student whose parent had tried tuition, then switched to ten minutes of practice a day at home once the method clicked, and did well. The section went from a list of general advice to something only she could have written.

The activity asks you to answer the people-first questions for your outline. For each section that comes out weak, add one detail from your own experience before you start drafting, rather than hoping to add it later.

Answer the people-first questions from Google's helpful content guidance for your outline and add one first-hand detail to each weak section.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).