// Technical SEO / Audits and migrations

FIND THEFRICTION.FIX THE CAUSE.

// The useful starting point

Turn search problems into an implementable plan. Technical SEO for indexing, site structure, redirects, performance and the changes that put valuable pages at risk.

// 01 / The short answer

An audit should lead to a decision.

Technical SEO examines whether search engines can reach, understand and index the pages your customers need. The useful question is not how many warnings a tool can generate. It is which issue is affecting an important page, what evidence supports the diagnosis and what needs to change.

I connect crawl findings with Search Console, site structure and the business purpose of each page. You get prioritised issues with affected examples, recommended action, an implementation owner and a way to check the result. The engagement can cover diagnosis, agreed fixes or migration support. Development work and release responsibilities are made explicit before work starts.

// 02 / Where this fits

When the foundations need attention.

Start with a specific change, symptom or risk so the investigation has a useful focus.

// 01

Important pages are missing from search.

A page may be blocked, excluded, duplicated, poorly linked or simply not selected for indexing. We inspect the affected URLs and the pattern behind them before changing settings across the site.

// 02

A rebuild or move is approaching.

A new design, platform or domain can change URLs, content and indexing controls together. Technical SEO brings current search value into the page plan and gives the launch an agreed checklist.

// 03

Traffic changed and the cause is unclear.

A template release, redirect change or tracking problem may coincide with a drop. We compare dates, affected page groups and available evidence to narrow the investigation instead of treating every decline as the same problem.

// 03 / What I do

From an error list to work that can ship.

The investigation follows the site and its commercial priorities. A brochure site, membership site and large catalogue do not need identical audits.

// 01

Crawl and indexing diagnosis.

Inspect response codes, indexing directives, canonical signals, sitemaps and internal discovery. Compare representative URLs with available Search Console evidence. Distinguish pages intended for public search from account, utility and duplicate routes.

// 02

Architecture and template patterns.

Review the paths to important pages, duplicate page purposes, navigation and repeatable template problems. Where one setting affects many URLs, document the pattern and test a representative sample before recommending a site-wide release.

// 03

Migration and redirect planning.

Inventory valuable URLs, record keep/change/retire decisions and map moved content to relevant destinations. Check old-to-new routes, retained content, metadata and launch indexing controls. Agree who releases, verifies and monitors the change.

// 04

Performance and implementation checks.

Investigate performance issues in the context of real templates and customer journeys. Separate image, script, theme, hosting and third-party causes where evidence allows. Retest agreed fixes and record remaining constraints rather than presenting a better tool score as the whole outcome.

// 04 / In application

Different sites. Different failure points.

Illustrative investigations showing how the method adapts; these are not reported client outcomes.

// Furniture and product businesses

A catalogue creates more URLs than useful destinations.

Filters and sorting produce many similar URLs while important furniture categories are hard to reach.

The approachMap indexable category purposes, review generated URL patterns and internal links, then test template changes on representative categories and products.

What to checkCheck discovery and indexing of intended destinations, useful organic entries and any impact on product browsing.

// Membership organisations

Public information and member resources overlap.

An organisation rebuilds its site and needs eligibility and event information discoverable while member-only resources remain restricted.

The approachRecord public and restricted page roles, test real access controls, then review crawl and indexing settings separately. Include sign-in and public signup journeys in release checks.

What to checkVerify intended public URLs and member access behaviour; review search discovery of membership information.

// Golf, coaching and venues

A redesign must preserve several customer routes.

Course information, coaching enquiries and an external booking service sit behind a redesigned navigation.

The approachPreserve useful URLs where possible, map changes, check internal destinations and test the handoff to the existing booking provider.

What to checkVerify redirects and priority journeys at launch, then review relevant search entries and enquiry actions.

// Illustrative diagnostic guide / not client results

The symptom is a starting point.

A reliable recommendation explains what to inspect before it names the fix.

The symptom is a starting point.
Observed symptomFirst investigationDecision it informs
A recently launched service page is absent from searchInspect the live response, indexing settings, canonical, internal links and URL inspection evidenceCorrect a technical exclusion or strengthen the page; do not assume every absence is a crawl block
Many pages drop after a platform changeCompare the release date, old URL map, redirects, retained content and live template settingsPrioritise a migration regression before commissioning broad new content
A tool reports hundreds of duplicate titlesGroup affected URLs by template and inspect whether each should be a search destinationFix the page model or template instead of manually renaming every generated URL
Traffic falls but Search Console clicks remain steadyCompare analytics collection, consent behaviour, dates and the affected channelsResolve a measurement discrepancy before attributing the change to organic visibility
Mobile product pages feel slowReview field evidence where available and test representative templates and third-party scriptsChoose a practical performance change with a browsing check, rather than chasing a score alone
// 05 / The method

