Sitemap + KB Topic Research: 7-Step Workflow for Writers

Most teams treat topic research like a scavenger hunt across keyword tools, competitor sites, and random brainstorms. That churn produces long lists but fragile ideas, because none of it is tied to what you actually sell or the pages you already have. The fastest, cleanest path is sitting in plain sight: your sitemap and your internal Knowledge Base.

When you limit inputs to the pages you own and the facts you can prove, decisions speed up. Writers stop debating volume and start shipping publishable work. The constraint sounds strict, yet it is the only way to keep narrative coherence, eliminate invented claims, and build an internal link structure that compounds. If you already run content in a system like Oleno, this is the operating model it enforces.

Key Takeaways:

• Anchor topic research to your sitemap and Knowledge Base to eliminate guesswork and protect narrative consistency
• Produce 10–12 enriched topics per seed with angles, narrative role, and link targets before drafting
• Assign topics to pillar, cluster, or support slots so internal links and demand creation are planned upfront
• Use a seven-part angle template to lock logic early and reduce rewrites
• Prioritize with a scoring checklist that ignores traffic estimates and rewards KB-grounded claims
• Validate quickly with a 10-minute evidence pass and a five-minute stakeholder check to avoid rework
• If you want the pipeline to run itself, operate the same workflow in Oleno with Topic Research, Topic Bank, briefs, and QA-Gate

Why Your Sitemap And KB Should Drive Topic Research

Set the constraints (no external dashboards)

Most teams think more data will clarify what to publish next, but piling on dashboards only adds delay and dilutes your story. Set a clear constraint: use only your live sitemap and your internal Knowledge Base. That rule forces every topic to map to a real page and a verifiable claim. It also removes “check volume” detours that slow sessions and derail narrative focus.

Write the constraint into your brief template so no one backslides into external metrics. The result is a tighter, faster session that produces publishable topics grounded in product truth. The upside is simple: fewer debates, cleaner decisions, and content you can defend.

Define the outputs (10–12 enriched topics per seed)

Pick a seed, usually a feature, problem, or core claim. Your goal is 10–12 enriched topics that each include an angle summary, a narrative slot, and named internal link targets. If a topic cannot carry those elements, park it. Approved topics become the production queue while parked ones keep a short note about what is missing. This binary split keeps momentum and prevents half-ready ideas from leaking into drafts.

The “complete or parked” rule protects writers from ambiguity. It also creates a visible handoff where editors know what is ready to brief and what needs more grounding.

Time-box the session (45–60 minutes)

Work in a fixed block. Use the first ten minutes to map sitemap slots, the next fifteen to extract entities and recurring claims from the Knowledge Base, then twenty minutes to draft angle stubs, and a final ten to prioritize and validate. One hour is enough to produce a clean, shippable queue for the week.

If a debate runs long, capture the question and move it to a quick stakeholder follow-up. Protect the clock. You can always re-rank next week when you see how the first articles land internally. Curious what this looks like in practice? You can Request a demo now.

Map Your Sitemap Into Narrative Slots

Inventory live coverage by URL and type

Export your sitemap and tag each URL as pillar, cluster, or support. Keep the inventory lightweight: the URL, the slot, and a one-line purpose. Note any pillars that under-serve your narrative or skip demand creation. This pass reveals thin areas and helps you avoid stacking new ideas on shaky foundations.

Use clear definitions so the team stays aligned:

• Pillar: broad problem or category page that frames the space
• Cluster: subtopic that resolves a specific angle under a pillar
• Support: tactical pattern, example, or teardown that ladders into a cluster

Identify gaps and candidate “slots to fill”

For each pillar, list missing clusters and support pieces. If you cannot name natural clusters, the pillar is probably too narrow or off-narrative. Fix the pillar before adding layers below. Cross-check internal link paths while you list gaps. If a page cannot send readers to a next step, capture a “link target needed” note so the topic owner knows what to build.

Extract Seeds From The KB (Entities And Claims)

Surface product and feature entities

Your Knowledge Base contains named features, subsystems, and nouns your sales team repeats. Build an entity sheet that captures the items you reference daily. Each entity can power multiple angles across different slots, which multiplies coverage without diluting the story.

