Google Search Console integration
Search Console revenue: which keywords make you money
Search Console tells you which queries bring clicks. Joinsight tells you which ones bring paying customers. Page revenue is measured from real first touches; keyword revenue is modeled from each query's share of the page's clicks, and labeled that way.
No card required. The trial clock starts when your first revenue source connects.
What Joinsight answers with Google Search Console
- Revenue per landing page from organic Google search, measured
- Revenue per query, modeled by splitting each page's revenue across the queries that sent it clicks
- How much revenue sits behind anonymized queries Google hides, kept in its own bucket instead of spread across the rest
- Keyword opportunities: queries at positions 8 to 20 on pages that already earn, ranked by impressions × revenue per click
- Alerts when a page that makes money starts slipping in search
What it reads
- Clicks, impressions, CTR and average position by query, page and day, with read-only access
- All 16 months Google keeps, backfilled on the day you connect
- The last few days again on every sync, because Search Console data arrives 2 to 3 days late
Good to know
- Keyword revenue is always modeled: Google never reveals which query a specific visitor typed.
- Anonymized queries can hide a large share of clicks. Their revenue is shown, not guessed.
- Only organic Google visitors are split by query. Other channels are attributed by page and channel.
Setup
- Sign in with Google and pick the Search Console property.
- Joinsight backfills 16 months of query and page data. Search trends show the same day.
- Connect Stripe or RevenueCat and install the snippet. Page revenue appears as customers arrive.
Questions
Why is keyword revenue labeled modeled?
Search Console reports clicks per query and page in aggregate. Joinsight knows which page a paying customer landed on, but not the exact query, so it splits that page's revenue by each query's share of clicks. The page number is measured; the query split is an estimate.
What are hidden queries?
Google anonymizes rare queries to protect privacy, so their clicks appear in page totals but not in the query list. Joinsight keeps the revenue from those clicks in a separate hidden-queries bucket.
Works well with
- Stripe
Connect Stripe with a read-only restricted key and see which landing pages, Search Console queries and channels brought your paying customers, next to accurate MRR and movements.
- RevenueCat
Connect RevenueCat to see mobile and web MRR as one number, deduplicated against Stripe, and tie App Store and Google Play revenue to the content and campaigns that drove it.
See what makes you money.
Connect Stripe or RevenueCat and Search Console, and you see combined MRR and 16 months of search history on day one. Page and keyword revenue follow as the snippet collects first touches.
No card required. The trial clock starts when your first revenue source connects.