How to audit your current website before a redesign

A pre-redesign audit records what your current site earns before anything changes: URLs, traffic, links, speed, content and integrations. Eight steps.

By Sohail Hussain21 November 20265 min read

A pre-redesign audit answers one question: what does the current site do for the business that the new one must protect or do better? To answer it, collect every URL, attach search and analytics data to each one, record which pages other sites link to, crawl for technical problems, measure speed on the main templates, list every integration, and write a short summary. For a 50-page company site this is two to three days of work, and it decides most of what happens next.

It is the first stage of the website redesign process and the first deliverable on every website redesign and migration project we take on. Skip it and the redesign is built on guesses about what matters.

What should a pre-redesign audit cover?

AreaQuestion it answersWhere the data comes from
URLsWhat exists?Sitemap, Search Console, crawl, CMS
Search performanceWhich pages bring visitors from Google, for which queries?Search Console Performance report
ConversionsWhich pages lead to enquiries?Google Analytics or your analytics tool
LinksWhich pages do other sites link to?Search Console Links report
Technical healthWhat is broken, duplicated or blocked?A crawler
SpeedHow fast are the main templates on a phone?PageSpeed Insights, Core Web Vitals report
IntegrationsWhat does the site connect to?The CMS, the code, the team
OwnershipWho controls the domain, hosting and accounts?Registrar, host, the team

Everything goes into one spreadsheet with a row per URL. Work it through in the eight steps below.

How do you collect every URL and its data?

Step 1: Export every URL

Pull URLs from the XML sitemap, Search Console's Pages report, your analytics landing pages and a crawl of the live site. Paste them into one column and remove duplicates. Sites almost always turn out to have more URLs than anyone expected: old campaign pages, tag archives, PDFs, test pages that were never deleted.

Step 2: Attach search data

From the Search Console Performance report, export clicks and impressions by page for the last twelve months (the report keeps sixteen). Add the top query for each of your most visited pages. The interface exports up to 1,000 rows per table, which is enough for most company sites; larger sites need the Search Console API.

Sort by clicks. On most sites a small group of pages brings most of the traffic. Mark those clearly: the redesign must protect them above everything else.

Step 3: Attach analytics and conversions

From your analytics, add landing-page sessions and conversions (form submissions, calls, bookings) for each URL. Search data shows which pages attract visitors; this shows which ones turn them into enquiries. Some pages do one, some the other, and a few do both.

Search Console's Links report lists your top linked pages and the sites linking to them. Add a column for the number of linking sites. Any URL with links from other sites must survive the redesign or redirect to a close equivalent, even if it gets little traffic.

How do you find technical problems?

Step 5: Crawl for technical problems

Run a crawler over the whole site. Screaming Frog is the usual choice; its free version crawls up to 500 URLs as of October 2026. Record:

  • Broken internal links and pages returning 404.
  • Redirect chains and redirects pointing at the homepage.
  • Missing, duplicate or overlong titles and meta descriptions. The meta length checker checks individual ones.
  • Pages with a noindex tag or a canonical pointing elsewhere, and whether that is deliberate.
  • Thin pages with very little text.
  • Images without alt text.

Check robots.txt too. Paste it into the robots.txt tester and confirm that nothing important is blocked. The technical SEO checklist has the full list of checks if you want to go deeper.

Step 6: Measure speed on key templates

Run one page of each main template through PageSpeed Insights on mobile: the homepage, a service page, a blog post and the contact page. Record LCP, INP and CLS from the field data where it exists, and the lab score where it does not. These become the numbers the new site must beat, measured the same way after launch.

What else should the audit record?

Step 7: List integrations, features and accounts

Pages are half the site. List everything else it does and connects to:

  • Every form, where it sends, and who receives it.
  • Integrations: CRM, booking system, payment gateway, chat, newsletter, WhatsApp button.
  • Tracking: analytics, conversion tags, the events your reports depend on.
  • Features visitors use: search, filters, downloads, calculators, a client login.
  • Accounts: who holds the logins for the domain registrar, DNS, hosting, analytics and Search Console.

The accounts list matters more than it looks. A redesign stalls for weeks when nobody can find who controls the DNS. Who owns your website explains what you should hold in your own name.

What does the finished audit look like?

Step 8: Write the audit summary

The spreadsheet is the evidence. The summary is what people read. Keep it to one or two pages with five parts:

  1. The pages that matter. The top 20 by clicks, the pages that drive enquiries, and every page with backlinks.
  2. The problems. Technical issues from the crawl, ranked by how much traffic they affect.
  3. What must be kept. URLs, content, features and integrations the new site must carry over.
  4. The baseline. Monthly clicks, enquiries and Core Web Vitals for the key templates, with the date measured.
  5. Open questions. Pages nobody can explain, accounts nobody can access.

From here, what to keep from your old website turns the page list into decisions, and redirect mapping turns the decisions into a redirect plan.

What can you skip?

On a five-page site with little search traffic, most of this is unnecessary. Note the URLs, check the forms and accounts, and move on.

You can also skip the "SEO score" that many audit tools produce. A single number blends serious problems with trivial ones and tells you nothing about which pages earn money. The value of the audit is the per-page data, read by someone who knows the business. A clear spreadsheet and two honest pages beat a forty-page automated report every time.

Was this guide useful?

Questions

Frequently asked.

Can I audit my website without paid tools?

Yes. Search Console gives you URLs, clicks, queries and linked pages. Google Analytics gives landing pages and conversions. PageSpeed Insights measures speed. Screaming Frog's free version crawls up to 500 URLs, as of October 2026, which covers most company sites. Paid backlink tools add detail, but Search Console's Links report is enough to protect what matters.

How long does a website audit take?

For a company site of around 50 pages, two to three days, most of it spent matching data to URLs and writing the summary. A ten-page site takes a day. Sites with thousands of URLs take a week or more, mainly because the URL list and the redirect decisions grow with them.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.