What happens to your research project website when funding ends? Without ongoing budgets for hosting and maintenance, and with researchers moving on, websites often disappear—along with valuable information. Don’t let this happen! Here’s our simple solution: convert your WordPress website into a static HTML site, so it’s stays visible to the world, but is hosted for free. I’ll show you exactly how to preserve your website for “eternity,” step by step.

This also works if you just want to host a website for free, and don’t need the website to change (much).

But Liesbeth, doesn’t archiving mean putting it away in a file cabinet for nobody to see? Yes, but in this article I mean that we’re storing the website for a long time, but also keep it visible to the world at the same time. A win-win!

Case study: The Seven Countries Study

Let’s walk through archiving your website using the Seven Countries Study as an example. You’ll follow along all the steps I took to archive this website and keep it available. This was one of the first websites we built when we founded The Online Scientist in 2012. The study itself is remarkable from a historical research perspective—it’s one of the longest-running research projects, starting in 1959 with a 60-year follow-up! We created the website together with the wonderful Professor Daan Kromhout, and it would be a shame to lose this treasure-trove of information simply because the project has ended.

It’s an easy way to make sure your research stays online and continues to benefit others without draining your budget.

Why you need to turn your WordPress into a static HTML website

WordPress websites are easy for researchers to edit and update during a project, especially if you work in a large team. However, they require hosting because they need a database to run on, to be able to use dynamic features like comments and seach forms. You also need to update the website regularly to protect against hacks and attacks. This always comes with recurring costs. That’s why we need to turn it into a simple HTML website first.

This has a lot of benefits:

  • No hosting costs: Static sites can be hosted for free on platforms like GitHub Pages, Cloudflare or Netlify.
  • No maintenance: You won’t need to update WordPress, plugins, or themes.
  • No security risks: Since there’s no database or login system, there’s nothing to hack.
  • Super fast website. Static websites load much faster because they don’t have to talk to the database.

It’s the perfect solution for keeping your research website running for a long time.

Some things don’t work on a static archive website

However, this means that pure HTML websites cannot have any interactive or dynamic features that require a database. While pages, posts, images, and PDF downloads will work fine, the following features won’t work anymore:

  • Forms: Contact & feedback forms.
  • Logins: User login systems for members-only content and administrative back-end dashboards.
  • Search: Search forms.
  • Event calendars: Dynamic calendars that display upcoming events or allow registration.
  • Webshops & payments: Online shops with payment processing and inventory management.
  • Interactive maps: Maps that show data points or respond to user input.
  • Comments: Blog comment sections that allow users to post and display discussions.
  • Hidden content: Everything that is only displayed in the back end.
  • Dynamic content feeds: Auto-updating sections like social media embeds.
  • Surveys and polls: Tools that collect and display user responses dynamically.
  • Interactions: Features like filtering datasets, creating reports, or showing personalized content.

For some of these features there are workarounds to make it work in a HTML website, but this is not an exhaustive technical article about static features.

Prepare your WordPress website

So, before we archive, we have to get rid of these dynamic functions and walk-through the website to check the content. Be aware that the archived version of your website will live on “forever”, so only include content that is valuable for your website visitors in the future.

