Tech for Retail 2025 Workshop: From SEO to GEO – Gaining Visibility in the Era of Generative Engines

Back to blog

Semantic cocoon creation: the 7-step method, from scoping to measurement

SEO

Discover Incremys

The 360° Next Gen SEO Platform

Request a demo
Last updated on

1/11/2026

Chapter 01

Example H2
Example H3
Example H4
Example H5
Example H6

A cocoon is built before it is written. If the concept is still unclear, start with our semantic cocoon guide: definition, architecture and rules. This method shows how to create a semantic cocoon (often called a topic cluster in English) in 7 steps: scope, map intents, set the pillar → zoom architecture, write without cannibalisation, link, publish in batches and measure, then equip. Each step produces a deliverable: a written scope, an intent table, a brief, a linking plan and tracking by page group.

 

Step 1: scope the root topic, the out-of-scope and the owners

 

The most common trap is to start with a keyword list and keep expanding without control. You end up with similar pages, with no coherent coverage, competing for the same queries. Scoping reverses the order: first you decide what the cocoon covers, what it excludes and which page owns each notion, then you look for queries.

 

Write the scope as an editorial rule

 

A useful scope comes down to three decisions, recorded in a shared document before any writing starts:

 

  • Root topic: the central object of the cocoon (a method, an offer category, a recurring problem), broad enough to support multiple angles and sharp enough to fit in a single pillar.
  • Sub-topics: the natural branches of the topic (method, use cases, measurement, mistakes, implementation), which become zooms if they carry a distinct intent.
  • Out of scope: what you will not cover, or not yet, and the page on the site that already covers it.

 

Write these boundaries as a sentence any writer can apply: "we cover X for profiles Y, in contexts Z, and we exclude A and B, covered elsewhere". That one sentence prevents costly iterations: it settles in advance the topics that spill over.

 

Name one owner per sub-topic

 

An owner is the only page on the site that develops a notion. Other pages mention it in one or two sentences and link to it. Without this rule, every article re-explains the definition, the anchors or the measurement, and the cocoon ends up copying itself. The scope therefore lists, for each sub-topic, the page that owns it, including when that page sits outside the cocoon.

 

Step 2: map queries by intent

 

Listing queries is not about piling up similar phrasings; it is about identifying differences in expectations. The same expression can hide a need to understand, to evaluate or to act: the page is decided by search intent, not by the words. For each query, record three things:

 

  • The underlying question: what the reader wants to know or do.
  • The expected deliverable: a definition, a method, a comparison, a template.
  • The next step: the page the reader will want to read next, inside the cocoon or elsewhere.

 

Link each query to a page and a role

 

Applied to the queries on this topic on our own blog, the map looks like this:

 

QueryIntentPageRole
semantic cocoonUnderstand the concept and its principlesCocoon guidePillar (T0)
semantic cocoon definitionUnderstand the conceptCocoon guide (merged)Pillar (T0)
create a semantic cocoonTake action, step by step7-step methodZoom (T1)
semantic cocoon toolGet equipped to run the method7-step method (merged)Zoom (T1)
semantic cocoon exampleSee complete architecturesThree model cocoonsZoom (T1)
semantic cocoon diagramSee complete architecturesThree model cocoons (merged)Zoom (T1)

 

Six queries, three pages: half the phrasings do not justify their own URL. When a query carries strong commercial stakes, spot it at this step using high-intent keywords: it often deserves a dedicated zoom, placed close to your conversion page.

 

Apply the merge rule

 

The rule settles doubtful cases: if two queries call for the same outline, the same examples and the same call to action, that is one page. The second phrasing becomes a variant woven into the content or a FAQ question, not a new URL. The criterion is not "the texts look similar" but "does the reader expect the same thing?" If yes, one page carries the intent and internal linking converges on it.

 

Step 3: design the pillar and its zooms

 

Design the structure before you write. A simple diagram, with the levels and the main links, prevents two drifts: publishing on the fly and multiplying neighbouring pages that tread on each other. It also tells you where to place a new idea and which page to attach it to, so it does not end up orphaned.

 

Two levels, three at most

 

The pillar (T0) defines the topic, sets the rules and points to each zoom. Each zoom (T1) covers one complete intent. A second-level zoom (T2) only exists if part of a T1 carries a distinct intent that does not fit in its page. Here is the architecture of the cocoon this page belongs to:

 

LevelPageParentWhat it promises
T0 (pillar)Cocoon guideNoneThe definition, the architecture, the rules, what a cocoon does and does not deliver
T1 (zoom)7-step methodPillarThe sequence from scoping to measurement, with the deliverables of each step
T1 (zoom)Three model cocoonsPillarComplete architectures, link templates and where links go
T2 (zoom)None to dateA T1A case that does not fit in its T1 without unbalancing it

 

