On this page
RNX code library · 8 controls
RNX-120Semantic Architecture & Entity Clarity
Read what these checks mean, why they matter and which evidence they concern. Each ID below keeps its canonical place in the RNX hierarchy.
These are free learning summaries, not full technical tests or an industry certification. Specialized checks apply only to the relevant feature. Experimental labels are preserved from the canonical source.
RNX-121 · Organization & Local Business Grounding
RNX-121.T001
Structured data parsing
core readiness
Check that structured data can be read without syntax errors.
Why it matters. Even truthful information is unusable if its format is broken.
Illustration — fictional. A misplaced quotation mark makes the machine-readable business labels unreadable.
When it applies. Inspected target: captured structured-data document. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-121.T002
Entity type fit
core readiness
Choose labels that match the real business, person, product or service.
Why it matters. A wrong type tells machines the wrong story.
Illustration — fictional. A service page is labeled as a review even though it contains no review.
When it applies. Inspected target: typed entity node. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-121.T003
Persistent entity reference
Experimental — not an established ranking requirement
Use a stable reference for the same real-world entity.
Why it matters. Consistent identifiers help related information stay connected.
Illustration — fictional. One identifier is reused for unrelated branches without a common parent distinction.
When it applies. Inspected target: entity identifier reference set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-121.T101
Vocabulary property value fit
core readiness
Use structured-data properties with the right kind of value.
Why it matters. A readable label can still be meaningless if a price field contains a review.
Illustration — fictional. The price property contains a full customer testimonial instead of a price value.
When it applies. Inspected target: structured property value. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-121.T102
Conflicting graph producer reconciliation
Experimental — not an established ranking requirement
Resolve contradictions between structured data produced by different site tools.
Why it matters. Two blocks are not inherently wrong, but conflicting stock claims are.
Illustration — fictional. The website theme labels an item in stock while the commerce tool labels the same item sold out.
When it applies. Inspected target: page graph producer set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-124 · Cross-Graph Entity Corroboration
RNX-124.T001
Cross-source identity comparison
Experimental — not an established ranking requirement
Compare business facts across the sources you can actually inspect.
Why it matters. Missing access leaves a gap, not proof of agreement.
Illustration — fictional. A similarly named firm's profile is merged with the subject because their names match.
When it applies. Inspected target: cross-source entity comparison. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-125 · Linked Data Connectivity
RNX-125.T001
sameAs identity equivalence
core readiness
Link identity references only to profiles of the same real entity.
Why it matters. A similar name or related company is not necessarily the same business.
Illustration — fictional. An identity link points to a general plumbing topic instead of this plumbing company's own profile.
When it applies. Inspected target: sameAs link target. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-126 · Namespace Collision Resolution
RNX-126.T001
Entity disambiguating identifier
Experimental — not an established ranking requirement
Use a verified distinguishing detail when names collide.
Why it matters. A domain, legal identity or location can prevent two firms being mixed together.
Illustration — fictional. Two same-name businesses are described with no domain, locality or other distinguishing identifier.
When it applies. Inspected target: entity disambiguation record. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.