{"id":1263,"date":"2026-05-05T05:00:19","date_gmt":"2026-05-05T05:00:19","guid":{"rendered":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/?p=1263"},"modified":"2026-05-05T05:00:19","modified_gmt":"2026-05-05T05:00:19","slug":"pages-that-already-work-what-to-protect-during-a-redesign","status":"publish","type":"post","link":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/pages-that-already-work-what-to-protect-during-a-redesign\/","title":{"rendered":"Pages That Already Work: What to Protect During a Redesign"},"content":{"rendered":"\n<p>This is for the people responsible for approving a redesign before someone accidentally weakens the pages that already carry the business. A redesign should improve the site, but its first job is to protect pages that already earn search clicks, support lead generation, help sales conversations, or answer questions customers ask before they buy.<\/p>\n\n\n\n<p><strong>Short answer:<\/strong> A page that already works is a URL with evidence behind it: qualified search clicks, key events, backlinks, sales or support reuse, or a clear role in helping customers decide. Identify those pages before wireframes by checking analytics, search performance, links, and the URLs your team sends to real prospects.<\/p>\n\n\n\n<p><em>Last reviewed: April 23, 2026. The thresholds and documentation references below summarize current Google, web.dev, and W3C guidance; check the source pages before acting on audit results.<\/em><\/p>\n\n\n\n<p>The pages worth protecting are not always the prettiest pages. A plain service page with a clear answer, a dated but useful comparison article, or an old FAQ page can carry more business value than a polished homepage hero. Treat those pages like working equipment: inspect them before replacing parts.<\/p>\n\n\n\n<h2 class='wp-block-heading'>Find the pages with real business value<\/h2>\n\n\n\n<p>Start with the tools that show real behavior, not opinions from the redesign meeting. In GA4, the Landing page report shows the first page a visitor sees when they arrive on the site.<sup>[1]<\/sup> Key events can mark form submissions, booking clicks, and other important actions.<sup>[2]<\/sup> In Search Console, the Performance report&#8217;s Pages tab shows which URLs get Google Search clicks, impressions, and CTR.<sup>[3]<\/sup> Those views answer different questions, so use them together.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Organic landing pages:<\/strong> Export URLs from the search performance Pages tab and keep any page that gets qualified clicks for non-trivial queries, even if it is not in the main navigation.<\/li>\n<li><strong>Pages tied to key events:<\/strong> Keep pages that appear before or during lead form submissions, sign-up starts, calls, quote requests, bookings, or other events your team has marked as important.<\/li>\n<li><strong>Pages with links:<\/strong> Check top externally linked pages and top internally linked pages before deleting, merging, or renaming URLs.<sup>[4]<\/sup><\/li>\n<li><strong>Sales and support pages:<\/strong> Ask sales and support which URLs they paste into email threads, proposals, onboarding notes, or help replies. A page can be valuable because it shortens a customer conversation, not only because it ranks.<\/li>\n<\/ul>\n\n\n\n<p>Put the protected URLs in one sheet before design starts. For each URL, record the current title tag, H1, main sections, primary CTA, internal links, canonical URL, structured data type if present, and the queries or key events that justify protection. If a page cannot be tied to search demand, links, revenue, support load, or a customer decision, it can still be improved, but it should not outrank a proven page in the redesign queue.<\/p>\n\n\n\n<h2 class='wp-block-heading'>Protect the elements that create performance<\/h2>\n\n\n\n<p>A working page may perform because several small parts line up: the title answers the query, the H1 matches the promise, the body includes a useful comparison table, the CTA appears after the proof, the schema matches visible content, and the page loads fast enough on mobile. If the redesign keeps the URL but removes those parts, the page can look better and still perform worse.<\/p>\n\n\n\n<h3 class='wp-block-heading'>Keep the crawlable promise intact<\/h3>\n\n\n\n<p>Use Google&#8217;s Search Essentials as the eligibility floor: pages need to be accessible to Google, linked in ways crawlers can follow, and built without spam tactics.<sup>[5]<\/sup> That does not mean a page will rank. It means the redesign should not break crawlability, indexability, or content clarity while chasing a new visual system.<\/p>\n\n\n\n<p>Mini case study: on one local service redesign, an old pricing FAQ looked too plain for the new templates and was almost folded into a generic service page. The audit showed search clicks for cost and eligibility questions, sales staff used the URL in follow-up emails, and the quote CTA sat directly under a comparison table. The redesign kept the URL, H1, table, FAQ answers, internal links, and CTA order, then improved typography and spacing. The page kept doing its job because the team changed presentation, not intent.<\/p>\n\n\n\n<h3 class='wp-block-heading'>Do not trade speed for polish<\/h3>\n\n\n\n<p>For performance, protect the real user experience. web.dev&#8217;s Web Vitals documentation defines good Core Web Vitals targets at the 75th percentile as Largest Contentful Paint at 2.5 seconds or less, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less, measured across mobile and desktop.<sup>[6]<\/sup> INP replaced First Input Delay as a Core Web Vital on March 12, 2024, so an old audit that only mentions FID is stale for redesign decisions.<sup>[7]<\/sup><\/p>\n\n\n\n<p>Use PageSpeed Insights to separate lab findings from field data.<sup>[8]<\/sup> When it has enough data, the field view is based on Chrome User Experience Report data from the previous 28-day collection period; the lab view comes from Lighthouse.<sup>[9]<\/sup> A staging page with a good Lighthouse run is useful, but it is not proof that real users on real devices will have the same experience after launch.<\/p>\n\n\n\n<p>The design team should also protect page weight. The 2025 HTTP Archive Web Almanac reports that, in July 2025, the median home page was 2.86 MB on desktop and 2.56 MB on mobile, with median home-page image weight of 1,058 KB on desktop and 911 KB on mobile.<sup>[10]<\/sup> That matters because new hero images, sliders, font files, tracking tags, and animation libraries often get added to the exact pages that already win traffic.<\/p>\n\n\n\n<h3 class='wp-block-heading'>Keep schema and accessibility tied to the page<\/h3>\n\n\n\n<p>For structured data, preserve markup only when it still describes what visitors can see. Google&#8217;s structured data policies require structured data to represent the page content, and Schema.org provides the vocabulary many sites use.<sup>[11]<\/sup><sup>[12]<\/sup> Do not carry over FAQ, Product, Review, LocalBusiness, or Article markup if the redesigned page removes the visible content that supported it.<\/p>\n\n\n\n<p>For accessibility, do not let a visual refresh remove functional cues. The W3C WCAG 2.2 guidelines define conformance levels A, AA, and AAA.<sup>[13]<\/sup> For most small-business sites, WCAG 2.2 AA is the practical target unless a contract, industry rule, or legal review sets another requirement. Preserve visible labels, keyboard access, meaningful link text, alt text for informative images, and color contrast checks on redesigned templates.<\/p>\n\n\n\n<h2 class='wp-block-heading'>Avoid unnecessary URL changes<\/h2>\n\n\n\n<p>Changing URLs during a redesign creates risk because Google, users, bookmarks, backlinks, internal links, email campaigns, QR codes, and sales decks may all point to the old location. Sometimes a URL change is necessary, but it should be a documented decision, not a side effect of changing WordPress page parents or rebuilding templates.<\/p>\n\n\n\n<p>Google treats permanent redirects such as HTTP 301 and 308 as strong signals that the target URL should become canonical, while temporary redirects such as 302 and 307 are weaker signals.<sup>[14]<\/sup> Its site move guidance also says to prepare a URL mapping, update internal links, update canonical annotations, and use sitemaps with the new URLs when addresses change.<sup>[15]<\/sup><\/p>\n\n\n\n<p>The same rule applies to old WordPress parameter URLs such as <code>?p=1263<\/code>. If a public page is still live at that kind of address, move it to a descriptive slug, 301 the old URL to the final page, and update internal links so readers and search results see the cleaner address.<\/p>\n\n\n\n<figure class='wp-block-table'><table><thead><tr><th>Redesign situation<\/th><th>Safer decision<\/th><th>Why it protects performance<\/th><\/tr><\/thead><tbody><tr><td>Same topic, same audience, same search intent<\/td><td>Keep the URL and improve the page in place<\/td><td>The page keeps its existing search, link, and user signals while the design improves clarity<\/td><\/tr><tr><td>Same topic, but the old slug must change<\/td><td>Map the old URL to the final new URL with a permanent 301 or 308 redirect<\/td><td>Permanent redirects send a stronger canonical signal when content has moved<\/td><\/tr><tr><td>Two weak pages are being consolidated into one stronger page<\/td><td>Choose the best final URL, merge the useful content, and redirect retired URLs to the consolidated page<\/td><td>Users and crawlers land on a relevant replacement instead of a thin or missing page<\/td><\/tr><tr><td>The new page serves a different intent<\/td><td>Do not redirect the old URL to an irrelevant page just to avoid a 404<\/td><td>Irrelevant redirects confuse users and can be treated like soft 404 problems<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Before launch, crawl the staging site with a crawler such as Screaming Frog SEO Spider and look for changed URLs, missing titles, duplicate H1s, noindex tags, broken internal links, unexpected canonicals, and redirects that point to another redirected URL.<sup>[16]<\/sup> After launch, use URL Inspection on important pages to check Google&#8217;s indexed view, live test result, and selected canonical.<sup>[17]<\/sup><\/p>\n\n\n\n<h2 class='wp-block-heading'>Use redesign as a preservation exercise<\/h2>\n\n\n\n<p>A useful redesign brief should name what must be preserved before it names what must look different. Use this mini-workflow before approving wireframes, copy decks, or WordPress template changes.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Export candidate protected URLs from analytics landing pages, key events, search performance pages, link reports, and sales or support notes.<\/li>\n<li>For each URL, copy the current title tag, meta description, H1, H2s, primary CTA, proof sections, comparison tables, schema type, canonical URL, and top internal links into a preservation sheet.<\/li>\n<li>Run the current URL through PageSpeed Insights on mobile and desktop, then record LCP, INP, CLS, and whether the result is field data or lab data.<\/li>\n<li>Enter representative URLs at <a href='https:\/\/websiteadvisor.deepdigitalventures.com\/'>Website Advisor<\/a> when you need a page-level review of issues the data tools do not explain: unclear answer depth, weak proof, confusing CTA order, missing trust cues, or redesign risks that require human judgment.<\/li>\n<li>Mark each page as protect, improve carefully, consolidate, redirect, or retire. Do this before the design team rebuilds navigation or page templates.<\/li>\n<li>When copy changes, keep the search intent and answer depth that made the page useful. Shorter is not better if the original page ranked because it answered comparison, pricing, eligibility, setup, or troubleshooting questions.<\/li>\n<li>When layouts change, keep the conversion path. A lead page that currently puts proof, objections, and CTA in a working order should not be replaced with a large image, vague headline, and hidden form.<\/li>\n<li>After launch, compare the protected set against the baseline sheet. Investigate drops by URL, not only by whole-site traffic.<\/li>\n<\/ol>\n\n\n\n<p>This is where redesign work becomes more disciplined. The team is not trying to freeze old pages forever. It is separating cosmetic debt from business value. A dated layout can be replaced. A useful answer, a crawlable URL, a proven CTA, and a fast mobile experience should be carried forward unless there is a specific reason to change them.<\/p>\n\n\n\n<h2 class='wp-block-heading'>The takeaway<\/h2>\n\n\n\n<p>Before a redesign, protect the pages that already work by URL, intent, content depth, internal links, schema, accessibility, and Core Web Vitals. If the same page is still serving the same audience and purpose, keep the address. If it must change, map it to a relevant final destination with a permanent redirect, update the links and canonical annotations, and verify the result after launch.<\/p>\n\n\n\n<p>The practical rule is simple: no protected page should launch with less useful content, fewer crawlable paths, weaker schema accuracy, slower mobile performance, or a harder conversion path than it had before the redesign.<\/p>\n\n\n\n<h2 class='wp-block-heading'>FAQ<\/h2>\n\n\n\n<p><strong>Should we avoid changing copy on pages that rank?<\/strong><br> No. Change weak copy, stale examples, and unclear calls to action. Keep the search intent, answer depth, title promise, internal links, and visible evidence that made the page useful.<\/p>\n\n\n\n<p><strong>Is a URL change always bad?<\/strong><br> No. It can be fine when the old URL maps to a relevant new URL, the move uses the right permanent redirect, internal links point to the new address, and the canonical and sitemap agree with the new structure.<\/p>\n\n\n\n<p><strong>What if analytics and search data disagree?<\/strong><br> Keep investigating. Analytics describes site behavior after visitors arrive, while search data describes visibility and clicks before they do. A page can be valuable in one system and quiet in the other.<\/p>\n\n\n\n<p><strong>Do we need to keep the old design exactly?<\/strong><br> No. Preserve the working parts, not the old pixels. The redesigned page can look much better as long as it keeps the useful content, clear CTA, crawlable links, accessible controls, and performance targets.<\/p>\n\n\n\n<h2 class='wp-block-heading'>Sources<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Google Analytics Help, Landing page report: https:\/\/support.google.com\/analytics\/answer\/14292358<\/li>\n<li>Google Analytics Help, key events: https:\/\/support.google.com\/analytics\/answer\/9267568<\/li>\n<li>Google Search Console Help, Performance report: https:\/\/support.google.com\/webmasters\/answer\/7576553<\/li>\n<li>Google Search Console Help, Links report: https:\/\/support.google.com\/webmasters\/answer\/9049606<\/li>\n<li>Google Search Central, Search Essentials: https:\/\/developers.google.com\/search\/docs\/essentials<\/li>\n<li>web.dev, Web Vitals documentation: https:\/\/web.dev\/articles\/vitals<\/li>\n<li>web.dev, INP became a Core Web Vital on March 12, 2024: https:\/\/web.dev\/blog\/inp-cwv-march-12<\/li>\n<li>PageSpeed Insights tool: https:\/\/pagespeed.web.dev\/<\/li>\n<li>Google Developers, PageSpeed Insights documentation: https:\/\/developers.google.com\/speed\/docs\/insights\/v5\/about<\/li>\n<li>HTTP Archive Web Almanac 2025, page weight chapter: https:\/\/almanac.httparchive.org\/en\/2025\/page-weight<\/li>\n<li>Google Search Central, structured data policies: https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/sd-policies<\/li>\n<li>Schema.org structured data vocabulary: https:\/\/schema.org\/<\/li>\n<li>W3C, WCAG 2.2 guidelines: https:\/\/www.w3.org\/TR\/WCAG22\/<\/li>\n<li>Google Search Central, redirects and Google Search: https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/301-redirects<\/li>\n<li>Google Search Central, site moves with URL changes: https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/site-move-with-url-changes<\/li>\n<li>Screaming Frog SEO Spider user guide: https:\/\/www.screamingfrog.co.uk\/seo-spider\/user-guide\/<\/li>\n<li>Google Search Console Help, URL Inspection tool: https:\/\/support.google.com\/webmasters\/answer\/9012289<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Before redesigning a website, identify pages that already perform and protect their rankings, conversion paths, copy, and internal links.<\/p>\n","protected":false},"author":3,"featured_media":1850,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"Pages That Already Work: Redesign Protection Guide","_seopress_titles_desc":"Before a website redesign, identify the pages already earning search, leads, links, or sales support, then preserve the elements that make them work.","_seopress_robots_index":"","footnotes":""},"categories":[16],"tags":[],"class_list":["post-1263","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-redesign"],"_links":{"self":[{"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/posts\/1263","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/comments?post=1263"}],"version-history":[{"count":6,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/posts\/1263\/revisions"}],"predecessor-version":[{"id":2069,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/posts\/1263\/revisions\/2069"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/media\/1850"}],"wp:attachment":[{"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/media?parent=1263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/categories?post=1263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/websiteadvisor.deepdigitalventures.com\/blog\/wp-json\/wp\/v2\/tags?post=1263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}