Which token scope is needed?

RankSage writes to · Personal access token

The ranked action queue, as Azure DevOps work items.

Any action-queue item can become an Azure DevOps work item, placed in the project, area and iteration you choose at export time, with the page and the evidence carried in the description.

How RankSage works

What it provides

What Azure DevOps gives RankSage.

Outbound export of action-queue items as work items, evidence included.

Placement-aware export from live project, area and iteration pickers.

Setup

How to connect.

Add a personal access token

Scoped to work-item write access on the organisation.

Choose project defaults

Changeable per export.

Export from the queue

Work items appear with links back to RankSage.

What it unlocks

The capabilities it feeds.

One ranked queue

Playbooks, recommendations and tasks merged into one what-do-I-fix-next list, ordered by a weighting you can read.

Content Gaps

See the topics competitors cover and you don't — scored by real search demand rather than by how many rival pages exist.

Frustration Report

Find the pages where visitors visibly struggle and the content is thin — the only place both signals point at the same URL.

Limits

What it does not do.

One-way: RankSage creates work items and does not read Azure DevOps back into reports.

Work items are created under the token's permissions.

FAQ

Questions about Azure DevOps, answered.

What it provides, what it needs, and where its edges are.

Work-item read and write on the organisation you connect. RankSage does not need code, build or release scopes.

See every integration

EARLY ACCESS

Start with the two that matter.

Google Analytics and Search Console, read-only, about five minutes. Add Azure DevOps whenever it earns its place.