Imagine someone wants to hire an SEO agency. They finish your article about SEO audits, click the suggested next step, and receive homework.
Meanwhile, someone learning SEO finishes the same explanation on a course website. They want to try an audit; the page offers a sales call to have one done for them.
Both websites covered the topic. Both added a call to action. Somewhere between the keyword and the button, they forgot who they were helping.

This is the problem I want an entity model to prevent. In Day 03, The Pipeline Shape Behind My SEO Projects, I explained how I organize the work; here, we decide what that work needs to explain and connect.
Entity-based SEO is a way of planning a website around identifiable subjects, their properties, and their relationships. For this article, the useful question is simple: if an agency and a course seller both cover SEO, why should their websites develop differently?
Both can cover audits, internal links, technical problems, content, and measurement. What changes is the attention each topic receives, the examples used to explain it, and where the reader can go next.
Watch the same subject change jobs.
This is the working map behind the article. Pick a subject, switch the business model, then open a row to see why its page, depth and next link change.
SEO topical map
14 of 14 rows visible · source: Wikipedia: Search engine optimization
How to Prioritize SEO Audit Findings
applies diagnostic method
Give the finding an owner, dependency and acceptance check.
Audit guide and sample record · Detailed
Implementation responsibilities
For a glance at what a completed EAV mapping contains, see the examples below. They are intentionally blurred. As I said in my first article, I will show the kitchen, but the pressure cooker stays with me. It is not that someone could use these screenshots to outrank my websites; every business is different, and the useful decisions vary at the point where they matter.


