How it works
Five parts, one shared vocabulary.
Topicweave starts with your vocabulary: 30 to 60 terms in your own words. The other four parts are built on it: connected work, topic pages, an insights library and a connective layer. Tag a piece of content once and it shows up everywhere it belongs.
Your visitors never see the weave. They just notice that every page leads somewhere useful.
A shared vocabulary
Your terms, in six categories.
Connected work
“This project demonstrates” on every project.
Topic pages
One page per idea, built from its definition.
An insights library
Evergreen answers, organized by theme.
The connective layer
Dense links and structured data.
01 · The threads
A shared vocabulary, in your words.
About 30 to 60 terms that describe what you do. We draft it with you as a strawman; you keep, cut or rename. It takes about half an hour to review, and it’s the one sign-off everything else waits on.
- Who you helpWho is it for?
- Professional firms, clinics, family businesses
- ServicesWhat can I hire you for?
- Service design, onboarding redesign, client portals
- How it worksHow do you do it?
- Journey mapping, staff workshops, prototyping
- What you watch forWhat do you worry about that others don’t?
- Client handoffs, accessibility, staff time
- IdeasHow do you think about the field?
- Client onboarding, trust at first contact
- Known forWhat should people ask for you by name?
- Plain-language UX, service design
“Service design” sits in two categories on purpose. The terms that come up in more than one category are usually the ones you own.
02 · Connected work
Your work becomes evidence.
Every project is tagged to the vocabulary and shows a “This project demonstrates” section, one row per category, each linking to its topic page. Your portfolio becomes proof for the things you say you’re good at, one tagged project at a time.
- Who we helpClinics
- How we workJourney mapping
- IdeasClient onboarding
Empty rows simply don’t show.
03 · Topic pages
Writing the definition creates the page.
One page per important idea: a clear definition in your voice, then the work that proves it and the writing that explains it. These are the pages people land on when they ask “what is…” or “who does…”.
Together they’re topic clusters that grow every time you publish: each new piece joins its topic pages on its own, with no audit to redo.
Example topic page · How we work
Journey mapping
Walking every step a client takes, with the people who serve them, before anything is redesigned.
- The definitionIn your voice, from the vocabulary
- Where we’ve applied it3 projects
- Related reading4 articles
04 · The insights library
A library, sorted by question.
Evergreen pieces that each answer one real question, organized by theme so the best answer never sinks under last month’s news. It launches with 8 to 10 strong pieces, drafted in your voice with the Voice Kit and approved by you.
- How we workWhat a journey map is really for
- For new clientsThe first 30 days decide the next three years
- Behind the workWhy handoffs fail on Friday afternoons
- AnswersHow long does a redesign take?
05 · The connective layer
The same fields, read by machines.
Dense links between projects, topics and articles, plus structured data (JSON-LD) written into each page’s HTML from the fields you already fill in, so crawlers can read it without running scripts. It updates on publish.
Taxonomies, internal links and structured data aren’t new on their own. Keeping them in sync across articles, projects, services and FAQs, every time you publish, is the work.
- Name→
headline - Related topics→
about · DefinedTerm - Short definition→
description - FAQs→
FAQPage - Site settings→
Organization · sameAs
{
"@type": "Article",
"headline": "Onboarding is a design problem",
"about": [{ "@type": "DefinedTerm", "name": "Client onboarding" }],
"description": "Why the first 30 days matter most",
"hasPart": { "@type": "FAQPage", "mainEntity": […3 questions] },
"publisher": { "@type": "Organization", "sameAs": […LinkedIn, YouTube] }
}
On Webflow? Check what your own pages tell machines today. It’s free and reads public pages only.
How we measure it
Three signals, grouped by your topics.
We don’t sell a rank tracker, and nobody controls what an assistant cites. What we can show is what happened, in your own vocabulary.
Search Console, by topic
The searches that show your pages, credited to the topics those pages are tagged with.
Visits sent by assistants
A cookieless counter notes arrivals from ChatGPT, Perplexity, Claude and Gemini. No personal data; it undercounts and says so.
A monthly assistant sample
Your clients’ questions, asked of four assistants, saved word for word. A baseline before launch, then checks over time.
Changes made through the Topicweave app are compared against similar pages left untouched, so a report shows what actually moved. About the app