Prebo Digital

Featured Articles

Stay ahead with our latest insights and proven strategies

Latest Articles

web-design-pricing — web-design heroWeb Design

Page Speed as a Profit Lever: Web Design Performance for South African Sites

The Scenario: Strong ROAS, Weak Profit - Where the Speed Tax Hides Picture a hypothetical Johannesburg e-commerce or B2B lead-gen operation running Google Ads. The dashboard reports healthy ROAS and a manageable CPA. Then finance reports thinner margin than the ad platform suggested. The gap is usually not bid strategy - it is a speed tax on paid media . Paid clicks land on a page that never finishes painting on a mid-tier Android device on a congested mobile network. The click is paid for; the conversion never registers. Every session that abandons before the largest element paints is ad spend you have already paid for and cannot reclaim. It shows up as a low conversion rate and a quiet CPA drag. Why Field Data, Not Lighthouse, Decides What You Fix Lighthouse is a lab diagnostic on simulated hardware - it tells you what could be slow. Field data (CrUX in PageSpeed Insights and GA4) reflects real devices and networks. For South African audiences that distinction is decisive, since your visitor mix skews toward mid-range Android on variable connectivity. Core Web Vitals thresholds are the measurement instrument, not the point: LCP good at ≤2.5s (poor >4s), INP good at ≤200ms (poor >500ms), CLS good at ≤0.1 (poor >0.25). INP replaced FID in March 2024. Google frames page experience as a tiebreaker-type signal, so treat speed as a conversion and media-efficiency lever , not a ranking trick. Instrument What it tells you When to use it CrUX / GA4 field data Real device/network experience by page group First - prioritise templates that hurt users PageSpeed Insights (lab) Diagnostic causes and opportunities Second - plan the fix, not pass/fail South Africa's Two Structural Speed Constraints First, hosting: an EU or US data centre adds round-trip latency to every request before a South African browser renders anything. A CDN with nearby points of presence, or local hosting for dynamic workloads, cuts that baseline. Second, network variance: peri-urban and rural mobile connections fluctuate, so a page borderline in Sandton can be unusable elsewhere. Design for the slower connection, not office fibre. The Fix Sequence, Ranked by Lever Work in lever order, not by whatever is quickest. Hosting and edge caching deliver the biggest structural gain, then front-end weight, then the marketing and tracking stack - stripping measurement to chase a score is a false economy. This sequencing sits at the heart of how performance-minded web design should be planned. Lever 1: Hosting, Edge Caching, and TTFB Measure TTFB before changing anything. A quick curl check localises the delay: curl -o /dev/null -s -w 'TTFB: %{time_starttransfer}s\nTotal: %{time_total}s\n' https://yourstore.co.za/ If TTFB sits well above half a second from a South African connection, edge caching and origin location are your first project - no image compression rescues a high-latency origin. Lever 2: Front-End Weight - Images, Fonts, and the Render Path Hero images are the usual LCP culprit. Serve responsive AVIF/WebP, size correctly, and preload only the hero asset. Trim font families, self-host where sensible, and defer non-critical script so main content paints earlier. Launch-day promo banners and double-loaded hero images are the recurring offenders on South African retail templates.

Nov 20, 20265 min read
Read more
how to read web design quote avoid hidden fees — web-design heroWeb Design

Web Design Affecting SEO Rankings: How Design Decisions Leak Rankings and Revenue

The Scenario: A Site That Looks Better and Ranks Worse A Johannesburg homeware store ships nationwide. In Q3 the team launches a bold redesign: new hero, filterable catalogue, new blog template. Organic sessions look flat for six weeks, then slide. The site is 'better' visually, but organic revenue began leaking the day the templates went live, because design decisions quietly removed signals Google used to rank and value the site. This is a diagnostic sequence for that situation. It treats design as build decisions that either preserve crawl equity, entity clarity and conversion value - or destroy them. Core Web Vitals tooling and mobile-first indexing are covered elsewhere; the real leaks sit deeper. Why 'Page Experience' Is Not a Ranking System Google states there is no single 'page experience' system and that meeting experience signals does not guarantee rankings. They are tie-breakers within a relevance system. When a redesign drops rankings, suspect relevance and crawlability before aesthetics. Core Web Vitals thresholds (field data, not lab data) LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1, assessed at the 75th percentile of field data. INP replaced FID in March 2024: a redesign adding heavy interactivity can pass in a lab and fail on mid-range Android on 4G - the profile of many South African shoppers, where data cost shapes abandonment. Lighthouse lab scores are a design review tool, not a ranking verdict. Pull field data before concluding a redesign 'failed Core Web Vitals '. Where design ends and content begins Design controls structure: what is in the HTML, how deep it sits, how templates render it. Content controls words and entities. Leaks happen at the seam - hiding text, flattening headings or burying a page changes content signals whether intended or not. Leak 1 - Information Architecture That Hides Value Navigation depth, orphan pages, internal links Redesigns often move pages from a flat menu into nested categories; pages once in the global nav sit four clicks deep or only in a footer accordion. Orphans lose link equity and are crawled less. Fix: a link-depth spec in handover - every revenue page within three clicks, descriptive anchors agreed before build. Tabs, accordions, infinite scroll Accordion content is usually indexable if in the DOM, but may be devalued as secondary and truncated in mobile-first rendering. Infinite scroll lazy-loading products behind JavaScript is riskier. Prefer paginated or progressively enhanced lists with real URLs. Leak 2 - Template Churn and URL Restructuring Redirect chains, canonical drift, the 90-day watchlist Every 301 hop costs latency and dilutes signal; chains of two or three are worse. Canonicals drift when new templates hardcode a canonical pointing at a listing rather than the detail page. Treat the first 90 days as an active watchlist: crawl errors, canonical mismatches, redirect chains and index coverage, reviewed weekly. Change-of-address hygiene If paths genuinely change, implement 301s server-side, update internal links and sitemaps, and use Search Console's change-of-address tool for domain moves. Keep old URLs responding with 301s for at least a year.

