Traffic has flatlined and nobody can explain it
Content is solid. Organic growth has stalled. Something structural is blocking search engines from reaching your pages.
Digital Strategy and Execution
Technical SEO determines whether your content can rank at all.
I audit your site's technical foundation, trace every blocking issue to its root cause, and hand your team a prioritised fix list they can actually act on.
The situations I see most often
Technical SEO problems are often invisible until rankings stall or drop. These are the patterns I see most often.
A previous audit produced a report nobody acted on
Someone exported 400 issues with no priorities or context. Developers pushed back. The report was filed and forgotten.
A migration or redesign sent rankings backwards
The site looked better. Then organic traffic fell. Migrations break things that only a technical audit will surface.
What you walk away with
Every technical SEO engagement produces three things: visibility into how search engines experience your site, a plan to fix what they cannot reach, and a foundation that supports everything you publish next.
A complete map of what search engines can and cannot reach
Every crawl barrier, indexation gap, and rendering failure documented. You see exactly how Google experiences your site, from Core Web Vitals through to JavaScript execution.
A prioritised fix list your developer can act on
Each issue has a severity rating, a root cause explanation, and a spec detailed enough to implement. Ordered by impact, so your team starts where it matters most.
Rankings that reflect your content
Pages index properly. Crawl budget stops being wasted. The structural layer supports all future content and links.
How it works
The process follows a consistent sequence, but the depth at each stage depends on what the site needs. Some audits finish in two weeks. A few take longer because the architecture demands it.
Crawl setup and baseline
Crawl tooling configured. Baseline from Search Console, analytics, and (where available) server log files. This establishes what Google sees, what it ignores, and where the gaps sit.
Diagnosis
Raw crawl data becomes a finding only after root-cause analysis. I trace each symptom back to the code, configuration, or architectural decision that caused it. Every issue gets an explanation before any fix is recommended.
Fix specification
Every finding is a written spec. What, why, affected pages, and expected outcome. Code snippets and redirect rules included where relevant.
Handover and review
I walk your team through the report. After implementation begins, I review the first round of changes to confirm correct application.
Ready to fix what search engines can't reach?
Start with a technical review. I will tell you what is blocking performance and give your team a clear plan to act on.
What clients say about the work
From clients across strategy, execution, and advisory engagements. Different sectors, different problems.
“Working with him was straightforward and collaborative. He is very detailed, reliable, and quick to translate discussions into clear, actionable steps. He also takes the time to guide and teach the team, which really helped build our internal capability. I can see why people describe him as a “walking Google” — he brings a wide range of knowledge and connects things quickly.”
Melissa Jailani
Digital Experience & Marketing Lead
“…every decision for the web site is always based on our side and Yassir best experience on the do’s and donts. The price you pay is what you get. Before production, during production and after production it is worth every ringgit spend. Hands down, the best experience and he knows what he is doing. My advice, don’t just get a web site, but get the web site. Great job Yassir, appreciate your work. The best.”
Elisa
Real Estate Negotiator
Common questions
Answers to the questions I get asked most often.
What access do you need to start?
Google Search Console access and crawl tool access to your site are the minimum. A staging environment is useful if configuration changes need testing before going live. Server log files are not essential but add significant diagnostic value where they are available.
How long does an audit take?
For most sites, two to four weeks from kickoff to final report. Site size and architectural complexity are the main variables. Very large sites with complex URL structures or significant JavaScript rendering take longer. I will give you a realistic estimate before the engagement starts.
Do you fix the issues or just identify them?
I identify, prioritise, and write specifications. Implementation is carried out by your development team using the specs I provide. For WordPress and common CMS platforms, I can implement directly where it makes sense. This is discussed and agreed before the engagement starts. A review of the first round of changes is included, provided it is scheduled within 60 days of delivery. For larger or more complex builds, I review your developer’s work after they apply the changes.
How is this different from running a crawl tool ourselves?
The deliverable is the interpretation, the prioritisation, and the business-impact ordering. Interpreting what the data means, tracing issues to their root causes, cross-referencing against Search Console and log file evidence, and sequencing fixes by commercial impact is where the work sits. The tool accounts for a small fraction of what an audit produces.
Ready to fix what search engines can't reach?
Start with a technical review. I will tell you what is blocking performance and give your team a clear plan to act on.