Koray Topical Map Construction

What a Topical Map Actually Is

A topical map is NOT a list of keywords grouped by topic. That is a concept map. A real topical map changes how the search engine perceives the source. Each node (row/tab) represents one web page and contains: entity + attribute pair (raw), processed title tag (verbalized), URL structure, image URL and alt tag, content brief reference, and publication date for momentum planning.

Five Core Components

1. Central Entity — The main entity that appears in every article across the entire site. Example: "Germany" for a visa site, "Water" for a health site. All content must connect back to this entity.

2. Source Context — Who you are, how you make money, your brand identity. This defines the Core Section. Example: "Visa consultancy" + "Germany" = Core Section is "Germany Visa."

3. Central Search Intent — The overarching purpose behind all user queries on the site. NOT the obvious action (taking a visa) but the deeper intent (visiting, knowing, learning, traveling to Germany). Must appear at the top of main content using predicates like "know" and "go."

4. Site-wide N-grams — Central Entity + Central Search Intent create repeating phrases across the entire site, training the search engine on the site's primary topic.

5. Quality Nodes — Standout articles (usually from the Core Section) that sit close to the homepage, create a strong first impression, and encourage deeper crawling.

Topical Map Architecture

Core Section (Inner)

• Comes from unifying Central Entity + Source Context
• Monetization section — goes deep on a specific attribute
• Example: All Germany visa types (D-type, C-type, tourist, work permit, job seeking, immigration)
• Quality nodes live here

Outer Section

• Comes from Central Entity + the "know" component of Central Search Intent
• Flat, not deep — many attributes at surface level
• Provides historical data, more sessions, more queries
• Proves topical relevance to the central entity
• Links to Core Section
• Example: Germany religion, climate, politics, geography, crime rate, culture

Supplementary Section

• Non-core entities and attributes
• Supports outer section context
• Does not require deep coverage

Node Types

| Type | Role | Depth | |------|------|-------| | Quality Node | Strong first impression, close to homepage | Highest | | Core Node | Monetization, attribute-deep | High | | Outer Node | Context, broad attributes | Medium | | Supplementary Node | Supporting context | Low |

URL Structure (Information Tree)

URLs must mirror the topical hierarchy:

• domain.com/core-section/attribute/
• domain.com/outer-section/attribute/

Flat URL structures signal flat topical organization. Deep hierarchies signal depth of coverage.

Building the Map: Step-by-Step

1. Identify the Central Entity for the site
2. Define Source Context (who you are + how you monetize)
3. Extract Central Search Intent — what is the deepest "why" behind user queries?
4. Enumerate all attributes of the Central Entity (root, rare, unique)
5. Assign each attribute to Core or Outer section
6. Create one node per attribute per section
7. Structure nodes as: Entity + Attribute → Processed Title → URL → Brief reference
8. Identify Quality Nodes (3-5 highest-impact articles)
9. Build publication schedule following momentum rules (patternless cadence)

Anti-Patterns

• Building a concept map and calling it a topical map
• No central entity (every article has a different primary entity)
• Core and Outer sections mixed in the same URL structure
• Quality nodes buried deep in the URL hierarchy
• Publishing all articles at once in alphabetical batches

Cross-References

• Use koray-semantic-seo-master for the three core principles (Vastness, Depth, Momentum)
• Use koray-content-brief after the map is built — one brief per node
• Use koray-contextual-vector when structuring each node's internal headings
• Use koray-query-semantics to generate the question network for each node

#seo-sop #seo #semantic #koray #topical-authority #content-architecture