Rankout
Start My Free Trial

Changes & implementation

For each work item RankOut drafts exactly one change, shows the diff, and applies it only after you approve — through the WordPress Connector, a GitHub pull request, or a recorded manual change — then validates it.

The Changes page is the execution queue. Nothing here touches a live site without an explicit approval.

How a proposal is drafted

When you ask RankOut to draft a change for a work item, it runs a bounded loop: it inspects the live page (read-only), works out the single most targeted change that accomplishes the action, and produces one proposal — a specific tool call or file change, a summary, and an explanation grounded in the action's what / why / how. It never runs a write operation during drafting.

  1. 1

    Draft

    From Changes or the work item, choose Draft proposal. RankOut inspects the page and produces a pending proposal. The work item moves to Waiting approval.

  2. 2

    Review the diff

    The proposal shows exactly what will change — the before and after values, or the full new file content for a PR.

  3. 3

    Approve or reject

    Approve to apply it. Reject to send the work item back to Ready with the proposal recorded as rejected.

  4. 4

    Apply

    For the WordPress Connector, RankOut runs the one approved tool call. For GitHub, it opens a pull request. For manual, you apply it and mark it done.

  5. 5

    Validate

    For connector changes RankOut immediately reads the affected value back and compares it to what was approved. Pass moves the item to Done; a mismatch moves it to Blocked with the details.

dashboard.rankout.app

A change proposal showing the before and after values with approve and reject actions

Loading…

Every proposal is one change, with a diff, waiting for a person to approve it.

Rollback

For a WordPress Connector change that was applied, RankOut records the WordPress revision it created. If the change needs undoing, Revert restores that revision through the connector and sends the work item back to Ready. GitHub changes are undone by closing or reverting the pull request in GitHub.

Validation is not impact. A schema or meta change can be validated in seconds — that only confirms it's live. Whether it moved rankings or citations is measured over weeks on the Results page.

Common questions