Tip 1: People First, Robots Second

Tip 1: People First, Robots Second

R
Richard Newton
Build store pages around the decision a shopper needs to make, then let search in.

What people-first means on an online store

A shopper in a clothing store holds and examines a dark long-sleeved base-layer top.

Google’s guidance on helpful content asks one thing of every page: that it was made to help a person, with ranking as the side effect. Most store owners agree with that in principle. Then they publish a buying guide that opens with three sentences restating the keyword. The gap between agreeing and doing is where this tip lives.

On a store, people-first content is something a shopper can use to make a decision. They leave knowing which size to order, whether the fabric will itch, how long delivery takes to Ireland, or which of two near-identical products suits them. A robot-first page leaves them knowing that the store would quite like to rank for “best merino base layer”.

The policy questions have homes of their own. Whether AI-written pages are allowed at all is answered in our explainer on whether Google bans AI content, and why so many store pages lost ground when Google got stricter is covered in the piece on content with no job. This one is about method: how to sit down and build a page that starts with the shopper and still gets found.

Start from the question the shopper actually has

A dark merino thermal shirt lies on a wooden table while a person measures its chest with a yellow tape measure.

Keywords are compressed questions. “Merino base layer sizing” is a person holding a tape measure, wondering whether to size up so it fits over a thermal. The keyword tells you the topic. It says nothing about what needs settling.

The quickest way to recover the real question is to look where shoppers already ask it. Every store has these sources, and very few feed them to whoever writes the blog:

  • Customer service emails and live chat transcripts, sorted by how often each question comes up.
  • Return and exchange reasons. “Too small”, “itchy” and “colour different from photos” are content briefs with evidence attached.
  • Product reviews and Q&A, especially the three-star ones, where people explain what they wish they’d known.
  • On-site search terms, including the ones that return nothing.
  • Search Console queries that already bring impressions to pages that answer them badly, which Search Console will show you if you look.

Take a store selling merino base layers. Its keyword tool says “merino vs synthetic base layer” has healthy volume. Its returns data shows the lightweight top coming back marked “too cold”. Its chat log is full of people asking whether the 150 weight works for skiing.

Those three sources describe the same shopper: someone choosing a fabric weight for a specific activity and temperature. The page that helps them is a fabric-weight guide organised by activity. It will still cover merino against synthetic, because that comparison is part of the decision, but it will no longer be the whole page.

Write down the decision before you write the page

Three differently thick folded merino tops in light, medium, and dark shades sit on a wooden table.

Before drafting anything, finish this sentence: “After reading this, the shopper can decide ___.” If you can’t fill the blank, there’s no reason for the page to exist yet.

For the base layer store, it reads: “After reading this, the shopper can choose between the 150, 200 and 260 weights for their activity and the temperatures they’ll be out in.” That sentence now governs everything. Sections that do nothing for the decision get cut, however many keyword variants they carry. Sections the decision needs get written even when no tool flags them, such as how each weight layers under a waterproof shell.

It’s also the fastest cure for padding. A definition of merino, a potted history of the sheep, a paragraph on why base layers matter: none of them moves the decision forward, so none of them survives the edit.

Put in what only a store would know

Hands hold and examine the ribbed cuff of a dark blue wool sweater on a countertop.

Anyone who’s read the top five results can write a generic article. Content written for shoppers contains facts that come from selling the thing, and stores hold far more of these than they use:

  • Fit knowledge: how the cut runs against a standard size chart, and which size people between sizes usually keep.
  • Materials detail from supplier spec sheets, such as fibre micron, knit, blend percentages and care limits.
  • Real-use observations from the team: how the 150 weight looks after 30 washes, which colours show sweat.
  • Logistics facts shoppers worry about, like delivery times by region and how returns work for items worn once.
  • Honest limits: the people it doesn’t suit.

That last one feels commercially risky. It rarely is in practice. A line that says “if you run cold and spend most of the day standing on a chairlift, skip the 150 and go straight to the 260” is the sentence that makes a shopper trust everything else you’ve written. It also prevents a return.

Making that experience visible to readers and search engines is its own discipline, covered in Tip 4 on showing your E-E-A-T. Here the point is simpler. Include it.

Then let the robots in

A hiker in a gray crew-neck layer zips a dark waterproof shell jacket on a mountain trail.

