SFT stands for Structure, Flow and Trust. It is an audit framework for examining whether a digital entity is understandable, whether authority moves to the right pages and whether important claims are supported. It is not Majestic’s Trust Flow metric, and it is not a substitute name for link analysis.
The distinction matters because search visibility now depends on more than page-level relevance. Search and answer systems must connect content to an organization, retrieve the right passage and decide whether the source is sufficiently reliable to reuse.
Structure: can the system identify the subject?
Structure covers information architecture, entities, canonical URLs, language relationships and structured data. A sound implementation establishes which organization, person, service or concept each important page represents.
Audit duplicate routes, conflicting canonicals, orphan pages and markup that does not match visible copy. For bilingual sites, verify that French and English pages are real equivalents connected reciprocally, not two disconnected inventories.
Flow: does authority reach the useful page?
Flow describes how users and crawlers move through the site. Navigation, contextual links, breadcrumbs and content hubs should guide both toward the page that answers the question.
Count links only after judging their purpose. A repeated footer link is not equivalent to a contextual recommendation from a relevant guide. Look for dead ends, excessive depth and clusters that compete for the same intent.
Trust: can the important claims be checked?
Trust is the evidence layer. It includes responsible authorship, primary sources, transparent methods, update history, real contact information and independent corroboration. Structured data can describe those relationships, but it cannot manufacture them.
| Pillar | Core question | Typical repair |
|---|---|---|
| Structure | What entity and intent does this page represent? | Clarify architecture, canonicals and schema |
| Flow | Can authority and users reach it efficiently? | Improve contextual links and hubs |
| Trust | Why should the claim be believed? | Add sources, authorship and verifiable proof |
How the three pillars interact
A technically perfect page with no evidence remains weak. A well-sourced report buried five clicks deep may not be retrieved. A popular URL that conflates several entities can create ambiguity. The method is useful because it treats these failures as connected rather than isolated checklists.
Score each pillar with documented observations, not an opaque universal number. The purpose is to prioritize remediation and compare the site with itself over time.
A repeatable audit cycle
- Select the commercial entity or topic to evaluate.
- Map its important URLs and external evidence.
- Test the structure, flow and trust conditions.
- Fix the highest-impact contradiction first.
- measure crawling, rankings, qualified visits and citations.
- Revisit the evidence when the business changes.
SFT is most useful as a shared operating language. Editors, developers and strategists can see how their work contributes to a source that is identifiable, reachable and defensible.