The opportunity queue

Where recommendations come from

The queue brings together eligible stored audit findings, cluster recommendations, and keyword-target candidates. It reads available evidence; opening the dashboard does not run a new audit or build a new cluster analysis.

Google Business posting has a separate calendar and publishing queue. Its posts are not actions in this SEO worklist.

What each row carries

• The move. A recommendation to retitle, rewrite, create, consolidate, differentiate, or prune.
• The evidence. Observed history or a labeled modeled basis, supporting statements, and a demand verdict when applicable.
• Confidence and limits. What supports the move and what the recommendation cannot establish.
• A projection, when available. A click ceiling with the arithmetic shown.

Reading the click ceiling

A projection phrased as “up to” clicks a month is a ceiling under stated assumptions. It is not expected additional traffic or a guaranteed return. Compare the observed rate, relevant comparison rates, and the formula before using the number.

A larger ceiling alone does not establish that one task should come first. The queue also considers evidence basis, screening, and confidence. It does not currently measure task effort.

Which actions you can take

Supported retitle rows open metadata editing in Site Audit. Rewrite rows can seed a refresh in Blog Studio when both the page and query context are available. Create rows can seed a new draft when a target query is available.

Consolidate, differentiate, and prune currently remain recommendations. They do not have an execution destination. You can dismiss a row you choose not to pursue.

Starting supported work marks the recommendation in progress. Starting a draft is not the same as publishing it.

For a retitle, apply the reviewed text using the Wix, WordPress, or Squarespace metadata guide. For a draft you publish yourself, follow the manual publishing steps.

Why candidates are set aside

Reasons can include already-covered targets, insufficient measured demand, refuted or unverified demand, missing page measurements, and duplicate moves. Read the stated reason rather than assuming every missing item has no demand.

An empty queue can mean there is no data to inspect yet, or that the inspected candidates did not support worthwhile work. Onça distinguishes these outcomes and reports the available refusal reasons.

The source context is explained in Sources and signals.