Archive a website before you redesign it

What to save before the old site goes: a screenshot of every page, the URL list your redirects need, and the copy. And where the Wayback Machine falls short.

Dave WeatherallUpdated 6 min read

The short answer

Before the old site goes, save three things: a full-page screenshot of every page at desktop and mobile sizes, the full list of URLs, which your redirects depend on, and the page copy. Add Search Console's list of the pages that get traffic. SiteHaul, a Mac app, saves the first three in one run.

What to save

WhatWhy you'll want itWhere it comes from
Screenshots of every pageHow it looked, and the before for a case studyDesktop and mobile, one file per page
The full list of URLsEvery old URL needs a redirect, or it becomes a 404 that used to rankThe sitemap, grouped by type
The page copyText you would otherwise have to ask the client forOne Markdown file per page
Which pages get trafficTells you which redirects to check firstSearch Console, under Performance, then Pages

The first three come out of one SiteHaul run. The last is a quick export from Google Search Console, if you have access to the site's account.

Why it's worth ten minutes

When the new site launches, the old one is usually gone within the hour. The questions about it come later. The client wants to know what the old services page said. Whoever handles SEO needs every old URL pointed somewhere on the new site. You want a before and after for your portfolio. Each of those is easy with a copy of the old site and close to impossible without one.

What about the Wayback Machine?

It's free and worth checking, but it isn't a copy of your site. The Internet Archive saves pages when it happens to crawl them, so a smaller site may have a handful of pages from different months, some missing their images or styling. Save Page Now captures an address when you ask, and with a free account it can save the pages that address links to as well. For a long list there's a Google Sheets service that takes thousands of URLs. Either way the copies live in the Archive, in public, and none of it covers a staging site or anything behind a login.

How to do it with SiteHaul

  1. Paste the live site's address and press Fetch pages.
  2. Leave every group ticked. For an archive you want all of it, especially the pages nobody remembers exist.
  3. If you want the text as well, tick Save page content as Markdown, which comes with the license.
  4. Press Screenshot selected.
What you get
oldsite.com-2026-10-02/
  desktop/     every page at 1440px wide
  mobile/      every page at 390px wide
  copy/        one Markdown file per page
  urls.md      every URL, grouped by type

Everything lands in one dated folder, in Documents/SiteHaul unless you changed it. Zip it and file it with the project, and you can answer most questions about the old site from that folder without logging in to anything.

A SiteHaul run folder in Finder: desktop and copy folders, urls.md, manifest.json, and a Markdown file per page
A finished run: screenshots, the URL list, and each page's copy as Markdown.

Turning the URL list into redirects

urls.md groups the old addresses the same way the sitemap did: pages, posts, products, categories. Work down it and give each one a home on the new site.

  1. A page that moved gets a 301 redirect to its new address.
  2. A page that was cut gets a 301 to the closest match on the new site.
  3. Only send a page to the homepage if nothing else fits. Google treats a pile of redirects to the homepage much like missing pages, so the rankings those pages had don't carry over.

Start with the pages Search Console says get traffic. Those are the ones where a broken redirect costs something the day the new site goes live.

Before and after

Run SiteHaul again once the new site is live. A page that kept its address keeps its filename, so services-desktop.png in the old folder and the new one are the same page a few weeks apart. SiteHaul doesn't compare them for you, but two folders side by side, or dropped into Figma, are most of a case study layout already. Tall pages need splitting for Figma, which full-page screenshots in Figma without the blur explains.

If the new site is on a staging server behind a password, it can be captured before launch too. See screenshotting a staging site behind a login. For the basics of capturing from a sitemap, see how to screenshot every page in a sitemap, or read how SiteHaul compares to a browser extension.

Questions

How long does archiving a site take?

Usually a few minutes. Each page takes a few seconds at both sizes, and a 50 page site is typically done in under ten minutes. It runs on its own once started.

Does SiteHaul save the HTML?

No. It saves screenshots, the URL list and, with the license, each page's text as Markdown. If you need a working offline copy of the HTML, use a mirroring tool like HTTrack or wget. It pairs well with screenshots, which show how the pages actually looked.

What if the old site has no sitemap?

Paste the URLs instead. Open Advanced, choose Capture a list of URLs instead, and add one address per line.

Is the free plan enough to archive a site?

For a very small one. The free plan covers ten pages a month at both sizes. A larger site, or the Markdown copy, needs the $49 license, which is a one-time payment.

Try it on a site you know

10 pages a month free, which is enough to try it on a real site. No account, nothing uploaded.

Download for Mac

Apple silicon · macOS 12 or later · Notarized by Apple.

See everything SiteHaul does →