---
name: measure-content-rankings-traffic-revenue
description: "See where content stops doing its job."
category: Strategy & Measurement
stage: —
definitive_article: GAP — to be written
status: needs-work
---

# Measure content → rankings → traffic → revenue

See where content stops doing its job. This guide puts pages, search visits, leads and sales in one clear view. Start with the pages you shipped and the sources that can prove each next step.

**The path:** Published content → Search visibility → Visits → Leads and sales

**Start when:** The team needs a sourced view from published content through search and business outcomes.

## Inputs

- The actual publishing log with canonical URLs and dates.
- Matching Search Console and site analytics reports, plus inquiry, booking and revenue records where permitted.
- The agreed source contract, period, targets and attribution limits; [Metrics, Analysis, Action: what happened, why and what to do](https://blitzmetrics.com/maa/).

## Steps

1. Create one row per canonical page or explicitly defined topic group. Name the metric and source for each stage: actual published assets; search impressions/position/clicks; site visits; qualified inquiries, bookings and revenue separately.
2. Pull matching periods and preserve metric definitions. Search Console clicks and analytics sessions measure different things; do not silently force their totals to match.
3. Attach page-level business outcomes only when the source supports attribution. Keep unknown or unassigned outcomes visible. Leads are not revenue, and publication is not an indexed-page result.
4. Find the first supported weak link relative to the target and observation window. Content without search visibility can need indexing, topic fit, structure or time; verify the cause before prescribing more pages.
5. For visible pages with few clicks, inspect queries, actual positions, competition and snippets. For visits with few leads, test the page and follow-up. Do not assign a title or offer failure from a ratio alone.
6. Choose a bounded next diagnostic or repair, with owner, evidence and pass rule. Check the [SEO Tree, the map of related pages](https://blitzmetrics.com/seo-tree/) before proposing page moves or new content.
7. Save the table and trend with source gaps. Feed the evidence into the weekly report and check the chosen action’s outcome in the next comparable period.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the result against its agreed requirements; see the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] The table distinguishes published assets, visibility, visits, leads, bookings and revenue.
- [ ] All values have dates and sources; unknown attribution is preserved.
- [ ] A supported weak link or open question has a specific next action and owner.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional page has 500 search impressions,20 clicks and 18 recorded sessions. It has two forms, but the sales record has no matching page attribution. The report shows the two forms and unknown page revenue. It checks form quality next rather than declaring that 18 visits made the week’s total sales.

## Handoff and Content Factory context

[Show what works and what needs review](https://local-service-spotlight.github.io/task-library/?task=show-whats-working-and-what-isnt#task-show-whats-working-and-what-isnt) and [Write the agreed weekly report](https://local-service-spotlight.github.io/task-library/?task=submit-weekly-maa-report-every-friday#task-submit-weekly-maa-report-every-friday) receive the linked table; the relevant page or tracking task receives the exact defect.

This work supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/) across its relevant stages. It uses the actual inputs and next owner above; a strategy or measurement guide does not manufacture transcripts, clips or other unrelated stage outputs.

## Start with an agent

Give the AI worker this recipe, the real Inputs, the desired result and the actions already authorized. Ask for the saved output, source evidence, passed and failed checks, and the next owner. A skill is a set of instructions. Loading it does not prove access, install a scheduled job or complete the work. Use the [current installation guide](https://localservicespotlight.com/install/) only if reusable setup is needed; a ZIP contains instructions and is not an access grant.

Use the actual supported app and verified source access. A model name is not a promise of browser control, memory or unattended work. For recurring work, inspect the real job’s trigger, owner, timezone and observed firing; this recipe creates no schedule. Before any media playback, mute the player and set volume to zero. A silent review does not prove sound was heard.

## Record the real execution

Open the run record when work begins. Keep one execution ID, the exact starting recipe revision, input sources and actual state. Write a [meta article, the record of one real execution](https://blitzmetrics.com/meta-article-prompt/) with results, checks, failures and next owner. Link it to this task in the [Task Library](https://local-service-spotlight.github.io/task-library/). Writing is required; public release follows existing authority.

Reuse the same execution ID for internal reviews, meta writing, revisions and retries. A blocked run stays open with its dependency and owner, without an invented finish time. Keep historical public examples as dated evidence; article counts alone are not verified execution frequency. Use supported findings to propose and verify a recipe improvement.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- A dedicated canonical article is not mapped in this task’s source. Use the linked method references above and resolve the correct existing owner before creating another page.
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=measure-content-rankings-traffic-revenue#task-measure-content-rankings-traffic-revenue)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records work together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `needs-work`. It is preserved, not promoted by this rewrite. That label alone does not verify document readiness, account access, an actual execution or a client outcome.

A relevant real execution, source evidence, independent reviewer and accepted handoff remain to be recorded. The fictional example teaches the method and does not fill a real-run evidence gap. The opening and full method need a named semantic reviewer; the task-specific path is source guidance, with visible desktop/mobile presentation still to check.