Start with what the business does with the subject
Give our two hypothetical businesses the same starting topic: SEO. One performs SEO work for clients; the other teaches people to perform that work.
That difference gives us a useful relationship before we have written a headline. The agency delivers an audit; the course teaches someone to conduct an audit.
In semantic SEO, I call the shared subject the central entity. Source context describes the website's purpose and its business relationship to that subject: in this case, selling delivery or selling instruction.
Now consider a page titled “What Does an SEO Audit Include?” Both websites need to explain what an audit examines and produces, but a reader evaluating the agency may also ask, “Who fixes the problems you find?”
A reader evaluating the course may ask, “Will I learn to fix those problems myself?” The topic is shared; the responsibility changes.
This affects the explanation well before the final button. An agency can show how it assigns implementation work, while a course can show how a learner practices that work and receives feedback.
An agency can still publish excellent tutorials. A course seller can still explain professional delivery. The business model guides the emphasis across the website without banning either business from useful parts of the subject.
Put each fact against the thing it describes
Before planning pages, I separate the things involved. SEO is a discipline, an audit is an assessment, an agency engagement is a service arrangement, and a course is a learning product.
They connect, but their properties differ. A course might have a six-week schedule; an audit might have a defined scope and a findings report.
Write “SEO takes six weeks” and the meaning falls apart. Six weeks to learn it, deliver an audit, implement changes, or see a result? The sentence needs to identify whose duration it describes.
This is where entity, attribute, and value become useful. In the hypothetical statement “This SEO course lasts six weeks,” the course is the entity, duration is the attribute, and six weeks is the value.
Relationships tell us how those things connect. “The course includes an audit module” differs from “the agency delivers an audit,” even though both statements contain the same topic.
Those verbs matter. A course containing an audit lesson does not establish that its seller will audit your website, just as an agency publishing a tutorial does not establish that its service includes training.
An ontology records the kinds of things involved and the relationships allowed between them. In our example, a lesson belongs to a course module, an audit finding needs evidence, and an implementation task needs an owner.
That gives the writer a practical check: what exactly are we describing, and what can we truthfully say about it? It also gives us the raw material for grouping the website's content.
Group the material, then decide what deserves a page
Suppose a proposed category list contains “Technical SEO,” “SEO Audits,” and “Beginner Courses.” The labels all relate to SEO, but the list mixes an area of work, an assessment, and a learning product.
I would separate the grouping rules. Subject areas can include technical SEO and content; agency offerings can include audits and implementation; course levels can distinguish beginner and advanced learning.
Those groups can connect without pretending to classify the same thing. A beginner course can contain a technical SEO module that teaches part of an audit.
This is categorization: deciding which relationship makes items belong together. A topical map then plans how the website covers those subjects and connects the coverage.
There is another decision before creating URLs. “SEO audit checklist” and “how to audit a website” may be served by one useful tutorial with a checklist inside it; two phrases alone do not establish two page needs.
I use QDP, my page-qualification method, to examine whether the subject, reader's task, supporting evidence, and actual search results justify separation. A candidate may become a page, a section, a filter, or an addition to something that already exists.
For our course, “six weeks” belongs in the course information. A lesson that teaches someone to interpret audit findings could need much more space. Counting both as one row in a spreadsheet tells us little about how either should appear on the site.
That distinction keeps the map useful: we can cover a fact without turning every fact into an article. The next decision is how much attention each part of the map deserves.
The same map can have different priorities
For this comparison, both SEO websites retain the same subject coverage. Neither gets to delete internal linking just because the other business teaches it more visibly.
I make the difference visible through four choices. Consider how each applies to the shared topic of SEO audits:
- Publishing order. An agency launch needs a clear service scope and a sample deliverable. A course launch needs a clear curriculum and a sample lesson.
- Depth. The agency can develop how recommendations become assigned work. The course can develop how a learner reaches and defends a recommendation.
- Prominence. The agency can feature its audit process from the service page. The course can feature the corresponding lesson from its curriculum.
- Links. The agency's explanation can lead to engagement details. The course's explanation can lead to an exercise and worked answer.
These are planning choices I can show in a brief. They describe what receives attention, where it appears, and why a reader would continue.
Map weighting visual
Same map. Different weight.
The map leans toward accountable delivery: what was found, who owns the fix, and how the result is checked.
A finding becomes a record with source URL, evidence, recommendation, owner and acceptance check.
The page explains where the agency's responsibility ends and the client's implementation begins.
Links lead to the scope or implementation detail when the passage creates that question.
The work is developed until a buyer can evaluate the delivery, not until every related term is mentioned.
Shared coverage still matters. Both sites can explain SEO history, for example, while giving it a different publishing date or amount of detail according to what it helps their readers understand.
The difference becomes clearest when we open one article and see what the reader actually receives. Let's give both businesses the same title: “How to Act on an SEO Audit.”
Follow one finding through both websites
Use a simple example: an audit identifies a link in an article that points to a page that no longer exists. For this example, the team has checked the destination and confirmed that an appropriate replacement page is available.
Both versions should explain the reasoning. Check the surrounding sentence, decide whether the replacement answers the same need, update the link if it does, and verify the published result.
One finding, two routes
Follow the decision, not just the keyword.
Observe · delivery
Record the source article and the dead destination.
On the agency website, I would show the finding as a task a client could understand. The record identifies the source article, the broken destination, the proposed replacement, the person responsible, and the check required before closing the task.
Imagine the agency recommends the replacement, while the client's editor makes the change. The article should say that plainly, because “we found it” and “we fixed it” describe different work.
The reader leaves understanding what the agency delivers and what their own team must do. A link beside that explanation can take them to the service scope, where the actual division of responsibility is stated.
On the course website, I would turn the same finding into an exercise. The broken link sits in this sentence: “Record the issue in your audit report before assigning the fix.” The learner must choose between two replacement pages: “SEO Audit Pricing” and “Sample Audit Report.”
The sample report answers the need created by that sentence. The pricing page shares the audit topic but gives the reader no help recording a finding.
The worked answer can link the words “audit report” to the sample, then show the learner how to check that the published link opens the intended page. The learner leaves with a decision they can repeat on another website.
Now the business difference is visible inside the content. The agency demonstrates accountable delivery; the course demonstrates teaching and feedback.
Changing “book a call” to “buy the course” at the bottom would leave all of this work undone. The offer needs to make sense in the example, the explanation, and the next step.
Try the same reasoning with CBD
Now take CBD ecommerce and a health education website's CBD section. Give both the same broad coverage: what CBD is, product forms, research, risks, labeling, and history.
The store helps visitors inspect the products it offers. The publisher helps readers understand the subject and assess the evidence; its educational purpose does not, by itself, tell us how the publisher earns revenue.
Use a shared article title: “How to Read a CBD Product Label.” Both versions should help the reader understand what the label states.
Imagine a label stating 600 mg of CBD in a 30 mL container. That describes 20 mg per mL on the label; it neither verifies the actual contents nor tells someone how much to take.
On the store's page, I would show where those figures appear on a product label, then explain how to locate the supporting report for the relevant batch. The reader needs to connect a particular product to its particular records.
On the health publisher's page, I would use the same label to introduce a different question: what can this number tell us about a health claim? A stated amount describes composition; evidence for a health outcome needs its own support.
That boundary matters on the store too. The FDA distinguishes approved drug uses from unapproved claims made for other CBD products, so a retailer cannot transfer a drug's approval to its own product simply because both involve CBD. The FDA explains that distinction here.
The two pages share the basic explanation while developing different parts of it. The store may spend more space matching labels and product records; the publisher may spend more space explaining how to read research claims.
Their links follow those passages. “Find the report for this batch” belongs beside the product-record explanation; “understand what the study measured” belongs beside the research explanation.
The entity model also stops facts from drifting between subjects. CBD is the compound, the bottle is a product containing it, and a report concerns an identified sample or batch. A result for one batch cannot automatically describe another.
The same principle worked in the SEO example: an agency's service commitment and a course's learning outcome belong to different offers. Keeping the subject of each claim clear makes the writing easier to trust and easier to understand.
Let the page's question shape the article
So far, we have chosen the relationships, grouped the subjects, assigned attention, and followed an example through the content. We still need to decide how each article begins and develops.
The page's macro context is its main subject and angle. In “How to Read a CBD Product Label,” that is label interpretation; a section explaining units is a smaller micro context within it.
The title makes a promise the article needs to keep. A store page with that title still owes the reader a useful label explanation, even if the business would also like to sell a product.
I use three structures from my content methodology to organize that explanation. Staying with our SEO example makes their differences easier to see:
- Entity defining: introduce the thing. “What Is an SEO Audit?” starts with a definition, then develops its scope, process, and outputs. “An SEO audit is a structured assessment of a website's search-related condition” gives the reader a category; the next sentence explains what that assessment examines and produces.
- Entity non-defining: answer the immediate question before the broader introduction. “What Does an SEO Consultant Do?” can lead with the consultant's function, then explain the role. In the methodology's single-answer version, the answer precedes the definition section; when the leading attribute has several values, those values can organize the main sections.
- Attribute as macro context: concentrate on one property. “What Deliverables Does an SEO Audit Include?” makes the outputs the whole article's subject. For our hypothetical offering, it could introduce an evidence record, a prioritized recommendation list, and an implementation plan, then explain each in turn.
Page-structure selector
Choose the question before the format.
The structure changes the opening, the sections and the page that should receive the next click.
What is the thing?
Give the reader a category before expanding the scope.
In that last article, the implementation plan is one value under “deliverables.” When we examine the plan itself, it becomes the subject, with its own task owners, dependencies, and completion checks.
That is why an entity and a value are roles in an explanation. The same thing can fill either role depending on which question we are answering.
The methodology uses the attribute-focused format to develop multiple values; a short single answer can stay inside broader coverage. We still qualify the need for a separate URL before publishing one.
For an agency, the deliverables article explains what a client receives and how to use it. For a course, it can explain how to produce those same outputs and judge their quality. The structure supports the page's question, while the examples express the website's purpose.
Make the next click continue the explanation
Internal linking is where this planning becomes a route someone can follow. I look at the sentence that creates a need for another page, then choose a destination that answers it.
In the agency article, “Check who is responsible for implementing the recommendations” creates a reason to open the service scope. In the course article, “Try choosing a replacement link yourself” creates a reason to open the exercise.
The return journey matters too. A prospective client reading the service page may need the sample audit to understand what they would receive; a learner reading the curriculum may need a preview lesson to judge the teaching.
Those connections make the shared topic useful in different ways. A page repeating the word “audit” has given me a possible connection; the surrounding passage tells me whether the link belongs there.
Before handing an article to a writer, I therefore want six questions answered. For our agency's audit article, the answers would be:
- Purpose: help a prospective client understand what happens after an audit.
- Inclusion: show one finding, the proposed action, the owner, and the completion check.
- Audience: a business or marketing lead considering the service.
- Benefit: make the division of work clear enough to evaluate the engagement.
- Next step: inspect the service scope when responsibility becomes the next question.
- Contextual relationship: connect the article with the audit overview, service scope, and relevant implementation guidance.
For the course, I would change the brief around the learner's job: perform the task, compare the answer, and understand the feedback. That change carries through the article instead of arriving as a surprise sales button.
Use the maps to inspect the difference
The comparison maps accompanying this article let you examine both versions of a topic side by side. They contain 28 shared CBD topics and 26 shared SEO topics, with different proposed priorities, treatments, and links for each business.

Start with SEO audit prioritization or CBD label information. Compare what each website needs to explain, then follow one proposed link and check whether it continues the reader's question.
Wikipedia's Cannabidiol and Search engine optimization articles supplied starting topic inventories. The maps label our editorial additions separately; their priorities and routes are worked planning examples, with search-demand and final URL decisions still to validate.

My understanding of these entity and context concepts developed through studying Koray Tuğberk GÜBÜR's semantic SEO work. Here, I have applied that foundation to decisions a content team can inspect: what belongs together, what needs explaining, how much attention it receives, and where the reader can continue.
Return to the two visitors at the beginning. The prospective client should now understand what hiring the agency involves, and the learner should have something useful to practice. We can finally stop assigning homework to the person trying to hire us.
In Next Article: The 8 Rules Every Money Page Follows, I will take this into the writing itself. Once the page's job is clear, we can decide how to order its answers and make each statement earn its place.




