1/11/2026
These semantic cocoon examples (topic clusters, in the usual English term) show the pages and linking of three types of site: e-commerce, institutional and software. An example reads better as a table than as a definition, and all three are explicitly fictional: a hiking gear shop, a public body and a B2B software publisher. For each, a table gives the pages, intents, parents and links, then the decisions. The definition and general rules stay in the semantic cocoon guide; this page shows them applied.
How to read a cocoon example
Each row in the tables below is one page, and each page answers a single question. The "Level" column gives its role: T0 for the pillar, T1 for a zoom, T2 for a zoom of a zoom, kept for cases where a T1 would otherwise become unreadable.
The "Intent" column states the question the page answers, in the sense of search intent. The "Parent" and "Outgoing links" columns form the structure: which page links to it, and which pages it links to in its body, with at most one link per destination page.
All three examples apply the same rule: one topic, one pillar, zooms, one owner per sub-topic, parent → children → siblings linking, measured by page group. From one example to the next, only three things change: the nature of the pillar, the place of commercial or service pages, and the architecture model.
Example 1: an e-commerce cocoon, "hiking backpack"
Take a fictional online shop selling hiking gear. Its "hiking backpack" cocoon starts from the category page, which acts as the pillar, and has seven editorial zooms. Product pages are not a level of the cocoon: they receive links from the zooms that help readers choose.
The pages and their links
The following table serves as both the site tree and the linking structure:
What this cocoon decides
The category page carries the generic query and the purchase intent: it keeps a short introduction that points to the zooms, without containing the buying guide. The guide, capacity and carrying system live in the editorial part of the site, and each has a single owner.
"Best hiking backpack" and "how to choose a hiking backpack" call for the same outline, the same examples and the same call to action: they are merged into the buying guide.
Boots, poles and route planning sit outside the cocoon: they are other topics, with their own pillar, linked once when the reader needs them. For the rules specific to categories and product pages, see e-commerce SEO.
Annotated anchors
Three links show how the anchor carries the information:
- Pillar → capacity zoom: "choose your pack capacity for the length of your outing", in the category introduction.
- Carrying system zoom → pillar: "see all hiking backpacks", after the adjustment section.
- Buying guide → carrying system zoom: "adjust the carrying system before your first outing", a link between siblings that follows the reading order.
Example 2: an institutional cocoon, "grant application"
Imagine a fictional public body that awards grants to associations and businesses. Its "grant application" cocoon starts from a process page and splits the rest by audience and by step. Its service pages (application form, user account) stay outside the cocoon and receive links.
The pages and their links
Here is the site tree, read as a linking structure:
What this cocoon decides
Each rule has a single owner: the list of documents appears only in the "supporting documents" zoom, the timescales only in the "timescales" zoom. The other pages link to them, which avoids three versions of the same list drifting apart at the first regulatory update. Each zoom shows the date it was last checked, because an administrative rule is always read as of a given date.
The cocoon also settles three boundary questions:
- Information and service: the form and the user account remain service pages, linked from the pillar and the submission zoom.
- Zooms by audience: they exist only because conditions and documents differ between associations and businesses; otherwise, they would be folded into the eligibility zoom.
- News: dated calls for projects link to the pillar without entering the cocoon.
Example 3: a B2B software cocoon, "project management"
The last fictional case: a project management SaaS publisher. Its "project management" cocoon lives on the blog, with one pillar, six T1 zooms and one T2 zoom. The product page receives a link from the pillar without being part of the editorial site tree.
The pages and their links
The following table shows the only three-level example:
What this cocoon decides
The blog informs and the product page sells: the pillar sends it a single link, at the point where the reader moves from "understanding" to "getting equipped". The zooms do not each link to it: their call to action follows the reader's maturity (read the next zoom, get a template).
"Agile method" and "agile methods" call for the same outline: they stay in the methods zoom. The backward schedule becomes a T2, because its intent (doing) differs from that of the templates (getting one).
This cocoon also aims for AI citability, with three writing choices:
- each zoom opens with a direct answer of two to four sentences to the question in its title;
- the Kanban or Scrum comparison fits in a criterion-by-criterion table;
- project portfolio management stays outside the cocoon: it will have its own pillar, linked once from the T0.
Annotated anchors
Three links show the logic chosen:
- Pillar → product page: "manage your projects in a single tool", after the section on stages, never in the introduction.
- Methods zoom → comparison: "compare Kanban and Scrum criterion by criterion", a link between siblings for the reader who is undecided.
- Templates zoom → T2: "build your backward schedule step by step", placed under the backward schedule template.
The 3 architecture models and when to choose them
The three examples do not draw the same structure. The table compares the three models used:
Applied to the examples, the e-commerce cocoon is a star with links between siblings, the institutional cocoon combines a star with a chain for the steps (documents, submission, timescales), and the software cocoon is hybrid, with a single T2. In all three cases, depth stays at two levels (three at most), and the number of zooms follows the number of distinct intents.
Where to place links in the page
The structure says where to point; the page says where to put the link. In all three examples, links are distributed as follows:
- Introduction: a link to the parent, to place the page in the cocoon from the first lines.
- Body: links to siblings and zooms, at the moment the question arises, for example after a paragraph that opens an alternative.
- "Depending on your situation" block: three to six links, to siblings or out-of-cocoon pages, each described by the reader's situation.
- End of page: a single action, towards a conversion or service page.
Two rules apply everywhere: one link per destination page per article, and no automated list of related content that nobody reviews.
Mistakes seen in cocoon structures
The structures we correct most often share the same flaws:
- Three needless levels: a T1 that only lists its T2s adds a click with no synthesis; remove it or turn it into a real zoom.
- Orphan zooms: a page with no link from the pillar stays invisible; the pillar links to all its children.
- A pillar that copies its zooms: it should summarise each zoom in one or two sentences and link to it.
- Two pages for one intent: same outline, same examples, same call to action; merge, redirect, then align the links.
- Identical anchors everywhere: repeated, a phrase no longer says anything; each anchor describes what the reader will find.
Adapting these examples to your case
None of the three cocoons can be copied as is. They show a way of reasoning that you apply to your topic, your intents and your existing pages.
On a topic you have not covered yet
The starting point depends on the type of site. The table sums up what the three examples suggest:
In every case, scope the pillar first (scope, list of zooms, owner of each sub-topic), write the zooms, then finalise the pillar last, when it can summarise what exists.
On a site that already has pages on the topic
The process starts from what exists rather than from a blank page:
- designate as the pillar the page that ranks best for the generic query;
- attach each existing page to an intent, and merge those that answer the same one;
- redirect the merged URLs to the page you keep and update the links;
- track the cocoon as a page group in Google Search Console (clicks, impressions, position), before and after each batch.
Depending on your situation
To go further, choose the page that matches your stage:
- You are starting a topic from scratch: follow the steps to create a semantic cocoon, from scoping to publishing in batches.
- You want detailed rules on links: read the principles of internal linking.
- You need to choose which topics to treat as a cocoon: start from your editorial strategy.
- You need to plan the production of the zooms: draw on an editorial plan example.
Before drawing the table for your own cocoon, you need to know which intents deserve a page. The Incremys opportunity analysis module helps you choose the intents to cover and estimate, for each one, the likelihood of gains.
FAQ: semantic cocoon examples
How many zooms are there in these examples?
Seven zooms for the e-commerce cocoon, seven for the institutional cocoon, and six T1s plus one T2 for the software cocoon. These numbers are not a target: they follow from the number of distinct intents identified for each topic. Another topic might need four or twelve, provided each zoom answers a question the others do not cover.
Do you need a cocoon for every e-commerce category?
No, only for categories that raise real questions before purchase. A category whose customers already know what to buy does not need editorial zooms: a good category page is enough. A cocoon is justified when several distinct intents (choosing, sizing, maintaining) come before or after the purchase and each calls for its own page.
Does an institutional website need a cocoon?
Yes, as soon as a process varies by audience, by step or by rule. Above all, the cocoon prevents the same regulatory information from being repeated across several pages and drifting apart at the first update. For a simple process that fits on one clear page, a cocoon adds nothing more.
Where does the product page go in a software cocoon?
Outside the editorial site tree, with a link from the pillar. The pillar mentions it at the point where the reader moves from understanding to getting equipped. The zooms do not systematically link to it: their role is to answer a specific question, and their call to action follows the reader's maturity rather than the offer.
Star or chain?
A star suits independent zooms, a chain suits a reader who must follow a set order. Most cocoons combine the two: a star around the pillar, and a short chain between the zooms that describe successive steps. In every case, the pillar links directly to each of its zooms.
Are these examples taken from real websites?
No, all three cocoons are fictional and built for illustration. The page titles, intents and links are plausible, but none describes an existing website or comes with measured results. Their value lies in showing complete architecture decisions that you can test against your own queries and pages.
Should you redo the table when you add a page?
Yes, every new page goes into the table first, with its intent, its parent and its links. If its intent overlaps with that of an existing page, enrich that page instead of creating a new one. The table thus remains the shared reference when several writers work on the same cocoon.
.png)
.jpeg)

.jpeg)
%2520-%2520blue.jpeg)
.avif)