Search Museum Next

Planning Your Museum’s Website Redevelopment

Editorial update, 10 October 2026: measurement, testing and launch guidance have been revised. Original Analytics screenshots are retained as historical illustrations.

At its core, a re-development is the process of taking something and designing it again for the second, third, fourth time… You get the gist. It’s process of re-thinking, re-imagining, making something more relevant, current and contemporary. In this article, we will be talking about a website redevelopment, rethinking your museums website to make it more streamlined, user-friendly and reflective of your organisation’s culture and values. Whether you are undertaking a website redevelopment yourself (and hats off to you if so!) or working with an external web developer, this article will contain lots of useful tips and tricks of the trade. 

During the process of a museum website redevelopment, it’s important to keep your eye on the prize. What we mean by that, is that you absolutely must keep in mind who the website is for. Every decision that is being made must be guided by the potential user. As museums it can sometimes be hard for us to get over our pride and keep in mind that if a website is beautiful but not user-friendly, then it’s not really successful. End-users need to be able to navigate your website with ease so make sure that this is your top priority. 

We will speak at-length on making your museum website user-friendly in this article, but it’s important to introduce that concept at the beginning as we are laying the redevelopment foundation. 

So what goes into a redevelopment? We have six steps to success to share with you…

  1. Website strategy
  2. User-testing
  3. Design
  4. Build
  5. Soft-launch
  6. Maintenance and improvement

If you follow these six steps you can be sure that your redevelopment will be on the right track and will result in a museum website that is not only more user-friendly, but better-orientated to your business and organisational goals. 

Define the museum’s website goals and owners

First, take a good look at what works and what does not. Check the homepage, main navigation and the pages visitors use most. If targeted fixes could solve the problem, start by improving your existing museum website rather than assuming a complete rebuild is necessary.

Set the project’s owner, budget and timetable. Agree who will approve content, maintain integrations and keep opening hours, prices and access information current after launch. Give priority to visit planning, ticket checkout, accessible information, school enquiries and membership.

Agree the launch test before agreeing the design. Can a first-time visitor find admission prices, check access information and book the correct exhibition on a phone? Can staff update a closure notice without a developer? Record the answers on the existing site, then test the same tasks on the new one. Before switching over, check the old-to-new URL map, ticketing handover, forms and measurement. A redesign is ready when those journeys work, not simply when everyone likes the homepage.

Set up useful museum website measurement before establishing the baseline. In GA4, events record interactions and key events identify important outcomes. A completed booking is different from a click to a ticketing provider.

  • Engagement and bounce: GA4 defines an engaged session as lasting longer than 10 seconds, including a key event or having at least two page or screen views; the timer can be adjusted. Bounce rate is the proportion of sessions that are not engaged. Investigate the visitor’s task before judging the result.
  • Exits: an exit describes where a visit ends, not how quickly someone leaves. Finishing on a confirmation page can be a successful outcome.
  • Completed actions: compare bookings, registrations and enquiries with the people or sessions eligible to take that action. Define the denominator and check the data quality.
  • Speed and usability: test real pages and booking steps, particularly on mobile. A short visit to check opening hours can succeed; long visits can indicate either interest or difficulty.

Historical Universal Analytics bounce-rate illustration from the original 2020 guide. Use the GA4 definitions above rather than this old interface.

Historical Analytics illustration from the original 2020 guide. The revised measurement plan should focus on the tasks and outcomes the museum needs to understand.

Research visitors and test real tasks

Test early and during development, as well as before launch. Give participants a realistic task, such as finding an accessible exhibition visit for a particular date, without telling them which links to click. Observe where they hesitate and ask them to explain what they expected.

Include people who do not already know your museum, disabled users and people using different devices. Recruit according to relevant needs and circumstances rather than assuming demographic categories explain every behaviour. Collect only the participant information needed for the research.

Some returning testers can help compare the old and new experience, but include fresh participants too: familiarity with the earlier test can make a journey easier. Choose remote or in-person sessions according to the task and access needs. If recording, obtain informed consent, explain who will see it and how long it will be retained, and avoid capturing real payment details.

Keep a prioritised issue list, assign owners and repeat the important tasks after changes. A participant’s preference is one piece of evidence; use it alongside observed task completion and the museum’s operational requirements.

Plan content, navigation and wireframes

Armed with information about which pages need some TLC and how your website could be improved overall, it’s time to delve into the design stage. We speak at length about brand consistency in this article.

Now is the time to dust off those cobwebs and make your website super consistent with the rest of your branding. Your website should incorporate your brand colours, fonts, mission etc… Many museums choose to do a website redevelopment as part of a rebranding process. This can be a very exciting time to debut a new look for your organisation. Make sure that you are being consistent and getting it right. You wouldn’t want someone to mistake your beautiful new website as belonging to a different brand!

Now that we’ve droned on about the importance of branding again, let’s turn our focus towards the design and layout of your website.

Your starting point is a sitemap, this is a visual map of how your website is navigated… essentially boiling down the journey of the user into a single visual. Complete a sitemap of your old website as well as your newly envisioned one. Then put the two side by side and make sure that all of the content you want to share with your audiences is still available, just the pathways to get there are much more clear. Design this new sitemap using input from the initial user-testing that you will have performed. 

