Loading
Because traffic is measurable in the analytics tool and revenue is not. So the report is sessions and rankings, and the question everybody actually has — did this produce customers — is answered with a proxy.
Meanwhile a documentation page pulling large volume and no trials outranks, in the report, a comparison page producing three customers a month.
Source tracking carries the landing page through lead, deal and closed revenue in Books, so organic performance is reportable in money on the same record.
Keyword clusters map to pages, and cannibalisation detection catches the case where three of your own pages compete for one term — common in SaaS, where docs, blog and product pages overlap.
It will not write the content or build links. It tells you what to write and in what order, with the evidence behind each.
And it cannot attribute what it cannot see. Self-serve signups that never become a deal record need the join supplying through the API.
The opportunity backlog is ordered by evidence rather than by whoever asked, and the priority matrix weighs effort against the revenue the cluster has actually produced.
Content gaps and competitor keyword gaps show where a comparison or an integration page is missing rather than assumed.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, where the source carries through to a closed deal in Books.
Yes — including docs and blog competing with product pages.
No. It produces briefs and priorities; writing stays with people.
Half an hour on your own numbers is usually enough to say whether Growth is the right place to start.