Nov 20, 20265 min read
Read more
web-design-south-africa — web-design heroWeb Design

Mobile-Responsive Web Design and SEO in South Africa: Closing the Mobile Revenue Gap

When mobile traffic grows but mobile revenue does not Picture a hypothetical Shopify store in Johannesburg selling homeware. Analytics shows most of its sessions now arrive on phones, yet the desktop sessions still produce the bulk of revenue. Blended customer acquisition cost creeps up, marketing efficiency (MER) looks worse than it should, and the team assumes the ad platforms are the problem. In reality the gap is usually on the site: a mobile version missing copy, oversized hero images, a checkout that fights the on-screen keyboard. This playbook is about closing that gap. It is a mobile-first indexing and mobile-experience audit framed for South African conditions, not a general SEO-and-design guide. It deliberately avoids re-teaching Core Web Vitals scoring or local voice queries, which our other guides cover. Explore how this applies to your store through our Web Development & Design work. Why mobile-first indexing makes your mobile site the 'real' site Google evaluates Google predominantly uses the mobile version of a page for indexing and ranking. Per Google Search Central's mobile-first indexing guidance, content hidden or stripped from the mobile render can be missed entirely, and structured data, metadata and internal links are read from that mobile version. Practically: the phone layout is not a secondary skin. It is the artefact being judged. If a marketing team reviews designs on desktop monitors and signs off on mobile as an afterthought, they are optimising the wrong surface. Fix content parity and page weight before any visual redesign. Those two levers move both rankings and mobile conversion rate. The South African mobile context: why page weight is a commercial decision Many local shoppers are on prepaid mobile data and variable mobile networks, so every uncompressed image and render-blocking script has a real cost to the user and a real abandonment risk for the brand. Page weight is therefore a commercial decision, not an aesthetic one. Underserved-network performance is heavily shaped by the delivery format and the number of kilobytes shipped before the first paint. Mobile audit playbook part 1: content parity Compare the mobile and desktop versions of your five highest-revenue landing pages. Check that H1s, primary copy, product specifications, internal links and structured data all exist on the mobile render. Anything hidden behind display:none on mobile, or loaded only on desktop breakpoints, should be flagged for review. Mobile audit playbook part 2: responsive images and perceived load Serve modern formats (WebP/AVIF) with correct srcset and sizes so phones never download desktop-sized media. The viewport meta tag and a responsive image set are the basics: <meta name='viewport' content='width=device-width, initial-scale=1'> <img src='/hero-800.webp' srcset='/hero-400.webp 400w, /hero-800.webp 800w, /hero-1200.webp 1200w' sizes='(max-width: 640px) 100vw, 800px' width='800' height='450' loading='lazy' alt='Product category hero'> Symptom-to-cause table Symptom Likely mobile cause Fix How to measure Low mobile rankings on key terms Content missing on mobile render Restore copy, links, schema on mobile Ranking comparison by device High mobile bounce Heavy hero images, blocking scripts WebP/AVIF, srcset, defer JS Session duration split by device Cart abandonment on phones Small tap targets, keyboard friction Segmented inputs, autofill, CRO testing Mobile checkout funnel drop-off

Nov 19, 20265 min read
Read more
seo-and-google-ads-integration — seo heroSEO

SaaS SEO and PPC Integration: One Demand-Capture Layer, One Qualified-Trial Signal

