Acting on Competitor Page Redesigns
Competitor Watch has flagged that a rival has substantially changed one of its important pages, such as a home page, a pricing page or a main service page. A redesign looks dramatic, but most of what changes is visual, and visual changes rarely move search rankings on their own.
What can matter is the less obvious detail: headings and copy that were rewritten, content that was removed, calls to action that moved, and speed that got better or worse. This guide shows how to line up the old and new versions, separate cosmetic changes from meaningful ones, watch what happens to their rankings, and test any idea worth borrowing on your own site before adopting it.
- Why a redesign alert deserves a calm look
- Lining up the old and new versions
- Changes that matter and changes that do not
- Checking speed and page experience
- Reading the ranking effect without fooling yourself
- The fix, step by step
- Testing an idea properly on your own site
- Staying ready for the next redesign
- Questions and answers
Why a redesign alert deserves a calm look
When a competitor refreshes a page that competes with yours, it is natural to assume they know something you do not. Sometimes they do: they may have run customer research or tests. Just as often a redesign follows a new brand guideline, a new agency, or a CMS change, and its effect on enquiries is unknown even to them.
Redesigns also go wrong. Pages lose sections of text that were earning search traffic, headings get replaced with slogans, useful internal links disappear from the navigation, and heavy imagery or animation slows the page down. Search engines rank the content and experience of the page, not its look, so a smart-looking redesign can lose ground while a plainer page holds steady.
That gives you two reasons to pay attention. A well-executed redesign might contain ideas you can test. A poorly executed one might open a gap you can fill. Neither is a reason to redesign your own page in a hurry.
Lining up the old and new versions
You need a reliable picture of the page before the change. There are a few places to get one:
- Your own records. If you took screenshots or saved notes when you first added the rival to Competitor Watch, those are the most trustworthy baseline.
- The Internet Archive's Wayback Machine. Enter the page address at web.archive.org and pick a capture from before the alert date. Not every page is captured, and captures can be missing images or styles, but the text and headings usually survive.
- Search result snippets. The title and description shown in search results sometimes lag behind a change for a while, which can hint at what the old title tag was.
Once you have both versions, compare them section by section rather than as a whole. It is easy to be distracted by new photography and miss that a whole block of explanatory text has gone. A simple two-column table in a document, old on the left and new on the right, works well.
For the text itself, copying the visible text of each version into a plain text file and comparing them with a diff tool shows every change in wording. On most computers you can do this with a free text comparison tool, or from a terminal:
diff --side-by-side --width=160 old-pricing-page.txt new-pricing-page.txt | lessChanges that matter and changes that do not
| Change | Likely to affect search? | Likely to affect conversions? | What to note |
|---|---|---|---|
| Title tag or H1 rewritten | Often | Slightly | Which query they now seem to target, and whether it overlaps with yours |
| Body text removed or cut down | Often | Sometimes | Which questions the page no longer answers |
| New sections added (FAQ, comparison, case study) | Sometimes | Sometimes | What customer question each new section answers |
| Calls to action moved or reworded | Rarely | Often | Where the main button sits, what it says, what it asks for |
| Trust signals added (reviews, accreditations, guarantees) | Rarely directly | Often | Which proof they now lead with |
| Form shortened or lengthened | No | Often | Number of fields and which ones are required |
| Navigation and internal links changed | Sometimes | Sometimes | Pages that gained or lost prominent links |
| New colours, fonts, photography | Rarely | Unknown | Usually nothing worth acting on |
| Heavier scripts, video, animation | Possibly, via speed | Possibly | Loading and responsiveness figures |
Pay particular attention to the second row. When a rival's redesign removes content that used to answer common questions, their page may slip for the searches that content served. If your page answers those questions well, you may gain without doing anything. If it does not, that is a precise and modest improvement to make.
Checking speed and page experience
Redesigns frequently change how fast a page loads and responds. Run the rival's page through PageSpeed Insights. The top section shows field data from the Chrome User Experience Report where Google has enough real-user visits; this reflects a rolling 28-day period, so it may still include the old design for a few weeks. The lower section is a lab test of the page as it is now.
The field thresholds Google uses for Core Web Vitals, assessed at the 75th percentile of visits, are:
- Largest Contentful Paint (LCP): 2.5 seconds or less is good.
- Interaction to Next Paint (INP): 200 milliseconds or less is good. INP replaced First Input Delay in March 2024.
- Cumulative Layout Shift (CLS): 0.1 or less is good.
Run the same test on your own equivalent page. If the rival moved from good to poor, their redesign has created a small disadvantage for them, though page experience is one signal among many and rarely decides rankings by itself. If they moved from poor to good while you are poor, that is a fair prompt to look at your own performance for your visitors' sake.
In browser developer tools, the Network panel shows how many requests and how much data the new page loads. A jump from a few hundred kilobytes to several megabytes, often from video backgrounds or large unoptimised images, usually shows up in LCP on mobile.
Reading the ranking effect without fooling yourself
The honest answer to "did the redesign help them?" is often "not yet known". Search engines need to recrawl and re-evaluate the page, and rankings move for other reasons at the same time. A sensible approach:
- Pick three to five queries where both your page and theirs appear.
- Record positions on the day of the alert, then weekly for four to six weeks, checking from the same location and device type each time.
- Note any confirmed Google update during the period, because broad movement across many sites is more likely to come from that than from one redesign.
- Watch your own page in Search Console for the same queries. If your impressions rise as theirs fall, the redesign may have cost them.
Only after several consistent readings should you conclude the redesign helped or hurt them. A single week's movement is noise.
The fix, step by step
Step 1
Capture the before and after
Save full-page screenshots of the new design on desktop and mobile, and copy its visible text into a plain text file. Find the old version from your own earlier notes or from a Wayback Machine capture dated before the alert, and save its text the same way. Visit again a day later from another browser to confirm the new design is live for everyone rather than a split test shown to some visitors.
Step 2
List what changed below the surface
Compare the two versions section by section and list changes to the title tag, H1 and subheadings, body text added or removed, calls to action, forms, trust signals such as reviews and guarantees, and internal links in the navigation. Ignore colours, fonts and photography unless they change what the page says. Note which customer questions the old page answered that the new one no longer does, and the reverse.
Step 3
Check speed and page experience
Run the rival page and your own equivalent page through PageSpeed Insights and record LCP, INP and CLS from the field data where available, remembering that it covers the last 28 days and may blend old and new designs. Look at the lab results and the Network panel in developer tools for the total page weight. Write down whether the redesign made their page faster, slower or roughly the same as yours.
Step 4
Watch their rankings for a few weeks
Choose three to five queries where both pages appear and record positions weekly for four to six weeks from the same location and device. Check your own Search Console figures for the same queries. Note any confirmed Google update in that period. Only conclude the redesign helped or harmed them after several consistent readings, and look out for old addresses on their site that now return errors.
Step 5
Turn good ideas into tests of your own
For each change that seems worth borrowing, such as a clearer headline, a shorter form or reviews placed nearer the button, write it as a hypothesis for your own page with a measure, for example enquiries per hundred visits. Test one change at a time, using a split test if you have enough traffic or a before and after comparison over several weeks if you do not. Never copy their wording, images or layout wholesale.
Step 6
Record the outcome and close the alert
Write a short entry in your log with the rival page, the date, the meaningful changes you found, what happened to their rankings and speed, and which ideas you chose to test. If the redesign removed content that answered questions your customers ask, add a task to strengthen that part of your own page. Close the alert once you have a decision, and recheck the page in three months.
Testing an idea properly on your own site
The value of watching a competitor's redesign is that it gives you ideas to test, not answers to copy. Your audience, prices and reputation differ from theirs, so the same change can have a different effect.
- Enough traffic for a split test: use your site's testing feature or a testing tool to show the old and new versions to comparable visitors at the same time. Decide in advance how long it runs and what counts as a win, and leave it running for full weeks so weekday and weekend visitors are both included.
- Not enough traffic: make the change, then compare a similar period before and after, using the same measure. Be cautious about conclusions, because seasonality and other changes can explain differences.
- Search-sensitive changes: if the idea changes your title tag, H1 or main text, expect a short period of movement while search engines reprocess the page. Avoid changing several of these at once, or you will not know which one mattered.
Platform notes
- WordPress: most page builders let you duplicate a page as a draft. Build the variation there, then swap content into the live page so the address stays the same.
- Shopify: theme changes can be previewed on an unpublished copy of the theme before publishing. Product and collection text is edited separately from the theme.
- Custom or static sites: put the change behind a feature flag or deploy it to a preview environment first, and keep the page address unchanged.
Staying ready for the next redesign
- Keep a baseline. When you add a rival to Competitor Watch, save screenshots and the text of their most important pages. Future comparisons are then quick and reliable.
- Know your own numbers. Record conversion rates and Core Web Vitals for your key pages, so you can tell whether a rival's change should worry you.
- Have a testing habit. A standing list of ideas to test, fed by competitor changes, customer feedback and your own analytics, stops any single redesign from triggering a rushed rebuild.
- Look after your own redesigns. Every lesson here applies to your site too. Before your next redesign, list the text and links that currently earn traffic and make sure they survive it.
1. Does a competitor redesign mean I need to redesign my site?
No. A redesign on their side tells you what they chose to change, not whether it worked. Many redesigns are driven by branding, a new agency or a platform change, and some make pages worse for search by removing useful content or slowing things down. Watch the effect on their rankings for several weeks, pick out any individual ideas worth testing, and test them one at a time on your own pages rather than rebuilding everything in response.
2. How can I see what a competitor page looked like before the redesign?
The best source is your own record, such as screenshots and saved text from when you started watching them. If you have none, the Internet Archive Wayback Machine often has captures of popular pages; enter the address and choose a date before the change. Captures may be incomplete, with missing images or styling, but the headings and text usually survive. Search result snippets can also lag behind a change briefly and hint at the old title.
3. Can a redesign hurt a competitor's rankings?
Yes, and it happens often. The usual causes are removing text that answered common questions, replacing descriptive headings with slogans, losing internal links from the navigation, changing page addresses without proper redirects and adding heavy media that slows the page down. None of these is certain to cause a drop, but each can. If their page slips while yours answers the same questions well, you may gain simply by being the more useful result.
4. How long should I wait before judging the effect of a competitor redesign?
Allow four to six weeks of weekly checks before drawing firm conclusions. Search engines need time to recrawl and reassess the page, and rankings move for many reasons at once, including Google updates and changes on other sites. Field speed data in PageSpeed Insights also covers a rolling 28-day window, so it takes about a month to reflect the new design fully. Look for a consistent pattern rather than one surprising reading.
5. Is it acceptable to copy a competitor's page layout?
Common patterns, such as a headline, a list of benefits, reviews and a button, are used everywhere and nobody owns them. Copying a competitor's specific wording, photography, illustrations or distinctive design closely is a different matter, because those can be protected, and a near-copy can also confuse customers about who you are. Take the underlying idea, express it in your own words with your own material, and test it. This is not legal advice.
6. Their new page loads faster than mine. Does that matter?
It can matter to visitors, and it is one of many signals search engines consider. Compare Core Web Vitals in PageSpeed Insights: good means LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real visits. If your page is poor on these, improving it is worthwhile for your own visitors regardless of what the competitor did, but faster speed alone rarely outranks a clearly more useful page.
Competitor Watch tracks the competitors you name for new content, backlinks, schema changes, page redesigns, pricing, keyword rankings, product launches and tech changes, so you know when a key rival page has changed and can compare it calmly.
Open Competitor Watch Fixes →