Website Redesign Without Losing Enquiries or Search Visibility: An Ethiopian Business Checklist

One of the biggest website-redesign mistakes is treating the existing website as if it has no value.

Imagine your existing website contains:

• 80 pages
• 25 blog posts
• 15 service pages
• Pages already indexed by Google
• Backlinks from other websites
• Contact and quotation forms
• Downloadable documents
• Years of business information

Building 20 beautiful new pages and deleting everything else can create problems. Before development starts, we first create an inventory of the existing website.

Website migration inventory

The objective is simple: know what exists before replacing it.

Changing URLs without planning redirects is one of the easiest ways to damage existing search visibility.

Suppose your old website has /our-services/web-design, but the redesigned website uses /services/website-development. The old URL should not simply disappear.

We prepare a migration sheet such as:

Where possible, valuable URLs can remain unchanged. Where they must change, permanent redirects are configured appropriately. This helps users, backlinks and search engines find the replacement page.

Google’s site migration guidance recommends mapping old URLs to their relevant replacements and using permanent redirects.

Many established Ethiopian organizations still operate websites originally developed with WordPress themes and large collections of plugins.

WordPress can be suitable for many projects, so migration should not happen simply because a website uses WordPress. However, organizations sometimes reach a point where their existing implementation has become difficult to maintain, slow or dependent on outdated plugins and themes.

For appropriate projects, DreamTech can rebuild the frontend using modern technologies such as Next.js while migrating the valuable information from the existing website.

The migration can include:

• Existing pages and page content
• Blog posts and images
• SEO metadata and existing URLs
• Redirects
• User login functionality
• Forms and existing navigation
• Search functionality
• Important integrations
• Downloadable documents

The objective is to preserve years of website content. We modernize the technology while preserving the business value of the existing website.

Moving away from a traditional WordPress frontend does not mean your company should need a developer whenever somebody wants to publish a blog post. We can provide a secure administrative CMS.

Authorized employees can manage content such as:

• Website pages and blog posts
• News, events and vacancies
• Team members, projects and services
• Images and documents
• Announcements, FAQs and testimonials

The public website can use a modern frontend while authorized staff manage information through an administrative interface.

Role-based CMS access

Not every employee should have complete control of a corporate website. Access can therefore be divided by role.

Permissions can be customized according to the organization’s actual workflow.

Some organizations need more than public pages. The redesigned website can include authenticated areas for members, customers, employees, students, partners, associations, churches, NGOs and professional organizations.

Depending on the project, members could sign in to:

• Update their profile
• View membership status
• Access private resources
• Download documents
• Check payments and renew membership
• Register for events
• Submit applications
• View announcements

Administrators can manage users from the corresponding dashboard.

A redesigned website can also become part of the organization’s actual operational and revenue workflow. Depending on the organization and provider requirements, we can integrate supported Ethiopian payment options, including Telebirr.

Donations

A church, NGO or charitable organization can accept donations directly through its website. Visitors can select an amount, provide the required information and proceed through the integrated payment process.

Membership payments

Associations and membership-based organizations can connect payment with their membership system. For example:

Member login → Membership renewal → Payment → Confirmation → Membership record updated

Service payments

Businesses can accept payments for eligible services or orders through their website. Payment integration requirements, merchant approval, transaction charges and availability depend on the selected payment provider.

Read the Telebirr integration process guide.

A website should not exist only so the owner, employees and their friends can visit it occasionally. A serious business website needs to support measurable business objectives.

For many companies, that means converting visitors into:

• Phone calls and WhatsApp conversations
• Quotation requests and bookings
• Purchases and registrations
• Applications and memberships
• Donations and qualified enquiries

That changes how we approach redesign. Alongside asking “Does this page look beautiful?”, we ask “What should a visitor do after seeing this page?”

A service page, for example, might follow this structure:

Customer problem → Solution → Evidence → Benefits → Relevant project → FAQ → Call to action

Calls to action can be placed where customers naturally need them: Request a Quote, Call Us, Book a Consultation, Send Your Requirements, Become a Member or Donate.

The objective is to transform the website from a passive company profile into an active customer-acquisition and service platform.

The redesigned website should work properly on a phone. We specifically test important mobile actions, including:

• Navigation and search
• Forms and call-to-action buttons
• Phone buttons and WhatsApp links
• Payment, login and registration
• Downloads and maps
• Page loading

A potential customer finding your company through Google on a phone should be able to understand your service and contact you without struggling with the interface.

Performance is one of the areas where DreamTech puts particular emphasis. A website that looks impressive but takes several seconds to become usable can lose visitors before they see the content.

We engineer modern websites around performance from the beginning. Depending on the project, this can include:

• Next.js
• Server-side rendering or static generation where appropriate
• CDN delivery
• Image optimization and modern image formats
• Code splitting and lazy loading
• Caching and database optimization
• Reduced JavaScript and optimized fonts
• Compression and optimized API requests

We use Google Lighthouse during development and quality assurance. For suitable pages and agreed testing conditions, our optimization target is:

A 100 score is a target rather than an unconditional guarantee for every page or every testing environment. Scores can change because of third-party scripts, external integrations, network conditions, dynamic content and later website changes.