A Johannesburg SaaS team selling into South Africa, the UK and UAE had two people running search: a paid specialist chasing trial starts on broad head terms like “project management software”, and a freelancer chasing “what is X” definitions that ranked but never produced a trial. Neither had seen the other’s query data. Six months in, CAC was climbing, trial-to-paid had flattened, and blended MER was a number nobody trusted. The problem was not channel performance; it was that SEO and PPC were operating as two demand-capture layers with no shared signal. Start With Intent Tiers, Not Channel Budgets The first integration step costs nothing: agree on one intent taxonomy before touching a campaign or a content calendar. SaaS demand splits around where the buyer is in their problem-solving process. A workable six-tier structure: Problem-aware (“how to reduce customer churn”) Solution-aware (“customer success software”) Comparison/alternative (“X vs Y”, “best X for agencies”) Integration/compatibility (“X + HubSpot integration”) Pricing (“X pricing”, “X cost per seat”) Brand-defence (“X login”, “X reviews”) Assign each tier a channel role and a primary metric before you look at spend. The table below is the artefact the two teams should be arguing over - not two separate channel plans. Intent tier Channel role Primary asset Primary metric Problem-aware Organic-led Explainer / use-case story Assisted trial starts Solution-aware Both, paid for coverage Category page Qualified trial start Comparison Both, shared URL Comparison / alternatives page Trial-to-paid rate Integration Organic-first, paid for demand capture Integration sub-page Activated trial rate Pricing Paid-led Pricing page Cost per qualified trial Brand-defence Paid-led Homepage / login Incremental signups The taxonomy is not a reporting artefact. It is how you decide which asset gets built, which query gets a bid, and which metric each channel is accountable for. The Comparison and Alternatives Page Both Teams Should Be Funding In SaaS, the highest-leverage shared asset is the comparison or alternatives page. One URL should serve both the organic ranking and the paid landing experience. Google’s Quality Score includes landing page experience, and organic dwell time on that same page feeds the same message-match judgement. Forking the paid version onto a noindexed variant loses the compounding effect: the organic page earns links and authority while the paid page starts from zero every test cycle. Our CRO service routinely finds that consolidating two pages into one shared, instrumented asset reduces test variance and speeds up learning. Do not fork the page for a small paid message tweak. Use dynamic text insertion or a query parameter that keeps the canonical URL intact. The same logic applies to integration pages. A page targeting “X + HubSpot integration” serves an organic long-tail query and a paid exact-match keyword. Build it once, instrument it once, and let both channels send traffic to it. A high-converting integration term with no organic page is a content brief; a ranking integration page with weak trial starts is a paid landing-page test. Feed the Paid Search Terms Report Into the Organic Roadmap

Nov 19, 20265 min read
Read more
Professional google ads specialist management for companies south africa imageGoogle Ads

Ecommerce Google Ads and SEO in South Africa: One Product Catalogue, Two Search Channels

Context: The Cape Town Store Bidding Against Its Own Category Pages Picture a Cape Town Shopify retailer selling outdoor gear. Its Performance Max campaigns outbid its own organic category listings for "hiking backpack sale", while the Merchant Centre feed is missing GTINs on a third of variants, the shipping field reads "free" when courier is R95 flat, and faceted colour-filter URLs are noindex. Paid and organic compete, and neither channel has clean product data. This is the reality behind "ecommerce google ads and SEO South Africa" - not a channel war, but a shared-asset problem. Why South African Ecommerce Search Is Not a Generic SEO-vs-PPC Question In larger markets, feed management and organic product SEO sit in separate teams. In a South African mid-market retailer, one or two people own both. That is an advantage: fix the product data once and both Google Shopping and organic product snippets improve together. The constraint is that local search language, payment expectations and delivery phrasing differ from US-centric template defaults. The Shared Asset: How One SKU Becomes Both a Shopping Target and an Organic Ranking Unit A single SKU carries fields that feed two systems: the Merchant Centre product data specification and the on-page Product schema . Title, GTIN, price, availability, shipping and returns overlap. A feed error - missing GTIN, price mismatch, absent shipping detail - is frequently the same defect that breaks organic merchant listing rich results. The feed and the schema are one fix, not two. Treat your product data source (Shopify or WooCommerce admin) as the single origin. Generate both feed and JSON-LD schema from it before either reaches Google. Merchant Centre Feed Hygiene as an SEO Prerequisite (GTINs, Price, Shipping, Returns) Feed quality is usually treated as a paid-search task. For a South African catalogue it is the cheapest organic win available. The fields that matter most are the ones South Africans check before buying: accurate ZAR price including VAT, realistic courier cost with an estimated delivery window, and a returns policy naming the actual period. A store selling at R899 with "free delivery" but a true R95 courier fee trains Google on a promise the checkout breaks - and the same inconsistency weakens the merchant listing. Category Pages vs Product Pages: Which South African Stores Should Build First Retailers with large catalogues should invest in text-rich, indexable category pages first , reserving product pages for long-tail high-intent capture. Category pages consolidate ranking signal, survive stock churn and give PMax a stable taxonomy to mirror. Product pages should mirror the feed, not outrank the category. Catalogue size Build first Rationale Under ~150 SKUs Product pages Thin category ceiling; each SKU can carry weight 150-2,000 SKUs Category hubs, then product Churn makes per-SKU SEO expensive 2,000+ SKUs Category taxonomy mirrors feed PMax and organic share the structure Faceted Navigation and Out-of-Stock Behaviour: Where Indexation and Paid Spend Diverge

