Inventory
List URLs, content, assets and owners.
Checklist / Website redesign
Protect what works, repair what does not and define the new journey before changing the surface.
A website redesign should begin with evidence: business goals, customer questions, analytics, search performance, content quality, forms, integrations and maintenance constraints. Inventory existing URLs and assets, identify what must be retained, define the new information architecture, prepare redirects and test conversion paths before launch.
Questionwhat the reader needs
Evidencedefinitions and boundaries
Next stepa useful action path
Why it matters
Inventory
List URLs, content, assets and owners.
CHAPTER 01
Understand the current condition.
Separate visual dissatisfaction from structural problems.
Evidence
Review analytics, queries and enquiries.
CHAPTER 02
Define the new customer journey.
Map intent before layout.
Architecture
Connect services, proof and actions.
Prototype
Test page types and mobile behaviour.
CHAPTER 03
Launch without avoidable loss.
Treat release as a controlled change.
Redirects
Map old URLs one-to-one.
Verification
Test status, forms, analytics and indexing.
Continue through the resources system.
Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.
Route 01
Resources
Use answer-first guides for website, SEO, CRM, automation, dashboards, field technology, portals and AI decisions.Route 02Ai Readable Website Structure
Structure public website information so people, search crawlers and AI-assisted discovery tools can identify entities, services, evidence and answers.Route 03Australia New Zealand Seo Guide
Plan service, industry and location content across Australia and New Zealand without cloned city pages or invented local presence.Route 04Business Automation Examples
Review practical workflow and connected-asset automation examples, including triggers, controls, exceptions and human approval.Route 05Customer Portal Guide
Plan customer identity, permissions, requests, documents, status, integrations and support before building a portal.Route 06Dashboard Design Guide
Define dashboard users, questions, metrics, data lineage, actions and refresh needs before choosing charts.Route 07Field Technology Guide
Plan mobile tasks, offline behaviour, job context, media, synchronisation, review and support for field systems.Route 08Google Sheets Vs Crm
Compare spreadsheets and CRM by ownership, relationships, workflow, permissions, history, automation and reporting needs.Route 09How Ai Assistants Help Businesses
Understand grounded search, summarisation, drafting and extraction use cases with permissions, source visibility and human review.Questions worth resolving
What to clarify before committing.
Should every old page be retained?
No. Retain useful intent and value; consolidate or retire weak duplication deliberately.
Will redesign improve rankings?
It can improve foundations, but rankings and enquiries are not guaranteed.
Bring the real problem
Audit the current website before rebuilding.
Bring the live site, analytics access and most important enquiry paths.