Working with page opportunities

A page opportunity is a specific page Iterant thinks you should have, with the reasoning attached. It is the unit of work between finding a gap and having the page live on your site.

Each one carries a draft title, a primary keyword and secondary keywords, a buyer intent, a thesis, the evidence behind it, and a score out of 100 that combines search demand with AI-citation gaps. Most also carry a theme, a role in that theme, and monthly search volume with a competition band.

Where they come from

The discovery agent writes the opportunities. Its runs pull from:

• search demand and keyword difficulty for topics in your space,
• competitor rankings and the coverage gaps they expose,
• AI-answer citations, including whether your brand is cited at all for a prompt,
• your own site's pages and the source material you have uploaded,
• past dismissals, so a reason you give once shapes what gets proposed next.

Opportunities come in two flavours. New proposes a page that does not exist. Optimize proposes improving a page you already have. The queue shows new ones by default, because Build now only applies to those.

Where you find them

• Home: your calendar. Confirmed slots sit on their dates; Suggested rows are opportunities the scheduler has proposed a date for but you have not committed to.
• Needs your attention: the triage strip on Home, holding anything that has gone sideways. See What needs your attention.
• A theme page: the full list for one theme, with bulk select. See Themes.
• The coverage map: planned opportunities appear as ◐ planned rows on the demand band, and clicking one opens its drawer in place. See Reading the coverage map.

Clicking any of them opens the same detail drawer.

Reading the detail drawer

The header carries the score (hover it for the SEO and GEO split), the current lifecycle pill, a link to the theme, and where the opportunity was discovered. Below that:

• Why this matters: search volume, AI searches, and mention counts, with a one-line demand argument.
• What's missing on your site: the gap, plus a You're not cited yet marker when your brand is absent from the AI answers for this topic.
• Why you can win this: the right-to-win argument and the domains currently being cited.
• Traffic evidence: Search Console and Analytics numbers when those integrations are connected, with prompts to connect them when they are not.
• Where this comes from: the non-traffic sources behind the recommendation, with a "may be out of date" caveat when the opportunity has drifted.
• The page we'll build: the pre-flight, covering action, intent, primary keyword, other keywords it targets, the question the page answers, your current rank, and who it needs to outrank.
• Brief: see Draft a brief first.
• Similar pages in this theme: nearby opportunities, so you can spot overlap before building.

The History tab shows what has happened to this opportunity and who did it.

The statuses

Two vocabularies are in play.

The decision track

The opportunity's own state, where it sits in your decision-making, independent of whether a page exists.

dismissed and superseded are terminal. An opportunity in either state leaves the queue and no longer blocks a fresh proposal for the same keyword. You can undo a dismissal from the toast for ten seconds after you dismiss it. A supersede cannot be undone.

What the dashboard shows

Once a page exists, the page's state takes over the display. The pills you see on cards, calendar slots, and the drawer are:

Early states (discovered, enriched, ready) and terminal ones show no pill.

Acting on an opportunity

Build it

Build now appears in the drawer while the opportunity is pre-draft: discovered, enriched, ready, or scheduled. Once a page exists, you work on the page instead.

Pressing it puts the opportunity on today's calendar if it had no slot, moves it to scheduled, and hands the brief to the agent. You land in the chat thread where the build is running, so you can watch it work and steer it.

Two guards you may hit:

• Pressing Build now twice in quick succession gets you Already requested. Try again in a few seconds.
• Starting a build for an opportunity that already has one running gets you Build already in flight. One build per opportunity.

Optimize-type opportunities have no Build now, since the action creates new pages. Improve an existing page through the page itself.

Draft a brief first

To see the shape of the page before committing several minutes of agent time, use Generate brief in the drawer. It takes about 20 seconds and returns a hero hook, a positioning angle, a 4-6 heading outline, and a handful of FAQ questions. Regenerate replaces it.

A brief is a preview, there so you can catch a wrong angle before the build starts.

Schedule it

Scheduling turns a pile of ready opportunities into a publishing plan.

Select opportunities on a theme page and choose Schedule. Iterant computes a plan and shows you the proposed dates grouped by week, with each row's role badge and a tooltip explaining why it landed on that date. Pillar pages are ordered ahead of the spokes that depend on them.

From there:

• Accept commits the dates. Slots are confirmed and the opportunities move to scheduled.
• Edit in Calendar saves the same dates as proposals without committing them, and drops you on Home to fine-tune.

For a single opportunity that already has a suggested date, the drawer's Suggested slot section lets you pick any day directly.

If scheduling fails, the message tells you which case you hit: opportunities that are no longer available, statuses that changed under you, prerequisites that depend on each other in a loop, or a scheduler error. Splitting the batch resolves most of them.

Dismiss it

Dismiss requires a reason. The reason feeds back into discovery, so future runs stop proposing the same kind of thing.

Dismissing a pillar that other pages depend on asks first, listing the dependent spokes, and offers Dismiss pillar only or Cascade-dismiss spokes.

Every dismiss leaves an Undo in the toast for ten seconds, which restores the state the opportunity was in beforehand.

What needs your attention

The triage strip on Home collects the three ways work stalls. It only appears when something is in it.

• Failed: generation or publishing failed. Retry re-runs the publish; View error opens the drawer for the detail.
• Needs review: a draft is waiting on you. Open in Canvas takes you to it.
• Drifted: the slot date passed and nothing happened. Reschedule picks a new date, or dismiss it if it no longer matters.

Clearing this strip is the fastest way to keep the pipeline honest, because the work in it is already paid for.

Troubleshooting