Nov 19, 20265 min read
Read more
Notebook with handwritten Amazon SEO strategy topics highlighted on a keyboard.CRO

SEO and PPC Landing Page Optimization: Converging Two Pages Into One Shared Asset

Context: The SaaS Trial Page That Forked in Two A hypothetical mid-market B2B SaaS brand in Johannesburg runs a free-trial funnel on a ZAR 180,000-per-month paid budget (figures illustrative). Paid built a stripped, noindexed landing page for the trial; content built an indexable page for the same offer answering comparison and pricing-intent queries. The organic page out-earns the paid one on trial starts, yet the paid page absorbs the entire budgeted traffic stream. Neither team can say which is the source of truth. That is the real question behind SEO and PPC landing page optimization : not how to fix conversion (that playbook lives elsewhere), but how two pages built for two channels for one offer converge into a shared asset. What the Term Actually Asks You to Decide SEO wants a page that earns clicks over time across many query variants and survives algorithmic judgement. Paid wants a page that converts a click it already bought against a known cost. The demands look opposed but are not - provided both pages optimise against the same job-to-be-done and fire the same downstream conversion event. Convergence is a policy and measurement decision first, a copy decision second. Teams that start by merging content usually break tracking on both pages. The Two-Page Trap: What the Fork Really Costs The fork is rarely deliberate - usually an accident of ownership, with paid building in an ad-platform builder and content in the CMS. Hidden costs compound: Two copy decks drift apart, weakening message-match on at least one channel. Two tracking implementations mean two conversion definitions - often two different 'trial start' events. Consent gating (POPIA in South Africa, UK GDPR for EU traffic) is often missing on the external paid page because it sits outside the CMS consent framework. Every test, fix and design change is paid for twice. Stripped paid landing pages are the most common place to find analytics and consent holes, because they rarely inherit the platform-wide tag manager and cookie banner. Cost Table: Indexed SEO Page vs Noindexed Paid Landing Page Dimension Indexed SEO page Noindexed paid LP Who owns it Content/CMS team Paid media team, often a builder Success metric Position-relative CTR, assisted conversions CPA / ROAS against media cost Consent & analytics Usually inherited from CMS Frequently missing or duplicated Iteration cost Shared with SEO, slower sign-off Fast to clone, easy to abandon Message-Match Is the Shared Variable Both Channels Optimise Build one copy brief from two query sources: the Google Ads search terms report and Search Console. Where the query sets overlap on intent, the hero headline must satisfy both. Where they diverge - paid skews to offer-seekers, organic to comparison-seekers - carry one primary message and route secondary intent into on-page sections. Technical Hygiene That Only Needs Fixing Once Core Web Vitals, mobile-first rendering and consent gating are properties of the page, not the channel. Fix them once on the shared asset. Test against Google's Core Web Vitals thresholds ; confirm the primary CTA renders without JavaScript blocking on mobile; and verify consent fires before any analytics tag on both entry paths. Converging pages while keeping two tag containers solves the visible problem and keeps the invisible one.

Nov 18, 20265 min read
Read more
local-advertising-strategies — google-ads heroGoogle Ads

Google Ads Data to Improve Organic CTR: Mine Paid Queries, Then Rewrite the Snippet

Context: A Store Whose Title Tags Ignore How Its Customers Actually Search Picture a mid-sized South African Shopify or WooCommerce store selling industrial fasteners and power tools. Its Google Ads search terms report is a live transcript of how buyers talk: "grinder 230mm JHB", "drill bits PTA price", "cheapest angle grinder ZAR", even misspellings like "angle grander". Meanwhile the organic title tags read like a manufacturer catalogue: "Angle Grinder 230mm | Product Range | [Brand]". The store bids against real search language on one side of the business and ignores it on the other. This playbook closes that gap with a repeatable loop: mine paid query data, validate phrasing inside responsive search ads, then rewrite the organic snippet with copy that has already earned clicks somewhere measurable. The Misread This Article Corrects: Paid CTR and Organic CTR Are Not the Same Metric In-house teams commonly treat Google Ads click-through rate as a proxy for organic CTR. They are not comparable. A paid ad competes with two or three other ads, carries a "Sponsored" label, and reaches a user often mid-purchase. An organic result competes with People Also Ask, local packs, shopping carousels and AI Overviews, with no label beyond its URL. Paid CTR tells you which messaging earns a click under paid conditions. Organic CTR tells you which snippet earns a click against other organic results and SERP features. Use the first to inform copy, never as a benchmark for the second. Why the SERP Snippet, Not the Page, Decides Whether You Get the Click Your landing page can convert beautifully and still lose the visit, because the click decision happens before arrival. The title link and meta description are the whole product on that screen. Per Google's documentation on title links , Google may rewrite your title when it believes a different one better matches the query. The snippet is a negotiation, not an instruction - which is why testing copy where you get hard performance data first is worth the effort. Which Google Ads Reports Actually Give You Organic Copy Inputs Search terms report - the real queries that triggered your ads, including modifiers, misspellings and place abbreviations. Responsive search ad asset reporting - which headlines and descriptions performed (see About Responsive Search Ads ). This is your cheap A/B lab. Search impression share - where high paid impression share meets weak organic visibility, you have an intent gap worth a title rewrite and often a new page. Reading the Search Terms Report for Title Language: Modifiers, Misspellings and Local Vernacular Do not just extract nouns. Extract modifier patterns . In the South African market we consistently see place abbreviations (JHB, PTA, CPT), currency framing ("price", "ZAR", "under R500"), servicing intent ("repair", "spares", "same day"), and genuine misspellings that reveal the user's vocabulary level. Each pattern is a snippet input. If a meaningful share of paid queries carries same-day intent, a title that omits urgency leaves clicks on the table.