Create a compact sheet for each entity:

• Feature or concept name
• Two supporting KB sources to cite
• The primary problem it solves
• The best-fit sitemap slot

Mine recurring claims worth teaching

List the statements you say on every call, like “deterministic pipeline” or “KB-grounded accuracy.” Claims with tension are magnetic because they challenge how readers currently work. Pair each claim with a counter-belief your audience holds so you can teach the difference later. Use exact KB phrasing to avoid drift when you draft.

Build a clean seed list

Combine entities and claims into one seed list with two or three citations and a likely sitemap slot. Keep it tight, because this list feeds your angle builder. If a seed cannot be grounded with citations, drop it. Publishability beats volume every time. This is where product truth becomes your topic engine, not external speculation.

Build Angles With The 7-Step Template

Use the 7-step angle template

Lock narrative logic before anyone writes. A simple template turns vague ideas into teachable angles that align with your brand’s point-of-view. Keep each element to one or two sentences so the angle stays scannable and easy to brief.

Fill these seven cues for every topic:

• Context
• Gap or problem
• Reader intent
• Motivation
• Tension
• Brand point-of-view
• Demand link

Write one quick example

Calibrate with a short example: Context, teams speed drafting. Gap, operations still manual. Intent, publish reliably. Motivation, cut rework. Tension, prompts versus system. Brand POV, pipeline over writer. Demand link, show how Topic to Publish runs without handoffs. This sets tone and depth for the rest of your angles and proves the seven-step angle template is practical.

Ready to eliminate manual topic wrangling and move straight from angle to brief? You can try using an autonomous content engine for always-on publishing.

Prioritize And Validate Without Analytics

Scoring checklist (rank fast, ship faster)

Rank topics in minutes using a simple 1–5 score across four dimensions, then sort by total:

• Editorial value: will a human care today
• KB grounding: citations ready and specific
• Publishability: briefable structure, clear H2s
• Internal links: obvious pillar and cluster targets

Add a pass or fail gate labeled “no traffic estimates.” If anyone argues volume, remind the group that this workflow is internal-asset-first. You can re-rank next quarter without changing how the work gets done today.

Rapid validation: evidence and quick-checks

Do a ten-minute evidence pass. Copy exact KB excerpts you plan to cite into the brief and flag any gaps for a subject matter expert. Then run a five-minute stakeholder quick-check. Ask only two questions: “Does this reflect our product truth?” and “Anything risky?” Capture a single go or no-go. Teams that skip this step often spend three to four hours fixing inaccuracies later. Validation is cheaper than rework.

Run The Workflow In Oleno (Productized Option)

Generate topics with Topic Research

If you want the system to handle the mechanical steps, run the same workflow in Oleno. Use Topic Research when you have a seed and expect 10–12 enriched topics with intent and angle cues. You still approve topics and choose narrative slots. The difference is that Oleno reads your sitemap and Knowledge Base, then structures the work automatically so you can focus on decisions.

Approve into Topic Bank and convert to briefs

Move approved topics into Topic Bank and reorder as needed. Convert each topic into a structured brief with H1, three to six H2s, internal link targets, and “claims requiring KB grounding.” The brief defines structure so the draft can be built without back-and-forth. Operate a weekly cadence, for example a one-hour session to seed and angle plus a 30-minute block to finalize approvals and brief conversions. When you want end-to-end execution, let the pipeline run from Draft to QA-Gate, to Enhancements, to Publish.

Want to see the entire pipeline without prompting or manual edits? You can Request a demo.

Conclusion

When your sitemap and Knowledge Base drive topic research, you remove guesswork, lock narrative consistency, and build internal links that compound. The hour you invest each week yields a queue of enriched, briefable topics tied to product truth rather than external noise. The seven-step angle template cuts rewrites and makes claims teachable. The scoring and validation pass prevents expensive fixes after publish.

If you prefer to operate this as a system, Oleno turns the same workflow into a governed pipeline. Topic Research generates enriched ideas, Topic Bank organizes approvals, structured briefs shape drafts, and QA-Gate enforces quality before publish. The transformation is simple: less coordination, more shipping, and content that always maps to what you sell.