Lesson 35: Creation of Topical Map with Annotational Semantics
Key Takeaways
- My main point here is that from beginning to the end we always stay in the same context in our topical map.
- Hello, this is the 31st lecture of the Semantic SEO course.
- In this lecture, we will focus on the topical map that we have created and how we can actually process a topical map from raw version.
- The raw topical maps, they just have entities and the attributes like water and the benefit.
- This is entity and this is the attribute.
Core Concepts
Main Teaching
Hello, this is the 31st lecture of the Semantic SEO course. In this lecture, we will focus on the topical map that we have created and how we can actually process a topical map from raw version. The raw topical maps, they just have entities and the attributes like water and the benefit. This is entity and this is the attribute.
How It Works
Then we have the drinking. So once you have an entity, then an attribute, then a target query or query network, I will suggest, then you will need to actually choose a predicate or an adjective or other types of context terms and the topical entries in your macro context, which will be reflected in your H1. In this case, you see that actually we talk about mainly the benefits of water. And then in the next one, we talk about what happens when you drink too much water.
Why This Matters
Here is the entity, but where is the attribute? It is implied in this area, which is the implication here is what happens when you're doing too much water implies the amount of water in your body or health effects of overhydration or health effects of water in your body. So you can directly connect it to the here because percentage of human body in terms of water amount. so when you look at here this is the entity but attribute one more time it is implied this time we talk about optimum percentage of the water in human body and how it affects our health so the context from here to here these t...
Implementation Notes
Then we also talk about long-term water retention in the body. So you are able to connect all these things to each other while actually creating your topical map. Sometimes to be able to help my teammates to understand the logic here I use these type of boldings or bolts or bold text. If I bold this area too it will be actually giving you a section which means that whatever you see here until to the next bold text it means that these things are mainly connected to each other.
Koray's Terminology
| Term | Meaning in Context |
|---|---|
| Topical Map | Content network design based on semantics with core and outer sections, processing a central entity with main and minor attributes |
| Macro Context | The main topic and primary context of a web page, processed in the main content area |
| Root Attributes | Attributes that appear in all instances of an entity class (e.g., population for all cities) |
Practical Application
- Analyze the query network for your target topic using search console data
- Map out the central entity and source context for your project
- Study the concepts presented in this lesson until they become intuitive
- Review the related case studies mentioned by Koray for real-world application
- Practice identifying the key terminology in your own SEO projects
- Apply the frameworks discussed to a test website or content network
Connection to Framework
Full Transcript
Hello, this is the 31st lecture of the Semantic SEO course. In this lecture, we will focus on the topical map that we have created and how we can actually process a topical map from raw version. The raw topical maps, they just have entities and the attributes like water and the benefit. This is entity and this is the attribute. Then we have the drinking. So once you have an entity, then an attribute, then a target query or query network, I will suggest, then you will need to actually choose a predicate or an adjective or other types of context terms and the topical entries in your macro context, which will be reflected in your H1. In this case, you see that actually we talk about mainly the benefits of water. And then in the next one, we talk about what happens when you drink too much water. So water here. Here is the entity, but where is the attribute? It is implied in this area, which is the implication here is what happens when you're doing too much water implies the amount of water in your body or health effects of overhydration or health effects of water in your body. So you can directly connect it to the here because percentage of human body in terms of water amount. so when you look at here this is the entity but attribute one more time it is implied this time we talk about optimum percentage of the water in human body and how it affects our health so the context from here to here these two are connected to each other and here again we have a health condition which is connected to water but in this case water retention is the entity rather than just the water and water is the essence of this specific entity now we focus on the root attributes of this specific entity type which is a health condition so my main message here to you is that once you choose one entity and one attribute try to augment it further choose the predicates in a wise way and try to reflect it further and further you don't always need to write your attributes clearly or explicitly you can also imply them and these implications will create other types of connections and they will help you to actually go for further other areas here for instance still we talk about benefits of water but this time water type is different when we look at here how long can you live without water here we talk about and the effect is directly used here another thing is this time we talk about state of not having the water and here we talk about state of having too much water and this one actually gives state of optimum water amount in our body. Then we also talk about long-term water retention in the body. So you are able to connect all these things to each other while actually creating your topical map. Sometimes to be able to help my teammates to understand the logic here I use these type of boldings or bolts or bold text. If I bold this area too it will be actually giving you a section which means that whatever you see here until to the next bold text it means that these things are mainly connected to each other. And on this example I didn't use it because I didn't need that. And if we continue further you will see that the word benefit appears one more time but again the water type is different. Then again we talk about water benefits or sorry water fasting which is an activity for actually losing the weight and again we have the water here and the benefit is one more time here. Then we talk about can you drink distilled water safely which is connected one more time. Benefit of the water in terms of human health but that water type is one more time different. And then we talk about drinking hot water and benefit is again here sparkling water benefit is again here. Then we talk about water quality then again health benefits of drinking water on empty stomach. Then we also bring the water weight which is connected to the water fluid retention and also the health effects of water one more time. My main point here is that from beginning to the end we always stay in the same context in our topical map. Sometimes we change the water type. Sometimes we change the water drinking time or water drinking condition like empty stomach. And sometimes we just change another attribute of water like the heat like cold water or the hot water. And whenever we change these things we try to actually see which which query network we can direct the target and we continue with this type of actually consolidation. One more thing is that even if you want to repeat this process with this topical map you will be ending up giving more authority to Svalbard. It's one of the good things in this methodology. If your competitor imitates you it will be giving you more and more authority. If you want you can do that. Thank you.