Kick-off and defining the project scope
The kick-off serves to establish exactly what the topical map is to cover and in what format we will work. At this stage I gather information about the offer, the audience groups and the product and service priorities, so that the map reflects the business needs from the start. We also establish the languages and markets the project concerns and identify the implementation constraints that may affect later decisions. The result is a clear scope of work that makes it possible to move on to assessing the current state of the content without differences in interpretation.
As part of these arrangements we specify the decisions that affect the further analysis and the number of recommendations. This concerns, among other things, whether the map is to go down to the level of individual pages/articles or stay at the level of topic clusters. We also discuss how far changes to the site are acceptable, such as adjustments to the navigation/URL structure or content consolidation, because this determines what can realistically be implemented.
Access and input materials needed for the analysis
For the analysis I need access and input materials that make it possible to assess the current content reliably and plan the topical map. In practice this covers visibility and traffic data, a list of existing URLs and information about the current site structure. If content plans exist, they are also a valuable input for comparison with the current topic coverage. Information about conversions and leads is helpful too, because it makes it possible to link content priorities with business goals.
The lack of this data limits the scope of the conclusions, especially in the part concerning the inventory and audit of existing content. A content audit requires in particular a list of URLs and basic performance/indexing data, so that the roles of pages can be assessed meaningfully and problems such as keyword cannibalisation or duplication can be detected. The input materials are also the basis for further steps, including assigning topics to existing or new addresses (URL mapping).
- Visibility and/or traffic data
- List of existing URLs
- Site structure
- Content plans (if any)
- Information about conversions and leads
Content inventory and audit
The content inventory and audit consist of putting in order what already exists on the site and assessing how these materials cover the topic areas that matter for the topical map. At this stage I prepare an inventory of pages and assign them roles, e.g. categories, guides or FAQ sections, so that it is clear which elements are responsible for which part of the topic. I then assess the topic coverage and whether the content responds to the right user needs. In parallel, I identify problems that make it harder to build visibility consistently, such as keyword cannibalisation and duplication.
The outcome of the audit is the flagging of content that needs improvement, consolidation or can remain unchanged in the context of the planned topical map. Where a topic is covered partially or unclearly, I point out the areas of under-coverage and the places where the role of a page does not match its content. If two or more URLs serve the same intent, I flag the risk of conflict and the need to tidy up the scope of the pages. This stage forms the basis for subsequent decisions about which topics to serve with existing pages and which require new material.
- Inventory of existing pages and role assignment (e.g. categories, guides, FAQ)
- Assessment of topic coverage and alignment with intent
- Detection of keyword cannibalisation and duplication within the content
- Flagging content to improve, consolidate or leave as is
Analysis of intent and page types in the context of the topical map
Intent analysis and page type analysis consist of matching topics to what the user is really looking for, and then indicating the right page format in the topical map. I classify topics by intent — informational, commercial or navigational — so that the later assignments to URLs are consistent and do not cause conflicts. On that basis I recommend the page type that will best serve a given topic: an article, a service page, a category, a guide, a definition or an FAQ. This brings order both to the plan for new content and to the decisions about updating existing pages.
In practice, this stage combines the conclusions from the audit with planning the target layout of content in topic clusters. If a current page serves a different intent than it should, I flag the need to change its role or scope before the topic is assigned as the target URL. When a topic requires several levels of explanation (e.g. from a definition through use cases to comparisons), the recommended page type helps to maintain a clear division into pillar and supporting content. As a result, the topical map can indicate not only “what to write about” but also “with which page type” a given topic is best implemented.
- Matching topics to intent: informational, commercial and navigational
- Recommending the page type: article, service page, category, guide, definition, FAQ
- Bringing the role of existing pages into line with their intent within the map
Research into topics and user queries
Research into topics and user queries consists of collecting the topic areas, questions and language variants related to the offer and to users’ real problems. In this step I identify the different ways in which needs are phrased, so that the map does not rely solely on a single wording of the keywords. I take into account synonyms and alternative takes on the same issues, which makes it easier to organise topics within a single cluster later. The collected material is the basis for the next stages of organising and assigning in the topical map.
The research results are organised as a list of topics and questions that reflects how users describe their needs in the context of the products or services on offer. If the project covers more than one language or market, at this stage I add language variants for the same issues. This makes it possible later to divide the topic scope consistently between pillar and supporting pages, instead of duplicating similar content under different wordings. This stage reduces the risk of missing important threads before work on the cluster structure begins.
- Collecting topics and questions related to the offer and to users’ problems
- Taking into account synonyms and different ways of phrasing needs
- Adding language variants for the agreed languages/markets
Grouping topics into clusters
Grouping topics into clusters consists of combining the collected topics into coherent sets based on shared intent and semantic proximity. In practice, I organise the list so that a single cluster contains threads that logically complement one another and guide the user through a given topic area. I then designate the pillar topics and the supporting topics, which helps to define the role of the individual elements in the map. This division simplifies planning the further work on the relationships between topics and the later assignment to URLs.
The result of clustering is a structure that can be transferred directly into the working topical map as organised groups of topics. With pillar and supporting topics defined, it is easier to check whether a given cluster is complete and whether it is not scattering into parallel threads with the same intent. It also prepares the ground for subsequent decisions about which topics should be developed as separate elements and which as support for the pillar topic. Grouping keeps the topic scope consistent before we move on to further planning work in the map.
- Combining topics into clusters based on shared intent and semantic proximity
- Designating pillar topics and supporting topics
- Organising the input material for further mapping in the topical map
