Use this worksheet when a page has traffic potential but the next action is vague, too aggressive, or hard to measure.
The goal is to make the reader promise, destination, and measurement event agree before a button is published. A strong route is not louder; it is easier to trust, easier to click, and easier to audit.
| Slot | Question | Working note |
|---|---|---|
| Reader state | What does the reader already understand after this page? | Checklist done, gap found, or measurement doubt confirmed. |
| Button promise | What will happen immediately after the click? | Copy a worksheet, check a snippet, or request a scoped diagnostic. |
| Destination | Does the destination satisfy the promise without surprise? | Template page for self-serve; Diagnostic Sprint for ambiguous multi-page issues. |
| Friction level | Is the ask proportional to the reader's certainty? | Template first, tool second, inquiry only when the issue has clear scope. |
| Measurement event | Can the route be measured without private data or credential sharing? | Use one event name, one label, one target, and no internal UTMs. |
| Intent | Safer label | Avoid |
|---|---|---|
| Self-check | Copy the CTA Route Map | Get the secret template |
| Measurement check | Check a measurement snippet | Fix all tracking now |
| Scoped review | Scope a Diagnostic Sprint | Book growth strategy |
click_template_cta_route_map
click_tool_d02_measurement_snippet
click_service_diagnostic_sprint
Recommended fields:
click_label
click_target
click_position
source_page_familyKeep internal navigation free of campaign UTMs. Use campaign UTMs only for approved external distribution, and keep them out of internal article-to-template routes.
When a site has more than one monetization route, separate the event families with the Route Click Event Map before reading conversion performance.
If several pages fail the same route check, treat it as a system issue and write a short scope note before changing design, measurement, or copy.