Technical SEO · Semantic SEO · Web performance
PI Startup Website Technical SEO Health Score Improvement
A 100+ page B2B company-formation estate moved from 62% to 97% Ahrefs technical health while the site was redesigned and migrated from Divi to Bricks.
Results at a glance
- Ahrefs technical health
- 62% → 97%
- Prioritised issues
- 42 fixed
- Toxic domains
- 250 disavowed
- PageSpeed
- 100 / 99
Site Audit score
Documented and closed
Link-risk reduction
Desktop / mobile
The problem
PI Startup Advisory ran a 100+ page WordPress estate on Divi, spread across several market-focused sites. The site was publishing consistently and attracting links, but the technical foundation was working against it.
Ahrefs Site Audit showed 62% technical health. The audit surfaced crawl and indexation problems, redirect chains, inconsistent canonicals, orphan pages, weak internal linking, and structured data that had been added page by page rather than designed as a system. The backlink profile also carried a large amount of toxic activity, which created unnecessary risk.
None of these issues looked dramatic on their own. Together they meant that new content entered the index slowly, search engines had to work harder to understand the site, and the team could not tell which fixes would actually move performance.
Why we decided to solve it
The company was investing in content, links and paid media. Technical debt was capping the return on all three.
The immediate trigger was a planned Divi to Bricks migration. Rebuilding the site without fixing the technical layer would have moved the same problems into a new design. We decided to treat the migration as an opportunity to clean the foundation first, then rebuild on top of it.
There was also a reporting problem. Search Console, Bing Webmaster Tools and Ahrefs each told a different part of the story. Without one prioritised list, the team risked fixing visible symptoms while the structural causes stayed in place.
The goal was not a perfect audit score. It was a site that could be crawled, understood, measured and extended across six markets without the same issues returning.
How we did it
Start with an audit the team could act on
I ran full-site crawls and cross-checked them against Search Console, Bing Webmaster Tools and Ahrefs. The output was a single list of 42 prioritised issues, grouped by cause and ordered by expected impact rather than by how easy they were to find.
Fix crawl, index and structure
We cleaned up sitemaps, robots.txt, redirects and canonical signals. Internal linking was rebuilt around service and market priorities, orphan pages were connected or removed, and indexation was reviewed page by page where the signals disagreed.
Design the schema layer
Instead of adding JSON-LD page by page, we created a reusable structured data system for organisation, local business, service, article, FAQ, how-to, breadcrumb and person schema. That made the markup consistent and gave the content team a pattern to follow.
Reduce link risk
I analysed the backlink profile, separated genuinely useful links from toxic patterns, and produced disavow files covering 250 toxic domains. The reasoning was documented so future link reviews would not have to start from zero.
Measure the work
GA4, Google Tag Manager and Looker Studio were configured to report organic sessions, channels and conversion events in one place. That replaced ad-hoc screenshots with a repeatable view of what changed after each release.
The result
Ahrefs technical health moved from 62% to 97%. The broader technical score rose from roughly 78 to 97 after remediation. The 42 prioritised issues were closed, indexation improved across Google and Bing, and the internal linking model gave the market sites a clearer structure.
The performance work that ran alongside the SEO programme brought the production build to PageSpeed 100 desktop / 99 mobile, with GTmetrix at 100% and 491ms and Pingdom at 99 and 900ms.
The link-risk work reduced exposure from 250 toxic domains, while separate acquisition campaigns added +830 referring domains on CompanyFormationinBahrain.com and +917 on CompanyRegistrationOman.com. Both domains reached Health Score 100.
The technical cleanup also made the Divi to Bricks migration safer. The new design system inherited a crawlable, measurable foundation instead of a list of unresolved issues. Reporting moved from screenshots to a shared GA4 and Looker Studio dashboard, so the next round of work could be judged against a baseline.
Evidence
What the work looked like.
Captures from the engagement. Images marked as redacted have sensitive business data blurred before publication.
Contact
Want to talk through a project like this?
I am open to remote SEO, web design and performance roles. If you need more detail on a specific project, ask — I will share what the client allows.
- [email protected]
- Phone
- +92 322 6189669
- Location
- Multan, Pakistan · Remote
- Status
- Open to remote roles