Nov 18, 20265 min read
Read more
How to Allocate Your Digital Marketing Budget Between SEO and Google Ads in 2026 — seo heroSEO

SEO and Paid Search for Brand Terms in 2026: Deciding What Brand Spend Is Still Worth

The Brand-Term CPA Creep: A Scenario SA Retailers Will Recognise Picture a mid-sized South African e-commerce brand - homeware, R80m turnover - ranked #1 organically for its own name for three years. Brand paid search was cheap insurance. Then brand-term CPCs climb, and Auction Insights shows a marketplace and an affiliate bidding on the brand name. Platform ROAS still looks flattering because the ad clicks convert - but some would have arrived anyway. This is the 2026 brand-search dilemma: not whether to buy your own name, but how much of it you need to rent. The answer is a query-by-query incrementality judgement backed by measurement that separates paid from organic contribution. Why Brand Queries Stopped Being a Cheap Win in 2026 Three forces converged. AI Overviews now answer some branded informational queries directly, compressing clickable space. Broad-match expansion under AI Max means brand campaigns can quietly match non-brand queries unless brand inclusion and exclusion are configured correctly. And competitors and affiliates have learned that conquesting a known brand is cheaper than building demand. None of this makes brand spend useless - each raises the cost of getting the decision wrong. SA brand-term CPCs are generally lower than UK/US equivalents, but trending upward as competitor bidding rises. Treat any figure as a range to measure in your own account. What Actually Changed: AI Max, Brand Controls and Branded AI Overviews AI Max changes the control surface: broad-match expansion reaches queries you never added, so brand inclusion and exclusion settings are strategy, not housekeeping. Incomplete brand exclusions let non-brand campaigns bid on your own name and inflate apparent brand CPA. Branded AI Overviews reduce paid click volume you can defensibly attribute, strengthening the case for incremental revenue over last-click. Audit brand inclusion lists quarterly and treat branded AI Overview impressions as an organic metric, not a paid failure. The Cannibalisation Argument, Stated Honestly Observational studies from Ahrefs, SEMrush and Search Engine Land repeatedly find paid and organic results on the same brand query largely overlap, suggesting much brand spend is cannibalistic. Google's own research argues genuine incremental lift exists. Neither is definitive: observational studies cannot control every confounder, and platform research has an obvious interest. Incrementality is real but site-specific - test it in your account. Build Your Brand Query Taxonomy Before You Bid or Block You cannot decide on the phrase 'your brand' alone. Break the brand universe into query groups by intent modifier. Brand query group Intent modifier Recommended action Exact brand name None Test pause or holdout Brand + product category Category Defend if organic weak Brand + reviews/legit Trust Defend Brand + coupon/discount Price Test, then likely pause Brand + competitor Comparison Pause unless margin justifies Mapping Intent Modifiers: When 'Brand + Reviews' Is a Different Decision

Nov 18, 20265 min read
Read more
google-ads-agency — google-ads heroGoogle Ads

Local Google Ads and SEO in Gauteng: Winning the Map Pack Across Multiple Suburbs and Cities

