Illustration: a new layout should follow a review of the information customers still need.
An old website can be frustrating enough that starting again feels like the obvious answer. But a new design does not have to mean forgetting everything. Useful explanations, original images, established page addresses and customer routes may deserve to survive.
Before replacement begins, decide what to retain, improve or leave behind. This is a business and content guide, not a technical migration checklist. It helps you prepare the questions that the project and its specialist checks must resolve.
Start with the reason for replacement
Write down what no longer works. Customers cannot find a service. The business has changed. Information is inaccurate. The site is difficult on a phone. Updating it has become impractical. Those are different problems and may require different work.
Moving unclear text into a prettier layout does not make it clearer. Removing a useful explanation solely because it looks old can discard something customers still need. Separate what the site says from how it presents it.
Choose the customer outcome first: easier service selection, clearer enquiries or more maintainable information. Do not treat replacement as an obligation to add every feature you have seen elsewhere.
Make an inventory you can understand
List the important pages and the job of each: homepage, services, contact information, practical guides, project examples and downloads. For a larger site, technical help may be needed to find everything. The business still needs to explain what matters and why.
Do not limit the list to pages in the menu. A printed card, customer email, bookmark or external link may point directly to a less prominent page. Downloads and form destinations can be important even if you rarely look at them.
Note whether information is current, who can approve it and whether it depends on another account or system. Record uncertainty rather than quietly assuming everything can be transferred.
Make four deliberate content decisions
Keep: accurate information serving a clear purpose. It may need presentation changes, but it has earned its place.
Improve: a useful subject with an unclear explanation, weak evidence or missing enquiry guidance. Strengthening the established destination can be better than creating another competing page.
Combine: material repeating the same job or making more sense together. Decide what must survive before merging it. A longer page is not automatically easier to use.
Retire: information that no longer belongs in the offer or is inappropriate to retain. Removal and treatment of the old address still need planning and approval.
These are review decisions, not instructions to delete live pages automatically. They give the redesign a content strategy rather than a transfer list.
Preserve answers customers rely on
Owners naturally notice the homepage first. A customer may rely on a preparation checklist, a direct contact route or a particular service explanation.
What should somebody measure, send or bring? Which choices are confusing? What needs explaining before a visit? Keep those useful answers, checking that the described material, service or process is still current.
Use genuine repeated customer questions where available. Do not invent demand because a page exists. Reliable website evidence can add context, but missing measurement is not proof that a page is unused, especially when it is shared directly or offline.
Review the service structure
An old menu may reflect the business at the time it was built rather than the choices customers make today. List current services and the distinctions visitors need to understand.
Some subjects deserve separate pages because their options and enquiry requirements differ. Others can be grouped without hiding an important answer. Check repeated descriptions under different names before adding another version.
The aim is a clearer route, not the fewest possible menu items. A newcomer still needs enough information to recognise whether the business can help.
Check photographs and proof separately
An attractive photograph can be wrong for the new site if it shows an old service, outdated premises or a product no longer offered. Identify actual work, illustrations and licensed supporting visuals accurately.
Keep permissions and credits. Do not move an image into a context implying a stronger claim than it supports. Review project wording and identifying information too: what was actually done, and what is appropriate to show?
If relevant proof is missing, record the gap. Clear text and an accurate illustration are preferable to fabricated customer evidence. Original files may also be more useful than a small copy taken from the old webpage.
Treat page addresses as part of the project
An established URL can live in an email, bookmark, printed item or another site's link. A new visual design does not inherently require a new address for the same useful page.
If URLs must change, map the old destinations to the appropriate new ones. Google's site-move guidance covers URL mapping and redirects and explains that search visibility can fluctuate during a move.
You do not have to implement those technical steps yourself. The scope should recognise old links rather than assume they can all lead to the new homepage. Record important shared and printed addresses, then verify their agreed treatment after launch.
Identify connected accounts before relying on a transfer
Domain registration, hosting, business email, forms, analytics and specialist tools may involve different providers. Gather provider names, relevant records and the account ownership you understand.
Do not send passwords casually in an initial enquiry. Identify the services first and arrange appropriate access for agreed work. Website replacement and email changes are different tasks, even where infrastructure is shared.
Mark inaccessible accounts and unknown services as unresolved. They should be investigated before a transfer plan depends on them.
Review forms and downloads as complete journeys
A form includes instructions, fields, validation, confirmation and a receiving destination. Review whether its questions still help assess the request and which details can wait for a conversation.
Downloads need current facts, the right version and useful links. Check whether their addresses appear elsewhere. A redesigned page is not enough if its document is obsolete or its form goes nowhere useful.
Test these journeys after implementation rather than judging only their appearance. Genuine test submissions should be agreed with the business so they are recognised as tests.
Give the archive individual attention
Some older articles explain lasting ideas. Others contain dated guidance, unsupported claims or services that no longer fit. Keep or improve useful material, retaining sources and distinguishing original publication from later revision.
Do not give every story a new publication date merely to make it look current. Check related links and recommendations too. An attractive new article layout should not send readers to obsolete destinations.
Keeping everything without review carries uncertainty forward. Deleting everything because it looks old can throw useful history away. Neither is a considered content decision.
Agree responsibilities and scope
Name who confirms service facts, approves wording and collects comments. Technical implementation and business approval are related but different responsibilities.
Discuss transfer, rewriting, image preparation, redirects, domain work, integrations and post-launch checks where relevant. Do not assume they are all included because the project is described as a redesign.
Time for Designs assesses website projects individually according to requirements. Content work, migration, integrations and support form part of the scope discussion. Annual services are quoted separately.
Test representative pages, not just the homepage
Before launch, review a main service, a guide, the contact route, an example and important downloads or functions. Follow real tasks on a phone and larger screen.
Can a customer find what to send? Have useful instructions disappeared? Are images accurate and links expected? Compare essential information with the approved inventory. These checks complement the agreed technical launch checks; they do not replace them.
Record what you keep, improve, combine or retire, along with important address changes. After launch, identify the exact page and behaviour when something fails. Pay attention to genuine customer questions, but do not treat every early fluctuation as a reason to redesign again.
Your replacement brief
- Why the current site needs changing.
- What customers should understand and do.
- Content to keep, improve, combine or retire.
- Original images, artwork and permissions.
- Important shared or printed page addresses.
- Domains, email, forms and connected tools.
- Unknown accounts or facts needing investigation.
- Who approves the business information.
- Required date and why it matters.
- Updates and support to agree after launch.
A partial brief is enough to begin. An acknowledged unknown is more useful than an untested assumption.
Replace weaknesses, not useful history
Read about website design and replacement, then call 062 61524, send the current site and essentials by WhatsApp or visit 98 Friar Street, Cashel.
Our website quotation guide helps with the initial conversation. For the customer journey itself, see how to check whether visitors know what to do next.
The strongest starting point is not an empty page. It is a clear decision about what is worth bringing forward.