Meridian Drainage runs four service pages. Google indexes one of them. That is the first finding on the audit, and it is the reason the site earns 24 impressions a month for “drain cleaning [city]” variants and books almost no organic calls from any of them.
The signal took ten minutes to surface. GSC’s pages report flags three of the four URLs as “Alternate page with proper canonical tag,” meaning Google is treating them as duplicates and consolidating signals to a single page. The impact: three of Meridian’s highest-margin services (hydro jetting, camera inspection, excavation) compete for nothing. This piece walks the full audit that produced that finding, plus four more, then hands over the artifacts we would ship to the account: a keyword map, a page brief, and a 30/60/90 measurement plan.
Why we built a composite instead of anonymizing a real client
Meridian Drainage is a composite. It has to be. Our client roster runs across ecommerce, SaaS, medical, finance, real estate, and local services, but we have not shipped a full drainage engagement, and dressing up an anonymized plumber to look like a drainage case would teach the reader less than saying so out loud.
Here is what is synthetic: the company name, the exact impression numbers, the city, the specific service radius. Here is what is real, drawn from patterns we have seen repeatedly on trade sites: four thin service pages canonicalized together, no city pages, a Google Business Profile categorized as “Plumber” instead of “Drainage Service,” missing service-level schema, and no dedicated emergency page even though emergency intent drives most of the demand.
The audit format is what actually transfers. Everything below (the issue-impact-evidence-recommendation shape, the phased build order, the acceptance criteria we hand to developers) is the same methodology we run on a Shopify migration, a SaaS pillar rebuild, or a multi-location home services brand. The vertical changes. The diagnostic pattern does not.
Five audit findings that actually move a drainage site
Every audit finding in a Meridian-style engagement follows the same shape: issue, impact, evidence, recommendation, acceptance criteria. That last one matters more than most SEOs treat it, because it is the sentence that tells a developer and a project manager what “done” looks like. What follows is the top five findings from Meridian’s audit, each written the way it would appear in the deliverable.
Service pages read like homepage blurbs, and Google canonicalized them together
Issue: four service pages (drain cleaning, hydro jetting, camera inspection, excavation) built from the same template with keyword-swapped H1s and near-identical body copy. Impact: three of the four earn zero impressions for their target queries and cannot enter the SERP for their service term at all. Evidence: GSC pages report shows “Alternate page with proper canonical tag” on three of four URLs; a Screaming Frog crawl confirms the canonical tags on those pages point away from the URL they live on. Recommendation: rewrite each page against the brief template shown later in this article, set canonicals to self-referential, and resubmit via sitemap. Acceptance criteria: pages report status changes to “Submitted and indexed” within three weeks, and impressions begin registering in GSC four to six weeks after that.
Most trade sites do not have a link problem. They have a duplicate template problem. No amount of new content will rank if Google has already decided the URLs are duplicates.
Without city pages, “drain cleaning [city]” has nothing to rank
Issue: no location-level pages. The site treats its service area as a footer sentence. Impact: Meridian earns roughly 340 monthly impressions across “drain cleaning [neighborhood]” and “blocked drains [city]” variants, ranks at average position 42, and captures almost none of the clicks. Evidence: GSC queries report filtered by city and neighborhood modifiers, cross-referenced against the site’s URL inventory (zero matching landing pages). Recommendation: three city pages built by hand for the top service areas, each with unique content about the drainage patterns local to that area, named landmarks, and route photography. Acceptance criteria: each page indexed within three weeks and ranking on page one or two for its exact “drain cleaning [city]” query within 90 days.
Never auto-generate these. Programmatic city pages kill more trade sites than they help; the Helpful Content signals target thin doorway pages specifically.
Emergency intent drives more than 60% of drainage searches and has no landing page
Issue: no dedicated emergency page. “24/7” appears only in the footer. Impact: emergency queries are the highest commercial-intent bucket in drainage, and Meridian competes for none of them. Evidence: impressions for “emergency drain unblocking [city]” appear in GSC at position 38, with an existing but unranked homepage as the responding URL. Recommendation: a dedicated emergency page with response-time proof, a phone-first CTA at the top of the fold, matching 24/7 hours on the Google Business Profile, and Service schema with a `hoursAvailable` field. Acceptance criteria: page indexed, phone number tracked separately from the main line, and appearing in the top five results for “emergency drain [city]” within 90 days.
Twenty-four-seven hours in the footer do not rank. A dedicated page with response-time proof does.
The GBP is live, categorized as “plumber,” and missing service-level detail
Issue: the primary GBP category is “Plumber,” there are no drainage-specific secondaries, and the five listed services carry two-word names with no descriptions. Impact: the profile competes in the plumber pack rather than the drainage pack, and Google cannot map profile services to landing page URLs. Evidence: GBP dashboard export plus a competing-profile audit of the top three drainage businesses in the same postcode (all use “Drainage Service” as primary). Recommendation: change primary category to “Drainage Service” (or “Septic System Service” where the offering warrants), add secondaries including “Plumber” and “Excavating Contractor,” and expand each listed service with a two-sentence description linking to its landing page. Acceptance criteria: profile visible in the “drain cleaning” local pack within four to six weeks.
“Plumber” as primary is where most drainage businesses lose the local pack before they even open the site. The category picker matters more than the description.
LocalBusiness schema is present; the service-level schema that earns rich results is not
Issue: a single LocalBusiness JSON-LD block on the homepage. Impact: no eligibility for service-level rich results, no `areaServed` signal that would help Google place the site in the right geographic pack, and no FAQ rich results on the service pages themselves. Evidence: Schema.org validator plus Google’s Rich Results Test on all four service URLs (structured data detected: LocalBusiness only). Recommendation: Service schema per service page with `serviceType`, `areaServed`, and `provider` fields; FAQ schema on each service page for the top three questions that service actually gets; aggregate review schema where the review inventory is legitimate. Acceptance criteria: each page passes the Rich Results Test and shows structured data detected in URL Inspection within a week of deployment.
LocalBusiness alone is table stakes. Service schema with `areaServed` is what earns the drainage-specific rich result competitors in the same pack do not have.
The keyword map, with the column most SEOs skip
The keyword map for Meridian sits at the intersection of four services (drain cleaning, hydro jetting, camera inspection, excavation and relining) and three intent layers (local, emergency, problem-based), with modifiers layered on top: near me, [city], [neighborhood], “cost,” “24 hour.” Search volumes come from Google Keyword Planner and public keyword tools; the column that changes the roadmap is not volume, it is the impact-and-effort score we attach to each row.
An excerpt from the map, showing the five rows we would build first:
- drain cleaning — 33,100/mo, informational-to-commercial intent, target: /services/drain-cleaning/, impact/effort 3/5 (high volume, low commercial fit)
- drain cleaning near me — 18,100/mo, local commercial intent, target: /services/drain-cleaning/, impact/effort 5/3 (converts, feasible with GBP fix)
- hydro jetting [city] — 480/mo aggregated, commercial intent, target: /services/hydro-jetting/[city]/, impact/effort 5/2 (higher ticket, lower competition)
- emergency drain unblocking [city] — 260/mo, urgent commercial intent, target: /services/emergency/[city]/, impact/effort 5/2 (highest close rate)
- camera inspection [city] — 90/mo, high-ticket commercial intent, target: /services/cctv-drain-survey/[city]/, impact/effort 5/2 (Sequoia GEO’s Aaron Husak notes the tankless-installation analogue produced calls with average tickets four times higher than “plumber near me”)
The reason the map is not sorted by volume: a 480/month “emergency drain unblocking” query converts at multiples of a 33,100/month “drain cleaning” search because one is a homeowner about to buy and the other is a research query. Most keyword-list PDFs the field publishes get this exactly backwards.
Fix indexation before you write a single new page
The build order matters more than the build list. Phase one on Meridian is not “make new stuff.” Phase one is unblocking what already exists so Google can actually see the improvements when they ship.
Phase one covers indexation, canonical resolution, and Core Web Vitals hygiene. Meridian does not meet the Core Web Vitals thresholds; the largest contentful paint sits at 4.1 seconds on mobile. Phase one also consolidates NAP across the site, GBP, Data Axle, Localeze, Foursquare, and Apple Business Connect so aggregators propagate a single record. Phase one takes roughly three weeks with no new page creation, and it is the phase most agencies skip because it does not produce a shippable deliverable a client can point at.
Phase two rewrites the four existing service pages against the brief template in the next section. Self-referential canonicals, Service schema, FAQ schema on each page, internal link blocks pointing between related services. Two weeks of content work, one week of dev QA.
Phase three builds the three city pages by hand. Not five, not a programmatic set of twenty. Three, because if the first three do not move rankings in 60 days, the pattern is wrong and scaling it just multiplies the mistake. Phase four adds supporting content and starts the local-authority link work: supplier links, trade body listings, local press.
Inverting the order (buying a link retainer in month one when the money pages are canonicalized to a duplicate) is spending on authority Google cannot route to anything. The Academy Sports migration we ran taught the same lesson at enterprise scale: comprehensive redirect mapping and site-architecture correction happen before you spend on demand generation, not after.
How we hand a page brief to a developer
The brief is the artifact that separates a page shipping cleanly in a sprint from a page bouncing between three stakeholders for a month. What follows is the top of the brief for Meridian’s emergency drain unblocking page, formatted the way our developers and writers receive it:
Page: /services/emergency-drain-unblocking/[city]/
Primary keyword: emergency drain unblocking [city]
Secondary keywords: 24 hour drain unblocking [city], blocked drain emergency [city], drain unblocking near me
Search intent: urgent commercial. Reader has a blocked drain right now and needs a phone number and a response-time promise above the fold.
H1: Emergency drain unblocking in [city], 24/7
Meta title: Emergency Drain Unblocking [city] | 24/7 Response | Meridian (58 chars)
Meta description: Blocked drain in [city]? Meridian responds within 60 minutes, 24/7. Fixed-fee unblocking from £95. Call now.
Body sections: (1) Response-time proof with tracked phone number and average dispatch time, (2) What we do on arrival (three-step process: assess, unblock, camera-verify), (3) Fixed-fee pricing with the three most common scenarios
Internal link block: hydro jetting service page, CCTV drain survey service page, [city] service area page
Schema types: Service (with `hoursAvailable` = 24/7 and `areaServed` = [city] with postcode range), FAQ (three questions covering response time, pricing, and what to do before arrival)
Acceptance criteria: indexed within three weeks per URL Inspection; passes Rich Results Test for Service and FAQ; tracked phone number distinct from main line; page loads under 2.5 seconds on mobile per PageSpeed Insights field data.
Most agencies deliver a keyword list and a Google Doc that says “write 800 words about emergency drain unblocking.” Dev then guesses at schema. The writer guesses at intent. Nobody agrees on what “done” means. A brief with acceptance criteria closes that gap before the work starts.
The 30/60/90 measurement plan, written before we touch the site
The measurement plan gets written during the audit, not after go-live. The reason is straightforward: the team needs to know what “working” looks like before there is a temptation to declare success on impressions alone. It also gives the client a signal-by-signal document to compare against at each review, which is more useful than a monthly report that averages everything into a single visibility score.
What we watch, and when:
- Day 30: GSC pages report status changes on the four canonicalized URLs (target: “Submitted and indexed”). Core Web Vitals field data updates in PageSpeed Insights for the rewritten pages. GBP profile appears in the “drainage services near [city]” pack for the first time. Expected: process-level movement, not traffic movement.
- Day 60: Impressions climbing on the rewritten service pages in GSC (typically 2× to 4× the pre-launch baseline). Average position on the target keywords moving out of the 40s and into the 20s. First rich results appearing in Rich Results Test verification. Early clicks on the emergency page from tracked phone numbers.
- Day 90: Clicks on money keywords (drain cleaning [city], emergency drain unblocking [city], hydro jetting [city]) at meaningful volume. First jobs attributable to organic via call tracking. Average position on target city queries in the top ten for at least two of the three cities. Review velocity from GBP tracking four to eight new reviews per month per crew.
Every number above is hedged for a reason. State of SEO research suggests SEO campaigns typically take 6 to 12 months to reach positive ROI, with peak results in year two or three. Early call volume, in our experience, tends to arrive four to eight weeks after the phase two rewrites ship, but no earlier. Monthly reports that show impressions climbing while conversions do not are a warning, not a win; measurement exists to trigger a conversation about intent alignment when signals diverge, not to give the account manager a screenshot to email at month-end.
What we would not do, even though every checklist recommends it
No link-building retainer in month one. Meridian’s money pages are canonicalized to a duplicate. Spending £1,500 a month on link acquisition before the pages are indexed is buying authority Google cannot route anywhere. Phase four handles links, and phase four starts in month three.
No blog cadence commitment before the service pages are fixed. A weekly blog compounds slower than a single service-page rewrite that shifts a page from unindexed to ranked. The blog earns its place once the money pages are working, because then the internal linking has somewhere useful to point.
No auto-generated city pages. Three by hand, not thirty programmatically. If the pattern works on the first three, we scale by writing more. If it does not, we save the client from twenty-seven thin doorway pages Google would deindex within a quarter.
No chasing generic near-me volume when the higher-ticket long-tail is open. “Camera inspection [city]” at 90 searches a month closes more revenue than “drain cleaning near me” at 18,100. The prioritization framework we use scores every keyword against commercial value, not raw volume, and the higher-ticket rows earn pages first.
Questions we get when scoping trade-vertical SEO
What is an example of an SEO project?
This article is the example. Meridian Drainage, five audit findings, a keyword map, a page brief, and a 30/60/90 measurement plan is the exact deliverable shape of a real MDRN engagement. Every SEO project runs the same underlying arc regardless of vertical: diagnose what is blocking rankings, prioritize by impact and effort, rewrite the money pages, measure. Request the same walkthrough for your site if you want it scoped against your GSC data.
How does SEO for a drainage or plumbing services company build trust and visibility?
Through three signals working in sequence: a complete GBP with responsive review management, service and location pages that match the exact queries searchers type, and Service and FAQ schema that let Google surface your answers as rich results. Each signal reinforces the others (a schema-rich page ranks; a ranked page earns clicks; clicks feed reviews; reviews validate the GBP). Audit each signal separately and fix the weakest first.
What are the four types of SEO, and where does AI visibility fit?
On-page (content and structure), off-page (links and mentions), technical (crawlability, indexation, speed), and local (GBP and geographic relevance). AI visibility (which leaked documentation and Google’s own statements suggest is emerging as a fifth type) depends on structured content and schema the other four already require, done well. Do not build a separate AI SEO strategy yet; do the four foundational types with structured data treated as a first-class deliverable.
What are the top five SEO strategies for a drainage business?
GBP category depth (primary “Drainage Service,” not “Plumber”), rewritten service pages with Service schema, hand-built city pages for the top three service areas, a dedicated emergency page with response-time proof, and review velocity of four to eight new reviews per month per crew. Local search is a stack of profile, pages, and proof, and skipping any layer collapses the others. Audit each layer against Meridian’s five findings above.
If you want this walkthrough for your business
The audit format, keyword map, page brief, and 30/60/90 plan shown here are what we hand to every engagement, drainage or otherwise. If your service pages are earning impressions but no clicks, or your GBP is live but not ranking in the local pack, the same diagnostic sequence applies. Request a technical audit and a 30/60/90 roadmap for your site and we will run the same findings-and-artifacts walkthrough against your data.
What to read next
This walkthrough runs from audit findings through to the local search fixes that follow them. These pages cover those pieces in their own right.
- SEO audit services is the audit engagement itself, for anyone who wants that review run against their own site rather than a worked example.
- Local SEO covers the local search side of the work in its own right, including Google Business Profile and city page questions.
- SEO for plumbers is the nearest trade page to drainage, worth a look if your work overlaps with plumbing.
- SEO for contractors takes the wider trade view, for drainage firms whose services run past drains alone.
- SEO pricing is usually the next question once you have seen how an engagement runs.
