The semantic content system

496

enrichment items

Swedish, verbatim

34

sections

in 3 parts

16

chain stages

plus one loop

5

stage groups

context to content

The source document, Innehållsberikning, opens with one sentence that defines its scope:

Sammanförd lista över möjliga innehållsberikningar från dina anteckningar och bilagor. Varje punkt beskriver ett element att välja, utveckla eller undersöka för en viss sida.

In English: a consolidated list of possible content enrichments, where each point describes an element to choose, develop or research for a given page. Two ideas carry the rest. First, a page is not written; it is assembled from elements that each answer a need, and the list is the catalogue of those elements. Second, the elements only make sense inside a chain that starts with what the site is a source about and ends with the link to the reader’s next question. AwesomeSEO models both: the chain as typed objects with validators, the library as data with annotations.

The source states the chain in one line, which the package keeps exactly as written and maps to 16 stages; the last link, nästa query, loops back to the query.

Source context → knowledge domain → contextual domain → central entity → main entity → attribute → value → predicate/frame → semantic roles → query theme → query template → query → question → answer → document → internal link → nästa query

The two ends of the chain carry the most weight and the fewest items. Source context is defined once, in the source’s own words:

8. Source context: Koppla sidans perspektiv till webbplatsens huvudentitet, verksamhet, erbjudande och redaktionella identitet.

And the internal link, the last stage, is not navigation but the answer to “what will this reader ask next?”:

183. Internlänkar: Koppla sidan till överordnade ämnen, syskonsidor, underkategorier och fördjupningar.

The 496 items grew in three parts: a base list, additions that extend it, and a third part on query, language and network modelling. The sections keep the source’s Swedish titles.

A reader who wants the gist of the base list can take its first section as the frame: who the page helps, what it is about, from which perspective. The first item:

1. Målgrupp: Beskriv vem sidan hjälper, personens kunskapsnivå, situation, behov och förutsättningar.

The list is practitioner material and is tiered as such. An item is raised above practitioner only through a playbook practice of a higher tier or a direct citation of Google documentation; items the list itself frames as hypotheses are marked speculative. 96 items rest on 43 playbook practices, 23 cite Google documentation directly, and a test in the repository enforces the policy against the factors package.

An example of each end. A confirmed item, resting on Google’s own guidance on links:

183. Internlänkar: Koppla sidan till överordnade ämnen, syskonsidor, underkategorier och fördjupningar.

Tier: confirmed Google Search Central: Link best practices for Google

And a documented one, resting on site-level focus signals from the 2024 leak:

8. Source context: Koppla sidans perspektiv till webbplatsens huvudentitet, verksamhet, erbjudande och redaktionella identitet.

Tier: documented via the practice “Define the source context before the first page”

Every item is annotated with the page types it fits. Asking for a page type returns its checklist in chain order: the items marked for that type plus the items marked for any page. Site-level items (data model, research, workflow) are listed only when asked for.

The checklist is a menu, not a quota. The quality thresholds in section 7 say what a page must pass; the checklist says what it may contain, so an editor chooses by the P-R-P score of each attribute (prominence, relevance, popularity, 1 to 5 each; 12 or more earns a section).

The product checklist has 249 items across 16 stages. Below, the first item of each stage, with its English label and tier. The full list is in the demo workspace’s semantic model.

Ten checks a page passes before it ships, from Koray Tuğberk Gübür, semantic SEO course material. All are practitioner tier: coherent and testable working rules, not confirmed ranking signals, and the product labels them that way.

The chain is a typed model: source context, domains, entities, attributes with values that carry a unit, a source and a date, predicates and roles, query themes, templates, queries, questions, answers, documents and links. 11 validators run over it and name the stage they break:

• Broken reference
• Main entity per document
• Main entity → central entity
• Question without an answer
• Answer format
• Link anchor
• Link → next query
• Context dilution
• Predicate completeness
• Value without source
• Document without inbound links

Brands never fill this in by hand. Onboarding captures the source context and central entity; the topical map derives clusters and the P-R-P placement of attributes; the content module generates briefs from the checklist for the page type and runs the quality thresholds before a draft goes for approval. The semantic model screen shows the chain, the validators and the library with search.

Source: Innehållsberikning, content/innehallsberikning.sv.md in the AwesomeSEO repository, Swedish, parsed verbatim into @awesomeseo/semantic. English short titles (at most six words), stage and page-type annotations and tiers are ours and live beside the text, never in it. The chain and the stage summaries follow Koray Tuğberk Gübür’s semantic SEO framework; its claims are practitioner tier unless the playbook raises them. Every count on this page is computed from the package at build time.