Skip to content
Semantec SEO
WorkAuditMIRENAFor agenciesLearningAboutContact
Start a project

Information Gain

Missing Relationship Audit: State the Connection and Its Direction

A missing relationship audit finds entities, ideas, steps or pages that appear together without an explicit, supported connection. Use it when relevant concepts read like a list and the reader must infer what requires, precedes, contrasts with, checks, replaces or leads to what.

Inspect the evidence and trust example

By Kevin Maguire

A person card and abstract branching node model beside an open blank ledger and navy pencil.
A relationship needs an explicit text explanation as well as a visual connection.
A magnifier examines blank cards beside a bicycle component, illustrating review of an explanation.
Inspect what the connection means; a nearby card is not evidence of a dependency.

Worked example: connect evidence to the reader’s decision

A page discusses evidence and trust in separate passages. Both topics are relevant, but their relationship remains implied. The missing explanation is how the decision’s evidence needs should affect the proof supplied and where the reader sees it.

A bounded editorial repair could say: identify what the reader needs to verify before acting, then choose the evidence class that can support that assertion and place it beside the relevant choice. This describes an editorial method. It does not claim that adding a source automatically creates trust, that every reader needs the same proof, or that a platform will reward a particular arrangement.

A relationship register for the evidence and trust example
Subject → predicate → objectSupport and boundaryExpression and placement
Reader decision → sets the question for → evidence reviewState the exact choice and the assertion that needs support. Different consequences can require different proof.Explain the decision before listing source types; do not start with a generic credibility checklist.
Claim type → informs the choice of → proof typeThe proof must fit the assertion. A policy text, direct observation and causal study answer different questions.Use a short explanation or comparison beside the claim; route an unresolved proof question to its dedicated owner.
Evidence limitation → narrows → permitted wordingRetain the source’s date, scope, sample or version. Missing evidence does not become a positive finding.Put the qualification in the answer and beside the recommendation, not only in distant notes.
Next unresolved decision → routes to → another ownerA destination must answer the next task; a shared topic is insufficient reason for the route.Use descriptive link text within the transition that states why the destination is relevant.

The arrows record an editorial reasoning direction, not a measured causal effect. A reader may still withhold trust after reviewing the evidence. Keep the distinction between a method for making a claim inspectable and an assertion about a user’s response.

Choose a predicate that can be challenged

A relationship becomes inspectable when the sentence names its subject, predicate and object. “These topics are connected” does not reveal the connection, its direction or the conditions under which it holds.

Common predicates and the confusion to prevent
PredicateQuestion to testBoundary to state
RequiresCan the proposed action proceed without this input?A genuine prerequisite differs from a useful enhancement or a local team preference.
PrecedesIs this an ordering dependency or simply the order chosen for presentation?Earlier in a process does not mean it causes the later outcome.
ChecksWhich claim or condition does this check assess?Passing one check does not establish the whole answer, identity or technical setup.
Contrasts withOn which shared dimension do these options differ?A contrast needs comparable scope; unrelated examples do not form a useful comparison.
ReplacesWhat ceases to apply, from which date and for which scope?A replacement can be partial or conditional. Similarity is not evidence of succession.
Routes toWhat next decision will this destination complete?An internal link connects pages technically, but the prose must explain the relevant task transition.
CausesWhat evidence distinguishes the proposed cause from alternatives?Do not turn association, timing or proximity into a causal statement. Route unsupported attribution to the proof audit.

Read the inverse aloud. “A requires B” does not imply “B requires A.” A page can belong to a category without that category belonging to the page. A process can precede a check without every earlier step being sufficient to pass that check. Check that the inverse wording preserves the intended meaning rather than silently reversing the claim.

Also test negation and scope. “Not supported in version A” does not establish “supported in every other version.” A source may describe a historical relationship while the page uses present tense. Preserve a date, market or version when it controls the predicate.

Audit the edges between the ideas

Start with concepts relevant to the reader’s decision that occur together but never explain their connection. The goal is a supported relationship at the point the reader needs it, not more linking phrases or a denser diagram.

