First-party implementation case study · 15 July 2026
How Mitrend Digital rebuilt its WordPress SEO foundation
A transparent account of the work completed on mitrenddigital.co.za using Kadence, WordPress core blocks, Twentig, Max Mega Menu and Rank Math—with no custom CSS and no replacement block suite.
The starting problem
The site looked substantial but its search footprint contained too much low-value surface area. A live audit found 265 published pages, including 115 thin location and industry-solution pages, 20 corrupted legacy blog pages, a 14-word off-scope accounting stub and two pages intentionally excluded from search.
Across the live output, a corrupted replacement phrase appeared 123 times, 145 routes rendered duplicate H1 headings, 69 resource articles lacked a visible reviewer and date, and several commercial pages referenced missing PNG assets close to two megabytes each.
The decision: improve the index, not just the page count
The thin pages were not bulk-filled with generic copy. They were grouped by intent and consolidated into the strongest relevant industry, service or resource destination. That preserved a useful journey for visitors while removing doorway-like pages from the sitemap.
- 85 thin industry-solution URLs redirected to the relevant retail, wholesale, manufacturing, service or partner hub
- 30 unsupported city pages redirected to the relevant national service page
- 20 corrupted legacy blog routes redirected to current resources or service pages
- The off-scope accounting stub redirected to the ecommerce and accounting handover service
Content, trust and conversion repairs
Seven high-priority pages were rewritten with a defined problem, delivery scope, acceptance checks and direct next action. The FAQ and glossary were rebuilt to remove misleading ERP language. All remaining live pages were cleaned of the corrupted phrase and low-contrast teal value.
- 69 resource articles now show the Mitrend Digital editorial reviewer and truthful updated date
- All 265 page templates were set to hide the duplicate Kadence title when the content already provides an H1
- The enquiry form now records a GA4
generate_leadevent after a successful submission redirect - Phone, email and WhatsApp contact clicks now send a separate contact-action event when GA4 is available
Verified phase-one result
| Check | Before | Verified after |
|---|---|---|
| Published WordPress pages | 265 live 200 routes | 131 live 200 routes and 136 relevant 301 consolidations |
| XML sitemap | 263 URLs across two page sitemap files | 129 indexable URLs in one valid sitemap |
| Duplicate or missing H1 on remaining live pages | 145 duplicate-H1 routes found | 0 failures across 131 live pages |
| Corrupted replacement phrase | 123 occurrences across 60 pages | 0 occurrences on remaining live pages |
| Resource reviewer/date | 69 articles missing both | 69 of 69 show both |
| Checked internal images | Missing and oversized hero assets | 0 broken among 17 unique live image URLs checked |
Every one of the 136 redirect sources was checked independently. All returned a permanent redirect to the intended destination, and none remained in the sitemap.
Performance result on the tested SEO service page
Five PNG assets of roughly 1.86–2.02 MB were resized and converted to WebP files of roughly 57–86 KB. A separate missing manufacturing image was restored as WebP.
| Mobile Lighthouse metric | Before | After |
|---|---|---|
| Performance score | 72 | 89 |
| Accessibility score | 96 | 100 |
| Largest Contentful Paint | 10.75 seconds | 3.44 seconds |
| Total transferred weight | 2.18 MB | 0.38 MB |
| SEO and best practices | 100 / 100 | 100 / 100 |
Method note: these are individual Lighthouse mobile lab runs on 15 July 2026. Lab scores vary and are not a substitute for Chrome UX Report field data.
What this case study does not claim
This work improves crawl efficiency, page relevance, trust signals, accessibility, performance and lead measurement. It does not prove higher rankings, organic traffic or enquiries yet. Those outcomes require a clean Search Console and GA4 observation period, query-level evidence and continued authority building.
Need the same evidence-first repair?
We can audit the current site, remove index bloat, strengthen the money pages, repair performance and leave behind a verified route and measurement baseline.
CASE STUDY · SEO REBUILD
The decision in one sentence
The Mitrend SEO rebuild focused on restoring a usable WordPress foundation, repairing routes and internal links, and replacing duplicated resource structure with a quality-gated publishing model. The transferable lesson is that technical cleanup and content proof must be managed together.
Choose this route when
- A migration or rebuild left route, canonical or block-storage uncertainty.
- A site has many pages but weak differentiation and unclear commercial paths.
- Internal links, anchors, redirects or sitemap exclusions need evidence.
- The next content batch needs a safe review and publishing gate.
What the system needs to make true
| Decision area | What Mitrend checks |
|---|---|
| Starting constraint | Route drift, duplicated resource structure and uncertain content quality. |
| Work completed | Native blocks, preserved URLs, fields, patterns, redirects and whole-site validation. |
| Transferable lesson | Repair the crawl path, clarify page purpose and publish reviewed evidence in sequence. |
How the work moves from diagnosis to handover
- Baseline routes, blocks, content overlap, metadata and internal links.
- Restore or rebuild the page structure while preserving valid public URLs.
- Move resources to a quality-gated native post model with fields and patterns.
- Re-crawl links, anchors, redirects, sitemaps, schema and responsive layouts before expanding.
What to verify before you invest
- Are old URLs either valid or intentionally redirected?
- Are held pages excluded from indexing without blocking access?
- Does each released page answer a distinct task?
- Can the team verify the result from a repeatable report?
Evidence to bring into the review
The case is supported by live route, hyperlink, anchor, sitemap and visual checks. It does not claim rankings or traffic outcomes that have not been measured.
Questions buyers usually ask
Does technical cleanliness guarantee rankings? No. Authority, proof, relevance and demand still matter.
Why hold legacy resources? To stop weak or duplicated pages competing while they are rewritten.
What is the next practical step? Release the next reviewed batch and monitor qualified organic visits and leads by cluster.
Choose the next practical step
Bring the current website, store or workflow and one real example. The review should leave you with a bounded next action, not a generic channel list.
Reviewed by the Mitrend Digital editorial team. Updated 18 July 2026.