Context: Four Branches, Two Targeting Systems That Never Agree A home-services group with branches in Sandton, Centurion, Benoni and Krugersdorp finds its Google Ads bidding on suburbs it cannot service, while its Google Business Profile (GBP) ranks for areas it does not target. Ads location settings and GBP service areas run on different assumptions: Ads targets where users are located or show interest, GBP defines where you serve. When they disagree, budget leaks and local visibility suffers. Until you reconcile these systems, every rand spent on local search risks chasing a postcode you cannot profitably serve. A Pretoria dental group with three clinics within 20 km cannibalises its own Ads and map pack rankings because catchments overlap. Location bid modifiers can separate them, but only after you define each branch's true service radius. Why 'Gauteng' Is a Targeting Mistake Before It Is a Strategy Mistake Gauteng is 15 million people across three metros and dozens of suburbs. Treating it as one market blurs budget and floods ads into areas you cannot service quickly. Within Johannesburg alone, Sandton, Soweto, Randburg and Midrand have different competitive dynamics. A single 'Gauteng' campaign cannot distinguish a Benoni homeowner needing plumbing from a Sandton office needing after-hours IT support. Treat these as separate markets: Johannesburg (Sandton, Soweto, Randburg, Midrand), Pretoria (Centurion, Pretoria East), Ekurhuleni (Benoni, Boksburg) and the West Rand (Krugersdorp). Google's location targeting documentation explains the settings; mapping them to your business is yours. Presence or Interest vs Presence Only The default 'presence or interest' setting shows ads to people in, or showing interest in, your targeted locations - a Soweto user searching 'plumber' could see your Sandton ad. For local services, switch to 'presence only' to restrict ads to people physically in your target area. For fixed-location businesses like a dental clinic, presence only is usually correct; for delivery or remote services, presence or interest may capture out-of-area demand. Validate that location targeting matches operational capacity. Serving a lead you cannot reach in reasonable time erodes margin and ruins reviews. Radius vs Polygon: Setting a Realistic Catchment Radius targeting draws a circle around an address, set in kilometres in South Africa. A 15 km radius around a Benoni branch might include parts of Boksburg and Brakpan but exclude Springs. If your average travel time is 30 minutes, 15 km is more realistic than 25 km in peak traffic. Use the radius tool to visualise branch overlaps; for irregular areas, combine radius with postal code targeting. Test radii in a draft campaign and use the 'Locations' report to see where ads actually served. Adjust on cost per qualified lead, not clicks. Location Bid Modifiers and Multi-Branch Cannibalisation

Nov 17, 20265 min read
Read more
google-ads-services — google-ads heroGoogle Ads

SEO and Google Ads Data Synergy: Building One Joinable Dataset Across Search Console, Ads and GA4

Context: The Two Dashboards That Never Join A mid-sized South African e-commerce store has an SEO lead reporting impressions and average position from Search Console, and a paid lead reporting ROAS from Google Ads. Neither report answers the real question: which converting paid search terms are also organic queries where the brand sits two positions from a profitable click? This guide is about data plumbing - building one joinable dataset from SEO and Google Ads sources so decisions come from reconciled numbers. Why SEO and Google Ads Data Disagrees Before You Touch It Three structural reasons the numbers never match exactly: Search Console anonymises low-volume queries and caps export rows, so tail terms vanish. The Ads search-terms report aggregates by match type and omits low-volume terms. GA4 attributes sessions and conversions by its own model, on different clocks and rules. Source Shows Hides Search Console Query, page, impressions, clicks, avg position Low-volume queries; capped rows; no conversion value Ads search-terms Matched terms, cost, clicks, conversions Low-volume terms; aggregated by match type; no organic data GA4 events Session source, landing page, engagement, key events Pre-consent detail; organic keyword (not provided) The Synergy Layer: Designing a Query × Page × Channel Table The deliverable is one table where each row is a query, a landing page, and a channel, with shared columns: query_page_channel query -- normalised, lowercased landing_page -- path only channel -- organic | paid clicks impressions cost_zar -- paid only sessions key_events revenue_zar avg_position -- organic only Choosing Your Join Key: Why Landing Page Beats Keyword String Joining on the keyword string is tempting but brittle - paid match types, close variants and organic phrase variations break string joins. Join on landing page path plus a normalised query instead. Tip: lowercase queries and strip trailing slashes on pages before the join. Document the rule so future analysts reproduce it. Where the Plumbing Breaks: Consent Mode, Server-Side Tagging and Lost Rows Consent Mode changes what arrives in your dataset. Users who decline send modelled or cookieless pings, and if GA4 or Ads is not set up to handle this, rows never appear - your join looks clean but silently under-counts. Server-side tagging through a cloud container improves accuracy and first-party resilience, but only if consent signals pass through consistently. Warning: a clean join on incomplete data is worse than a messy join on complete data. Audit consent state distribution before trusting any synergy metric. POPIA and GDPR: What Happens to the Synergy Layer When Consent Strips Query Data Under POPIA in South Africa and GDPR in the UK/EU, query-level and user-level data must be handled lawfully. Aggregate at the query × page × channel grain rather than the individual user grain, keep retention periods defensible, and document your lawful basis. Do not attempt to re-identify anonymised Search Console queries - treat the row limit as a compliance feature, not a bug.

Nov 17, 20265 min read
Read more
voice search seo web design south africa — seo heroSEO

Keyword Research for SEO and PPC in South Africa: Building One Asset That Feeds Both Channels

