What’s prio now?
No extra input. The current GSC snapshot is ranked as-is. This is prio 1, this is prio 2. Use it weekly when the question is simply: what should we work on next?
Turn the latest Search Console snapshot into a numbered “do this first” list.
Dump the current GSC data. TopicalLoop tells you what is prio 1 right now — create a pillar, improve a page to catch extra intent, merge overlapping URLs, or update decaying content — ranked by expected incremental traffic. Or tell it what you want, and it uses the data to find the highest-traffic way to do it.
A ranking layer, not another catalogue
Traffic Priorities is the most concrete content decision point in TopicalLoop. It reads the latest Google Search Console snapshot and returns a numbered list. Prio 1 is the highest-leverage content move — not a tray of maybe-later opportunities.
Goal
You state an outcome — a pillar around a topic, more commercial intent, a service cluster. The same GSC data shows the highest-traffic way to get there, instead of starting from a blank brief.
Every action is exactly one of four types
No mixed labels, no “consider reviewing”. Each row is one content move the data can support from the current snapshot.
New pillar
The query is already in Search Console. No existing page owns that intent. Creating a new page is the move — not expanding something that does not rank for it.
Improve page
An existing URL already collects impressions or ranks for extra intents. Expand that page instead of publishing a competitor to yourself.
Merge
Two or more URLs are splitting the same intent. Combine them rather than writing a third page into the overlap.
Update
An existing page is decaying or stale relative to the demand still showing in GSC. Refresh it before the impressions disappear.
How it sits next to the rest of the platform
Agencies already have lists. Priorities answers a different question: given this week’s Search Console data, what is the one move with the most incremental traffic?
Site Brain
Topic ownership: which URL owns which topic. Priorities uses that map so “new pillar” is not suggested when a page already owns the intent.
Opportunities
A catalogue of GSC and keyword signals, tagged high, medium or low. Useful inventory. It is not a numbered “do this first” list.
Refresh & Consolidate
The execution queue for existing pages — merge, update, expand. Priorities decides the move; Refresh is where the work on current URLs gets queued.
How teams use it
- After a Search Console sync, open Overview → Priorities in the project workspace
- Run “What’s prio now?” at the start of the week, or switch to Goal when you already know the outcome
- Take prio 1 into a Content Studio brief, or into Refresh & Consolidate if the move is merge or update
- Re-run after the next GSC sync — the list is the current snapshot, not a stored backlog
- If two pages already share impressions for the same intent, prefer improve or merge over a new page
This replaces the familiar “export GSC, paste it into a chat, ask what to do” workflow. The ranking stays inside the same workspace as Site Brain and content execution. It does not publish anything and it does not promise rankings — it ranks the next content decision against the data you already have.
Frequently asked questions
How is Traffic Priorities different from Opportunities?
Opportunities is a catalogue of GSC and keyword signals, tagged high, medium or low. Traffic Priorities is a ranking layer on the current Search Console snapshot: a numbered list of what to do first, not another inventory of possible work.
How is Traffic Priorities different from Refresh & Consolidate?
Refresh & Consolidate is the execution queue for existing pages — merge, update, expand. Traffic Priorities decides which content move is prio 1 right now. A priority can become a brief in Content Studio or a task in Refresh & Consolidate.
Does Traffic Priorities publish changes automatically?
No. It is a decision layer on Search Console data. Your team still writes, reviews and deploys. It does not promise automatic publishing or guaranteed rankings.
Where do I find Traffic Priorities in the app?
In a project workspace, open Overview → Priorities. After a Search Console sync, the current snapshot is ranked into a numbered list. The Dashboard also links to Traffic Priorities.
Related pages
See what prio 1 looks like on a live workspace
Book a short demo. We will walk through a Search Console snapshot, the numbered list, and how prio 1 becomes a brief or a refresh — without treating it as another opportunity export.
Book an agency demo