Crawling and indexation
Review discovery, indexing controls, sitemaps and important URL patterns to understand whether useful pages can enter search.
Technical SEO.
A stronger foundation for what comes next.
A useful page can only help if people and search engines can reach it. I identify the technical barriers, translate priorities into development work and check what changes in practice.
Discuss your website or migrationThe thinking behind the work
From diagnosis to implementation.
The value of an audit is in the changes it enables. A long list of issues is not the same as a workable plan.
Technical SEO should connect a finding to its effect on the website. I look at which pages matter, what is preventing discovery and which fixes deserve attention before the team spends time on low-impact details.
I work closely with developers on audits, repairs, rebuilds and migrations. Recommendations need enough context to implement correctly, with a practical way to validate the result. That collaboration is part of the work, not a document handed over at the end.
For a migration, the search plan starts before launch. Existing URLs, content, templates and language versions need deliberate decisions, followed by checks after release and guidance the team can maintain.
A useful starting point when
01Search visibility fell after a redesign or platform change.
02Important pages are difficult to crawl, index or use.
03You are planning a new platform, domain structure or multilingual migration.
From diagnosis to delivery
A finding becomes useful when it changes the website.
Technical reviews need context: which pages matter, what users need and how the site is maintained. A clear implementation brief connects the problem, the proposed change and the check that confirms it worked.
The practical distinction
Prioritise the barrier, define the fix, then verify the actual page.
One use case: a website migration.
A migration shows how technical SEO connects planning, implementation and validation. Select a stage to explore this example; audits and ongoing technical improvements are also available as focused projects.
The purpose
Know what needs to survive.
Inventory useful URLs, search performance and content before deciding what will move. Work with developers to define destination structure and template requirements.
What the work produces
- URL and content inventory
- Redirect and language mapping
- Technical requirements
The decision it supports
What existing value needs a clear destination?
The purpose
Test the implementation, not the promise.
Review the staged website’s templates, links, redirects and indexing controls. A complete design does not establish that the migration is ready for search.
What the work produces
- Staging crawl and template checks
- Redirect and canonical validation
- Launch checklist and responsibilities
The decision it supports
Can the critical journeys work on the new website?
The purpose
Check what search engines can actually reach.
Verify the released routes, redirects and indexability, then monitor search evidence. Investigate unexpected changes with the development team rather than treating launch day as the finish.
What the work produces
- Live route and indexing checks
- Search Console monitoring
- Prioritised follow-up fixes
The decision it supports
Did the release behave as intended?
The purpose
Leave a foundation the team can maintain.
Document the decisions, recurring checks and responsibilities. The people publishing future content should understand the technical rules that protect the site’s structure.
What the work produces
- Maintenance guidance
- Publishing and template safeguards
- Ownership and review cadence
The decision it supports
Can the team preserve the improvements?
What the work can include.
The scope follows your starting point, priorities and the people available to implement it.
Architecture and internal links
Examine how templates, navigation and links connect important content, including unnecessary duplication or isolated pages.
Canonicals and redirects
Resolve conflicting URL signals and define appropriate destinations during consolidation, restructuring or migration.
Rendering and page experience
Investigate whether important information is available in rendered pages, alongside relevant mobile and loading-performance issues.
International technical SEO
Coordinate language versions, hreflang and site structure with the real content and audiences, including phased multilingual launches.
Developer collaboration
Translate findings into prioritised tickets, review implementation and provide maintenance guidance rather than leaving a disconnected audit report.
A wider view of discovery
Make expertise accessible before optimising discovery.
Technical work also considers whether useful information is accessible to the relevant search and AI systems. That includes readable page content, appropriate crawler controls and structured data that accurately describes what visitors can see.
Different platforms have different access and preview controls. I review the relevant requirements rather than assuming one file or schema type unlocks every AI answer. Technical eligibility supports discovery; it does not guarantee a ranking or citation.
The work in practice.
Different businesses, different starting points. Explore the approach and the context behind each result.
+64.7%
Organic clicks from outside Japan
Property development
Japanese property. A stronger international search presence.
Read case study
2×
Website traffic after technical fixes and selected content optimisation
Personal finance product reviews
After a difficult revamp. Twice the website traffic.
Read case study
81 → 736
Search clicks across the reported comparison
UX design & development
An underperforming site. A useful enquiry channel.
Read case studyLocal context changes the work.
Explore the search behaviour, languages and commercial considerations in each market.
Before we begin.
A few practical questions about the work.
Do you implement fixes or only provide an audit?
I can lead diagnosis, prioritisation and implementation review, working with your developers on changes. The scope makes clear which tasks I handle directly and which require access or development work from your team.
When should SEO become involved in a migration?
Ideally before the new structure and templates are finalised. Early involvement makes it easier to preserve useful URLs and content, define language requirements and plan validation before launch.
Can you investigate a traffic drop after a redesign?
Yes. I review the timing, affected pages, search evidence and technical changes to identify plausible causes. The response should be based on diagnosis rather than assuming every drop comes from the same issue.
Do you support multilingual websites?
Yes. The work can cover language-version structure, hreflang, indexing and migration coordination. Content owners and local reviewers remain important, especially where versions launch at different times.
Will an audit guarantee higher rankings?
No. An audit identifies constraints and opportunities; results depend on the issues, implementation, content and competition. We agree how fixes will be checked and what evidence should be monitored.
What happens after the website is handed over?
Where included in scope, I provide maintenance guidance, publishing considerations and a practical review schedule. Ongoing monitoring or advisory support can be agreed separately.
A clear next step
Let’s work out
what comes next.
Share your website, the challenge and what you would like to improve. We can start with the work that matters most.
Discuss your website or migration