
Illustrative scenario, not a client case: a Johannesburg B2B services brand has demand spread across Sandton CBD, Rosebank, Midrand, Roodepoort and Soweto. One search campaign, one blog, one 'Joburg' landing page. Paid and organic teams have never compared notes.
Context: One Johannesburg Business, Six Trade Areas, Two Channels That Never Compare Notes
Johannesburg demand is not distributed evenly, and it is not distributed by suburb boundaries either. A buyer in Midrand weighing a B2B service searches differently from a Rosebank professional researching the same offer, and a Soweto customer may use a completely different phrase for the same intent. If your paid team targets 'Johannesburg' and your SEO team builds one city page, both channels are guessing at a geography neither has mapped.
The fix is not another dashboard. It is a shared asset: a node-level intent map that both Google Ads and your organic programme read from. This is the discipline we apply as a Johannesburg-based agency founded in 2016 by an ex-Google employee, and it is covered in more depth through our strategy consulting service.
Why a Single "Johannesburg" Campaign Is a Targeting Mistake Before It Is a Strategy Mistake
Google Ads location targeting lets you reach people by country, region, city, radius or location group - and the choice of method materially changes who sees the ad. Targeting the metro as a single city collapses six distinct demand pools into one bid strategy, one budget and one average CPC that describes nobody.
The same error repeats organically. One 'services in Johannesburg' page competes for every node at once, ranks for none convincingly, and gives Google no clear signal about which geographic intent it should satisfy. Neither channel is wrong about its tactics; both are wrong about their unit of analysis.
The Intent Map: Node × Service × Urgency as the Shared Asset Behind SEO and PPC
Build one grid before spending anything. Rows are trade-area nodes, columns are service lines, and each cell captures the dominant intent and urgency. Both channels then work from the same source of truth.
| Node | Dominant intent | Paid treatment | Organic treatment |
|---|---|---|---|
| Sandton CBD | High-value B2B, research-heavy | Exact-match service terms, bid up on radius | Node page with case-led proof |
| Midrand | Logistics and trade, price-sensitive | Broader modifiers, cost-control caps | Comparison-led content |
| Soweto | Mobile-first, vernacular phrasing | Local language variants, call assets | Plain-language service pages |
Reading Johannesburg Search Language: Abbreviated Place Names, Vernacular and Service Modifiers
Johannesburg searchers rarely type the full name. 'Joburg', 'JHB', 'Sandton', 'Midrand' and 'Fourways' all appear as shorthand, and the same service may be described with different words depending on the node. Your intent map should record the actual query phrasing observed, not the phrasing your brand prefers. SEO builds geo pages around node plus service intent; PPC mirrors that language in ad copy and keyword variants.
Do not create a page for every suburb on the map. Only nodes with genuinely distinct intent or service demand earn their own page - otherwise you are publishing doorway content that Google's people-first guidance explicitly discourages.
PPC Mechanics That Make a Node Map Real: Location Targeting and Bid Modifiers
In Google Ads, apply the node map through location targeting plus bid adjustments: bid up where margin supports it, bid down or restrict radius where it does not. Many advertisers miss the presence versus presence-or-interest toggle, which quietly widens reach beyond the node. That single setting can undo an otherwise sound target map.
Where SEO Earns Its Place: Node-Level Landing Pages Built for Genuine Local Intent
Organic work earns its place inside nodes where paid clicks are costly and demand is durable. Node pages should answer the specific service question that node asks - with local proof, staff, service radius and pricing signals - not a template with the suburb name swapped. Our SEO and AI SEO service builds these pages against the same intent map that informs paid media.
The Sequencing Playbook: Paid Buys the Node While Organic Catches Up
Sequencing is the difference between two channels running in parallel and two channels compounding. The rule: paid buys the node the moment commercial intent is proven, while organic builds the page that will eventually carry that demand at a declining cost. As organic ranking improves in a node, shift paid emphasis there from broad capture to high-intent defence - remember Google's guidance that top positions frequently capture a disproportionate share of clicks, so plan for the plateau rather than assuming a straight linear gain.
Reverse the logic where CPCs in a node are prohibitive or auction competition is saturated. Organic gets prioritised first, with paid used narrowly to test which queries and offers actually convert before budget is committed at scale.
A Trade-Area Decision Table: Where to Lead With Paid vs Where to Lead With Organic
| Node condition | Lead channel | Why |
|---|---|---|
| Urgent, commercial query | Paid | Deterministic capture now |
| Saturated, expensive auction | Organic first | Own the node at declining cost |
| Long research cycle | Organic, paid retargeting | Content informs, paid re-captures |
| New service launch | Paid first | Proves intent before content spend |
Measurement: Per-Node CAC, MER and Attribution Accuracy
One blended 'Johannesburg' CAC hides the fact that one node may be profitable and another loss-making. Measure CAC, MER and LTV per node. Treat platform-reported conversions as directional and reconcile against a server-side pipeline before making budget calls; our custom reporting approach is built for exactly this reconciliation.
// Illustrative config, not a recommendationcampaign.location_targeting = presence_onlybid_modifier(radius_5km) = +20%bid_modifier(radius_10km) = baselinebid_modifier(radius_20km) = -30%What the Playbook Assumes: Consent, POPIA and Clean Data Before Any Node Spend
None of this works on dirty data. Consent mode must be implemented before geo reporting means anything, and POPIA obligations shape what you can collect and retain. The assumption is a clean event pipeline, server-side tracking where appropriate, and a single source of truth both channels write to.
Common Failure Modes in Johannesburg Combined Programmes
- Presence-or-interest left on, widening reach beyond the node.
- Node pages built as duplicated templates with the suburb swapped.
- Organic and paid reporting to different conversion definitions.
- Budget held flat per node long after organic took over demand.
What Outcomes a Node-Level Programme Is Designed to Produce
Expect clearer attribution, node-level CAC you can defend to a CFO, and a paid-to-organic handoff that lowers blended acquisition cost over time - not overnight. Prebo Digital is a Google Premier Partner (2022-2026) and verified Amazon Ads Partner; our Google Ads team builds the map before the media plan.



