Architecture du site
Silo structure, hub and spoke, and topic clusters comparé — what's en réalité différent, ce que Google recommends, and pourquoi lien internes beat URL folders.
Langues
Architecture du site is the définir of crawlable discovery and navigation paths entre votre pages, plus supporting entry points comme sitemaps — it's pas the même chose as votre URL folders. Silo, hub and spoke, and topic clusters are overlapping practitioner étiquettes pour que structure, pas documented Google categories — hub and spoke and topic clusters share the même underlying pattern plus que ils genuinely differ. Google's documented minimum is a crawlable lien to every page vous care à propos de; que supports discovery, it doesn't guarantee exploration, indexation, ranking, trafic, sitelinks, or AI citations. Aucun Google source exige banning liens entre topic areas — evaluate strict-silo rules contre utilisateur navigation and relevance, pas assumed authority mechanics. Ce que matters is contextual maillage interne, pas URL folders.
Evidence for this claim Google uses links to discover pages and as a relevance signal, so crawlable internal navigation supports discovery and understanding. Scope: Current Google internal-link guidance. Confidence: high · Verified: Google Search Central: Link best practices Evidence for this claim Google recommends navigation paths from menus to categories and subcategories to products, with direct links to important pages. Scope: Current Google ecommerce site-structure guidance, broadly applicable to hierarchical sites. Confidence: high · Verified: Google Search Central: Ecommerce site structureTL;DR — Architecture du site is the crawlable network of liens entre votre pages — pas simplement votre URL folders. The goal is simple: every important page devrait have a lien pointing to it, and connexe pages devrait lien to chaque autre. You’ll hear three noms pour organizing que network — silos, hub and spoke, and topic clusters — they’re overlapping practitioner étiquettes pour roughly the même idea, pas three separate systems. None of ce guarantees rankings or trafic by itself — it’s ce que rend pages findable and understandable. Google likes a pyramid: home page at the top, broad category pages in the middle, spécifique articles at the bottom.
Ce que architecture du site is
Architecture du site is the network of crawlable liens que connects votre pages —
the paths moteur de recherches (and readers) utiliser to découvrir and déplacer entre les —
plus supporting entry points comme an XML sitemap. It’s pas the même chose as votre
URL folders: une page’s chemin (/blog/category/post/) doesn’t by itself establish
où que page sits in the architecture. It’s the difference entre a tidy
library où every book has a shelf and a sign pointing to it, and a pile of
books on the floor.
It matters pour search pour two raisons:
- Discovery. Moteur de recherches trouver pages mainly by suivant standard
<a href>liens from pages ils déjà know à propos de. Si nothing liens to une page, it’s hard pour Google to trouver it at tout. - Context. Quand une page liens to un autre with relevant words autour the lien, it helps Google comprendre ce que the lié page is à propos de.
Discovery isn’t the finish line, though — une page being lié and crawlable doesn’t guarantee it obtient indexé or ranks. Architecture obtient vous trouvé and understood; it doesn’t promise an outcome past que.
The three models you’ll hear à propos de
- Silo structure — vous split votre content into separate topic “silos” and garder chaque silo’s pages linking mostly to chaque autre. The old, strict version dit jamais lien entre silos.
- Hub and spoke — un broad overview page (the hub) liens out to a définir of detailed pages (the spokes), and chaque spoke liens back to the hub.
- Topic clusters — a “pillar” page covers a big topic, and “cluster” pages cover the plus petit subtopics, tout interlinked.
Here’s the partie la plupart guides bury: hub and spoke and topic clusters décrire the même underlying structure. Un nom came from library/information-architecture personnes; the autre was popularized by HubSpot in 2017 as a content-marketing idea. None of ces three are Google-documented categories — they’re practitioner étiquettes with overlapping implementations, pas an official taxonomy. I’ll expliquer que plus in the Avancé version.
Ce que en réalité matters
Vous don’t besoin to pick a brand nom. Vous besoin:
- A clair hierarchy: home page → category/hub pages → spécifique pages.
- Every important page lié from au moins un autre page (aucun “orphans”) — Google’s propre documentation puts it plainly: every page vous care à propos de devrait have a lien from au moins un autre page on votre site.
- Réel
<a href>liens, pas click-only navigation Google can’t reliably follow. - Connexe pages linking to chaque autre with descriptive lien text.
- Nothing important buried so deep que robots d’exploration struggle to reach it.
None of ce is a guarantee of exploration, indexation, or ranking — it’s ce que rend a page reachable and legible in the premier placer.
The chose la plupart personnes obtenir incorrect
Vous don’t have to éviter linking entre sections. Aucun Google source exige banning liens entre topic areas. The strict silo rule — “jamais lien entre silos” — trades away liens que voudrait genuinely aider readers navigate and aider Google comprendre the destination page, pour the sake of a rule que isn’t documented anywhere. Judge cross-links by si they’re relevant and utile to a reader, pas by si ils cross a silo boundary. The valuable idea from silos is grouping connexe content ensemble, pas walling it off.
Vouloir the deeper version — how popularité des liens flows, flat vs. deep hierarchies, and quand chaque model fits — switch to the Avancé tab.
Evidence for this claim Google uses links to discover pages and as a relevance signal, so crawlable internal navigation supports discovery and understanding. Scope: Current Google internal-link guidance. Confidence: high · Verified: Google Search Central: Link best practices Evidence for this claim Google recommends navigation paths from menus to categories and subcategories to products, with direct links to important pages. Scope: Current Google ecommerce site-structure guidance, broadly applicable to hierarchical sites. Confidence: high · Verified: Google Search Central: Ecommerce site structureTL;DR — Silo, hub and spoke, and topic clusters are overlapping practitioner étiquettes, pas documented Google architecture categories — but ils converge on un structure Mueller has décrit favorably: a pyramid / top-down hierarchy. Hub and spoke and topic clusters share the même underlying pattern plus que ils genuinely differ — un comes from information architecture, the autre from HubSpot’s 2017 content-marketing rebrand. The partie of silo thinking worth keeping is topical concentration of lien internes; the partie to drop is the strict “no cross-silo links” rule — aucun Google source exige it, so judge cross-links by relevance and utilisateur navigation à la place. Ce que Google leans on is maillage interne and context, pas URL folder structure. Garder hierarchies reasonably shallow, lien connexe pages à travers clusters quand it’s relevant, and remember architecture enables outcomes comme topical authority and AI-search visibility — it doesn’t guarantee les, and it can’t rescue contenu pauvre.
Pourquoi SEOs argue à propos de ce at tout
Architecture du site is un of ceux topics où three communities invented overlapping vocabularies and alors spent fifteen années insisting leur word was the réel un. I’ve spent six-plus années at Ahrefs on the product side autour Site Audit, looking at ce que site structures en réalité regarder comme in explorer données à travers a huge number of sites — and the gap entre the dogma and ce que fonctionne is wide. So let me essayer to collapse the confusion.
Là are three named models:
- Silo structure — content grouped into isolated thematic sections. The strict interpretation (popularized by Bruce Clay) prohibits cross-silo lien internes to garder chaque silo’s “link equity” concentrated.
- Hub and spoke — a broad overview hub page liens out to detailed spoke pages, qui lien back. The hub is parfois appelé a pillar page.
- Topic clusters — HubSpot’s 2017 framing: a pillar page targets a broad keyword, cluster pages target long-tail subtopics, everything interlinked.
The clarification I’ll plant my flag on
None of “silo,” “hub and spoke,” or “topic cluster” is a Google-documented architecture category. They’re practitioner étiquettes, and En pratique leur implementations overlap heavily. “Hub and spoke” is the older information-architecture term: a central overview page linking to detailed subtopic pages with reciprocal liens. “Topic clusters” is HubSpot’s 2017 content-marketing rebrand of essentially que même pattern — a pillar page plus interlinked cluster content. “Pillar page” is simplement the marketing word pour the hub. Appel les flatly identical overstates it — HubSpot’s framing leans plus on planned topical coverage as a content strategy, pendant que “hub and spoke” is older, plus general information-architecture vocabulary — but si you’re choosing how to structure liens, you’re solving the même problem soit façon: a central page, detailed subtopic pages, and reciprocal liens entre les.
And une fois vous autoriser cross-silo liens — qui nothing Google has publié indique vous pas to — a “silo” is a hub-and-spoke cluster En pratique. So the three noms mostly converge on un workable structure: grouped, hierarchical, internally lié, with sensible cross-links. Treat les as overlapping vocabulary pour que structure, pas as three competing systems to choisir entre.
Ce que Google en réalité recommends
Google’s recommendation is a pyramid / top-down hierarchy: the home page covers the broadest topic, category/hub pages sit in the middle, and spécifique content pages live at the bottom. John Mueller put the pourquoi plainly: the top-down approach or pyramid structure “helps us a lot plus to comprendre the context of individual pages dans le site.” That’s the payoff — structure isn’t a ranking trick, it’s how Google figures out ce que chaque page is à propos de and how pages relate.
Worth noting: Google uses the term “hub page” in its propre documentation — describing how “a hub page, such as a category page, links to a new blog post” pour discovery. So the hub-and-spoke framing isn’t an SEO invention; it’s Google’s propre language.
Lien internes beat Structure d’URL
Ce is the unique la plupart misunderstood partie of architecture. A lot of silo advice is
really à propos de URL folders — putting /category-a/ pages sous un chemin and
forbidding liens to /category-b/. But Google focuses on maillage interne
signals, pas URL chemin segments. Mueller has repeatedly noted que some SEOs
over-focus on Structure d’URL; Google fonctionne out hierarchy from how pages lien to chaque
autre, pas from folder noms.
The implication is big: une page at /blog/technical-seo/site-architecture/ signals
nothing to Google au-delà ce que its content and inbound liens dire à propos de it. Logical
URLs are bon pour humans and pour managing le site — but ils aren’t the
architecture. The lien graph is the architecture. Ce is aussi pourquoi “virtual
silos” (concentrating liens by topic regardless of folder) fonctionner fine, and pourquoi
strict “physical silos” (folder-based isolation with aucun cross-links) buy vous explorer
and UX problems pour aucun offsetting benefit.
Google’s documentation is spécifique à propos de ce que counts as a lien it peut reliably
follow: a standard <a href> element with a resolvable URL. Navigation construit
seulement from JavaScript click handlers or non-standard markup doesn’t obtenir vous the
même reliable discovery chemin, aucun matter how clean votre Structure d’URL semble. Obtenir
the crawlable-link contract correct premier — folder naming is secondary.
Où strict silos go incorrect
The legitimate insight in silo thinking is topical concentration — grouping connexe content and linking generously dans a topic area genuinely helps readers navigate and helps Google comprendre ce que une page is à propos de. The échec mode is the strict rule: jamais lien entre silos. Aucun reviewed Google source exige que prohibition — so judge it on its propre terms, pas as an assumed authority mechanic:
- it empêche natural, contextually relevant liens readers voudrait benefit from,
- it hurts UX by dead-ending utilisateurs at artificial silo boundaries, and
- une page peut encore be relevant to plus que un topic area, and a lien que helps a reader trouver it shouldn’t be blocked parce que it crosses a étiquette vous drew.
Shari Thurow has been making ce point pour années (“stop the silo madness”), and Ahrefs’ propre contrarian prendre (Joshua Hardwick’s “why it makes no sense”) lands in the même placer. Garder the concentration; drop the wall — and faire the appel fondé on si a lien genuinely sert the reader and the destination page, pas on unverified claims à propos de how strictly Google weighs isolation.
Flat vs. deep hierarchies
Two échec modes at the extremes:
- Aussi flat — everything un click off the home page. Popularité des liens and topical signal obtenir diluted; the home page can’t meaningfully vouch pour hundreds of equal children, and vous lose the topical grouping que helps context.
- Aussi deep — pages importantes nombreux clicks from home. Mueller’s framing: going aussi deep “rend it harder pour us to explorer and harder pour us to réussir the signals autour.” Deep pages tend to obtenir crawled moins and inherit moins internal authority. Google hasn’t publié a spécifique click-depth number; don’t treat quelconque fixed count as a requirement — the correct depth dépend on votre site’s size and how distinct its categories are, qui is its propre topic (voir the flat vs. deep and crawl-depth deep dives in ce cluster pour the fuller decision framework).
The target is a shallow hierarchy with strong contextual linking: garder pages importantes reachable in as few hops as votre site’s scale reasonably permet, grouped into hubs, with cross-links où topics genuinely relate. Ce is the même crawl-depth concern que montre up whenever you’re auditing how far bots have to travel to reach votre money pages.
Ce que maillage interne en réalité fait
Architecture’s réel job is shaping the lien interne graph. Three choses to obtenir correct:
- Linkability. Every important page devrait have a lien from au moins un autre page — ideally several. Google’s propre guidance is explicit à propos de ce minimum. Pages with aucun inlinks are harder to trouver and harder to rank, but a lien doesn’t guarantee soit outcome.
- Context. The words avant and après a lien, and the anchor text itself, peut aider personnes and Google comprendre ce que the target is à propos de. Ce is how a hub “explains” its spokes — it’s pas a promise of a spécifique ranking effect.
- Concentration. Linking densely dans a topic cluster puts relevance signals où ils belong — the kernel of truth silos were toujours reaching pour. Si que concentration translates into something practitioners appel “topical authority” isn’t something Google documents directement; treat it as a reasonable hypothesis worth testing on votre propre site, pas a guaranteed mechanism.
Ce site is a live exemple. patrickstox.com runs a pillar → cluster → article →
sub-article hierarchy à travers a few hundred pages, en utilisant pillar, cluster,
clusterSelf, subcluster, and subsubcluster taxonomy — and it deliberately
cross-lists articles à travers clusters (the alsoIn pattern) plutôt que walling
les off. That’s hub-and-spoke with intentional cross-linking: exactly the model I’m
describing, pas a strict silo.
Quand to utiliser qui model
Honestly? Construire the hub-and-spoke / topic-cluster structure and arrêter worrying à propos de the étiquettes:
- Pick a pillar/hub topic with réel breadth and search demand.
- Identifier the subtopics que have leur propre demand — ceux become spokes.
- Interlink hub ↔ spokes and spoke ↔ spoke où relevant.
- Cross-link to autre clusters quand the context is genuinely connexe.
There’s aucun magic number of cluster pages per hub. The correct count is cependant nombreux distinct subtopics with réel demand exist — pas an arbitrary target of 5, 10, or 30. Wikipedia is the canonical exemple: broad overview pages linking deeply to detailed subtopic pages, tout densely interlinked, aucun silo walls anywhere.
Architecture and AI search
AI Overviews and AI assistants utiliser requête fan-out — ils decompose a question into multiple connexe sub-queries. The reasonable hypothesis, pas a documented guarantee: a site with organized, interlinked coverage à travers a topic’s subtopics has a meilleur chance of surfacing à travers plus of ceux sub-queries, since plus of the subtopics are covered by a findable, crawlable page. I haven’t seen controlled evidence isolating architecture as the causer ici, so treat it as something to tester on votre propre content plutôt que an established mechanism. Gary Illyes’ public position is que AI search optimization nécessite normal SEO — well-structured, crawlable, high-quality content — pas a special architecture. The structure que déjà sert traditional search is the même un you’d construire pour AI search; there’s aucun separate playbook.
Auditing votre architecture
A practical réussir, mostly with explorer données:
- Trouver orphans — pages with aucun lien internes in. Explorer le site (Ahrefs Site Audit, Screaming Frog) and regarder pour zero-inlink pages.
- Trouver over-deep pages — important URLs buried nombreux clicks from home; aucun fixed number is the rule, but si explorer données montre les getting crawled moins, dig in.
- Map topics and trouver hub candidates — clusters of connexe pages manquant a central overview.
- Run an internal-link gap analysis — connexe pages que devrait lien to chaque autre but don’t.
The honest caveat
Architecture is infrastructure, pas a ranking shortcut. It enables exploration, contrôle how popularité des liens flows, and helps engines comprendre context — but a beautiful hub-and-spoke structure wrapped autour thin, low-value content encore won’t rank. Illyes has noted it’s rare to voir two results from un domain in a SERP; structure sert content quality and relevance, it doesn’t substitute pour les. Obtenir the structure correct so que bon content peut do its job — that’s the whole point.
The neighboring topics in ce cluster — how lien internes réussir signals, how explorer depth affecte discovery, and faceted navigation on grand sites — tout plug into the même architecture decisions covered ici.
AI summary
A condensed prendre on the Avancé version:
- Architecture du site = the crawlable lien graph, pas l’URL folders. It shapes discovery and how clearly Google understands chaque page’s context — it doesn’t guarantee exploration, indexation, ranking, or AI citations by itself.
- Three practitioner étiquettes, un overlapping structure. Silo, hub and spoke, and topic clusters aren’t Google-documented categories; ils converge on a pyramid / top-down hierarchy, qui Mueller has décrit favorably: the pyramid structure “helps us a lot plus to comprendre the context of individual pages.”
- Hub and spoke and topic clusters mostly overlap. Même underlying pattern, différent communities — IA term vs. HubSpot’s 2017 content-marketing rebrand. “Pillar page” is simplement the marketing word pour the hub.
- Drop strict silos. The valuable bit is topical concentration of liens; aucun Google source exige the “never link between silos” rule, and it hurts UX.
- Lien internes > Structure d’URL. Google fonctionne out hierarchy from liens, pas chemin segments; Mueller has said SEOs over-focus on Structure d’URL.
- Garder it shallow, but don’t chase a fixed number. Google hasn’t publié a click-depth threshold; aussi deep hurts exploration and signal flow, aussi flat dilutes topical signal.
- Aucun magic cluster count. Cover the subtopics with réel demand; Wikipedia is the model.
- AI search nécessite normal SEO (Illyes) — organized, interlinked coverage is a reasonable hypothesis pour helping with requête fan-out, pas a documented guarantee.
- Architecture is infrastructure, pas a ranking shortcut — it can’t rescue thin content.
Documentation officielle
Primary-source guidance from the moteur de recherches on structure, liens, and hierarchy.
- In-Depth Guide to How Recherche Google Fonctionne — URL discovery via liens, and Google’s propre utiliser of “hub page” / category-page language.
- Crawlable liens — Faire votre liens crawlable — every important page devrait be lié from au moins un autre page; liens doit be
<a href>; anchor text and surrounding context pour understanding lié pages. - Importance of Lien Architecture (2008) — Google’s long-standing guidance que lien interne structure shapes PageRank flow and perceived page importance.
Bing / Microsoft
- Bing Webmaster Guidelines — a clair, flat, crawlable structure; reasonable lien internes; heading hierarchy (H1/H2/H3); submit sitemaps.
Quotes from the source
On-the-record statements from Google. Où the source page supports it, chaque lien is a deep lien que jumps to the quoted passage.
John Mueller, Google — on hierarchy / pyramid structure
- “The top-down approach or pyramid structure helps us a lot more to understand the context of individual pages within the site.” — John Mueller, on site structure. Coverage (Moteur de recherche Journal) · Coverage (Moteur de recherche Roundtable)
John Mueller, Google — on Structure d’URL vs. lien internes
- Mueller has cautioned que some SEOs over-focus on URL/folder structure; Google relies on maillage interne to comprendre hierarchy, pas URL chemin segments. Coverage (Moteur de recherche Roundtable)
John Mueller, Google — on explorer depth
- “I don’t think it would always have a negative effect. I do think if you make it too deep, then that makes it harder for us to crawl and harder for us to pass the signals around.” — John Mueller, on deep page hierarchies.
Recherche Google Central docs — on discovery via hub pages
- “Other pages are discovered when Google extracts a link from a known page to a new page: for example, a hub page, such as a category page, links to a new blog post.” Jump to quote
Recherche Google Central docs — on linkability
- “Every page you care about should have a link from at least one other page on your site.” Jump to quote
Gary Illyes, Google — on crawlability and AI search
- “MAKE THAT DAMN SITE CRAWLABLE.” — Gary Illyes (Reddit AMA), underscoring que discoverability via liens is the priority over quelconque spécifique architecture brand.
- Illyes has said AI search optimization exige seulement normal SEO — well-structured, crawlable, high-quality content — with aucun special architecture changements nécessaire.
Site-architecture checklist
A réussir to confirmer votre structure helps exploration, context, and lien flow:
- Clair top-down hierarchy: home page → hub/category pages → spécifique pages.
- Every important page is lié from au moins un autre page (aucun orphans).
- Pages importantes aren’t buried needlessly deep (aucun fixed click-depth rule — vérifier explorer données pour pages getting crawled moins as ils obtenir deeper).
- Chaque topic area has a hub/pillar page que liens to its subtopic pages.
- Subtopic pages lien back to leur hub and to relevant sibling pages.
- Cross-cluster liens exist où topics are genuinely connexe (aucun strict silo walls).
- Lien internes utiliser descriptive anchor text with relevant surrounding context.
- Aucun important page relies on click-only navigation — liens are réel
<a href>. - Structure d’URL is logical pour humans, but you’re pas relying on folders to signal architecture (liens do que).
- Explorer données reviewed pour over-deep pages, orphans, and internal-link gaps.
The mental models
1. The lien graph IS the architecture. URL folders are pour humans and housekeeping. Google fonctionne out hierarchy and context from how pages lien to chaque autre. Audit and design the lien graph, pas the folder tree.
2. Three noms, un structure. Silo, hub and spoke, topic clusters → tout converge on a grouped, hierarchical, internally lié pyramid une fois vous autoriser sensible cross-links. Arrêter shopping pour the “right” model; construire the cluster and lien it bien.
3. Garder the kernel, drop the wall. From silos, garder topical concentration (lien densely dans a topic). Drop the isolation rule (jamais lien entre silos) — aucun Google source exige it, and it hurts utilisateurs.
4. The depth dial. Aussi flat dilutes topical signal; aussi deep starves pages of exploration and lien authority. Google hasn’t publié a click-depth number, so aim pour shallow-with-strong-linking judged contre votre propre explorer données, grouped into hubs, plutôt que a fixed target.
5. Architecture is a multiplier, pas a source. Bon structure multiplies the valeur of bon content by making it discoverable and contextually clair. Multiply zero (contenu pauvre) and vous encore obtenir zero.
Architecture model référence
| Model | Utile idea | Mistake to éviter | Practical implementation |
|---|---|---|---|
| Pyramid | Broad pages lead to increasingly spécifique pages | Burying pages importantes aussi deep | Home → hub/category → detail page |
| Hub and spoke | A central overview organizes connexe subtopics | Linking seulement outward from the hub | Hub ↔ spokes, plus relevant spoke liens |
| Topic cluster | Content coverage is planned autour a subject | Treating the étiquette as a différent architecture model | Utiliser the même hub-and-spoke graph |
| Silo | Connexe pages recevoir concentrated topical liens | Forbidding every cross-topic lien | Garder topical grouping; autoriser utile cross-links |
Ce que chaque couche devrait do
| Couche | Principal job | Audit question |
|---|---|---|
| Home | Route utilisateurs and robots d’exploration into major areas | Are le site’s réel priorities represented? |
| Hub or category | Expliquer the groupe and lien to its members | Peut every important spoke be reached? |
| Detail page | Satisfy a spécifique intent and reinforce its context | Fait it lien back and to genuinely connexe pages? |
| Cross-link | Connecter connexe nécessite à travers groupes | Voudrait a reader naturally follow it? |
Testez vos connaissances: Architecture du site
Five rapide questions on silos, hubs, clusters, and ce que Google en réalité recommends. Pick an réponse pour chaque, alors vérifier.
Ressources utiles
My connexe writing
- The Beginner’s Guide to SEO technique — où architecture du site and maillage interne fit in the bigger picture.
- Lien internes pour le SEO: An Actionable Guide — how lien internes réussir signals and shape the lien graph que is votre architecture.
- SEO Silo Structure: Pourquoi It Rend Aucun Sense — the Ahrefs contrarian prendre on strict silos (the cas pour dropping the wall).
- How to Construire a Topic Cluster — the practical hub-and-spoke / cluster construire, step by step.
My speaking
- How Search Fonctionne (SlideShare) — my walkthrough of exploration, rendering, indexation, and ranking, the pipeline architecture has to serve. (Standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)
From autour the industry
- Arrêter the Silo Madness: Effective Architecture du site pour le SEO and Findability (Shari Thurow, Moteur de recherche Land) — the definitive cas contre strict silos.
- Architecture du site pour le SEO: Structure Que Ranks & Scales (Moteur de recherche Land) — a thorough structure guide.
- Complet Guide to Topic Clusters (Moteur de recherche Land) — the cluster model in depth.
- Topic Clusters: The Suivant Evolution of SEO (HubSpot) — the 2017 origin of the “topic cluster” terminology.
- SEO Content Strategies: The Hub and Spoke Model (Botify) — the même structure sous its information-architecture nom.
- John Mueller Recommends Pyramid Site Structure (Moteur de recherche Journal) — the source pour the pyramid/context quote.
Journal des modifications
Mis à jour le 18 juil. 2026.
Résumé éditorial et détails enregistrés des changements.Détails des changements
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
Comparaison complète indisponible — aucun instantané antérieur n’a été archivé pour cette révision.