How to create a knowledge base for your online store: 6 steps, a starter map and an article template (2026)

Short answer: Build your knowledge base from the questions customers already send you, not from a blank page. Tag four weeks of chats and emails, write 15–25 articles that answer the most common ones, group them into 5–6 collections named the way customers think ("Orders and delivery", "Returns"), and put the search where people already ask: inside your website chat. Then spend 30 minutes a month fixing the articles behind the questions that still arrive.

Below: when a knowledge base is worth it (and when a FAQ page is enough), a starter map for an online store, an article template you can copy and the monthly routine.

Why most knowledge bases don't stop the questions

People do try to help themselves first. In a 2017 Harvard Business Review article, the authors report that "across industries, fully 81% of all customers attempt to take care of matters themselves before reaching out to a live representative" (HBR, 2017). The problem is what they find. A Gartner survey of 5,728 customers (December 2023) gives these numbers (Gartner, 2024):

Read that 43% as a to-do list. Most failed self-service is a content problem: the article doesn't exist, has the wrong title, or hides the answer under three paragraphs. And the 14% is a warning. A knowledge base cuts repeat questions; it does not replace a way to reach a person. Keep the chat button next to every article.

Do you need a knowledge base or just a FAQ page?

These thresholds are our rule of thumb, not a standard. The real test: if your team pastes the same long answer more than a few times a week, it deserves an article.

Step 1: Pull the questions out of your inbox

Don't brainstorm topics. Export or scroll through the last four weeks of chats and emails, and give each conversation one tag for the question behind it ("where is my order", "change address", "size advice"). 100–200 conversations is enough for a small store.

Sort the tags by count. The top 15–25 become your first articles. Write down the customer's own words too: if people write "parcel" and "tracking", don't title the article "Shipment status information".

If you use Topics in Shopxare, Are AI labels conversations for you and shows the trend, so this step takes minutes instead of an afternoon.

Step 2: Plan collections the way customers think

Five or six collections are enough to start. Name them after the customer's task, never after your departments. Here is a starter map for an online store:

That is 23 articles. One level of sub-collections is plenty; customers won't dig through three.

Step 3: Write every article with the same template

People scan. Jakob Nielsen's research found that "on the average Web page, users have time to read at most 28% of the words during an average visit; 20% is more likely" (Nielsen Norman Group, 2008). So the answer goes in the first two lines, and everything else is support for it.

Copy this template:

Title: [The question, in the customer's words]
Summary (1 line, shown in search): [The answer in one sentence]

[Answer in 1–2 sentences. Numbers, deadlines, costs.]

## How to do it
1. [Step with the real button or menu name]
2. [Step]
3. [Step]

## Good to know
- [Exception 1, e.g. sale items, international orders]
- [Exception 2]

## Still stuck?
[What to send us (order number, photo) and how: "Open the chat below."]

Last checked: [month year] by [name]

Example: a filled-in article

A small UK shop selling bike parts gets about 40 return questions a month. Their article:

How do I return an item? You can return unused items within 30 days of delivery. Returns are free in the UK.

You have 30 days from delivery to send back unused parts in their original packaging. We refund to your original payment method within 5 working days after the parcel arrives.

How to do it

1. Open the returns page from the link in your dispatch email.
2. Enter your order number and postcode.
3. Print the label and drop the parcel at any Post Office.

Good to know

• Fitted parts (e.g. chains that were cut to length) can't be returned unless faulty.
• Returning from outside the UK? You pay the postage; use a tracked service.

Still stuck? Open the chat and send your order number. We answer within 2 working hours.

Three rules that make the biggest difference: one question per article, real numbers instead of "a few days", and a "Last checked" line so your team knows when it went stale.

Step 4: Put the answers where customers already ask

A knowledge base nobody opens does nothing. Place it in four spots:

1. Inside the chat. In Shopxare, turn on the Help center search card on the Messenger home. Customers search before they type a message, and they can still write to you if the article doesn't help.
2. In your saved replies. End a templated answer with the article link, so customers learn where to look next time. (Saved replies)
3. In transactional emails. Link "Where is my order?" in the dispatch email and "How to return" in the delivery email.
4. For your AI agent. Are AI uses your published help center articles as a knowledge source and keeps them in sync when you publish, change or delete one (Teach Are AI). Clear, one-question articles are also what makes AI answers accurate. Our guide to an AI chatbot that answers from your own content covers the test before going live.

A note on Google: FAQ rich results are gone. Google stopped showing them from 7 May 2026 (Google Search Central, 2026). Don't plan your help center around special search snippets; plan it around clear titles that match what people type.

Step 5: Set it up and launch in one afternoon

In Shopxare the help center is part of the free plan. The steps:

1. Help center → New collection for each of your 5–6 collections (name, description, icon).
2. New article: title, collection, a one-line Summary, the body. Save draft, then Publish.
3. Moving from another tool? Import reads up to 500 articles from your current help center's address (Intercom, Zendesk, Freshdesk, Help Scout and others) or from a CSV file. (Help center articles)
4. Selling in several languages? Open an article, pick the language, click Add a language, translate and publish that version.
5. Help center → Settings: name, address, languages, switch Published on, then Preview. You can also connect your own subdomain such as help.yourshop.com (look and address).

Before launch, search for your top 10 questions in the customer's words. If an article doesn't come up, fix the title.

Step 6: Keep it current with a 30-minute monthly check

Stale articles are worse than missing ones, because the customer acts on the wrong information. Once a month:

• Read the questions that still arrive. Which tags are still high? Each one points to an article that's missing, hard to find or unclear.
• Check what the AI couldn't answer. In Shopxare, Are AI → Overview → Questions the AI could not answer lists the gaps.
• Look at "Was this helpful?" reactions on articles and rewrite the ones people mark as unhelpful.
• Update anything that changed: delivery prices, cut-off dates before Christmas, carriers, return windows. Change the "Last checked" line.

To see if it works, track contact rate (conversations per 100 orders) before and after. Our post on customer service KPIs has the formula.

When a separate documentation tool is the better choice

A help center inside your support tool fits most stores: one place for chat, inbox and articles, and the chat can search them. A dedicated documentation tool is the better pick if you publish large technical manuals, need review and approval steps for every change, or keep versioned docs for several product releases. And if you have ten questions and no team, a well-written FAQ page is still the fastest win.

If you want the help center, chat and AI agent in one place, Shopxare is free with no credit card: start here.

FAQ

How many articles does a knowledge base need at launch?

Enough to cover your top 15–25 questions. That usually answers most of what a small store receives. Add articles when the monthly check shows a new repeated question, not before.

What should a knowledge base article include?

The question as the title, the answer in the first one or two sentences, numbered steps, exceptions, and how to contact you if it didn't help. Add a "last checked" date.

What is the difference between a knowledge base and a FAQ page?

A FAQ page is one page of short answers. A knowledge base has separate articles grouped in collections, with search, room for steps and images, and a version per language.

How do you keep a knowledge base up to date?

Give every article an owner and a "last checked" date, and review once a month: questions that still come in, unhelpful ratings, and anything that changed in prices, delivery or returns.

Should the knowledge base be public or internal?

Start with a public one for customers. Your team can use the same articles in replies. Internal-only notes, like refund limits per role, belong in a separate internal document.