Performance is treated as an engineering requirement. Before handover, we test agreed representative pages and document the results. See Google’s Lighthouse guidance and Lighthouse score variability.

We plan infrastructure for actual visitors. If marketing succeeds, traffic should grow.

Depending on the project, our architecture can use:

Visitor → CDN → Optimized application → API/server → Database

A CDN can serve cached resources from infrastructure closer to users while reducing unnecessary work on the main server.

This architecture is particularly valuable when a website receives traffic from:

• Google Search and Google Ads
• Social media campaigns and news coverage
• SMS campaigns and events
• Product launches
• Large membership bases

Performance and capacity requirements are assessed according to the project rather than assuming every website needs identical infrastructure.

Speed without security is not enough. Our redesign checklist can include:

• HTTPS/SSL and security headers
• Secure authentication and role-based permissions
• Input validation and rate limiting
• Secure cookies and CSRF protection
• XSS and SQL injection protections
• Dependency review
• Backup procedures and restricted administration
• Logging and monitoring
• Cloud/CDN protection where appropriate

The exact controls depend on whether the website is informational, e-commerce, membership-based or connected to sensitive business systems.

The final cost depends on the existing website, number of pages, migration complexity, integrations and administrative requirements.

A practical planning range is:

These ranges are planning estimates. We review the existing website before confirming the final scope and price.

For eligible websites, DreamTech offers managed hosting at approximately 10,000 ETB per year.

Our hosting setup can include CDN-based delivery and the infrastructure required for the agreed website architecture.

For qualifying website-redesign projects, hosting can be included free for the first two years, subject to the agreed project scope and normal usage limits.

After the included period, the standard hosting fee can begin from approximately 10,000 ETB/year, depending on traffic, storage, server resources and infrastructure requirements. A very high-traffic application may require a different infrastructure plan.

Before touching the production website, create a complete backup.

Content

• Pages backed up
• Blog posts backed up
• News backed up
• Images backed up
• Videos identified
• PDFs/documents backed up
• Team profiles backed up
• Project/case-study content backed up

SEO

• Existing URLs exported
• Page titles recorded
• Meta descriptions recorded
• H1 headings recorded
• Canonical URLs checked
• Sitemap downloaded
• Important backlinks identified
• Google Search Console reviewed

Technical

• Database backup
• Website files backup
• DNS information recorded
• Email/DNS records documented
• Analytics configuration recorded
• Existing integrations documented

Do not depend solely on the live website as your backup.

The replacement website should normally be developed separately from the production website. This gives developers, SEO reviewers and the client time to inspect the new version before customers see it.

During staging we verify:

• Content, responsive design and navigation
• Forms and CMS
• Authentication and permissions
• Integrations and SEO
• Performance and security
• Redirects

The existing production website remains available until the replacement is ready for launch.

Before switching domains or production environments:

Content

• Important old content migrated
• Contact details verified
• Phone numbers tested
• Email addresses verified
• Images checked
• Documents accessible

SEO

• Page titles configured
• Meta descriptions configured
• Canonical URLs checked
• Robots configuration reviewed
• Sitemap generated
• Structured data checked where relevant
• Redirect map prepared

Conversion

• Contact forms tested
• Quote forms tested
• Phone buttons tested
• WhatsApp links tested
• Registration tested
• Login tested
• Payment flow tested where applicable

Performance

• Images optimized
• Caching enabled
• CDN configured
• Lighthouse tests completed
• Mobile pages tested

Security

• HTTPS configured
• Security headers reviewed
• Admin permissions reviewed
• Authentication tested
• Backup confirmed

When the new website goes live:

• Confirm DNS
• Confirm HTTPS
• Test homepage
• Test important service pages
• Test mobile website
• Test forms
• Test phone links
• Test WhatsApp links
• Test login
• Test payments where applicable
• Activate redirects
• Check old URLs
• Submit sitemap
• Verify analytics
• Verify Search Console
• Check indexing configuration
• Check server errors

Do not consider the project finished simply because the homepage opens.

After launch, take the URL inventory created before development and test it. Every valuable URL should return either:

• 200 — the page still exists
• 301 — the page correctly redirects to its replacement

Important URLs should not unexpectedly produce 404 — Page Not Found. This is particularly important for URLs receiving backlinks or existing Google traffic.

Technical testing alone is not enough. Someone should behave like an actual customer.

Example test

Search Google → Open service page → Read content → Click Request Quote → Complete form → Submit → Confirm company receives enquiry

Repeat similar tests for:

• Phone, WhatsApp and email
• Registration and login
• Donations and membership
• Payments and downloads

A website can technically be online while its most important business function is broken.

A redesign should be evaluated using data. Depending on the website, monitor:

• Organic search clicks and impressions
• Indexed pages and rankings for relevant searches
• Website visitors
• Contact-form submissions, phone clicks and WhatsApp clicks
• Quote requests and registrations
• Purchases, donations and membership renewals
• Conversion rate
• Page speed and error rates

Compare these against a genuine pre-redesign baseline whenever one exists. Without baseline data, avoid claiming that the redesign increased traffic or conversions by a particular percentage.

Changing the colors and replacing a WordPress theme is not necessarily a website transformation. A properly planned redesign can improve several layers simultaneously:

That is the difference between replacing a website and rebuilding it as a useful business system.