Revenue Journey Assessment
Pricing
from $9.95 / website scan
Revenue Journey Assessment
Scores a business website across five revenue-journey stages - awareness, consideration, decision, conversion, retention - and names the stage that leaks worst. Twenty checks, weighted for the kind of business the site turns out to be. Website-only.
Pricing
from $9.95 / website scan
Rating
0.0
(0)
Developer
Richard Norwood
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Give it a website. It returns a scored read of how that business turns a stranger into a repeat customer — and which stage of that journey leaks worst.
Five stages — awareness, consideration, decision, conversion, retention — weighted for the kind of business the site turns out to be. Sign in to Apify, paste a URL and press Start; there is nothing else to configure.
What you get
One row per run, in the default dataset.
Every run — the scored assessment
Seventeen columns and one nested object. This is the complete list.
| Field | What it is |
|---|---|
overall_score | 0–10, the five stages weighted for this kind of business |
awareness_score consideration_score decision_score conversion_score retention_score | 0–10 per stage |
weakest_stage / strongest_stage | where to spend the next hour, and what already works |
business_class | detected from the site: local, professional_services, ecommerce, saas, content_creator, influencer |
business_class_confidence | 0–1, how much evidence stood behind that call |
naics_code / naics_title | the industry the site reads as |
brand_name | the name detected on the site, or the one you passed |
business_url | the URL as crawled, normalised |
assessment_id | UUID for this run's row |
assessment_date | ISO timestamp of the run |
source_channel | always marketplace here |
assessment_detail.crawl_quality | how good the crawl actually was — see Honest about a bad crawl below |
assessment_detail.audit | how many checks the run flags as unreliable, and why |
assessment_detail.upgrade | your weakest stage, named in one line |
Every run crawls the site, runs every check, and writes this row.
assessment_detail carries the three keys in the table above:
{"crawl_quality": { "status": "degraded", "reasons": ["Only the homepage was crawled"], "pages_crawled": 1, "ttfb_ms": 1561 },"audit": { "needs_review_count": 2, "review_reasons": ["Crawl degraded"], "classifier_confidence": 0.82 },"upgrade": "awareness is the weakest stage at 2.0/10. A full audit - which checks failed, what the crawler found, and what to do about it - is at richardnorwood.com."}
The scores tell you where the journey leaks. Which checks caused it, and what to do about it, is a full audit — see richardnorwood.com.
The full row shape is published in the actor's dataset schema — see the Storage tab on any run.
What it costs
Pay per event. One event, charged once per run:
| Event | Price | What it buys |
|---|---|---|
website-scan | $9.95 | everything above — every column in the table |
A run whose crawl fails outright is charged nothing. The row still gets written, with its zeros
and its crawl_quality: "failed" flag, but you are not billed for a scan that scraped nothing.
No plan gates any of it. Every run does the same work and returns the same shape.
Scored on what a website can show
This actor reads the website and nothing else.
For the full picture — richardnorwood.com
Honest about a bad crawl
A slow, blocked or single-page crawl produces weak readings, and the run says so rather than
reporting them as findings. assessment_detail.crawl_quality carries the status and the
reason:
{"status": "degraded","reasons": ["Only the homepage was crawled — sub-page signals may be missing"],"pages_crawled": 1,"ttfb_ms": 1561}
Every run carries the status, the reasons, and a count of how many checks the crawl made unreliable. A zero that means "we could not see" is never scored as a zero that means "it is not there" — the affected checks are flagged, not silently averaged in.
Input
Only businessUrl is required.
{"businessUrl": "https://www.example.com","brandName": "Example Co","businessClass": "local"}
| Field | Notes |
|---|---|
businessUrl | Required. Must start with http:// or https:// |
brandName | Optional. Defaults to the name detected on the site |
businessClass | Optional override. Leave it out and the classifier decides |
proxy | Defaults to Apify residential proxy, US |
maxConcurrency | Default 5 |
maxRequestRetries | Default 3 |
A run takes roughly one to three minutes depending on how many pages the site exposes.
Getting the results
The run's Output tab links straight to the row. Via API:
https://api.apify.com/v2/datasets/<defaultDatasetId>/items
Or ?format=csv for a flat export — assessment_detail is a nested object, so JSON is the
richer read.


