RNX is Runexus's methodology for organizing checks of search and AI discovery readiness. This edition follows its November 2026 corrective proposal. It is not an adopted industry standard, a search-engine certification or a promise of ranking results.
The reference uses ten numeric families. A family is a broad area. Under it are more specific parent codes and atomic controls. Atomic means a check narrow enough to evaluate on its own evidence.
Read an identifier
In RNX-112.T001, RNX-100 is the family, RNX-112 is the immediate parent and .T001 identifies an atomic control. That control checks domain-name resolution. Another control under the same parent checks the security certificate. They need different observations even though both affect access.
The family titles below are the exact titles in the canonical hierarchy. Their formal wording is preserved so that this guide, the standard and a report refer to the same thing.
- RNX-100 · Perception Standard
- RNX-200 · Authority Standard
- RNX-300 · Intelligence & Communication Standard
- RNX-400 · Governance, Compliance & Ethics
- RNX-500 · Performance & Efficiency Standard
- RNX-600 · Topic Architecture Standard
- RNX-700 · Resilience, Adversarial Defense & Future Compatibility
- RNX-800 · Search Demand, Intent and Content Strategy
- RNX-900 · On-Page Search and Experience Presentation
- RNX-1000 · Measurement, Experimentation and Search Operations
Decide whether a check belongs
A product-feed check belongs to an applicable product feed, not every website. A private-agent authorization check belongs to an implemented private service. A local-hours check needs a business with relevant hours. Some checks examine business plans or provider accounts rather than public web pages.
Applicable means the actual conditions fit. Not applicable means they do not. Unknown means necessary evidence is missing. Not evaluated means the review has not been performed. Unknown and not evaluated are not failures, and they are not passes.
Read the evidence label
The reference preserves the source's lane labels. Core readiness identifies its core lane. Experimental identifies controls outside mandatory SEO/AEO compliance; it does not mean the underlying security or business practice is unimportant. It means you must not treat it as an established ranking requirement. Other source labels, if present, are retained.
The short entries explain purpose. They do not replace the canonical definitions, applicability logic or full technical tests. No business should claim complete RNX conformance merely by counting filled fields or turning every possible feature on.