Contextter Product Docs

Priorities and evidence

Every Action Center item should help a teammate understand why it is in the queue, what is affected, what to do, and how to verify the result. A short title alone is not enough for a safe SEO decision.

Impact

A relative signal for how much the available evidence suggests the action could matter within the current workspace.

Effort

A practical estimate of the work needed to investigate, implement, and verify the recommendation.

Evidence

The keywords, affected URLs, issue instances, page details, or link relationships that support the recommendation.

What a complete action contains

FieldWhat to look for
SourceKeyword Database or Site Audit, so the original evidence remains inspectable.
ProblemA plain-language explanation of what is wrong or what opportunity exists.
Affected scopeThe keyword set, pages, URLs, links, or issue instances involved.
Recommended stepsA small sequence that can be assigned and completed.
Impact and effortRelative decision context, not universal truth.
VerificationThe data refresh, tracking check, or next crawl that can confirm the outcome.

Example: missing canonical tags

The action might say that several pages do not name a preferred URL. The problem description explains that ranking signals can become divided and indexing less predictable. A useful task sequence is:

1
Open the affected URLs and identify the preferred page for each group.
2
Check whether the page should self-canonicalize or consolidate to another URL.
3
Add or correct the canonical tag in the rendered page output.
4
Run another crawl with the same relevant scope.
5
Confirm that the issue instances are resolved and no new conflicting targets appeared.

Why priorities can change

The queue can change when the selected goal changes, fresh keyword data arrives, a new crawl changes affected scope, or completed work removes a previous issue. This is expected. Action Center is designed to remain useful as evidence changes, not to freeze one report forever.

Review before assigning work

Before an action becomes a ticket or client commitment, confirm that the source evidence is current, the affected scope is representative, the proposed fix matches the site implementation, and the team can verify the result.