Context: The Brand Holding Two Keyword Exports That Disagree Picture a Johannesburg online retailer that has exported three spreadsheets in one week. The first is a Google Keyword Planner export showing that a head term commands 8,000-12,000 monthly searches (a wide band, not an exact number). The second is a Search Console performance export showing a completely different set of long-tail queries bringing in clicks it never planned for. The third is a paid search-terms report that agrees with neither, surfacing competitor-intent phrases and misspellings. All three are 'right' and all three are wrong at the same time, because none share a common definition of keyword, intent, or owner. Every volume number in this article is an estimate or a band. Keyword Planner reports rounded ranges, and third-party tools model rather than measure. Treat all figures as directional inputs, never as budgets. Why a Keyword Research Layer Sits Under Both SEO and PPC Most teams treat keyword research as a first-step deliverable: it happens once, gets filed, and both channels quietly drift into their own lists. The discipline that fixes this is a shared keyword layer - one master asset that both the SEO roadmap and the paid account draw from, with a single definition of what each term means for the business. This is the layer where decisions about revenue, not traffic, actually get made. A query that a paid campaign bids on is a known cost per acquisition. A query ranking organically is a decelerating cost. When the same term appears in both, you need a deliberate owner rather than two teams competing on the same SERP. Prebo Digital's SEO and AI SEO and Google Ads teams both work from one keyword map for exactly this reason - attribution accuracy collapses when two channels each keep a private definition of the same intent. The Master Sheet: Fields That Make One Asset Serve Two Channels The master sheet does not need to be elaborate, but it needs to hold the fields that answer 'who funds this term, and what do we expect back?' Field Values Why it matters Term Normalised exact phrase Dedupe across all exports Intent stage TOF / MOF / BOF Routes channel by default Channel fit SEO / PPC / both Prevents internal competition Volume band Rounded range Sizing, never forecasting Current organic rank Position + landing URL Shows overlap risk Paid CPC / impression share ZAR estimate + % Sizes paid test cost Illustrative value ZAR band Prioritisation (hypothetical) Reading South African Search Language: Abbreviations, Vernacular and Price Modifiers A keyword list imported from a US template will miss most of the South African demand. Local query language is not decoration, it is a ranking and bidding lever. Place abbreviations: Jo'burg, JHB, CPT, Durbs, PTA and Sandton appear alongside the full names, sometimes in one query. Language modifiers: English, Afrikaans and isiZulu/isiXhosa service terms each carry distinct intent. Mobile-heavy 'near me' phrasing that bypasses neighbourhood names entirely. Price modifiers: cheap, affordable, 'cost per month', 'price in ZAR' signal BOF intent even on informational vocabulary. These variants should be separate rows in the master sheet, not folded into one parent term, because they carry different CPCs and different organic difficulty. Free Versus Paid Keyword Data Sources for South African Budgets Source Cost Best use Limitation Keyword Planner Free with Ads account Volume bands, CPC ranges Rounded ranges, not exact Search Console Free Real queries, 16-month window Only your own site's demand Google Trends Free Seasonality, relative interest No absolute volumes Third-party (Semrush, Ahrefs) Paid Competitor gaps, expansion Modelled estimates Reconciling Keyword Planner Volumes, Search Console Queries and the Paid Search-Terms Report The reconciliation is mechanical. Normalise every term to lowercase and strip punctuation, then join all three exports on that normalised key. Where Keyword Planner suggests a term but Search Console shows no impressions, the demand may be new or unmet. Where Search Console shows queries with impressions but no Planner history, you have discovered a real local pattern worth investigating. Where the search-terms report shows a paid query converting at a good cost, that term is a strong candidate for an organic content pillar. normalised_term = term.lower().strip().replace(' ', ' ')join_key = normalised_term # one key, three exportsmaster = planner.merge(search_console, how='outer', on='join_key')master = master.merge(paid_terms, how='outer', on='join_key')master['channel_fit'] = master.apply(route_by_intent, axis=1)

Nov 17, 20267 min read
Read more
core web vitals seo web design south africa — seo heroSEO

Integrated PPC and SEO for Real Estate: Turn Listings, Location Pages and Lead Forms into One Growth Engine