There is no magic number: a pillar carries as many zooms as there are distinct intents, typically 4 to 12. This cocoon has only two because the other queries were merged. To see the architecture applied to an online shop, a public body and a software publisher, see our semantic cocoon examples in tables.

 

For URLs, keep slugs consistent across the cocoon: the URL expresses the topic without over-optimisation, and pages within the same group are recognisable at a glance. This clarity helps maintenance as much as search engines.

 

Step 4: write pages that do not cannibalise each other

 

Two neighbouring pages rarely compete because of their keywords. They compete because they say the same thing. The brief is where you prevent that repetition, before writing, especially when several writers are involved. The starting test is simple: if you cannot sum up the page as "This page helps you…" without using "and", the angle is still too broad.

 

Add a "what not to say" section to the brief

 

A zoom brief contains the usual sections, plus one that sets the boundaries with neighbouring pages:

 

Brief sectionExpected contentWhat not to say
PromiseOne "This page helps you…" sentence, for whom, in what contextAnother zoom's promise, even rephrased
Intent and readerThe dominant intent, the profile, their starting questionSecondary intents that have their own page
H2/H3 outlineThe sections required, in the order the reader needs themAn outline identical to a neighbouring page's
Boundaries3 to 7 notions owned by another URL, with a link to eachFull development of those notions
ProofWorked examples, definitions, sourced and dated figuresUnsourced figures and invented cases presented as real
Links and call to actionThe pillar, useful siblings, one action consistent with the stageDecorative links to pages unrelated to the question

 

The title, meta description and heading hierarchy fall under general writing rules: the cocoon brief does not reinvent them, it adds the boundaries.

 

Link, rephrase or leave out

 

A page can mention a notion it does not own. It then gives a short definition, in two to four stable sentences, and links to the owner for the full development. For each neighbouring notion, the writer chooses between three moves:

 

  • Link when the reader changes goal: from understanding to comparing, from defining to implementing, from the overview to the specific case.
  • Rephrase briefly when the notion is only a prerequisite for following the page, without re-explaining its implications.
  • Leave out when the link adds nothing to the journey, even if the topic seems related.

 

If a paragraph could fit into several pages, treat it as a signal: either it belongs to an owner and should become a link, or the page is missing a distinctive angle.

 

Answer first, for the reader and for AI

 

A zoom that answers its question directly is also easier for answer engines to cite. At the time of writing, Google's AI Overviews and AI Mode are available in France. The structure of a citable zoom rests on a few rules:

 

  • a direct answer at the top of the page and at the top of key sections;
  • an explicit H2/H3 hierarchy, where each heading carries the question it answers;
  • lists and tables for steps, criteria and comparisons;
  • dated proof, and blocks that make sense without rereading everything above.

 

The list format is not a detail: 80% of pages cited by AI use lists (State of AI Search, 2025). To go further on this aspect, read our GEO content strategy method.

 

Step 5: link parent, children and siblings

 

Internal linking makes the architecture readable, for readers and for crawlers alike. In a cocoon, it comes down to five rules, to be written into every brief:

 

  • The parent links to all its children: the pillar points to each zoom, from the section that discusses it.
  • Each child links to its parent, within the first third of the page.
  • Siblings link to each other when the reader needs the other page to move forward, not on principle.
  • Anchors are descriptive: they say what the reader will find after the click, never "click here".
  • One link per destination page per article, and links outside the cocoon whenever they serve the reader.

 

No watertight silo, no internal nofollow, no link obfuscation and no page-by-page PageRank calculation: the cocoon organises reading, it does not try to hold on to authority. Link placement, anchors and orphan-page diagnosis are covered in our guide to internal linking and its rules.

 

Step 6: publish in batches and measure by page group

 

Publishing on the fly rarely produces a coherent cocoon: links arrive late, the pillar promises pages that do not exist yet, and results are hard to read. Publishing in batches, with deliberate dependencies, solves all three problems.

 

Fix the production order

 

The order is as follows: scope the pillar first (outline, scope, list of children), write the zooms, then finalise the pillar last. Scoping the pillar first keeps the zooms from drifting; writing it last stops it from copying everything its children develop. The table below breaks this sequence into batches:

 

BatchPagesWhat you measureWhen to read it
ScopingPillar outline, scope, list of zooms and their ownersThe baseline of the page group: clicks, impressions, position, AI citations per questionBefore publication
Batch 1Priority zooms, linked to the existing or upcoming pillarIndexing, impressions, new queries capturedA few weeks
Batch 2Remaining zooms, links between siblingsClicks and position by group, internal clicks between zoomsOne quarter
Batch 3The finalised pillar, linked to all its zoomsBefore / after for the full group, AI citations per questionThe following quarter

 

