EEAT Mechanics

Topic-Embeddings: How Google Understands What Your Page Is About

The focus vectors and radius that determine topical relevance — and why a weather site needs a narrow focus to rank for weather queries

By Thomas Wawra· Published · Version 1.0· Systems referenced: Topic-Embeddings (Focus/Radius)

What are Topic-Embeddings?

Topic-Embeddings are Google's representation of what a page is about — not in keywords, but in a high-dimensional vector space where similar topics are close together. The system produces two values: a focus vector (where the page's topic sits in the embedding space) and a radius (how broad the page's topic coverage is).

The Google API leak confirmed the existence of Topic-Embedding fields. The focus vector is self-supervised: it is derived from the actual text of the site — from the real usage of language across all pages, without human labels. The resulting vectors flow as focus vectors into NSR (System 7).

Topic-Embeddings are the modern replacement for keyword matching. Instead of checking whether a page contains the word 'weather,' the system checks whether the page's topic vector is close to the query's topic vector in the embedding space. This allows Google to match 'storm warning' with 'severe weather alert' even if the exact words don't overlap.

Claim-level evidence (3)
B
Topic-Embeddings represent page topics as vectors in high-dimensional space.
Source: Google API leak — field description · Topic-Embeddings (Focus/Radius)
B
Two values: focus vector (topic position) and radius (topic breadth).
Source: Google API leak — focus and radius fields · Topic-Embeddings (Focus/Radius)
B
Focus vectors are self-supervised from actual text — no human labels.
Source: Google API leak — self-supervised from Sprachgebrauch · Topic-Embeddings (Focus/Radius)

Focus and radius: what they mean

The focus vector represents the center of the page's topic in the embedding space. A page about 'Hamburg weather' has a focus vector close to other weather-related pages, but closer to pages about Hamburg than to pages about Munich weather. The focus vector captures both the topic (weather) and the specificity (Hamburg).

The radius represents how broad the page's topic coverage is. A page that discusses only Hamburg weather has a small radius — it is tightly focused. A page that discusses weather, climate, tourism, and local history has a large radius — it covers many topics. The radius affects how Google matches the page to queries: a small-radius page matches a narrow set of queries very well, while a large-radius page matches a broad set of queries less precisely.

For ranking, the focus vector determines which queries the page is relevant to, and the radius determines how confident Google is in that relevance. A page with a small radius and a focus vector close to the query will rank higher than a page with a large radius and the same focus vector — because the small-radius page is more clearly about the query's topic.

Claim-level evidence (3)
C
Focus vector captures both topic (weather) and specificity (Hamburg).
Source: Inference from vector embedding semantics · Topic-Embeddings (Focus/Radius)
C
Radius = topic breadth. Small radius = tightly focused, large radius = broad coverage.
Source: Inference from radius field semantics · Topic-Embeddings (Focus/Radius)
C
Small-radius pages rank higher for specific queries — more clearly about the topic.
Source: Inference from focus + radius ranking interaction · Topic-Embeddings (Focus/Radius)

Topic-Embeddings in the ranking architecture

Topic-Embeddings feed into NSR (System 7), the normalized site rank. The focus vector becomes one of the inputs that NSR uses to compute the site-level quality and authority value. This means topic relevance is not just a matching function — it is part of the quality assessment.

The E-E-A-T dimension mapping for Topic-Embeddings is Expertise (Exp: indirect) and Authority (A: indirect). A page that is tightly focused on a specific topic signals expertise — it demonstrates deep knowledge of one area rather than shallow knowledge of many. The authority signal comes from the focus vector's proximity to other authoritative pages on the same topic.

Topic-Embeddings operate at the document level (Reach: Doc). Each page gets its own focus vector and radius. The site-level topic profile is an aggregation of all page-level vectors — this is what NSR computes. A site where most pages have focus vectors in the weather region of the embedding space will have a site-level focus vector in the weather region, making it more likely to rank for weather queries.

Claim-level evidence (3)
B
Topic-Embeddings feed into NSR (S7) — topic relevance is part of quality assessment.
Source: Google API leak — feedsInto: [7] · Topic-Embeddings (Focus/Radius)
B
Topic-Embeddings are Expertise (indirect) and Authority (indirect) signals.
Source: Google API leak — dims: {Exp: indirekt, A: indirekt} · Topic-Embeddings (Focus/Radius)
C
Site-level topic profile is an aggregation of page-level focus vectors.
Source: Architectural inference from document-level + NSR aggregation · Topic-Embeddings (Focus/Radius)

Implications for SEO practitioners

For large publishers, the focus vector creates a strategic tension: broad coverage (many topics, large radius) vs. narrow focus (few topics, small radius). A weather site that also covers travel, cooking, and sports will have a large radius — which means its weather pages will rank lower for weather queries than a pure weather site's pages.

The self-supervised nature of Topic-Embeddings means that the system learns from the actual text on the page. There is no way to 'inject' a focus vector through meta tags or structured data — the focus vector is derived from the content itself. If the page is about weather, the focus vector will reflect that, regardless of what the meta tags claim.

For sites with programmatically generated content, the radius matters: thousands of location pages with genuine weather data will have small-radius focus vectors (each page is tightly focused on one location's weather). This is good for ranking — the small radius makes each page clearly relevant to its specific location query.

The embedding-based approach also explains why synonyms work: 'storm warning' and 'severe weather alert' will have focus vectors that are close in the embedding space, even though the words don't overlap. Google doesn't need the exact keyword — it needs the right topic vector.

Claim-level evidence (4)
C
Broad coverage dilutes focus — weather + travel + cooking = large radius, lower weather rankings.
Source: Inference from focus + radius interaction · Topic-Embeddings (Focus/Radius)
C
Focus vectors are derived from content — cannot be injected via meta tags.
Source: Inference from self-supervised derivation · Topic-Embeddings (Focus/Radius)
C
Programmatic location pages with genuine data have small radius — good for specific queries.
Source: Inference from per-page focus vector architecture · Topic-Embeddings (Focus/Radius)
C
Synonyms work because topic vectors are close, even if words don't overlap.
Source: Inference from embedding space semantics · Topic-Embeddings (Focus/Radius)

This Deep Dive is Schicht 2 content — interpreted and referenced, but always pointing back to Schicht 1 (the reference layer). Every claim is mapped to a source with an evidence code: [A] DOJ/sworn material, [B] leak field, [P] patent, [O] official Google communication, [C] interpretation.

© Thomas Wawra · Senior SEO Manager · wetter.com — a Funke Digital company