See which page fields carry the topic Field Relevance measures lexical match strength separately for the domain, URL path, title, META description, and visible content. It then applies the displayed influence assigned to each field. This answers a broader structural question than a body-content analyzer: does the complete page presentation consistently signal the subject, or is relevance concentrated in one location while other important fields remain vague? Begin by confirming the target URL and search phrase. Read the rows from highest influence to lowest, but consider whether each field can be responsibly changed. A weak title may be easy to clarify. A weak domain is normally a business constraint, not an optimization task. A weak URL path can require redirects, internal-link updates, canonicals, and analytics coordination. The table helps prioritize; it does not make every row equally editable.
Translate the decimal calculation into plain language Each field first receives a 0–100 match score. Useful occurrences increase the value, repeated occurrences add progressively less, and unrelated competing text can dilute the result. The field’s score is then multiplied by its influence. A raw internal number such as 2.1359 is not presented as an unexplained SEO target; the visualizer converts the calculation into percentages and contribution bars that can be compared directly. The combined score is a weighted summary of those contributions. A small improvement in a high-influence field can matter more than a large improvement in a low-influence field. Inspect the formula beside each row before deciding what to edit. This prevents a common mistake: spending time perfecting a path token or domain fragment while the title and description still fail to explain what the page offers.
Distinguish Field Relevance from BM25 content BM25 Content Analyzer evaluates literal search words only in visible body content and uses BM25’s document-length normalization. Field Relevance evaluates multiple page fields and combines their separately scored contributions. The two tools can highlight some of the same words because both use lexical evidence, but they answer different questions. BM25 asks how the body document uses the words; Field Relevance asks which page surfaces establish relevance. Use this analyzer when the page feels inconsistently labeled across snippets, headings, and URL presentation. Use BM25 when the title and metadata are already clear and the concern is literal search-word evidence within the main copy. A body revision can affect both measurements, but a title edit belongs to Field Relevance and should not change the BM25 body score. That predictable separation is how the tools avoid becoming duplicates.
Review a showdown row by row When a comparison page is available, do not jump straight to the total bars. Compare the same field on both URLs. The outperformer may have a clearer title but a noisier description, or a stronger path but weaker visible copy. Those differences point to distinct editorial decisions. Choose a gap that is both important and appropriate for the target page rather than attempting to imitate every stronger percentage. Domain and path differences often reflect site architecture, brand naming, or legacy migrations. Treat them as context. For editable metadata and content, ask whether the comparison communicates page type, audience, offering, or intent more directly. Draft your own accurate language. The goal is consistent labeling throughout the target experience, not duplication of another organization’s taxonomy or claims.
Test the field you intend to improve Open the preview, change one eligible field, and predict which contribution bar should move. Measure the revision and verify that unrelated rows remain stable. If a title edit changes only the title row and the weighted total, the visualizer is behaving transparently. If you change visible copy, inspect both its raw field strength and its influenced contribution before deciding whether the edit is worthwhile. Read the revised title and description as a searcher would encounter them. Confirm that they are specific, truthful, and not overloaded with repeated terms. Evaluate URL changes outside the preview as migrations with technical safeguards. Document the field changed, its before-and-after contribution, and the user-facing improvement. This creates a defensible optimization decision instead of an unexplained attempt to raise an aggregate relevance number.
Use field patterns to guide page governance Repeated field weaknesses across many pages often point to a template or editorial-process problem. Titles may omit the service category, descriptions may be copied across locations, or paths may preserve internal terminology that customers never use. Apply the analyzer to representative page types and record which fields consistently underperform. That pattern can support a focused template change or writing standard instead of dozens of isolated keyword edits. Validate any shared change on several intents before rolling it across the site. Field influence should also shape ownership. Content teams can usually revise titles, descriptions, and body copy. Engineering or platform teams may control generated paths. Brand leadership may govern naming in the domain or product labels. Route each finding to the team capable of changing it safely. A visible low row with no practical owner should remain documented context rather than becoming a vague task assigned to a writer. This keeps recommendations actionable and prevents risky architecture changes from being disguised as routine SEO work. After publication, compare snippets and landing-page experience as well as the recalculated score. Search engines may rewrite titles or descriptions, and a technically stronger field can still produce a weaker message if it becomes generic. Review click expectations, consistency with on-page headings, and whether the content fulfills the promise made in metadata. Field Relevance is most valuable as a coordination view across page surfaces: it helps every visible label describe the same real offering while allowing each field to perform its distinct role.
