Turn search problems into an implementable plan. Technical SEO for indexing, site structure, redirects, performance and the changes that put valuable pages at risk.
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.
Start with a specific change, symptom or risk so the investigation has a useful focus.
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.
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.
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.
The investigation follows the site and its commercial priorities. A brochure site, membership site and large catalogue do not need identical audits.
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.
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.
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.
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.
Illustrative investigations showing how the method adapts; these are not reported client outcomes.
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.
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.
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.
A reliable recommendation explains what to inspect before it names the fix.
| Observed symptom | First investigation | Decision it informs |
|---|---|---|
| A recently launched service page is absent from search | Inspect the live response, indexing settings, canonical, internal links and URL inspection evidence | Correct a technical exclusion or strengthen the page; do not assume every absence is a crawl block |
| Many pages drop after a platform change | Compare the release date, old URL map, redirects, retained content and live template settings | Prioritise a migration regression before commissioning broad new content |
| A tool reports hundreds of duplicate titles | Group affected URLs by template and inspect whether each should be a search destination | Fix the page model or template instead of manually renaming every generated URL |
| Traffic falls but Search Console clicks remain steady | Compare analytics collection, consent behaviour, dates and the affected channels | Resolve a measurement discrepancy before attributing the change to organic visibility |
| Mobile product pages feel slow | Review field evidence where available and test representative templates and third-party scripts | Choose a practical performance change with a browsing check, rather than chasing a score alone |
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.
Crawl the agreed scope, inspect representative URLs and compare data sources. Group issues by cause, reach and business importance, identifying assumptions or missing access.
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.
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.
The right scope makes the work useful. Agree the deliverables, dependencies and responsibilities before starting.
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.
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.
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.
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.
A practical account of URL mapping, redirects and launch responsibilities.
An editable WordPress rebuild with clearer service structure and SEO foundations.
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.
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.
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.
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.
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.
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.
Choose the service that solves the problem in front of you.
Understand performance evidence before deciding what to change.
Bring technical planning into a wider structure and design project.
Resolve catalogue and category discovery as part of commercial search.
Connect the technical backlog with content and business priorities.
Work directly with Dan Smith. Based in Christchurch, working with businesses across New Zealand.
Send the website, affected page examples and what changed or concerns you. If a launch is approaching, include the proposed changes and release date.
Good websites work harder. Cookies help us see what’s working.
Essential cookies keep things running. With your permission, analytics cookies help us understand how you use the site, and marketing cookies help us measure ads and show relevant ads. Optional tracking stays off until you say yes. You can change your mind in Cookie Preferences.
The essentials keep this site working. Analytics and marketing cookies are optional. Choose what suits you and change your mind here at any time.
Essential cookies enable basic functions and are necessary for the proper function of the website.
Optional analytics cookies help us understand visits and interactions using browser identifiers. They run only if you accept Statistics and the relevant service.
Google Analytics 4 measures page visits and meaningful interactions after you accept analytics cookies. We do not send contact form answers, names, email addresses or phone numbers in analytics events.
Service URL: policies.google.com (opens in a new window)
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Measures page visits and successful enquiries and helps Daniel James show relevant ads on Facebook and Instagram after you visit. This runs only if you accept Marketing and Facebook Pixel.
Service URL: www.facebook.com (opens in a new window)