After a redesign, the new page always looks better in the meeting room. The real question is what changed underneath: which words disappeared, which headings moved, where the links now point, who approved the swap, when the old version was last working well, why a key section was shortened, and how you can prove any of it without asking a developer to dig through code.
Comparing two versions of a page sounds technical, but most of the work is careful observation. You need the old version, the new version, and a simple method for recording differences in content, structure, and behaviour. Site owners, marketers, and small teams do this every time a template changes, a homepage is refreshed, or a product page is rewritten under deadline pressure.
Redesigns rarely change only colours and fonts. A new template can drop a paragraph that explained your main offer, move a call to action below three screens of images, or rename headings that search engines relied on to understand the page. Traffic and enquiries often dip weeks later, and by then nobody remembers exactly what the old page said.
Start by saving the old version properly. If the redesign is already live, look for a staging copy, a cached copy, an archived snapshot, or the document the copy was written in. Take full-page screenshots on desktop and mobile, and copy the old text into a plain document. Record the date you captured it, because an old screenshot from the wrong month creates confusion later.
If you need to share the sheet and screenshots with a freelancer or your team, tidy attachments and clear subject lines help more than people expect. Even basic guidance on professional sending, such as the notes in Google Mail support, reduces the chance your comparison file lands in spam and the fixes stall for a week.
With both versions captured, compare the skeleton first. Read only the headings, in order, from each version. A good page tells a coherent story through its headings alone. If the old page promised a clear benefit in its main heading and the new one offers a vague slogan, that is a real loss, even if the design looks cleaner.
Next, compare depth. The Page Depth Analyzer can help you think about how far important content and pages sit from the surface, and the same idea applies inside a single page. Count how far a reader must scroll to reach prices, proof, answers, and the main action on each version. Content that moved far down the page often performs as if it were removed.
Then check every link. Click each one on the new page and confirm the destination still makes sense. Redesigns often rebuild menus and buttons from scratch, and a familiar label can quietly start pointing at a generic page. List any changed destinations in your sheet, and pay special attention to links that supported your best-converting journeys.
More comparison checklists and publishing guides are collected on the Seovaro blog, which is a useful place to build a repeat routine if your team redesigns pages often. The routine matters more than any single tool, because pages change constantly in small ways, not just during big relaunches.
Not every difference is a problem. Some old copy deserved to go, and some new sections will outperform the originals. Your comparison sheet lets you sort differences into three groups: restore immediately, keep and monitor, or test properly. Restore anything that removed essential information, broke a link journey, or weakened the main promise of the page.
For the keep-and-monitor group, write down what you expect to happen and when you will check. Look at visits, scroll behaviour if you have it, clicks on the main action, and enquiries or sales from the page. Compare the same period length before and after the redesign, and be honest about outside factors such as seasonality or a campaign running at the same time.
Redesign coming up, or one just launched? Try the Page Depth Analyzer on your most important page, build the simple comparison sheet described above, and restore the first weakened section you find before you debate colours for another week.
Check staging or preview copies first, then web archives, cached search copies, backups, and the original copy documents or design files your team approved. Even a dated screenshot or a PDF proof is better than memory, because it lets you quote the old wording exactly in your comparison.
Start with the pages that earn traffic, enquiries, or sales, plus the homepage and any page whose template changed. Low-value pages can wait. A careful comparison of your ten most important pages catches nearly all of the damage a redesign typically causes.
Check that the new page still says what the old page promised, in the same order of importance, with working links to the same key destinations. If the main heading, the core explanation, and the main action all survived intact, most other differences are cosmetic and safe to judge over time.
On launch day if you can, and always within the first week. Early comparison catches missing content while the old version is still easy to recover and the team still remembers the project. Waiting until traffic drops makes the same work slower, more political, and more expensive.