Use cases

Use cases route one Marketing Signal report by job. They do not create separate products or change the report.

Start at the hub

Send someone to Use cases when they know their job but not the right workflow. The hub lists only approved, published child pages.

The report identity stays the same:

One numeric score and one band
Scored from N of M applicable checks.
SEO, Content, Answer Engine Optimization (AEO), Analytics and Tracking, Conversion, and Trust and Proof
Visible result states and prioritized findings
Points available for score-moving gaps

Choose the destination

Send a developer to Marketing Signal for developers when a new or changed page needs page-level marketing QA. The workflow covers one rendered page before or after a change, one selected finding, and a later Page Check.

Send someone to Agent workflows when they already have a finding and need the person-or-agent handoff.

Send someone to Marketing Signal checks when they need the scoring method, category meanings, result states, or report limits.

Keep the job page honest

Use-case pages explain how a role uses Marketing Signal. They do not promise whole-site coverage, automatic fixes, deployment, monitoring, rankings, citations, traffic, or conversions.