First we have to add some things to the website:

  • For the new static website we need a disclaimer to tell visitors that it’s an archived website. We usually put this in the footer of the website. Explain to them that the website is not maintained anymore and can contain outdated information and links. Also add the date of archiving, and for full transparency you can add the link to the GitHub repository (in our case https://github.com/TheOnlineScientist/SevenCountriesStudy). Below are some examples you can use:
    • Short example: “This website is archived as of [date]. It is no longer maintained, and some information may be outdated or incorrect.”
    • Long example: “This website was archived on [date] on GitHub [link to files] and is no longer maintained. The content is preserved for historical purposes and reflects the state of the project as of its last update. Some information may be outdated, links may no longer work, and no further updates or corrections will be made. For inquiries about the project, please refer to [institution/funding body] or consult the original publications. Use this resource with caution, as it may not represent current developments.”

Then we need to back up a few things:

  • Create a full website backup before you make any changes. If anything goes wrong, you still have a backup of the latest WordPress website. We like the free All-in-One WP Migration and Backup plugin for this.
  • Download the latest statistics of the website. It’s nice to remember how popular the website was.

Once we have a backup, we need to remove the following:

  • All dynamic functions: comments, forms, search, filtering.
  • Irrelevant content: Remove updates and news if you suspect that it won’t age well, or would be irrelevant to your audience in the future (e.g. that blog where you describe how fun the kick-off meeting was).
  • All personal data (from team members, PhD students, and PI’s): Since the website will not be maintained by anyone, you cannot edit personal or sensitive data anymore (well, technically you can still update the static website, but that defeats the point of archiving). There is nobody to answer GDPR requests for data removal, so remove all data or keep it limited to the basics. Discuss among your team whether you want to mention the names of the team and any acknowledgements. Personal data includes names, email addresses, social media links, photographs, IP addresses, biographical information with sensitive content such as political or religious beliefs. See more about this on the AP website.
  • Links that are likely to change or become irrelevant over time, such as links to old Google sign-up forms and event websites.

Places where you can host a website for free

Here are some hosting options that allow you to host a static website for free:

  • GitHub Pages: Free, reliable, and widely used. It’s great for open-source projects and guarantees longevity. Many researchers are already familiar with GitHub.
  • Netlify: Easy to use with drag-and-drop deployment, custom domain support, and advanced features in the free tier. Ideal for beginners.

We chose GitHub Pages since it’s well-known and likely to remain stable for the next decade, though Netlify might be more user-friendly for beginners.

In addition to hosting, we also need a plugin to convert WordPress to pure HTML. We found two good options: Simply Static and Staatic. We chose Simply Static because of its longer track record.

Since all of the websites we build are made with WordPress, we’ll focus on ways to archive WordPress websites. To extract other types of websites (created with a CMS), you can use HTTrack, although this tool requires more technical knowledge to configure properly.

Step-by-step guide to create a static website

1. Prepare your content: Clean up the website by removing dynamic features, sensitive data, and broken links. Make a backup and add the disclaimer to the footer of the website. I also checked the website content to see if everything works welll and is fully responsive.

2. Install Simply Static: In your WordPress dashboard, go to the plugins page, click Add new plugin, and search for Simply Static. Then activate the plugin.

3. Configure the Simply Static plugin: Go to the Settings > General page, and select “Relative Path” under “Replacing URLs”.

For the Path field there are two options:

  • When you’re planning to add a custom domain, leave the path empty (there will be a trailing slash / when it’s empty). This makes sure the links show correctly. (Jump to the steps about GitHub to see how to configure a custom domain).
  • If you want to use the default GitHub Pages domain name (e.g. https://theonlinescientist.github.io/SevenCountriesStudy/) then the path field should have the name of your GitHub repository. In our case that’s “/SevenCountriesStudy” (be aware that this is case-sensitive).

What’s a custom domain? A custom domain means that you can visit the website from the original domain name (in our case www.sevencountriesstudy.com). See the steps to configure this later in this article. This is great, because people can still find it under the same name, but also means it’s not entirely free. You’ll have to renew the domain name yearly (or buy 10 years in advance), and make sure someone has an account at a domain registrar. Alternatively, you can use the GitHub pages link, if you only need it to be archived.

Then check the “Force URL replacements” button. You can ignore the other features; the free version of the plugin worked well enough for us.This is what the settings and relative path should look like:

4. Generate the static site: Press the purple “Generate button” to generate the static version of your website. This takes a few minutes.

5. Download the ZIP file. After the export is finished, go to Tools > Activity Log to download the ZIP archive.

7. Login to GitHub. If you’re new to GitHub, sign up and create a username that works well for your purpose (Bunny1981 is a bit too embarrassing for a research project maybe). You can also create an account for your department.

8. Go to GitHub Pages. And follow their steps to create a page:

9. Choose between User or organization site and Project site. You get one site per GitHub account and organization, and unlimited project sites. For our purpose we chose Project site, since we archive multiple websites for our clients. We then choose to start from scratch, since we’re uploading a pre-made website.

10. Create a new repository. Click the “New” button to create a new repository. Give it the name of the website. This is usually the original domain name. In our case it’s SevenCountriesStudy.

11. We then use GitHub desktop to make it easy to upload your static files from the downloaded ZIP archive. Install GitHub Desktop to your computer and open it. It will automatically prompt you to sign in and connect your account.

Choose “Clone repository”. You can now choose a file location on your computer that acts as a local version of your online GitHub files.

To find the location on your computer you can click “Show in Explorer”:

13. Add the static files to GitHub: Find the static website files (from Simply Static) on your computer and copy them to the location that you just created with GitHub desktop.

14. If it’s the first time you copy files over, you first need to click Publish Branch. GitHub automatically notices when files are changed. You will see a list of files that were changed in the overview on the left. To copy these to the online GitHub environment, add a summary (title) of the changes you made (bottom-left), and click the “Commit to main” button.

15. Now select the main branch. Go to your GitHub account in your browser. Click on the Settings tab and scroll down to the GitHub Pages section. Then select the main branch source and click on the Save button.

16. Then in GitHub Desktop you can push the changes that you just committed to origin with “Push origin”.

17. Now, check your website! The name of the website will now be https://USERNAME.github.io/REPOSITORYNAME/ If you still need to configure the custom domain, it might not look right (no images, no style, and links don’t work), but that will change once you set the domain.

18. In our case the website was live at: https://theonlinescientist.github.io/SevenCountriesStudy/ (this is now overridden with the custom domain www.sevencountriesstudy.com)

Test your static site: Verify that the website looks good, and all pages and image work correctly.

Add a custom domain to your static website

Of course, at this point nobody knows the new GitHub URL. So you need to point your domain to the new location. We use versio.nl for domain names.

Custom domains allow you to serve your site from a domain other than your GitHub username. For the full documentation about this see the article: Learn more about configuring custom domains.

  1. Go to Settings > Pages (bottom of the left vertical menu) > Custom domain.
  2. Put in the domain name you want to use.
  3. Go to your domain registrar where you’ve bought the domain name.
  4. Renew the domain name for as long as you can. 10 years would be great (in academic terms this would be “forever”).
  5. Go to Domain name settings > DNS (or something similar, it depends on the registrar how this works).
  6. Add these A records (check the correct records on the GitHub documentation)
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

We also added a CNAME with the repository name as value. This might take a day or two for these settings to update, so be patient.

Disclaimer: These are the settings that I used while following other guides and documentation. But I’m not an expert on DNS settings. So check to see if this works, and if not, ask a website developer to help out.

Example of the DNS settings at your domain registrar that configure your custom domain

If everything runs smoothly, and you can see the website from the old domain name, you can remove the website from your previous hosting and delete the account.

This is a detailed documentation about my own process. However, yours might be a bit different, so play with it and try out different settings to make it work for you! Account for some costs if you want someone else to archive the website for you (it takes a couple of hours to do this right), or make sure you schedule some time for this yourself.

Enjoy eternity

So for your next research project, consider what you’re going to do when the project ends! Don’t let important information dissappear. It’s an easy way to make sure your research stays online and continues to benefit others without draining your budget.

About the Author: Liesbeth Smit

Liesbeth combines her knowledge of science communication, technology and design to explain difficult topics to a wide audience. You can use her practical tips immediately in your (poster) presentations to create a bigger impact. She developed dozens of websites, infographics and animated videos, and regularly gives workshops about design at The Online Scientist.

Search for more scicomm tips: