Opportunities

Pages ranking just off page 1, where a small push could move them onto it.

In appWorkspaces›Opportunities

Why these pages and not others

A page sitting at position 11 to 20 already has most of what it needs: Google understands it and is willing to rank it. Moving it up a few places changes the clicks it gets far more than the same work on a page at 60.

That's the whole idea. These are the shortest routes to more search traffic you have.

What each card tells you

The queries the page is close on, how close, and what's between it and page 1. Usually that's thinner content than the pages above it, or fewer internal links pointing at it.

Start at the top. The order is by how much there is to gain, not by how easy each one looks.

What to do with it

Rebuild in Studio opens a full Content Studio session for the page, with the near-miss queries already loaded.

Ask Advisor puts the decision to your Strategist, which is the better first step when you're not sure whether the page or the links are the problem.

Working a finding

Open any finding and you can take it somewhere else without retyping it. Ask Advisor opens the Strategic Advisor with that finding and its full context already loaded, so you can ask why it matters or what to do first and get an answer using your own numbers. Create brief (or Rebuild in Studio) opens a Content Studio session for the page, pre-filled the same way.

Both carry the finding with them. You're not starting a conversation or a brief from nothing, which is the whole point of launching them from here rather than from their own screens.

Most findings also carry an AI Playbook: a written recommendation for that specific page. Some are generated automatically after a run, the rest are generated when you ask. You can also tick several rows and generate advice for all of them in one go, with the cost shown before anything runs. How many are written automatically is the Auto-generate for top setting in that analyzer's Configure panel, and zero means they're only written on request.

Mark applied does more than tick it off. The page joins Impact Tracking in Command Center, which then follows its clicks, impressions and position from that date onward, so you can see whether the change did anything.

Getting rid of one you don't want

Ignore on any finding hides it. It leaves the queue and moves to the Ignored pill in the filter rail, where Restore puts it back, so nothing is destroyed. The Ignored pill only appears once you've ignored something.

Ignoring handles one finding. If the same pages keep coming back, add them to Excluded pages in Settings, under Data Pipeline: find Opportunities in the analyzer list and click Configure. One pattern per line, * as a wildcard, and plain text matches anywhere in the URL. Matching pages stop becoming findings from the next run.

That's the difference worth knowing: ignoring hides one finding, excluding a page stops future findings for it. Tag pages, author archives and paginated listings are the usual candidates.