Measure the cocoon as a group, not URL by URL: in Google Search Console, filter the cocoon's pages and track the group's clicks, impressions and position; record AI citations separately, question by question. Progress after a batch is a correlation, never proof of causation: other factors move at the same time.

 

Decide page by page: create, optimise, merge, deindex

 

Each review of the results leads to a decision per page, taken with the group's signals:

 

  • Create when an important intent has no page, or shows up as impressions without clicks on queries no page covers.
  • Optimise when the page exists but plateaus: angle, proof, direct answer at the top, links received.
  • Merge when several URLs answer the same intent: keep the best one, integrate the useful parts, redirect the other.
  • Deindex or delete when a page has neither a clear intent nor value, with a redirect when a neighbouring page takes over the topic.

 

Alternate creation waves and optimisation waves, so you do not pile up new pages without consolidating the others. The chain of roles (writing, review, integration, approval) belongs to general organisation, described in our article on editorial content production.

 

Step 7: equip the process without multiplying tools

 

A tool does not make up for a poorly scoped perimeter. Start simple, with a spreadsheet and Search Console, instrument measurement, then add tooling when the volume of pages makes manual management fragile. Four functions matter:

 

  • Crawl and depth: a crawler finds orphan pages, broken links and pages buried too far from the pillar.
  • Query mapping: link queries, intents and pages, and see which URLs share the impressions of the same query.
  • Planning and briefs: organise batches, write briefs with their "what not to say" section, assign, review.
  • Tracking by page group: the cocoon's clicks, impressions and position in Google Search Console, journeys in Google Analytics 4, AI citations per question.

 

On WordPress, let dedicated pages (pillar and zooms) carry the topics and keep categories and tags for internal organisation, without giving them the role of reference pages. To choose among tool families without stacking them up, see our overview of SEO tools by use case.

 

Depending on your situation

 

The method is the same for everyone, but the entry point changes with your context:

 

  • You need to explain the concept to your team before starting: begin with the cocoon guide, linked in the introduction, for the definition and the rules.
  • You want to see a complete architecture before drawing yours: the three model cocoons in step 3 give one template per sector.
  • Your pages exist but are poorly linked: the internal linking guide in step 5 covers diagnosis and fixes.
  • Your briefs are ready and you are writing: apply the SEO writing rules for the title, meta and headings.
  • You are starting from a content-rich site: begin with an SEO audit of your existing content to spot duplicates and orphan pages.

 

To turn the intent table into a publishing plan, briefs and assigned batches, the Incremys editorial planning module centralises the plan, briefs, assignment and review.

 

FAQ: creating a semantic cocoon

 

Where do I start from scratch?

 

Start by writing the scope: the root topic, the sub-topics and what you exclude. Then list the queries, attach each one to an intent and apply the merge rule. The pillar outline comes next, with the list of zooms. Writing only starts once these three deliverables have been approved.

 

How do I proceed on a site that already has dozens of articles?

 

First map existing content by intent: pages that own a topic, duplicate pages, orphan pages. Merge and redirect the duplicates, then rebuild internal linking around a clear pillar. Only then create the missing pages. On a content-rich site, the first gains come from consolidation, not from new URLs.

 

Should the pillar be published before the zooms?

 

It should be scoped first, not finalised first. The pillar's outline, scope and list of children are fixed at the start. The zooms are written next, and the pillar is finalised last, when it can summarise and link to pages that are already differentiated instead of copying them.

 

What should I do when two pages in the cocoon compete for the same query?

 

Check whether the reader expects the same thing on both pages. If yes, merge: keep the stronger URL, integrate the useful content from the other and redirect it. If not, reposition one of the two on a distinct angle and add the other's notion to its "what not to say" section.

 

When can I tell whether a cocoon is working?

 

The first signals are impressions and new queries on the page group, a few weeks after each batch. Clicks and position for the group are read over a quarter, against the baseline. Bear in mind that progress remains a correlation: always compare the group before and after.

 

Can a zoom link to a page outside the cocoon?

 

Yes, whenever the reader needs it. A cocoon is not a watertight silo: when a notion belongs to a page elsewhere on the site, the zoom summarises it in a few sentences and links to its owner. The link to the pillar, however, remains mandatory in every zoom.

 

Do I need a dedicated tool to get started?

 

No. A spreadsheet, Google Search Console and a crawler are enough for a first cocoon: mapping, checking links and tracking the page group. A tool becomes useful when the number of pages, writers and batches makes manual tracking fragile and duplicates appear too late.

Discover other items

See all

Next-Gen GEO/SEO starts here

Complete the form so we can contact you.

The new generation of SEO
is on!

Thank you for your request, we will get back to you as soon as possible.

Oops! Something went wrong while submitting the form.