Technical SEO Consulting
Technical SEO Audits
An engineering-led technical SEO audit that diagnoses why your site is not ranking — and gives you a prioritised, developer-ready roadmap to fix it. No templated checklists. No junior analysts. Just senior diagnosis of the issues that actually move rankings.
What's Included
Comprehensive solutions tailored to your specific needs
Indexation forensics
Page-by-page reconciliation between submitted, crawled, indexed, and ranking — using GSC, log files, and live crawls to find the leaks.
Rendering & JavaScript SEO
How Googlebot's renderer sees your stack, where hydration breaks meta and content, and whether SSR, ISR, or prerendering is justified.
Architecture & internal linking
Depth analysis, PageRank flow modelling, orphan detection, topical cluster mapping, and a concrete restructuring plan.
Core Web Vitals diagnosis
Field (CrUX) and lab analysis of LCP, INP, and CLS with engineering-level root causes, not just plugin suggestions.
Schema & rich result validation
Structured data audited against Google's live rich-result requirements, not the generic schema.org spec.
International & hreflang audit
Reciprocity, x-default usage, language-country targeting, and IP-redirect issues across every locale.
Problems I Solve
Symptoms this engagement is built to fix
Pages that Google has indexed but refuses to rank, despite seemingly strong content.
A sudden traffic drop after a redesign, migration, or Google core update with no obvious cause.
Tens of thousands of crawled-not-indexed URLs draining your crawl budget on the wrong pages.
JavaScript-rendered pages that look perfect to humans but appear empty to Googlebot.
Duplicate, near-duplicate, or canonical chaos across e-commerce facets and parameter URLs.
Core Web Vitals stuck at Needs Improvement no matter how many plugins your team tries.
Why most SEO audits miss the issues that actually matter
Most technical SEO audits are 80-page PDFs generated by a tool, lightly annotated by a junior, and quietly ignored by your engineering team. They list every H1 length warning and every external link without nofollow, then bury the three findings that actually explain why your traffic is flat. I take the opposite approach. I start from your real ranking gaps in Search Console, your real crawl pattern in server logs, and your real rendered HTML — then work backwards to the root causes. The deliverable is a short, ranked list of issues that, if shipped, will measurably move your rankings within one to three months, plus a long appendix for the secondary work that can wait.
What the audit actually covers (and why)
Crawlability and indexation: robots.txt directives, crawl traps, faceted navigation, parameter handling, internal redirect chains, soft 404s, and the gap between submitted, crawled, and indexed URLs in GSC. Rendering: how Googlebot's evergreen Chromium actually sees your JavaScript, where hydration timing breaks meta tags, and whether dynamic rendering, SSR, or prerendering is the right fix for your stack. Site architecture: depth from the homepage, internal link equity distribution, orphan detection, and topical clustering. On-page signals: title tags, descriptions, canonicals, hreflang, structured data validation against Google's actual rich-result requirements. Performance: Core Web Vitals from CrUX field data, not just lab tests, with engineering-level diagnosis of LCP, INP, and CLS. International SEO: hreflang reciprocity, language-country targeting, and IP-based redirect anti-patterns. Security and trust: HTTPS implementation, mixed content, security headers, and HSTS preload eligibility.
How rendering, indexation, and ranking actually connect
Modern SEO failures are almost always rendering failures or indexation failures dressed up as content problems. Googlebot crawls your HTML, queues your page for the renderer, executes your JavaScript with constraints your team has never tested against, then decides whether your content is worth indexing and whether your indexed page is worth ranking. Each of those stages has its own failure modes. A React app that sets meta tags after hydration will lose all of them in the snapshot Google indexes. A WordPress site with aggressive caching can serve different HTML to bots and humans, triggering soft 404s on real product pages. A Shopify theme that nofollows its own collection pagination will hide half your catalogue. My audit traces signals through every stage instead of testing them in isolation, which is why the recommendations are short and the impact is large.
How the audit is delivered to your team
You receive three artefacts. First, an executive summary written for non-technical stakeholders that explains, in plain language, what is wrong, what it is costing in lost organic traffic, and what the prioritised fix sequence looks like. Second, a developer-ready issue log: each finding has a specific URL or pattern, the observed behaviour, the expected behaviour, the reproduction steps, the proposed fix at code or configuration level, and the predicted impact on rankings. This is the document your engineers will actually use. Third, a one-hour walkthrough call where I explain the findings, answer questions from your dev team, and help sequence the work into sprints. Implementation support is available afterwards on retainer if you want me to ship the fixes directly with your team.
Where this engagement fits in your wider SEO strategy
A technical audit is the foundation, not the strategy. Fixing the technical floor lets every other investment — content, links, PR, paid — actually compound. Without it, you are pouring water into a leaking bucket. After the audit, most clients move into one of three retainer shapes: ongoing monthly technical SEO oversight as the site evolves, a focused Core Web Vitals or site migration project, or a quarterly re-audit cadence with a smaller scope. I will recommend the shape that actually fits your stage and budget, not the largest one. If you are an in-house team that simply needs a senior second opinion, I am also happy to do exactly that and step back.
What You Receive
Deliverables & expected outcomes
- Executive summary written for non-technical stakeholders
- Developer-ready issue log with reproduction steps and proposed fixes
- Prioritised 90-day implementation roadmap by ranking impact
- Annotated GSC, log file, and crawl data appendix
- One-hour walkthrough call with your engineering team
- 30 days of follow-up Q&A by email and WhatsApp
Illustrative Engagement
A representative scenario
The problem
A European SaaS platform was stuck on page two for its highest-intent commercial keywords despite a strong content programme. Organic traffic had plateaued for nine months and a previous agency audit had recommended more blog posts.
The approach
Log file analysis revealed Googlebot was spending 62 percent of its crawl budget on parameterised filter URLs and zero percent on the cornerstone solution pages. The renderer was also dropping product schema due to a hydration race condition introduced in the last Next.js upgrade.
The outcome
After parameter handling, canonical consolidation, and an SSR-rendered schema layer shipped, the cornerstone pages moved from positions 12–18 into the top five within ten weeks, and indexed URLs dropped by 38 percent while clicks rose by 71 percent.
Composite scenario based on typical engagements. Replace with a real, attributed case study once published.
My Process
A proven methodology for delivering exceptional results
Discovery & access
We align on commercial goals, target keywords, and the URLs that actually drive revenue. You provision GSC, Analytics, log file, and (where useful) staging access.
Multi-source diagnosis
I crawl the live site, parse server logs, reconcile GSC coverage and performance data, validate structured data, and pull field Core Web Vitals — looking for signal contradictions, not surface issues.
Prioritised deliverable
You receive the three artefacts: executive summary, developer issue log, and 90-day roadmap. Every recommendation has an expected impact rating and an effort estimate.
Walkthrough & handover
A working session with your engineering team to sequence the fixes into sprints, followed by 30 days of follow-up support while the work ships.
Why Choose Me?
With 7+ years of experience and a track record of delivering results, I bring expertise, reliability, and a results-driven approach to every project.
- Senior diagnosis instead of a templated tool export
- Recommendations sequenced by ranking impact, not finding count
- Developer-ready issue log your engineers will actually use
- Field data, log files, and rendering analysis — not lab guesses
- Plain-English executive summary for non-technical stakeholders
- Optional implementation support so fixes actually ship
Starting at
€497
Senior-led 200+ point engineering audit with prioritised roadmap, developer-ready issue log, and walkthrough call. Implementation support available on retainer.
Frequently Asked Questions
Related Services
Further Reading
Related articles from the blog
Ready to Get Started?
Let's discuss your project and create a custom strategy for success.