Topical Map Template With a Real Worked Example: Ten Rows From Our Own Map
A topical map template is the row structure of a topical map with no rows filled in. This article fills it with the complete, live Holistic Radar topical map, version 2, dated 7 October 2026, the map this site is built from. It covers the template fields, the framework foundation row, and the attribute filtration verdicts. It then publishes ten rows explained field by field, all 31 core rows, all 55 outer rows, and the bridge from every outer node to the core. It closes with the 17-node launch batch, the 60-day publication schedule, the nine corrections version 2 made to version 1, and the questions teams ask about templates.
What a topical map template contains
A topical map template is a fixed set of columns, one row per accepted attribute, that turns an entity’s query network into a list of pages.
The template has 15 schema fields, set out in full in what is a topical map. Version 2 adds four production fields that record how each row becomes a page:
| Field group | Fields | Example value |
|---|---|---|
| The attribute | Attribute, source queries, volume | Semantic SEO – Topical Map |
| Classifications | Structural class, competitive class, section, predicate, contextual vector | Node, root, core, Rank, procedural |
| Filtration verdicts | Prominence verdict, relevance verdict | Prominent, relevant |
| Position | Priority rank, URL slug, parent, internal link targets, bridge target | P2, /services/semantic-seo/topical-maps/, /services/semantic-seo/ |
| Version 2 production fields | Raw pair, processed title tag, zone class, status | Topical Map Production: Entities, Attributes and Intent |
The raw pair is the entity and attribute before any wording decision. The processed title tag is the pair verbalised with a conjunctive “and”, a plural set, or a hypernym and its hyponyms. The zone class records section and level together. The status records the production stage, from architecture to published.
A blank template takes an hour to reproduce. A populated row takes far longer, because every row needs a harvested query network, a filtration verdict and a section decision. The template is free. The rows are the work.
Whose map this is, and why it is published
The map below is the Holistic Radar topical map for the central entity Semantic SEO, and this site is built from it row for row.
Agencies publish blank templates. Holistic Radar publishes its own populated map for two reasons. First, a populated map shows what a finished row costs, which a blank grid hides. Second, a published map is a checkable claim: every URL in the tables below resolves on this site, and every title tag matches the live page.
Version 2 was rebuilt against the full course text and the Master Handbook. Version 1 was built from lessons dictated one at a time, and the corrections between the two are logged at the end of this article.
The framework foundation row
The framework foundation is the one row that every other row inherits: one central entity, one source context, one pair of functional predicates, and three attribute classes.
| Field | Value |
|---|---|
| Central entity | Semantic SEO |
| Entity class | SEO methodology. The instance is Holistic Radar, and attribute classes are measured against the class. |
| Source context | A consultancy paid to turn search visibility into revenue through three service clusters: Visibility, Conversion, and Demand and Retention |
| Central search intent | Semantic SEO plus the source context: growing organic and AI search visibility into revenue |
| Functional predicates | Know: understand, define, audit, measure. Rank: map, build, publish, rank. |
| Sitewide n-gram boundary | semantic SEO, topical map, query network, topical authority, content network, cost of retrieval |
| Unique attributes | Radar Scan, Holistic Authority Score, Six-Layer Pyramid, Semantic Instruments, AI Confidence |
| Root attributes | Semantic SEO definition, topical maps, query research, content network, technical SEO, copywriting, proof of results |
| Rare attributes | AI search optimization, citation readiness, cost of retrieval engineering |
| Deploy order | Unique, then root, then rare |
| Expansion vectors | Depth in the core, vastness in the outer section, momentum through patternless publishing |
A unique attribute identifies one instance of the class and nothing else. Every provider of semantic SEO has topical maps. Only Holistic Radar has the Six-Layer Pyramid, so the pyramid carries information gain and takes the strongest home page headings.
Attribute filtration: which candidates earned a URL
Attribute filtration is the test every candidate passes before it earns a row: prominence, popularity and relevance to the source context.
| Candidate attribute | Prominent | Popular | Relevant | Verdict |
|---|---|---|---|---|
| Topical map | Yes | High | Yes | Core node and outer node |
| Semantic SEO definition | Yes | High | Yes | Home page and /learn/semantic-seo/ |
| Query network | Yes | Low | Yes | Kept standalone as a service node and a quality node |
| AI search optimization | No | High | Yes | Secondary core seed |
| Topical vs domain authority | No | High | Yes | Outer node |
| SEO salaries, jobs and courses | No | High | No | Rejected: dilutes the source context |
| Link building tactics | No | High | No | Rejected: outside the source context |
Rejected rows stay in the map. A rejected row records a decision, and that decision stops the attribute from reappearing in a later brief. Popularity values are estimates until keyword data confirms them.
Ten rows explained, field by field
The ten rows below cover every zone class in the map, and each one shows the decision its fields record.
| # | Raw pair | Slug | Zone and attribute class | The decision the row records |
|---|---|---|---|---|
| 1 | Semantic SEO – Overview | / | Root anchor | The home page holds the central search intent in its H1. Nothing else competes for it. |
| 2 | Holistic Radar – Scanner Audit | /method/radar-scan/ | Core seed, unique | The first unique attribute takes the first home page H2. |
| 3 | Holistic Radar – Map Framework | /method/six-layer-pyramid/ | Core seed, unique | The method that produces the map sits one click from the root. |
| 4 | Semantic SEO – Service | /services/semantic-seo/ | Core seed, root | The flagship service owns four nodes, the deepest seed in the map. |
| 5 | Semantic SEO – Query Network | /services/semantic-seo/query-research/ | Core node, rare | Low popularity, kept standalone because it is a quality node. |
| 6 | AI Search – Citations | /services/ai-search/citations/ | Core node, rare | A rare attribute gets a node only under a seed that already carries it. |
| 7 | Web Development – Service | /services/web-development/ | Core seed, adjacent | Adjacent services stay flat and receive traffic only through justified bridges. |
| 8 | Semantic SEO – YMYL | /industries/ymyl/ | Core node | Industries are nodes of the root, not seeds, so they inherit the central entity. |
| 9 | Topical Map – Definition | /learn/topical-map/ | Outer node, root | The outer node defines. The core node sells. Both exist, and neither cannibalizes the other. |
| 10 | Holistic Authority Score – Definition | /learn/authority-score/ | Outer node, unique | A unique attribute in the outer section carries information gain no competitor holds. |
The full core section: 30 rows
The core section is Semantic SEO plus the source context, and it runs three levels deep: root, seed and node.
| Node | Raw pair | Processed title tag | Slug | Zone class | Priority |
|---|---|---|---|---|---|
| Home | Semantic SEO – Overview | Semantic SEO Agency: Topical Maps, AI Search and Copywriting | / | Root anchor | P1 |
| Radar Scan | Holistic Radar – Scanner Audit | Radar Scan: Semantic SEO Audit and Authority Score | /method/radar-scan/ | Core seed, unique | P1 |
| Six-Layer Pyramid | Holistic Radar – Map Framework | Six-Layer Pyramid: Topical Map Architecture and Layers | /method/six-layer-pyramid/ | Core seed, unique | P1 |
| Semantic Instruments | Holistic Radar – Analysis Toolkit | Semantic Instruments: Query Network and Attribute Analysis | /method/semantic-instruments/ | Core seed, unique | P1 |
| AI Confidence | Holistic Radar – AI Extraction Method | AI Confidence: Extractable Answers for AI Search | /method/ai-confidence/ | Core seed, unique | P1 |
| Semantic SEO | Semantic SEO – Service | Semantic SEO Services: Topical Maps and Content Networks | /services/semantic-seo/ | Core seed, root | P1 |
| Topical Map Production | Semantic SEO – Topical Map | Topical Map Production: Entities, Attributes and Intent | /services/semantic-seo/topical-maps/ | Core node | P2 |
| Query Network Research | Semantic SEO – Query Network | Query Network Research: Queries, Entities and Intent | /services/semantic-seo/query-research/ | Core node, rare | P2 |
| Content Network Build | Semantic SEO – Content Network | Semantic Content Network Build: Core, Outer and Bridges | /services/semantic-seo/content-network/ | Core node | P2 |
| Semantic SEO Audit | Semantic SEO – Audit | Semantic SEO Audit: Symptoms, Causes and Fixes | /services/semantic-seo/audits/ | Core node | P2 |
| AI Search Optimization | AI Search – Service | AI Search Optimization: Citations and Answer Extraction | /services/ai-search/ | Core seed, rare | P1 |
| AI Search Citations | AI Search – Citations | AI Search Citations: Becoming a Source for Answer Engines | /services/ai-search/citations/ | Core node, rare | P2 |
| Technical SEO | Technical SEO – Service | Technical SEO Services: Crawling, Indexing and Speed | /services/technical-seo/ | Core seed, root | P1 |
| Crawl and Indexation | Technical SEO – Indexation | Crawl Budget and Indexation: Technical SEO Fixes | /services/technical-seo/indexation/ | Core node | P2 |
| Conversion Copywriting | Copywriting – Service | Conversion Copywriting: Semantic Copy for Search and Sales | /services/conversion-copywriting/ | Core seed, root | P1 |
| Semantic Copy | Copywriting – Semantic Copy | Semantic Copywriting: Facts, Entities and Microsemantics | /services/conversion-copywriting/semantic-copy/ | Core node | P2 |
| Web Development | Web Development – Service | SEO Web Development: Speed, Structure and Crawlability | /services/web-development/ | Core seed, adjacent | P2 |
| Retrieval Cost Engineering | Web Development – Retrieval Cost | Cost of Retrieval Engineering: Rendering, Markup and Speed | /services/web-development/retrieval-cost/ | Core node, rare | P3 |
| CRO and Analytics | CRO – Service | CRO and Analytics: Conversion Tracking and Testing | /services/cro-analytics/ | Core seed, adjacent | P3 |
| Paid Media | Paid Media – Service | Paid Media Management: Search, Social and Retargeting | /services/paid-media/ | Core seed, adjacent | P3 |
| Email and Lifecycle | Email – Lifecycle Service | Email and Lifecycle Marketing: Automation and Retention | /services/email-lifecycle/ | Core seed, adjacent | P3 |
| Ecommerce | Semantic SEO – Ecommerce | Semantic SEO for Ecommerce: Category and Product Topical Maps | /industries/ecommerce/ | Core node | P2 |
| SaaS | Semantic SEO – SaaS | Semantic SEO for SaaS: Feature, Use Case and Integration Maps | /industries/saas/ | Core node | P2 |
| YMYL | Semantic SEO – YMYL | Semantic SEO for YMYL Sites: Trust, Expertise and Consensus | /industries/ymyl/ | Core node | P2 |
| Local | Semantic SEO – Local | Local Semantic SEO: Service Areas, Entities and Reviews | /industries/local/ | Core node | P2 |
| Professional | Semantic SEO – Professional Services | Semantic SEO for Professional Services: Authority and Leads | /industries/professional/ | Core node | P2 |
| Case Studies | Holistic Radar – Results | Semantic SEO Case Studies: Results and Page Counts | /case-studies/ | Core seed, root | P2 |
| PropXpro | Case Studies – PropXpro | PropXpro Case Study: A 216-Page Semantic Content Network | /case-studies/propxpro/ | Core node, unique | P2 |
| Vital Transportation | Case Studies – Vital Transportation | Vital Transportation Case Study: 400+ Pages Built | /case-studies/vital-transportation/ | Core node, unique | P2 |
| BuraqTech | Case Studies – BuraqTech | BuraqTech Case Study: A 38-Cluster Semantic SEO System | /case-studies/buraqtech/ | Core node, unique | P2 |
| Team | Holistic Radar – Team | Holistic Radar Team: Semantic SEO Experts and Credentials | /team/ | Core seed, root | P2 |
Priority follows distance from the central entity. P1 pages define the entity. P2 pages are its nodes. P3 pages are the adjacent services that sit furthest from it.
The full outer section: 55 flat nodes
The outer section is Semantic SEO plus the Know predicate, and every outer node is one definitive page at /learn/ with no sub-pages.
| Article | Raw pair | Slug | Attribute class |
|---|---|---|---|
| Learn semantic SEO hub | Semantic SEO – Learn | /learn/ | Outer anchor |
| What Is Semantic SEO | Semantic SEO – Definition | /learn/semantic-seo/ | Root |
| What Is a Topical Map | Topical Map – Definition | /learn/topical-map/ | Root |
| Topical Map vs Topic Cluster | Topical Map – Comparison | /learn/topic-cluster/ | Root |
| How to Build a Topical Map | Topical Map – Process | /learn/map-building/ | Root |
| Topical Map Template (this article) | Topical Map – Template | /learn/map-template/ | Root |
| What Is a Query Network | Query Network – Definition | /learn/query-network/ | Rare |
| Why Declaring Order First Changes What Gets Extracted | Extractive Summary – Order | /learn/declared-order/ | Rare |
| How to Write a Content Brief | Content Brief – Process | /learn/content-brief/ | Root |
| The Ten Question Types | Questions – Types | /learn/question-types/ | Rare |
| Building a Semantic Content Network | Content Network – Process | /learn/content-network/ | Root |
| Content Cannibalization | Content – Cannibalization | /learn/cannibalization/ | Root |
| Content Gap Analysis | Content Gap – Analysis | /learn/gap-analysis/ | Root |
| Internal Linking Architecture | Internal Linking – Architecture | /learn/internal-linking/ | Root |
| How to Lower Cost of Retrieval | Cost of Retrieval – Reduction | /learn/retrieval-cost/ | Rare |
| How to Run a Semantic SEO Audit | Semantic SEO – Audit | /learn/seo-audit/ | Root |
| The Holistic Authority Score | Holistic Authority Score – Definition | /learn/authority-score/ | Unique |
| Topical Authority vs Domain Authority | Topical Authority – Comparison | /learn/topical-authority/ | Root |
| Semantic SEO and AI Search | Semantic SEO – AI Search | /learn/ai-search/ | Rare |
| Entity SEO | Entity SEO – Resolution | /learn/entity-seo/ | Root |
| Semantic Search | Semantic Search – History | /learn/semantic-search/ | Root |
| How AI Answers Choose Sources | AI Search – Sources | /learn/ai-optimization/ | Rare |
| Search and AI Crawlers | Crawlers – AI Bots | /learn/crawlers/ | Rare |
| Featured Snippets | Featured Snippets – Formats | /learn/featured-snippets/ | Rare |
| Structured Data | Structured Data – Schema | /learn/structured-data/ | Root |
| E-E-A-T | E-E-A-T – Trust Signals | /learn/eeat/ | Root |
| Helpful Content | Helpful Content – Evaluation | /learn/helpful-content/ | Root |
| Anchor Text | Anchor Text – Meaning | /learn/anchor-text/ | Root |
| Canonical Tags | Canonical Tags – Duplicates | /learn/canonical-tags/ | Root |
| Technical SEO Checklist | Technical SEO – Checklist | /learn/technical-checklist/ | Root |
| JavaScript SEO | JavaScript SEO – Rendering | /learn/javascript-seo/ | Rare |
| Core Web Vitals | Core Web Vitals – Speed | /learn/web-vitals/ | Root |
| How Search Engines Rank Pages | Ranking – Retrieval and Re-Ranking | /learn/ranking/ | Rare |
| Microsemantics | Microsemantics – Sentence Rules | /learn/microsemantics/ | Rare |
| Conversion Copywriting Frameworks | Copywriting – Frameworks | /learn/copywriting-frameworks/ | Root |
| Conversion Rate Optimization | CRO – Tests | /learn/conversion-optimization/ | Adjacent |
| Paid vs Organic Search | Paid Search – Comparison | /learn/paid-organic/ | Adjacent |
| Email Lifecycle Stages | Email Lifecycle – Stages | /learn/lifecycle-stages/ | Adjacent |
| Semantic Markup | Semantic Markup – Markup roles | /learn/semantic-markup/ | Root |
| Historical Data in SEO | Historical Data – Time records | /learn/historical-data/ | Rare |
| Information Gain | Information Gain – Added value | /learn/information-gain/ | Rare |
| Holistic SEO | Holistic SEO – Whole-site frame | /learn/holistic-seo/ | Unique |
| YMYL SEO | YMYL SEO – High-stakes topics | /learn/ymyl-seo/ | Root |
| Semantic Keywords | Semantic SEO – Keywords | /learn/semantic-keywords/ | Root |
| Semantic Analysis for SEO | Semantic SEO – Analysis | /learn/semantic-analysis/ | Rare |
| Semantic SEO Strategy | Semantic SEO – Strategy | /learn/semantic-seo-strategy/ | Root |
| Semantic SEO Tools | Semantic SEO – Tools | /learn/seo-tools/ | Root |
| Semantic SEO Examples | Semantic SEO – Examples | /learn/semantic-seo-examples/ | Root |
| How to Use Python for NLP and Semantic SEO | Semantic Analysis – Python Method | /learn/python-semantic-seo/ | Rare |
| Semantic Triples | Page Semantics – Triples | /learn/semantic-triples/ | Root |
| Entity Gap | Content Gap – Entity Gap | /learn/entity-gap/ | Rare |
| Source Context | Topical Map – Source Context | /learn/source-context/ | Root |
| Central Entity and Central Search Intent | Topical Map – Central Entity | /learn/central-entity/ | Root |
| Topical Relevance | Topical Authority – Relevance | /learn/topical-relevance/ | Root |
| Lexical Semantics | Page Semantics – Word Relations | /learn/lexical-semantics/ | Root |
| Contextual Vector | Page Semantics – Direction | /learn/contextual-vector/ | Root |
The first 17 rows are the planned outer nodes. The next 19 extend the outer section to the retrieval, trust and adjacent attributes buyers research before they hire. The last five rows are the later additions: the history, information gain, holistic SEO, YMYL, and markup nodes. The five practice and proof nodes that follow them are semantic keywords, semantic analysis, semantic SEO strategy, semantic SEO tools, and semantic SEO examples. The three adjacent rows are single bridge pages, not clusters, because Web Development, CRO, Paid Media and Email sit outside the entity’s own neighbourhood.
Bridges from every outer node to the core
A bridge is valid only when its justification passage names the concept that connects the outer page to the core page.
| Outer node | Bridges to | Justification |
|---|---|---|
| /learn/semantic-seo/ | /services/semantic-seo/ | Knowing what semantic SEO is raises who builds it |
| /learn/topical-map/ | /method/six-layer-pyramid/ | The data structure leads to the method that produces it |
| /learn/topic-cluster/ | /services/semantic-seo/topical-maps/ | The comparison leads to the service that builds the map above every cluster |
| /learn/map-building/ | /services/semantic-seo/topical-maps/ | Nine steps and four failure modes lead to wanting them done right |
| /learn/map-template/ | /method/six-layer-pyramid/ | Real rows are proof of the method |
| /learn/query-network/ | /services/semantic-seo/query-research/ | Knowing the signals leads to needing the network built |
| /learn/declared-order/ | /services/conversion-copywriting/semantic-copy/ | Summary order is a writing rule, so the writing service applies it |
| /learn/content-brief/ | /method/semantic-instruments/ | Field provenance leads to the toolkit that establishes it |
| /learn/question-types/ | /method/semantic-instruments/ | The question inventory comes from the same analysis |
| /learn/content-network/ | /services/semantic-seo/content-network/ | Sequencing and pace lead to the network actually built |
| /learn/cannibalization/ | /services/semantic-seo/audits/ | Cannibalization is a symptom an audit separates from its cause |
| /learn/gap-analysis/ | /services/semantic-seo/topical-maps/ | Gaps close through nodes added to a map |
| /learn/internal-linking/ | /services/web-development/ | Link architecture is implemented in the site build |
| /learn/retrieval-cost/ | /services/web-development/retrieval-cost/ | Lowering the cost is engineering work on the page |
| /learn/seo-audit/ | /method/radar-scan/ | Separating symptoms from causes is what the scan does |
| /learn/authority-score/ | /method/radar-scan/ | Understanding the score leads to wanting the site’s own number |
| /learn/topical-authority/ | /services/semantic-seo/ | Domain authority fails where topical coverage succeeds |
| /learn/ai-search/ | /services/ai-search/ | What transfers to AI search leads to the AI-specific service |
| /learn/entity-seo/ | /method/ai-confidence/ | An entity that resolves cleanly is one an answer engine can quote, and the method builds that confidence |
| /learn/semantic-search/ | /services/semantic-seo/query-research/ | How search reads meaning leads to the query network that expresses it |
| /learn/ai-optimization/ | /services/ai-search/citations/ | Source selection is the step a citation service targets |
| /learn/crawlers/ | /services/technical-seo/indexation/ | What a crawler fetches decides what gets indexed |
| /learn/featured-snippets/ | /method/ai-confidence/ | A lifted answer is an extractable answer, which the method builds |
| /learn/structured-data/ | /method/ai-confidence/ | Schema consistency is one input to AI confidence |
| /learn/eeat/ | /team/ | Trust signals belong to a named source, so the reader meets the experts |
| /learn/helpful-content/ | /services/conversion-copywriting/ | What Google rewards is a page that answers, and copywriting produces the answer |
| /learn/anchor-text/ | /services/semantic-seo/content-network/ | Anchors are assigned when the network is built |
| /learn/canonical-tags/ | /services/technical-seo/ | Duplicate control is a technical SEO fix |
| /learn/technical-checklist/ | /services/technical-seo/ | The checklist is the repair order the service runs |
| /learn/javascript-seo/ | /services/web-development/retrieval-cost/ | Rendering cost is lowered in the build |
| /learn/web-vitals/ | /services/web-development/ | Speed is engineered, not configured |
| /learn/ranking/ | /services/semantic-seo/audits/ | Re-ranking rewards responsiveness, and an audit measures it page by page |
| /learn/microsemantics/ | /services/conversion-copywriting/semantic-copy/ | Sentence rules are applied by the semantic copywriting service |
| /learn/copywriting-frameworks/ | /services/conversion-copywriting/ | Frameworks answer the buyer, and the service writes them |
| /learn/conversion-optimization/ | /services/cro-analytics/ | Tests that start from the query need tracking to read |
| /learn/paid-organic/ | /services/paid-media/ | Paid media fills demand while organic coverage compounds |
| /learn/lifecycle-stages/ | /services/email-lifecycle/ | Lifecycle stages turn first visits into repeat revenue |
| /learn/semantic-markup/ | /services/web-development/retrieval-cost/ | Markup is the first control on parsing overhead, and the engineering lowers it |
| /learn/historical-data/ | /services/semantic-seo/audits/ | A site’s recorded history is the evidence an audit reads to separate symptoms from causes |
| /learn/information-gain/ | /method/radar-scan/ | What a page adds beyond the index is judged against its class, and the scan measures the site against that class |
| /learn/holistic-seo/ | /method/six-layer-pyramid/ | A whole-site frame is the dependency model of six layers that the pyramid sets out |
| /learn/ymyl-seo/ | /industries/ymyl/ | High-stakes topics lead to the industry page that serves them |
| /learn/semantic-keywords/ | /services/semantic-seo/query-research/ | Keywords are the output of query research, and the network groups them |
| /learn/semantic-analysis/ | /services/semantic-seo/topical-maps/ | An analysis of the entities and terms on existing pages is the first step of coverage planning, which the production service carries out |
| /learn/semantic-seo-strategy/ | /services/semantic-seo/content-network/ | A strategy is executed as a content network |
| /learn/seo-tools/ | /method/semantic-instruments/ | A tool is only as good as what it measures, and the toolkit measures queries and attributes |
| /learn/semantic-seo-examples/ | /case-studies/ | A worked example leads to results at scale |
| /learn/python-semantic-seo/ | /services/semantic-seo/query-research/ | The scripts lead to the service that runs them on client queries |
| /learn/semantic-triples/ | /services/conversion-copywriting/semantic-copy/ | Sentence-level facts lead to the service that writes every client sentence as one |
| /learn/entity-gap/ | /services/semantic-seo/audits/ | Page-level gaps lead to the audit that lists them for every page |
| /learn/source-context/ | /method/six-layer-pyramid/ | The framing component leads to the method whose first layer it is |
| /learn/central-entity/ | /services/semantic-seo/topical-maps/ | Both components lead to the service that sets them before any row |
| /learn/topical-relevance/ | /method/radar-scan/ | The relevance measure leads to the scan that scores coverage |
| /learn/lexical-semantics/ | /services/conversion-copywriting/semantic-copy/ | Word relations lead to the service that writes one name per concept |
| /learn/contextual-vector/ | /services/semantic-seo/content-network/ | The planning concept leads to the build that gives every URL one vector |
Outer pages link to the core generously. Each core page links back to at most one outer node, and only where a definition is needed.
The 17-node quality launch batch
A quality node launch batch is the set of core pages published together on day one, sized at 15 to 20 for a new domain.
| # | Page | Slug |
|---|---|---|
| 1 | Radar Scan | /method/radar-scan/ |
| 2 | Six-Layer Pyramid | /method/six-layer-pyramid/ |
| 3 | Semantic Instruments | /method/semantic-instruments/ |
| 4 | AI Confidence | /method/ai-confidence/ |
| 5 | Semantic SEO | /services/semantic-seo/ |
| 6 | Topical Map Production | /services/semantic-seo/topical-maps/ |
| 7 | Query Network Research | /services/semantic-seo/query-research/ |
| 8 | Content Network Build | /services/semantic-seo/content-network/ |
| 9 | Semantic SEO Audit | /services/semantic-seo/audits/ |
| 10 | AI Search Optimization | /services/ai-search/ |
| 11 | AI Search Citations | /services/ai-search/citations/ |
| 12 | Technical SEO | /services/technical-seo/ |
| 13 | Crawl and Indexation | /services/technical-seo/indexation/ |
| 14 | Conversion Copywriting | /services/conversion-copywriting/ |
| 15 | Semantic Copy | /services/conversion-copywriting/semantic-copy/ |
| 16 | PropXpro | /case-studies/propxpro/ |
| 17 | Vital Transportation | /case-studies/vital-transportation/ |
Every page in the batch sits one click from the home page. Every fact carries one value across all 17 pages, because a conflict between two pages loses the citation to both.
The 60-day publication schedule
The publication schedule runs 60 days from architecture to momentum, at 3 to 4 pages a week after launch.
| Days | Phase | Work |
|---|---|---|
| 1 to 5 | Architecture | Source context, central entity, raw and processed map, distilled URL taxonomy |
| 6 to 12 | Briefs | Competitor dissection by structural vector, the 17 quality nodes selected, briefs written |
| 13 to 25 | Assignment and staging | Drafts reviewed against the microsemantic standards and staged with original visuals |
| 26 | Launch | The 17 quality nodes published together, home page links verified |
| 27 to 60 | Momentum | Irregular batches of outer nodes, industries and adjacent seeds, crawl frequency watched in server logs |
No batch goes live during an active core update. Batch sizes stay irregular, so the publication history shows no synthetic pattern.
What version 2 corrected in version 1
Version 2 of the map corrected nine assumptions version 1 made, and every correction is logged so the map’s reasoning stays auditable.
| Version 1 assumption | What the course says | Applied in version 2 |
|---|---|---|
| Unique attribute means proprietary | Unique means specific to one instance of the class | Methods and the Holistic Authority Score reclassified as unique |
| Outer section has hubs and sub-pages under a blog path | Outer nodes are flat: one definitive page each | Flat nodes at /learn/ |
| Predicates must be Knowing, Going, Living | Domain pairs such as Know and Go are valid | Know and Rank kept as the domain pair |
| Cost of retrieval is described by six stages and five layers only | The course gives a formula, 8 responsiveness dimensions and R4 | Formula, dimensions and R4 added beside the six stages and five layers, article titles unchanged |
| Ten question types come from the course | Not in the supplied course text | Treated as Holistic Radar’s own framework |
| Query class forwarding | Not in the supplied course text | Dropped in favour of justified contextual bridges |
| Quality nodes are low-volume attributes | Quality nodes sit near the top, 15 to 20 launched together | 17-node launch batch and a 60-day schedule |
| Services above methods on the home page | Unique attributes take the top heading weight | Methods placed before services |
Topical map template versus topical map production
A topical map template is the empty structure. Topical map production is the service that fills it for one subject, with the query network harvested and every row filtered.
Teams with an analyst and time can fill this template themselves. Teams without them commission topical map production, delivered to the same fields and published to the same standard as the map above.
The rows above are the output of one method applied end to end, scored layer by layer from source context to revenue. → Topical map architecture
Topical map template questions
How many rows does a complete topical map have?
A complete topical map has one row per accepted attribute. The Holistic Radar map has 31 core rows and 55 outer rows, plus the rejected rows that record each discard.
Is a spreadsheet or a database better for a topical map?
A spreadsheet suits maps under a few hundred rows. A database suits larger maps, because bridges and anchor counts are queries across rows.
Does a local business need a different template?
A local business uses the same template with one added field: the service area each row serves. Multi-location sites add one row per location and attribute pair.
Does the template need a search volume column?
The template needs a popularity estimate, not a volume figure. Popularity decides filtration. Volume changes monthly and never decides on its own whether a row exists.
Topical Map Template With a Real Worked Example in the semantic SEO topical map
Topical Map Template With a Real Worked Example is the worked example attribute of semantic SEO, the central entity of the Holistic Radar topical map, and sits in the outer section under the Know predicate.
The outer section holds the page because the page teaches the concept without a direct sale, so internal link equity flows from it to Six-Layer Pyramid, since real rows are proof of the method.
→ What Is a Topical Map: the schema behind each of the ten rows
→ How to Write a Content Brief: the document that turns one row into one page