01
What a knowledge hub is (and isn't)
It is a structured library of genuinely useful answers, organised into topics that mirror how people shop your catalogue. It isn't a blog with random posts, and it isn't thousands of near-identical pages swapped by keyword.
02
Subdomain or subfolder?
Both can work. A subdomain (for example learn.yourstore.com) keeps the hub's technical setup separate from your store platform, which makes it faster to launch and easier to manage without touching checkout. A subfolder can share more of the main site's authority but often needs more development work on the store platform. The right choice depends on your platform, team and risk appetite. What matters most is clean internal linking between the hub and the store.
03
Hub architecture: pillars, clusters and product links
Pillars
cover broad topics (e.g. "outdoor cooking").
Clusters
answer specific questions under each pillar (e.g. "gas vs charcoal for small balconies").
Product links
point each answer to the relevant category or product pages.
Cross-links
connect related answers so readers and crawlers can move through the topic.
04
Keeping the hub on-brand and accurate
Every page should reflect your products, policies and voice. Straider grounds content in your catalogue and guidelines and runs quality checks before anything is published.
05
Measuring it
Search Console:
impressions and clicks for the hub's queries.
GA4:
hub sessions, clicks through to products, and assisted conversions. Set up cross-domain measurement if the hub is on a subdomain.
AI referrals:
visits from ChatGPT, Perplexity, Copilot and Gemini.