A magnifying glass beside five connected website page models with cobalt and amber links.
A route between pages should carry a relevant next decision, not an unexplained association.
  1. Inventory the implied connections. Read adjacent passages, lists, comparison rows, procedure transitions and linked pages. Name the reader decision affected by each missing connection.
  2. Write the candidate proposition. State subject, predicate and object using stable entity or task names. Choose a relationship that can be tested, directed and limited.
  3. Check the evidence. Read the controlling source and record its date, scope, tense and confidence. Confirm that it supports this edge rather than merely mentioning both subjects.
  4. Test direction and alternatives. Check the inverse, distinguish prerequisite from preference, and examine plausible exceptions. Record conflicting evidence without forcing agreement.
  5. Choose the expression. Use a sentence, table field, diagram label or internal route suited to the relationship. A complex edge may need both a visual model and a complete text equivalent.
  6. Read the decision path again. Confirm that terms, evidence, page boundary, component and next action remain consistent. Stop if the evidence, identity, destination or ownership cannot support the proposed connection.

A missing connection may expose a missing process step rather than a sentence repair. If the method jumps from collecting data to publishing without a necessary review, the answer needs an action and owner, not just “then.” Route that work to the process audit while retaining the relationship that explains why the step is needed.

An open folio holding source notes and page instructions beside an owner badge and checklist.
Preserve the predicate, direction, evidence and placement for the next editor.

Place the connection where it resolves the task

The output is a relationship register with predicates, direction, evidence, placement and internal routes. Each accepted edge should make a previously implied part of the answer explicit without enlarging the claim beyond its support.

  • In the direct answer. Add the relationship needed to interpret the definition or recommendation. Avoid leaving the central dependency to a caption many paragraphs later.
  • In a transition or procedure. State why one action follows another and which input or check changes the next move. Keep sequence and causality distinct.
  • In a comparison or diagram. Label the dimension or edge, retain conditions and provide the same meaning in text. A decorative line is not an explanation.
  • In an internal route. Describe the unfinished decision and the destination that owns it. A link cannot compensate for a missing explanation on the current page.

For each accepted relationship, retain the subject and object, controlled predicate, direction, inverse check, source passage, date, market or version, uncertainty and exception. Add the expression and exact placement, responsible owner, accepted or unresolved state, next route and review trigger. A changed process, replacement record, source correction or new version can reopen the edge.

When support is absent, hold, qualify, replace or remove the relationship. Do not add ownership, dependency, replacement or cause merely because the concepts are adjacent. If the useful explanation belongs in an existing page, table or source record, improve that owner rather than creating another page to repeat the same concepts.

Questions about implied relationships

Does mentioning two entities establish a relationship?

No. Shared context can suggest a question to investigate, but it does not establish ownership, causality, dependency or replacement. Name the proposed connection and seek evidence for it.

Is an extra transition enough?

Only if it states the missing relationship. “These ideas work together” remains vague. Explain the prerequisite, comparison, check or route and include the condition that changes it.

How does this differ from a proof type audit?

A relationship audit identifies the edge the reader needs and how to express it. A proof type audit tests the kind and strength of evidence required for that assertion. The two can be used together; writing an edge does not prove it.

When does a relationship add useful information?

When it changes how the reader interprets an answer, performs a step or chooses the next destination. Rearranging headings, adding topic breadth or drawing more arrows does not create useful evidence by itself.

Related decisions and sources

Information Gain

Choose the useful connection before adding another format or page.

Missing Proof Type Audit

Check the evidence class needed for the proposed assertion.

Missing Process Step Audit

Repair an omitted action that prevents the method from reaching its outcome.

Google: creating helpful content

Use the public self assessment questions as a wider editorial reference.

The examples are teaching scenarios, not records of a client project. The illustrations explain record separation and revision; they are not evidence of the assertions described. These editorial methods do not guarantee rankings, indexing, traffic, rich results, citations or AI feature inclusion.

Semantec SEO

Semantic SEO agency
All English speaking markets

support@semantecseo.com
Discuss an audit

Services

  • Website audits
  • Topical maps
  • Writing instructions
  • Writing & rewriting
  • Internal linking
  • Entity analysis
  • Structured data
  • Page design
  • Location content
  • Measurement

Learning

  • Semantic SEO
  • Reader intent
  • Entities and facts
  • Topical mapping
  • Semantic writing
  • Evidence & sources
  • Internal links
  • Structured data

Company

  • About us
  • For agencies
  • Project pricing
  • Contact us

Policies and trust

  • Legal info
  • Terms
  • Privacy
  • SEO & AI disclaimer
  • Citation policy
  • Claims policy
  • Security

Founded by Kevin Maguire. Kevin Maguire on LinkedIn.

AI supports our internal analysis, writing and review. Search rankings and AI citations are external outcomes we cannot promise.

© 2026 Semantec SEO · HTML sitemap