InfiniteRanks documentation
Turn a recommendation into an accountable page task
A useful recommendation names the evidence, affected page, owner and acceptance test. Review it before changing a product claim.
Attach the observation
Start with the exact question and captured answer. Include the cited URL and the passage that creates the concern. Record collection conditions and whether citation evidence is complete. A task without this context can drift into a generic instruction to add more text.
State a reader-facing acceptance test
Instead of “improve AI readiness,” write “explain which export formats are supported and show a valid sample file.” Ask the product owner to confirm the fact. Assign an editor and reviewer. Include constraints that must remain visible, such as plan availability or required permissions.
Follow the approved change
Move work through planned, active, review and follow-up stages as appropriate. Record the live URL and change date after publication. Reuse the baseline questions when checking results. A recommendation is a hypothesis about useful work, not a guaranteed citation increase.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.