AEO Consultant, South Africa

Where South African buyer questions really come from

Keyword tools miss the questions that decide many South African purchases, because those questions are asked out loud or typed into a chat. The better sources sit inside your business:

• sales call notes and quote requests, where buyers ask about lead times, delivery to outlying towns or whether you handle the paperwork for a tender
• help desk tickets and emails, which reveal what customers still do not understand after they have bought
• WhatsApp conversations, often the first contact a South African customer makes
• what Google suggests, and lists under People Also Ask, when the location is set to South Africa
• questions your staff hear in Afrikaans, isiZulu or other languages, noted in the words customers use

Exports from support and sales systems contain personal information, so I ask for them stripped of names, numbers and account details. POPIA governs how that information is processed, and your information officer should confirm the approach, with legal questions referred to your advisor.

The questions then become a question map: grouped by topic, tagged with buying stage and assigned to one page each, so two pages never compete for the same answer. For each question the map notes what the current best answer on the web gets wrong or leaves out, which is often where your opening lies. The method follows my answer engine optimization approach, applied to South African phrasing.

Answer-first paragraphs and FAQ pages that hold up

A good answer passage can be read on its own. If someone asks whether you install solar systems in sectional title complexes, the first sentence should say yes or no, the second should name the main condition, such as body corporate approval, and the detail should follow. Assistants and snippets lift that opening; a human skimming on a phone reads the same lines.

For each priority page I check a short list:

• Does the heading state the question in the words buyers use, including South African terms like bakkie, geyser or levy?
• Does the first sentence answer it without a preamble about how much you value the customer?
• Are steps numbered and options set out in a table?
• Is anything stated that sales or operations would not confirm?

FAQ blocks need discipline. They should answer questions the main text does not cover, not repeat it in another format, and a long FAQ list on every page dilutes all of them. A separate support hub suits businesses with many after-sales questions, while a QAPage format only fits pages where real users ask and answer. Where answers involve tax, consumer protection or employment rules, they stay general and point readers to an advisor, since a crisp one-line answer on a legal matter is easy to quote and easy to get wrong.

FAQPage, HowTo, QAPage and speakable markup used carefully

Structured data helps machines see that a passage is a question and its answer, or a set of steps. It does not earn a visual result by itself. Google has cut back sharply on where FAQ and HowTo enhancements appear, and its rules keep moving. The reason to add markup is that it labels the content truthfully; a special display is a bonus I never count on.

The working rules are simple:

• FAQPage only where the questions and answers are visible on the page and written by your business, not user submissions
• HowTo for genuine step-by-step instructions, such as preparing a site for an installation, where every step in the markup appears in the text
• QAPage only for pages where a user asks a question and others answer, which rules it out for a typical company FAQ
• Speakable-style markup, where supported, pointing to short passages that make sense read aloud, with support treated as limited and subject to change

Before anything goes live, each block runs through a validator and is read side by side with the page text. Markup that claims answers the reader cannot see creates risk without benefit. Where your site needs a broader cleanup, the schema markup consulting work covers organization, product and local business data, and the technical SEO work for South Africa deals with how templates generate it.

Spoken questions, snippets and the People Also Ask box

People talk to assistants in full, chatty sentences: what time does the Centurion branch close on Saturday, does this courier deliver to farms outside Tzaneen, how do I reset a prepaid electricity meter. Assistants answer them from short passages and from structured business facts, so a reply that runs to a paragraph of qualifications, or opening hours that differ between your site and your business profile, works against you. Consistent branch details overlap with local SEO in South Africa, and I flag conflicts rather than duplicating that work.

Snippets and related-question boxes come next. For each priority question I note who holds the answer today, the format it takes and what it does better than your version. The winning answer is often shorter and clearer, not longer. Recasting a single section as a one-line definition, numbered steps or a tidy table is sometimes all it takes to contend.

These positions move. A snippet may be replaced by an AI summary, a different site or nothing at all, so I track them as trends across the question set. Search Console reports how question-style searches perform, and an inquiry form field mirrored in the CRM captures which guide or answer started the conversation, so effort follows questions that lead to real conversations.

Afrikaans and isiZulu answers, and keeping every answer current

Where customers ask in Afrikaans, isiZulu or another South African language, the answer has to sound natural to them, not translated. A literal rendering of an English sentence about warranty conditions can read as stiff or even change the meaning. The engagement runs in English; answers in other languages come from people who grew up speaking them, on your payroll or through a local writer, using the words customers actually typed or said, which the question map preserves.

Not every answer needs every language. I recommend local-language answers where the question log shows demand and your business can reply in that language when the customer follows up. A clear English answer is better than a neglected translation.

Answers also age. Prices change, a product is discontinued, delivery areas shrink or grow and regulations are revised. An answer engine will keep repeating your old reply long after you have forgotten it. Every published answer goes into a register with:

• an owner in the business
• the facts underneath it: a price list, a service area, a rule
• the events that should trigger a rewrite
• its language versions, so all are updated together

For how assistants choose which sources to cite, rather than how answers are phrased, see generative engine optimization in South Africa.