Diagnose. Prioritise. Verify.

// 01

Establish the baseline.

Gather site access, available search data, change history and priority pages. Define the symptom or release risk and record what success would mean for this engagement.

// 02

Build the evidence.

Crawl the agreed scope, inspect representative URLs and compare data sources. Group issues by cause, reach and business importance, identifying assumptions or missing access.

// 03

Agree and implement fixes.

Write a practical backlog with examples, owners and checks. Complete the agreed work directly where scoped, or work with your developer on changes requiring their environment or platform expertise.

// 04

Check the release.

Retest the affected patterns and customer routes, record deployment dates and review available search evidence afterwards. Unresolved constraints remain visible with a named next action.

// 06 / A clear agreement

Know what happens after the audit.

The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.

Included in the agreed work

  • Agreed crawl and review of representative page templates
  • Prioritised findings with evidence, affected examples and recommended action
  • Implementation scope and ownership for each agreed fix
  • Validation of scoped changes and a handover of outstanding work

Separate or out of scope

  • An unprioritised export presented as a completed strategy
  • All development, hosting or platform changes by default
  • A guarantee that every eligible URL will be indexed
  • A site rebuild, penetration test or indefinite post-launch support unless separately agreed

What shapes the cost

Scope depends on URL and template complexity, access, the number of domains or platforms, diagnostic uncertainty and whether implementation is included. Migration work also depends on the quality of the existing URL inventory and how many routes change. The proposal separates investigation, fixes and monitoring.

What shapes the timing

Diagnosis comes before broad remediation. For a migration, inventory and mapping must inform structure before launch; checks then happen on staging and on the live site. Developer availability, release windows and data access determine the schedule. Search engines may take further time to reflect verified changes.

Who owns what

You provide access, business priorities and a history of relevant changes. I document findings and complete or coordinate the agreed SEO work. Your developer or hosting provider owns changes assigned to them; a named person approves production release. The handover records what was deployed, checked and left open.

// 07 / Work you can inspect

See the decisions before the deliverable.

My redesign guide explains the working method: inventory current pages, make URL decisions, test staging and assign post-launch checks. The AK Electrical case shows those website foundations in context: an editable WordPress rebuild with clearer service architecture.

The redesign SEO checklist

A practical account of URL mapping, redirects and launch responsibilities.

AK Electrical's website foundations

An editable WordPress rebuild with clearer service structure and SEO foundations.

// 08 / Useful questions

Before we start.

Can I commission an audit without ongoing SEO?

Yes. An audit can be a defined engagement with a prioritised backlog and handover. We agree whether you need diagnosis only, implementation support or a subsequent programme. The useful outcome is knowing what to do, who will do it and how completion will be checked.

Will you fix the issues or send a report?

That is specified before work starts. I can complete agreed work within the relevant scope and access, while some changes need your developer, platform provider or host. Each priority should have an owner and acceptance check; otherwise an audit can leave the business with a list it cannot use.

Do we need to rebuild the website to fix technical SEO?

Not necessarily. A template setting, internal linking change or redirect correction may address an important issue without a rebuild. I investigate the cause first. If the platform materially limits the required change, I explain the constraint and alternatives before recommending a larger project.

Can you protect rankings during a redesign?

I can help reduce avoidable risk through inventories, relevant URL mapping, content checks and launch validation. No one can promise unchanged rankings or traffic. Involve technical SEO while the structure is being decided so useful pages are considered before design and development lock them out.

Does a good speed score mean the SEO work is done?

No. Speed is one aspect of a working website. A fast page can still be excluded from indexing, answer the wrong question or make an enquiry difficult. Performance work should address evidence from real page types and be checked alongside the customer’s route through the site.

What access will you need?

Usually the website and CMS, Search Console and relevant analytics, plus information about hosting, recent releases and any staging environment. Access requirements depend on the investigation. Use individual accounts with appropriate permissions; ownership should stay with your business.

// A useful next step

LET'S FIND THE CAUSE.

Send the website, affected page examples and what changed or concerns you. If a launch is approaching, include the proposed changes and release date.