Skip to main content
    Proof
    Aussie Plumbing — ad spend scaled 1.8× with enquiries up 2.1×, so each enquiry cost lessI-ELEC — a 231-page electrician website for Inner SydneyWhat a plumbing lead costs on Google AdsWhat a lead costs on Google Ads, industry by industrySLS Solicitors — cost per recorded Google Ads conversion down 58.48%Wilco Plumbing — search campaigns and service pagesWilco Plumbing — service menus and guided enquiriesHow much should a trade business spend on marketing?State Choice Plumbing — a drains, hot water and gas websiteAussie Drains — a 600-page drain website for SydneyWhat an electrician lead costs on Google AdsAussie Electrical — a 650-page electrical website for SydneyThe most efficient ways for a trade business to get leadsEOL Melbourne — click-to-enquiry rate up from 28% to 33.4%What a cleaning lead costs on Google AdsAlliance Plumbing — ad spend scaled 1.8× with enquiries up 2.1×, so each enquiry cost lessImpress Blinds — cost per recorded Google Ads conversion down 62.63%FixCare Property - cost per enquiry down 28%Rubbish Removal WA — cost per enquiry down 53.18%Floral Cakery — cost per enquiry down 49.82%ILLUMINATE Laser Emporium — cost per enquiry down 48.54%Sydney Fence Painting — cost per enquiry down 33.68%Alliance Plumbing — cost per enquiry down 29.6%Gridless Build Solutions — cost per enquiry down 29.16%FacilityWorx — cost per enquiry down 23.62%Cornerstone Roofing — cost per enquiry down 20.47%Council finance — budgeting and workforce designCouncil planning — clearer approvals and reportingCultural audiences — media strategy and creative conceptsCommunity participation — surveys, maps and project pagesPublic-sector research — survey design and analysisPublic art — site studies and visual conceptsRegional identity — visitor guides and wayfinding conceptsCouncil systems — integration and migration planningA pressure washing business — service-led search campaignsA pressure washing business — a clear enquiry journeyA carpet cleaner — Google Ads built around cleaning servicesA roofing company — campaigns for repairs and restorationA CCTV installer — campaigns for security enquiriesA fence painter — search campaigns for specific surfacesA maintenance business — live in 8 weeks, 3 stacks gone5.0 across every Google review$120M+ in media under management250+ active engagements across five countries
    SoudCoh

    Technical SEO audit Four checks decide whether content counts.

    Content and links are wasted spend if a crawler cannot reach the page, the index will not keep it, the renderer never sees the words, or it is too slow to serve. Crawl, index, render, speed — in that order.

    Get a technical auditSee real client wins

    250+ live client engagements · Melbourne-based, working across Australia, the UK, the UAE, Saudi Arabia and New Zealand · First call inside one business day

    Client case studies

    Website structure you can explore.

    Explore client websites with clear service pages, local content and useful internal links. Each case study explains the website work we delivered and shows the actual pages.

    Showing 69 of 69 client projects

    Swipe through the projects or use the arrows.

    A closer look

    The work, in three steps.

    WELND

    WELND

    Website project

    Start with the business and its customers.

    WELND is a finance and mortgage brokerage based in Port Melbourne, specialising in tax, trading and unsecured debt for clients across Australia.

    • Australia
    • Website design and build
    • Lending and location page structure
    Explore the full project
    WELND home page with the debt test button beside a photo
    Home page

    Google reviews

    Hear from our clients.

    Read SoudCoh’s reviews on Google (opens in a new tab)
    Inside the crawl

    Seven ways a live
    page stops counting.

    None of these are exotic, and not one of them looks like a problem in a browser.

    • Pages nothing links to, and pages six clicks deep

      No internal link points at it. Its cousin sits six clicks from the homepage — technically live, practically invisible.

    • A robots.txt rule nobody remembers writing

      One line left over from a redesign, or a block added to stop a crawler hammering search. Everything under it stops being read.

    • Filters multiplying into thousands of near-identical addresses

      Colour, size, sort order, page number, plus redirect chains three hops long. The crawl gets spent on machinery.

    • The internal links are buttons

      A link built as a click handler gives a crawler nothing to follow. Only a browser will ever perform it.

    • A noindex tag that came across from staging

      The most expensive line a deploy can carry. Alongside it, canonicals aimed at the wrong host, or at themselves.

    • The HTML response is almost empty

      The application paints the content afterwards. Words that are not in the response are words not counted.

    • The slowest thing on the site is your own marketing tags

      Third-party scripts outweigh everything the business wrote, and images without dimensions move the layout under a reaching thumb.

    The checks, actual size

    Reached, kept, read, served.

    Technical work is a short list of yes-or-no questions, and most sites fail one without ever seeing a symptom.

    • 4

      checks before content counts

      Crawl, index, render, speed. Failing the first makes the other three irrelevant, so the audit runs in order.

    • 3

      Core Web Vitals metrics

      Google publishes three: when the largest thing appears, how fast the first tap is answered, how far the layout moves.

    • 200

      the status code that proves nothing

      A page can answer 200, look correct in your browser, and still be excluded from the index.

    • 1

      canonical per page

      One signal about which address is the real one. Two of them hands the decision back to the search engine.

    • 2

      renderings of every page

      The HTML response and the painted page. A crawler is given the first; your business has only seen the second.

    • 0

      broken URLs a sitemap should list

      A sitemap lists addresses you want indexed. Entries that redirect, 404 or carry noindex are the ones we count.

    Everything else you buy is downstream of these four.

    A page a crawler cannot follow a link to, that the index has quietly dropped, or that serves an empty document is not competing badly. It is not competing.

    Which is also why this work has a ceiling. Removing obstacles gets the content a fair hearing; it does not make the content more persuasive.

    The record

    Australia · UK · KSA · UAE · NZ

    250+

    Active client engagements

    Search, paid media, web and tracking under one roof

    Google reviews

    5.0

    Rating across every review

    We ask our own customers the same way before we sell it to you

    SoudCoh platform records

    1,093

    Changes pushed through approval

    Each one queued, approved, then pushed, and written to the account's change history

    Firm-level figures from the SoudCoh record, not audit forecasts. No crawl, index or speed figure is claimed here — your own site on day one is the baseline. The approval count comes from SoudCoh platform records.

    Ten things happen in a technical SEO audit. Here they are, in order.

    This is the part most agency pages keep vague, and the only part that decides whether the money works.

    1. Crawl the site the way a search engine would

      Every reachable URL with its response code, redirect path, canonical, depth and inbound links. Not a sample.

    2. Compare the crawl against what is actually indexed

      The pages you have and the pages a search engine kept are rarely the same set. The gap is the finding.

    3. Read the server logs

      The only record of what a crawler genuinely requested — usually parameters, old redirects and pagination.

    4. Check what is in the response, not what is on the screen

      Raw HTML against the painted page. Anything appearing only after JavaScript, a tab or a scroll is listed as at risk.

    5. Find the duplication and the bloat

      Near-identical pages competing, parameter URLs nobody meant to publish, thin pages dropped, exclusions nobody has read.

    6. Fix the canonicals and the sitemap

      One canonical per page, pointing where you intend. A sitemap of live indexable URLs, generated rather than hand-kept.

    7. Rebuild the internal linking

      Orphans given inbound links, depth pulled in, and navigation built as anchors a crawler can actually follow.

    8. Measure speed and layout stability on a real device

      Field data where it exists, plus a mid-range phone on a mobile connection. Every result gets a named cause.

    9. Validate the structured data

      Checked for validity and, more often the real problem, for whether it is in the response at all.

    10. Hand over a prioritised fix list, and say who ships it

      Ordered by what each defect costs, not by a severity colour. An audit nobody implements is worth nothing.

    The sequence

    Crawl first. Opinions later.

    1. Week 0

      The brief and the access

      A short call on which pages actually earn, then read-only access to Search Console, analytics and the logs.

    2. Week 1

      The crawl and the render check

      The crawl runs, the index comparison is built, and every template is read raw against painted.

    3. Weeks 2–3

      The audit lands

      A prioritised fix list written for a developer: what to change, where, and what it should unblock.

    4. Weeks 3–6

      The first wave of fixes

      Blocking defects first — anything stopping a page being reached, kept or rendered. Usually small changes.

    5. Weeks 6–12

      Re-crawl and verify

      We crawl again and confirm each fix landed in production rather than in a ticket marked done.

    6. From there

      Rhythm

      A crawl on a fixed cadence, because sites regress on every deploy. Reporting names what regressed.

    You keep the audit whether or not you hire us to implement it, and we ask for read-only access wherever it will do.

    SoudCoh Compound

    The two numbers technical work moves most.

    A slow or broken page wastes every click that reaches it, paid or organic. Technical work fixes the page a click lands on, and every fault we find goes onto the checklist for the next site we look after.

    See SoudCoh Compound

    What we publish.

    These are lead-generation accounts and every tile says so. No technical case study here is dressed up as yours — this work is reported against your own baseline, measured on day one.

    The usual questions

    Twelve answers before the first call.

    FAQ

    Technical SEO, answered.

    Scope, timing, who implements the fixes, JavaScript, Core Web Vitals, access and cost.

    The first call is free and there is no deck.

    Ask us about your rankings

    A full crawl, a comparison against what is genuinely indexed, the server logs, a raw-versus-painted check on every template, canonicals, sitemaps, link depth, speed and structured data. It ends in a prioritised fix list, not a crawler export.

    The crawl and the render checks run in the first week; the written audit lands in the second or third. Large sites and hard-to-obtain logs take longer, and we say so at scoping.

    Sites regress on every deploy. A full audit once or twice a year, with a lighter crawl in between to catch regressions while they are still cheap to fix.

    Either. Our team can ship the changes or your developers can, with us reviewing what landed. What we will not do is hand over a document and call it finished.

    Often more than an old one. New builds arrive with a staging noindex still attached, an almost-empty HTML response, and links built as click handlers.

    Not automatically, and the honest answer needs looking. If the headings, copy, links and schema are in the initial response, the framework is fine. If it is a container div, server-side rendering is the fix.

    Measurably, but modestly. Speed rarely outranks relevance — a slow page that answers the question beats a fast one that does not. The larger effect is on conversion.

    Good, and it happens. Every finding carries its evidence: the crawl row, the log entry, the raw response. Sometimes they are right and the recommendation changes.

    Search Console, read-only — without it we are guessing at what is indexed and why. Logs are optional, but they are the only honest record of what a crawler requested.

    We say so, and name which check was never the problem. Technical work removes obstacles; it does not create demand. The constraint may sit in the content or the market.

    It scales with size and complexity. A brochure site and a store with tens of thousands of filtered URLs are not the same job, so it is quoted after scoping.

    No long-term lock-in. An audit is a defined piece of work and the findings are yours either way. For ongoing work we ask for enough runway to be fair to it.

    Technical work sits underneath everything else.

    Which is why it rarely arrives on its own. SEO services compares the options side by side.

    Get the audit

    We crawl the site, read the response your pages actually serve, and hand you the list of what is stopping them counting. Yours to action either way.

    Get my auditSee real client wins

    No pitch deck. No upsell. A written list of what is broken.