None of this means ignoring search. It means treating search as a translation layer that goes on second. Once the page settles the decision, check it against how people phrase the query:

  1. Use the shopper’s own words in headings. If people search “is merino itchy”, a heading like “Does merino itch against bare skin” matches the query and the worry behind it.
  2. Answer the core question high on the page, in a sentence that still makes sense if lifted out on its own. AI Overviews and answer engines quote passages, so a clean, self-contained answer helps the skimming shopper and the summary layer at once, which is the approach in our guide to AI Overviews for ecommerce.
  3. Add the comparisons people make, such as 200 against 260, as sections where they genuinely inform the choice.
  4. Link to the products and collections the decision leads to, on the words a shopper would click, like “the 260 weight crew neck”.
  5. Write a title and meta description that promise exactly what the page delivers.

The order matters more than it looks. A page written keyword-first and “humanised” afterwards keeps a robot’s skeleton, with sections that exist because a term needed somewhere to live. A page written decision-first and then optimised has a shopper’s skeleton with the right labels attached.

The robot-first patterns that still slip through

A dark merino base-layer top hangs on a wooden hanger in a rustic outdoor gear room.

Blatant keyword stuffing is rare these days. The versions that survive are quieter, and store blogs are full of them:

  • The mirrored competitor. Headings copied from whatever ranks first and reworded. It gives the searcher nothing they haven’t already seen.
  • The variant farm. Separate posts for base layers for hiking, for skiing and for running, each mostly identical. One well-organised guide serves the shopper better, and Google’s scaled content abuse policy is aimed squarely at pages churned out mainly to manipulate rankings, whoever or whatever writes them.
  • The product page in disguise. A “guide” where every section ends in a buy button and the advice always lands on the most expensive item.
  • The definitions opener. Two hundred words explaining what a base layer is, to a reader who searched for fabric weights.

One test fixes all of them. Ask what your reader can decide now that they couldn’t before. If the honest answer is nothing new, merge the page, cut it or rewrite it.

A pre-publish checklist

A person reviews a checklist beside a laptop and a folded dark merino crew-neck top on a wooden table, with a plain mug nearby.
  • The decision sentence is written down, and every H2 serves it.
  • The main question is answered within the first 100 words.
  • At least one fact came from your own store: fit, materials, testing, returns or delivery.
  • The page names the shoppers the product doesn’t suit, wherever that’s true.
  • Headings use the words shoppers use, taken from real queries, reviews or chat.
  • Links point to the specific products and collections the decision leads to.
  • You would happily send this page to a customer who emailed the question.

The last check is the one to keep. If you’d rather write the customer a fresh reply than send them the link, the draft isn’t finished.

Your customer service team already writes people-first content every day, one email at a time. A blog built from those answers starts in the right place, and it tends to look like the boring content that answers the obvious questions. That is a compliment. The robots follow the shoppers, eventually, and they’ve been getting quicker about it.


This is Tip 1 in Sprite’s 11-part series on ecommerce content that compounds. Next: Tip 2: Post Regularly.

Frequently asked questions

Where do I find shopper questions if my store is new?

Borrow the questions before you have your own. Read reviews and Q&A on marketplace listings for comparable products, note the questions your supplier gets asked, and check the “People also ask” boxes for your main product terms. Ask friends who fit your target customer what they would want to know before buying. Log every pre-sale email and chat from day one, even if there are only a handful, because those early questions tend to be the ones every later shopper has too. Once pages go live, Search Console queries fill in the rest.

Should I still do keyword research for people-first pages?

Yes, but use it as a vocabulary check rather than a brief. Keyword research tells you what shoppers call things and which comparisons they search for, which is useful for headings, titles and deciding what sections a guide needs. It can’t tell you what the guide has to resolve for the shopper, so start with the question and the decision, draft the page, and then check it against keyword data. If a keyword would pull the page away from the decision it serves, that keyword belongs on a different page or nowhere.

Won’t admitting a product’s limits cost me sales?

It usually redirects a sale rather than losing one. A shopper told that the lightweight top won’t cope with chairlift days is being pointed at the heavier one you also sell. The ones who genuinely shouldn’t buy anything from the range were likely to return it, which costs you postage, handling and a disappointed customer. Honest limits also make your positive claims more believable, because the reader can see you’re willing to say no. Keep the tone practical: describe the situation the product suits badly and name the alternative.

How long should a shopper-first buying guide be?

As long as the decision needs and no longer. A guide to choosing between three fabric weights might be comfortably covered in 800 words, while a guide to fitting walking boots across different foot shapes may need far more. Use the one-line decision you wrote before drafting as the ruler: every section should move the shopper closer to choosing. If you find yourself adding sections to reach a target word count, stop, because padding is exactly what makes a page read as written for a robot.

Sprite builds brand authority through continuous, automated improvement. Quietly. Consistently. And at Scale.

No commitment
30-day free trial
Cancel anytime
Powered bySprite
Your Turn

See What You Could Save

Discover your potential savings in time, cost, and effort with Sprite's automated SEO content platform.