A great way to do this is to use card sorting. This is something that can be done with users as a part of user-testing, or with your team to decide how content will be laid out in an easily-digestible visual way. 

You can either do an open card sort, or a closed card sort. The difference is that with an open sort, there are no rules as to how the content can be laid out. Either you and your team, or the user who is undertaking the testing can make suggestions as to how they think the content should be laid out (this includes dropdowns, click-throughs etc…) A closed card sort is separated into categories that are typically informed by primary navigation buttons. For example, you and your team know that you need to have the following categories: about us, programmes, events and donate. You would then use a closed card sort to determine how all of the other pages of the website fall under those four main categories. 

The second step in the design of your website is establishing a wireframe for each page. A wireframe is the most basic form of a website with content laid out in a very clean and visual way to guide developers as to the importance of certain content and where it should go. 

You don’t need a fancy-schmansy graphic like the one we have here for every page. Even a piece of paper with a visual map drawn on it will be super helpful to a web developer if you are working with one or to your team if you are tackling this redevelopment in-house. 

Having a sitemap allows feedback from team members and stakeholders at an early stage in the redevelopment rather than making changes once the full design has been implemented which is not only a waste of time, but of money as well. 

Build integrations, accessibility and measurement

Create an inventory of existing pages, files, URLs and metadata. Decide what to keep, revise, merge or retire, and map old URLs to the most relevant new destinations. Keep meaningful titles, descriptions and content that visitors still need.

Agree the ticketing and CRM handovers, consent controls and event measurement with the relevant suppliers. Test keyboard use, headings, contrast, form labels, error messages and assistive-technology access. Include an accessibility review and user testing in acceptance, rather than leaving them until launch.

Once the layout of the site, content and design elements have been agreed upon by all team members and signed off by management, it’s time for the build to commence! 

Make sure that as you undergo the process of creating the website, and/or handing off the beautifully organised and presented package to a web developer, that you are using proper SEO practice to ensure that your new site will be running smoothly and efficiently. Meta descriptions, image alt tags and proper page titles are all elements that should be taken seriously. Allocate the time to build the site up properly and do things the right way initially so there isn’t even more work for you to do once the build is done. 

The main framework of the museum website is built first, then text and images are added. If you are re-developing a website on your own, then you’ll have lots of control of when and where content is added. However, if you are working with an external developer, then it’s imperative to present to them a package of all images and text when it’s time for the build that is neatly organised and mapped out. 

We’ll give our top tips below on making your developer’s life 1000x easier:

  • Use file-sharing software (Google Drive, Dropbox etc…) This way, you’re not sending over a giant WeTransfer file or even worse, multiple emails with copy and images. Using a platform that allows for file sharing makes segmenting and organising information much easier. Create different folders according to sections of your website and have everything labelled accordingly.
  • Include a wireframe for each page. If you want your pages to look a certain way and for the focus to be on particular elements, make sure that you communicate that to your developer by using a wireframe. 
  • Write out copy for each page in a document and clearly indicate how phrases should be formatted. Make sure to indicate your header, subheader, body copy and footer information. 
  • Label images properly and make sure that they are optimised for the web. It’s better to send over images that are too hi-res rather than too low-res. It’s easy to make images smaller but difficult to recover detail from an image that is too small. 

Prepare redirects and a controlled launch

Review the new site in a controlled staging environment before changing the public site. Test content, forms, ticket types, payments through the agreed test process, confirmation messages, access information and measurement. Include both returning and fresh testers, and resolve issues that block essential journeys.

Prepare backups and a rollback plan with the developer. Validate the old-to-new redirect map, important metadata and the XML sitemap. Agree who can approve launch, who will monitor it and what would trigger a rollback.

At release, remove staging access or indexing restrictions only where appropriate for the public site. Recheck redirects, forms, ticketing handovers, consent behaviour and Analytics events on the live domain. Monitor errors, failed bookings and visitor feedback before promoting the new site widely.

A controlled release is different from leaving the website “secretly” live for weeks. Set explicit acceptance criteria and give someone responsibility for responding if the visitor journey breaks.

Maintain and improve the new website

Now that your website is built and live, the journey is simply not over. Good websites are consistent, updated, relevant, smooth and user-friendly. You will continue to be all of those things only if you update your website on a regular basis, refresh content and optimise for SEO. 

It’s frustrating to see so many organisations creating brand new websites that then don’t get the love and attention they deserve after the spotlight has moved onto something else. Make sure that all of your hard work doesn’t go to waste and that you are monitoring analytics and consistently looking for ways to improve your website and keep it relevant to your target audiences.

–

MuseumNext offer online learning for museum professionals striving for engaging, relevant and flexible professional growth content. Learn more about our virtual museum conferences here.

Related Content

Paws and Patrons: Planning a Pet-Friendly Museum Visit

What do Airbnb, Instagram, and your local museum have in common? Potentially, a growing audience of dog lovers who can’t bear to leave their furry...

Museum Livestreaming: Planning Access Beyond the Building

Not everyone has the means or opportunity to visit a museum, so should curators bring the exhibit to the viewer? From social media to video...

QR Codes in Museums: A Practical Guide to Planning and Use

A QR code can connect a museum label to a web page, audio recording, translation or online service. Its value depends on whether that destination...

Subscribe to the latest museum thinking

Fresh ideas from museums around the globe in your inbox each week