TECHNICAL SEO CONSULTING
I help teams find out why search engines are missing, duplicating or misreading their pages. Then I turn the evidence into work that developers can estimate, release and check. That can mean a one-off audit, support through a website migration or technical SEO work alongside an existing team.
WHERE I START
A crawl can produce thousands of warnings. That does not make all of them important. I start with the commercial pages, the search demand they serve and the behaviour that prompted the review.
If organic landing pages disappeared after a release, I compare what changed. If a new store is creating millions of filter URLs, I trace how they are generated and linked. If Google sees an incomplete JavaScript page, I compare the server response, rendered HTML and browser behaviour.
The aim is to separate evidence from tool noise and give the team a sensible order of work.
TECHNICAL AUDIT SCOPE
The final scope follows the website. A small lead-generation site does not need the same investigation as an international marketplace, and a migration audit has different risks from a performance review. These are the main areas I draw from.
JAVASCRIPT SEO
The framework changes where I look, but not what a search engine needs: stable URLs, crawlable links, useful content, accurate metadata, clear status codes and a page that renders reliably.
I work from the production output and the way the application is built. That helps distinguish a framework problem from a configuration, content, routing or deployment problem.
I review App Router or Pages Router output, rendering choices, the Metadata API, dynamic routes, canonicals, redirects, status codes, caching and ISR behaviour.
For React sites and single-page applications, I check whether important routes, links and content exist without depending on a browser interaction or an unreliable render.
I check route discovery, server-rendered output, head management, hydration, middleware redirects and whether production rendering matches the intended page.
The review covers route handling, Angular SSR or prerendering, metadata, link discovery, rendering errors and the amount of client-side work required.
I inspect SSR and prerender settings, route output, load functions, status handling, canonicals and content that is added only after the page reaches the browser.
I check static and server-rendered routes, content collections, islands, canonical output, sitemap coverage, redirects and the effect of third-party scripts.
I can review the SEO requirements before the build, test routes and templates on staging, and check the production release. That includes migrations from a CMS or older platform into Next.js, Nuxt, Astro or another modern stack.
WEBSITE MIGRATIONS
A migration may involve a new domain, CMS, JavaScript framework, design, URL structure, protocol or international setup. The safest time to protect search traffic is before those decisions become expensive to change.
Before URLs or templates change, I capture the pages, redirects, canonicals, search landing pages, internal links and performance data that need protecting.
I check the proposed URL structure, redirect rules, template requirements, analytics setup and launch responsibilities while there is still time to change them.
I crawl and render the staging site, compare it with the agreed specification and log anything that needs fixing before launch.
After launch, I test important URLs, redirects, canonicals, robots controls, sitemaps, analytics and rendering on the production site.
I monitor crawl errors, indexation, landing pages and search demand so the team can act quickly when the release behaves differently from the plan.
A finding is not finished when it reaches a slide deck. I can stay involved while the team decides on an approach, breaks the work into releases and checks it on staging.
I consider the number and value of pages affected, the strength of the evidence, the risk, the effort and anything the fix depends on. A widespread indexation error will normally outrank a minor markup warning.
The deliverable can be a focused investigation, a full audit and roadmap, migration support, or ongoing technical work. We agree which one fits after looking at the site.
I do not publish client examples or performance figures without permission and a source that can support them.
DELIVERABLES
The format depends on the people using it. A developer may need a ticket and a test case. A marketing lead may need a decision, the likely effect and the owner.
COMMON QUESTIONS
The scope depends on the site and the question behind the audit. It can cover crawling, indexation, rendering, internal links, templates, canonicals, redirects, structured data, performance, international signals and analytics. I agree the scope before starting so the audit does not become a long list of checks that have no bearing on the business.
I can turn findings into development tasks, discuss the approach with your developers, review pull requests or staging output where access allows, and check the production release. Direct code changes depend on the stack, access, risk and agreed scope.
Bring SEO in before the new URL structure and templates are fixed. That leaves time to record the current site, influence the build, prepare redirects and set acceptance checks. A review a few days before launch can still find problems, but the safe options are usually narrower.
Yes. I review the search output and behaviour of Next.js, React, Nuxt, Vue, Angular, SvelteKit, Astro and comparable JavaScript stacks. The exact checks depend on whether the site uses server rendering, static generation, incremental regeneration or client-side rendering.
An audit can find barriers and missed opportunities, but the result depends on the issue, the search market and whether the right changes are implemented. I do not guarantee a particular ranking. I define what should change, how we will verify it and which search or business measures are relevant.
I normally need the public website, Google Search Console and analytics. A migration or rendering investigation may also require a staging site, crawl exports, log files, a tag manager, monitoring tools or read access to the relevant code. Access should remain client-controlled and limited to what the work needs.
Send me the website, the market you care about and a short description of what is going wrong. I'll tell you whether I can help and what I would look at first.