RuneIndex is the free public website assessment at runexus.io/scan. Enter your website's public address and start the assessment. Use a site you are authorized to assess. The report is a snapshot of captured evidence, not a complete audit of everything the business does.
Read the three parts
Website Analysis contains checks supported by the scanner's website observations. AI Analysis contains controls actually evaluated from captured content when the AI service is available and produces usable evidence. An AI reading of your website is not a live observation of your business being recommended in a consumer AI product.
Additional RNX Controls identifies checks that were not assessed in the completed analysis. Some need owner records, specialist testing or a feature the site does not use. Do not treat that list as a set of confirmed failures or as work every business must implement.
Understand colors and scores
Read the status words and evidence before the color. PASS means the observed check met its rule within the tested scope. PARTIAL means a supported intermediate state where the control allows one. FAIL means evidence supports a failed requirement. Unavailable evidence should remain unresolved.
The current score rings use red below 40, orange below 60, yellow below 70, green from 70 to below 100, and blue for 100. An unmeasured result has no numeric score. Section rings summarize evaluated observations in their numeric RNX families. The headline score uses the public scorecard's rules and coverage safeguards; it is not a simple count of every entry in this book.
A high score does not guarantee a ranking or recommendation. Read which checks were evaluated and which evidence is missing. Two scans with different coverage are not necessarily fair comparisons, even when their headline numbers look precise.
Turn a finding into a next step
Open the affected finding and note its exact RNX ID, source address, captured evidence and explanation. Confirm the issue against the intended page or business record. Assign a person to correct it, record the change and assess again. Check whether the affected observation changed; do not assume every later traffic change was caused by that fix.
If AI analysis is unavailable, keep the useful Website Analysis findings. Do not fill the gap with guessed AI results. A failed fetch may also need investigation before any content judgment is possible.
Use the score to start a conversation. Use the evidence to choose the work.