A better website for the business you’ve become. Refresh your design, clarify your message and make it easier for customers to take the next step, with a plan for your existing content and URLs.
Explore published MediaPlus website projects and their page designs. These projects are listed as CMS websites in our portfolio.
Website design, consultation & development.
View project detailsThese are examples of our website design and development work, not before-and-after redesign comparisons. Select an image to explore the page design.
An outdated appearance is one reason to redesign. The more useful question is whether your website still helps customers understand, trust and contact your business.
Important offers are missing, buried or explained inconsistently.
Menus, text, buttons or forms make it harder for customers to find their way.
Visitors can read about your business but struggle to request a quote or make an enquiry.
Routine changes depend on an ageing system or a complicated editing process.
Navigation and page layouts have grown without a clear structure.
Your website no longer reflects your positioning, customers or current capabilities.
Choose a scope that addresses the problems in your existing website, from selected page improvements to a full rebuild.
Review your current website, goals and available performance data. Identify what to keep, improve, combine or replace.
Organise services and information around customer needs, with useful links and clear routes between pages.
Refresh typography, imagery, spacing and page layouts around your brand and different screen sizes.
Clarify your offer and position relevant project examples, buyer questions and contact options where they help visitors decide.
Build the agreed layouts and functionality on a suitable platform, with an editing approach your team can manage.
Plan existing content, URL changes, redirects, technical checks and measurement requirements before release.
Some pages already attract relevant searches, earn links or generate enquiries. Others need clearer content or a simpler layout. We assess their role before recommending removal or consolidation.
Changing URLs, content and navigation can affect search visibility. A considered migration helps manage that risk, although no redesign can guarantee unchanged rankings.
A comparison article and a service page meet different needs. Review search intent before retaining, rewriting or redirecting existing content.
Agree on priorities, responsibilities and approval stages before development begins.
Discuss your customers, goals and frustrations. Review your website and available analytics.
Agree on the sitemap, templates, functionality, content responsibilities and migration scope.
Develop the visual direction and important page layouts for review.
Develop approved designs, prepare agreed content and connect required functionality.
Check layouts, navigation, forms and migration requirements, then coordinate release.
Check launch issues and available performance data to prioritise the next improvements.
The investment depends on your existing website and the requirements of the replacement. Your proposal should make the work and responsibilities easy to understand.
A redesigned website is a foundation for ongoing improvement. Discuss related requirements as part of your brief, with a clear scope for each service.
If the structure and platform still work well, selected layout or page updates may be enough. Broader content, usability or platform limitations may justify a full rebuild.
Existing content can be reviewed for reuse. Useful pages may be retained, while outdated or unclear information may need revision. The proposal should identify who supplies and approves final content.
It can. Changes to URLs, content and technical settings can affect visibility. Migration planning and launch checks help manage the risks, but rankings cannot be guaranteed.
No. A visual redesign does not automatically require new URLs. Where a change is needed, include a relevant destination in the migration plan.
The replacement can generally be prepared in a separate development environment. The release approach depends on your platform and hosting setup.
Timing depends on layouts, functionality, content readiness, migration requirements and approvals. A project schedule is established after reviewing the scope.
Discuss what your team needs to manage so the editing approach and any training or handover requirements can be agreed before development.
Maintenance should be defined in your proposal, including any updates, backups, monitoring and support responsibilities.
Share your current URL, the problems you are experiencing and your priorities. Let’s discuss whether a focused refresh or a wider redesign is the right starting point.