What is in the queue
Items arrive from across the product and carry the source they came from: work on your content, a change to your website, something the answers are saying. Each one shows an expected impact, from very high down to very low, and a next step rather than a restatement of the problem.
A separate needs attention count flags items that have gone stale or whose underlying finding has changed.
The sidebar badge is personal
The number next to Actions in the sidebar counts the items assigned to you, not the total in the queue. Two people looking at the same workspace see different numbers, and someone with nothing assigned sees none at all. This is on purpose. A badge showing the team’s whole backlog is a number nobody acts on; a badge showing your own three is one you clear.Working the queue
Filter by state to separate triage from execution. The usual rhythm is to take the new items once a week, decline what does not fit, assign the rest, and leave in-progress work to the people holding it. Record a decline rather than leaving the item new. The next person to open the queue then sees the decision instead of re-making it.How an action relates to the finding behind it
Closing an action records that you did the work. It does not verify the result. Whether the answers changed is what the next tracking run tells you, and whether your site changed is what the next audit tells you. So expect a lag. Content published this week will not move brand visibility until the engines have re-read your site and a run has asked the questions again. Judge the work on the next few runs.Where items come from
- Gap trends. Accepting a suggestion on a gap creates work, usually a brief.
- Audit report. A content finding can become a brief directly; technical findings become site work.
- Content performance. A published page that is not being cited.