Two estate agencies operate three suburbs apart in Sandton. One runs Google Ads on 'property for sale in Bryanston' while its organic listing pages sit outdated and cannibalised; the other has no paid search but ranks for a handful of agent-name queries. Neither sees the full seller-lead pipeline. This playbook is for the marketing director or agency principal who suspects paid and organic are pulling in different directions and wants one engine instead of two invoices. Reality Check: Why the Property Portals Own the Head Terms (and What to Do About It) Property24 and Private Property dominate broad terms like 'houses for sale Johannesburg'. Bidding against them on generic head terms is expensive and rarely profitable for an individual agency. The better strategy is suburb-level and seller-intent queries where portals are weaker: 'free property valuation Bryanston', 'estate agent Sandhurst', 'sell my house Fourways'. These terms carry higher intent and lower competition, making them ideal for both paid and organic capture. Tip: Map every paid search term to a suburb or seller-intent query. If a term cannot be mapped, it probably belongs to a portal, not your agency. The Seller-Lead Funnel Is the Meeting Point for PPC and SEO Buyer enquiries are transactional and often go to portals; seller enquiries are where agencies build long-term pipeline. A free valuation is the highest-value lead magnet because it starts a relationship before the mandate is signed. Both channels should feed the same lead form and the same CRM stage. When a seller requests a valuation, that is a qualified lead; when they book an appointment, that is a sales-qualified lead. Align PPC and SEO to these two events, not to clicks or sessions. Turn Paid Search Terms into the Organic Roadmap: The PPC-to-SEO Loop Google Ads search terms reports reveal exactly how people phrase property queries, including misspellings and local vernacular ('bryanston property', 'houses for sale in bryanston'). Export these terms monthly and cluster them by suburb and intent. Any term with high impressions and low organic ranking becomes a priority page brief. This turns paid spend into a keyword research engine that SEO can act on. Paid search term Organic action Page type 'free valuation bryanston' Create dedicated valuation landing page Conversion page 'estate agent sandhurst' Optimise agent profile page Agent bio 'houses for sale fourways' Build suburb hub with live listings Suburb hub Listing Churn Is Both an SEO Problem and a Paid-Feed Problem Every sold listing that returns a 404 erodes crawl equity and wastes paid clicks. A listing that 301-redirects to the suburb hub preserves link equity and gives buyers a next step. On the paid side, stale feed items cause disapprovals and wasted spend. Treat listing lifecycle as a shared data pipeline: when a listing is marked sold, trigger the redirect and remove it from the feed within the same hour. Architecture That Survives Churn: Suburb Hubs, Listing Pages and RealEstateListing Schema Build a three-tier structure: a national or regional homepage, suburb hubs that aggregate live listings and local content, and individual listing pages that expire gracefully. Suburb hubs should be evergreen and target 'property for sale in [suburb]' plus seller-intent terms. Listing pages use RealEstateListing structured data so Google can surface price and availability in rich results. See Google's structured data intro for implementation basics.

Nov 16, 20266 min read
Read more

Why Choose Us

500+ Expert Articles

A content hub covering SEO, paid media, CRO and web design for South African businesses.

200+ Success Stories

Campaigns and builds delivered across retail, services, B2B and ecommerce.

200+ Happy Clients

Businesses that trust Prebo Digital with their digital growth.

4.9 Average Rating

Rated 4.9 out of 5 across verified Google reviews.

24h Response Time

Questions answered within one business day, every time.

Google Premier Partner

Premier Partner status since 2022, placing us in the top 3% of agencies.

Amazon Verified Partner

One of the first verified Amazon Ads partners in South Africa.

Meta Business Partner

Certified to run paid social across Facebook, Instagram and beyond.

Get a Quote

Fill out the form below and our team will get back to you within 24 hours

What Our Clients Say

Hear from businesses we have helped succeed

“Great service and professional team.”

ES
Emelda Schuster

“Shout out to Leesha @Prebo Digital for great diligence and care handling our Google Ads account. Other agencies take your money and do nothing until you ask. Not Leesha & Prebo Digital. They do what they say and show up with a friendly face. Work to fix issues. Highly recommended.”

BS
Bradley Schmidt

“Excellent service and support.”

DB
Des Brown

“Very skilled and knowledgeable in the digital industry and you understand the importance of budgets. Start-ups do not have hundreds of thousands to spend at first and you guys really make the most of every budget provided.”

CS
Cat street

“Prebo will take your business to the next level. Extremely smart people, great service. Always go above and beyond.”

MG
Mike Gray

“A dedicated, knowledgeable and enthusiastic team of individuals that are determined to see your brand grow!”

AW
Alastair Waldeck

“A great agency to work with that always provides excellent service. Very professional and dedicated team.”

LV
Lynelle van Niekerk

“In the 4 months since we joined hands with Prebo our leads quantity and quality has increased with much more direct impact on our target market. The team is on point and forever in contact with new ideas and solutions to maximize our potential within the set budget cap. Very innovative group of people!”

RB
Rikus Booyens

“Great service from Prebo Digital team.”

MC
Mothusi Calvin Mogorosi

“Great Agency - growth-minded, a diverse team of talented individuals with collaborative success at its heart”

DD
David Delaney

“Outstanding digital marketing services.”

DD
DUNCAN DUNSHAM

“Industry experts!”

RB
Ricardo Banda

“Excellent work and professional service.”

MM
Menzi Mohale

“Expertise, ethos, excellence”

AJ
Andrew Johnson

“Professional and reliable service.”

ED
Ebert Du Plessis
5.0/ 5
·15 reviews