Last updated: November 02, 2026
Quick Answer: track rankings during a site redesign by freezing a baseline before anything changes, mapping every old URL to its replacement, and comparing the same keyword set before and after launch in the same rank tracker and Google Search Console. The goal is not to stare at daily noise; it is to preserve a clean before-and-after line so you can tell whether a redesign changed visibility or just changed tracking conditions.
What to capture before the redesign starts
Start by saving a pre-change baseline for How to Track Rankings During a Site Redesign Without Losing Baselines that you can recreate 30, 60, or 90 days later. Without that snapshot, a redesign turns into guesswork because you lose the old URL structure, the old template set, and the old rankings for the exact pages that earned them.
Use a rank tracker that can export CSV or XLSX data, and capture the same keyword set you will use after launch. Include branded terms, non-branded terms, and page-level terms tied to important URLs. A clean baseline usually includes:
- target keyword
- current URL ranking for that keyword
- current position
- search engine
- location or device setting
- date of capture
Also save the current sitemap, a crawl export, and a list of top landing pages from Google Search Console. That gives you three reference points: what you rank for, which URLs carry that ranking, and what search engine sees as the current site structure.
The part most teams skip is page-to-keyword mapping. If one page currently ranks for 12 queries, write that down before the redesign. If the page later splits into two new URLs, you need the original map to know where the ranking should have gone. A redesign without that map makes every change look like a ranking loss.
If the site has separate templates, save baseline screenshots of title tags, H1s, canonicals, and indexability for the pages that matter most. A simple spreadsheet is enough. The point is not beauty; it is comparison. A baseline that can be searched and sorted beats a polished document nobody updates.
How to set up tracking so the redesign does not break your baseline
Set the tracker up so URLs can change without erasing the record. A cautious setup is a keyword list tied to the query, not just to one URL. That way, when a page moves, the ranking history stays attached to the keyword even if the landing page changes.
First, lock the tracking settings:
- Pick one search engine, one country, and one device profile for the baseline. If you track desktop in the U.S. before the redesign, keep that exact setup afterward. The result you want is a line chart that compares like with like.
- Export the keyword list and keep the same list frozen through launch week. If a keyword is removed or replaced midstream, the comparison becomes muddy.
- Save the current landing URL for each keyword inside the tracker or spreadsheet. The result is a direct before-and-after link between query and page.
- Tag high-priority keywords by page type, such as product, category, service, or article. That makes it easier to spot whether one template lost visibility across many URLs.
- Turn on notes or annotations for redesign milestones. Mark the audit date, staging crawl date, redirect freeze, launch date, and post-launch crawl date.
Google Search Console matters here because it keeps your baseline tied to actual search performance, not only tracker output. Use the Performance report to export queries and pages before the redesign begins. Then repeat the same export after launch and compare the page dimension, not just the query dimension. That is where URL changes show up.
The trade-off is simple: a fixed tracking setup is cleaner, but it is slower to adapt if the site strategy changes during the project. If the keyword set changes every week, you will not know whether the redesign shifted rankings or the target changed.
For a broader workflow, this belongs inside a rank tracking strategy and workflow, not as a one-off cleanup task.
What to do during the redesign to preserve ranking baselines
Preserve the baseline by checking the site at migration checkpoints, not by waiting until launch day. The useful checkpoints are usually pre-staging, pre-redirect, launch, and 7 to 14 days after launch, because that is when URL mismatches and indexing problems first appear.
Because the page map already exists, use this order:
- Crawl the staging site and export the URL list. Compare it with the pre-redesign URL list. The result should be a one-to-one or clearly documented many-to-one mapping, not a surprise set of new paths.
- Build the redirect map for every old URL that has rankings, links, or traffic. Each old URL should point to the most relevant new URL with a 301 redirect, not the homepage. When this works, the old page returns one hop to its replacement.
- Check titles, H1s, canonicals, and internal links on the redesigned templates. You should see the same topical intent carried forward, even if the layout changes.
- Freeze the redirect map before launch. Late changes are where baselines get lost because the old URL no longer has a stable destination.
- Launch and crawl the live site within 24 to 72 hours. The crawl should show the old URLs resolving as expected, the new URLs indexable, and the canonical tags pointing where they should.
- Compare Google Search Console coverage and Performance exports against the baseline. The pages report should show the new URLs appearing in place of the old ones where redirects were applied correctly.
The main cost of skipping checkpoints is time. A missing redirect can make ranking data look like it disappeared when it actually moved to a different URL. If you catch the problem early, the baseline survives and the searcher still sees continuity.
Do not use analytics alone as proof that rankings are fine. Traffic can hold steady while specific queries fall, especially on pages that still attract brand demand. A rank tracker shows the query-level change; Search Console shows whether the site is gaining or losing visibility at the URL level.
How do I compare rankings before and after a redesign?
Compare rankings by query, device, location, and landing URL in the same date window on both sides of launch. A careful comparison is the same keyword set, the same location/device setting, and the same tracker on both sides of launch. A rank tracker may show the keyword stayed at position 8, while Google Search Console may show that the ranking page changed from an old URL to a new one.
Use a 7-day or 28-day comparison window depending on the site’s volume. Short windows are noisy on smaller sites. Longer windows smooth out daily fluctuation but can hide the launch effect. The useful method is to compare:
- pre-launch average position
- post-launch average position
- old URL ranking history
- new URL ranking history
- clicks and impressions for the same query set
If the redesign changed only the template and not the content, look for stable query coverage and a changed URL path. If the content changed, expect more movement and compare by intent group rather than by one page alone. A page that lost rankings because it no longer matches the old query mix is not the same as a page that lost rankings because the redirect failed.
A good comparison shows one of three outcomes:
- rankings moved cleanly from old URLs to new URLs
- rankings stayed steady with no visible URL churn
- rankings fell only on pages with changed content, missing redirects, or broken internal links
What not to do: compare “before” from one tracker and “after” from another. Different crawl methods, different location settings, or different SERP features can make the baseline unusable. Stick to one rank tracker and one GSC property.
This is also where the obvious alternative falls short. A spreadsheet of URLs alone can tell you what changed, but it cannot show whether the change affected search demand. The tracker fills that gap.
Which signals show the redesign is still safe?
The redesign is still safe when the old URLs resolve correctly, the new URLs are indexed, and rankings move only as much as the content changed. That safety check is less about one big score and more about a cluster of signals lining up.
Watch these signals during the first 2 to 4 weeks:
- 301 redirects from old URLs to the right new URLs
- canonical tags on the new URLs
- crawlable internal links to the new URLs
- indexed pages count in Google Search Console
- query overlap between pre- and post-launch exports
- ranking movement on the exact keywords in the baseline
A healthy redesign often shows some temporary volatility. That is normal. What is not normal is a sudden drop across many keywords with no matching redirect or indexation issue. If the old URL disappears from the tracker but the new URL never appears, the baseline has been broken somewhere in the handoff.
One practical guardrail is to keep the top 20 or top 50 ranking URLs under manual review for at least 14 days after launch. That small list catches the pages most likely to lose value. Another is to annotate every major edit in the tracker so you can connect a ranking shift to a concrete change, not a vague launch period.
The honest limitation: rank tracking cannot prove causation on its own. A dip after redesign may come from content edits, redirect errors, internal linking changes, crawl budget issues, or unrelated market movement. That is why the baseline must be paired with GSC exports and crawl data. One source is never enough.
Common mistakes that erase baselines
The most common mistake is changing the tracked URL list at the same time as the redesign. That destroys the comparison because the “before” and “after” reports no longer measure the same pages. The fix is simple: freeze the keyword set and log URL changes separately.
A second mistake is relying on the homepage redirect for everything. That costs rankings because Google still needs page-level relevance. Redirect old category pages to the nearest matching category or service page, not to a generic front door.
A third mistake is tracking only the final live URL and ignoring the old one. That hides migration gaps. Keep old URLs in the redirect map and keep their history in the tracker until the new URL has taken over.
A fourth mistake is forgetting to annotate launch dates, staging pushes, and redirect updates. Without those notes, the chart looks noisy and the team starts guessing. A 24-hour or 48-hour annotation can explain a lot more than a month of vague trend lines.
According to Google Search Console Help and Google’s Search Essentials documentation, Search Console and a rank tracker serve different roles, so it is safer to treat them as complementary rather than interchangeable; if the handoff is unclear, consult a qualified SEO professional and review the sources before making changes. The tracker is your position snapshot. Search Console is your actual performance record. Use both, or the baseline will tell only half the story. For official guidance, see Google Search Console Help and Google Search Essentials.
What to hand off before launch so the baseline survives
Hand off a single migration sheet before launch so no one has to reconstruct the plan from memory. The sheet should include the old URL, the new URL, the redirect type, the page owner, the primary keyword group, and the launch status. A simple 5-column or 6-column sheet is usually enough.
Also hand off a checkpoint list with dates:
- baseline capture
- staging crawl
- redirect freeze
- launch
- 24-hour validation
- 7-day review
- 14-day review
That timeline keeps the team from arguing about whether a ranking change is “too early” to matter. If the redirect map is final on Friday and launch is Monday, the 24-hour crawl should show whether the baseline survived the handoff.
The strongest handoff is one that names responsibility. Someone owns the redirects, someone owns the tracker export, and someone owns the Search Console comparison. If those jobs are split across three tools with no owner, the baseline becomes a shared assumption, which is the same thing as losing it.
Key takeaways
- Freeze a baseline before redesign work starts, not after templates are already changing.
- Track keywords, URLs, and settings together so pre- and post-launch data stay comparable.
- Use redirects, crawl data, and Search Console together; one tool cannot protect the baseline by itself.
- Keep launch notes and migration checkpoints so ranking changes can be traced to a real event.
- A careful comparison uses the same keyword set, the same location/device setting, and the same tracker on both sides of launch.
When should I start tracking before a redesign?
Start before any URL, template, or redirect work begins. A 30-day baseline is useful, and a 60- or 90-day baseline is better if the site has seasonal demand or uneven traffic. The key is to capture the current ranking set, URL map, and Google Search Console exports while the site is still stable.
How do I compare rankings before and after a redesign?
Compare the same keywords in the same rank tracker settings and tie them back to the old and new URLs. Use Google Search Console to confirm whether rankings moved to replacement pages or disappeared. A 7-day or 28-day comparison window works well, depending on how much search volume the site gets.
What should I monitor during a redesign?
Monitor redirects, indexability, canonical tags, internal links, ranking changes on the tracked keyword set, and page-level data in Google Search Console. The first 24 to 72 hours after launch are the most useful for catching broken handoffs. After that, keep reviewing the highest-value URLs for at least 14 days.
Drafted with AI; not yet reviewed by a person.