01
The loop: discover → improve
Step 01
Discover:
find the questions Emberline's shoppers ask and where the site isn't visible yet.
Step 02
Plan:
group those questions into pillars and clusters that mirror how people shop.
Step 03
Create:
draft answers grounded in Emberline's catalogue and brand guidelines.
Step 04
Check:
run every draft through the quality gates.
Step 05
Release:
publish in paced batches.
Step 06
Measure and improve:
read Search Console and GA4 data, refresh what underperforms, and only then expand.
02
Anatomy of a hub
- Main storewww.emberline.exampleMain store
- Hubdemo.straider.aiKnowledge hub
- PillarsPillarsBroad topics
- ClustersClustersSpecific answers
- ProductsProduct linksCategories & SKUs
Quality gates
- Dedup
- Relevance scoring
- QA
- Index health
Main site
Store with categories: grills, smokers, pizza ovens, accessories
Hub
demo.straider.ai (live fictional demo)
Pillars
"Choosing a grill", "Smoking basics", "Outdoor pizza at home", "Care & maintenance"
Clusters
"Gas vs charcoal for a small patio", "How long to preheat a pizza oven", "Cleaning cast-iron grates"
Product links
Each answer links to the matching category or product, e.g. compact gas grills or grate brushes
| Layer | Emberline example |
|---|---|
| Main site | Store with categories: grills, smokers, pizza ovens, accessories |
| Hub | demo.straider.ai (live fictional demo) |
| Pillars | "Choosing a grill", "Smoking basics", "Outdoor pizza at home", "Care & maintenance" |
| Clusters | "Gas vs charcoal for a small patio", "How long to preheat a pizza oven", "Cleaning cast-iron grates" |
| Product links | Each answer links to the matching category or product, e.g. compact gas grills or grate brushes |
Cross-links connect related answers so readers (and crawlers) can follow a topic from start to finish. For more on hub structure, see Knowledge hub for ecommerce and the platform.
03
How pages earn their place
A page only goes live once it passes four gates:
Dedup:
it isn't a near-copy of another page in the hub or on the main site.
Relevance scoring:
it answers a real shopper question that fits Emberline's range.
QA:
it's checked for accuracy, brand voice and correct product links.
Index health:
we keep an eye on how search engines treat the hub and adjust before adding more.
We don't publish the specifics of how those checks are run. Those details are how we keep quality high.
04
How releases are paced
Emberline's hub would start with a small first batch and grow week by week. Release volume goes up only as earlier pages get indexed and start earning impressions. If a batch underperforms, we slow down and improve it before adding more. The pacing is deliberate: it's how a hub builds trust instead of noise.
05
What you see in reporting
Weekly report:
pages released, pages indexed, and impressions and clicks from Search Console.
Engagement:
hub sessions and clicks through to products in GA4.
AI referrals:
visits from assistants like ChatGPT, Perplexity, Copilot and Gemini.
Next steps:
what we're refreshing, what comes next, and why.
