Back to Insights
Technical SEO

Web Design and SEO: Why They Belong in the Same Brief

Author

Tanuj Sarva

Published

November 18, 2026

Read Time

6 min read

Web Design and SEO: Why They Belong in the Same Brief

Key takeaways

  • A redesign is the most reliable way to lose rankings you already have, and it almost always happens by accident rather than through a bad design.
  • Five decisions cause most of the damage: changing URLs without redirects, moving content into JavaScript, dropping copy for visual reasons, losing internal links to a cleaner navigation, and rebuilding the title and heading structure from scratch.
  • The copy reduction is the one nobody flags. A redesign that halves the words on a page halves what the page can be found for, and the design review will call it an improvement.
  • JavaScript-rendered content is the modern version of the same problem. If the body only exists after a script runs, anything that does not run scripts sees an empty page.
  • The fix is cheap and has to be early: a crawl and a ranking inventory before design starts, then a redirect map signed off before launch.
  • Get this wrong and the recovery costs more than the redesign. That is the one case where we will tell you to delay a project you have already paid for.

A business commissions a redesign because the site looks dated. Three months after launch the enquiries have dropped and nobody can explain why, because the new site is plainly better.

It is better at everything except being found. That is not a conflict between design and search; it is what happens when search is not in the brief and so nobody is responsible for it.

This covers what to put in the brief, which five decisions do the damage, and the two checks that catch almost everything before launch.

Why do redesigns lose rankings?

Short answer: Because a redesign changes the things rankings were built on while being judged on how it looks. URLs move, copy gets cut for visual balance, navigation gets simplified, and each of those is an improvement by design criteria and a loss by search criteria.

Nobody in the process is doing anything wrong. The designer is making a better-looking site, the developer is building what was designed, and the client is approving something they prefer.

The loss happens in the gap between those roles, which is why the fix is a brief rather than a person. A requirement written down before design starts is the only thing that survives the handoffs.

The clearest symptom of a redesign done without a brief is a traffic drop that begins at launch and does not recover. If that describes your site, the cause is almost always in the redirect map or in content that no longer exists.

Which five decisions do the damage?

Short answer: Changing URLs without redirects, moving body content behind JavaScript, cutting copy for visual reasons, replacing a messy navigation with a clean one that drops internal links, and rewriting titles and headings from scratch without reference to what they were ranking for.

  1. URL changes with no redirect map. Every link anyone ever built now points at a 404. This is the most damaging and the easiest to prevent.
  2. Content behind JavaScript. If the body appears only after a script runs, anything that does not run scripts sees nothing. Google documentation is explicit that AI features draw on the same ranking systems, so an unreadable page is unreadable twice over.
  3. Copy cut for layout. A page reduced from nine hundred words to two hundred can be found for far less. The design review will record this as cleaner.
  4. Internal links lost to a tidier menu. A navigation reduced from forty links to eight removes the main route into thirty-two pages.
  5. Titles and headings rebuilt from scratch. The old ones were often the reason pages ranked, and nobody checked before replacing them.

Number three is the one we argue about most with clients and designers, and it is the one with no technical signature. Nothing breaks; the page simply says less.

What should go in the brief?

Short answer: Four requirements, written before any design work: URLs stay or are redirected one to one, the body content renders without JavaScript, every page keeps at least as many words as it has now, and the current title and heading structure is the starting point rather than a blank page.

Those four are specific enough to be checkable and loose enough not to constrain the design. None of them dictates how anything looks.

Add a fifth if you have a large page set: internal links are preserved or deliberately re-planned. A tidier navigation is a legitimate goal, as long as the pages it stops linking to get a route in from somewhere.

Put the requirements in the contract, not the kickoff call. A requirement that exists only in a conversation is a requirement that loses to a deadline.

What should I check before launch?

Short answer: Two things, both cheap. Crawl the old site and the staging site and compare the URL lists, which catches every missing redirect. Then view the staging pages with JavaScript disabled, which catches every piece of content that only exists in a browser.

The second check takes about ten minutes and catches the failure that is hardest to diagnose afterwards. A page that looks complete to everyone reviewing it can be empty to a crawler.

Do them on staging, not after launch. A redirect map applied two weeks late has already cost you whatever was crawled in those two weeks.

Then take a baseline. Export your current impressions and positions from Search Console before launch, because without it you cannot tell a seasonal dip from a self-inflicted one.

Should the same agency do both?

Short answer: Not necessarily, and insisting on it narrows your choice of designer for no good reason. What matters is that one named person owns the search requirements through the project, with authority to stop a launch, and that person can sit on either side.

The arrangement that fails is the one where search is a review stage near the end. By then the URLs are decided, the content is written and the only options are expensive.

The arrangement that works is a short, early engagement to set the requirements and a short one before launch to check them. That is a few days of work protecting a project worth considerably more.

We do this as a defined piece rather than a retainer, because it is bounded work with a finish line. If it turns out your redesign is already past the point where requirements can shape it, we will tell you that instead.

Frequently asked questions

Will a redesign always hurt my rankings?

No. A redesign with a one-to-one redirect map, content preserved and a server-rendered body routinely launches with no loss at all. The damage comes from the decisions listed above, each of which is preventable in the brief.

How long does a redesign take to recover from?

It depends entirely on what was lost. A redirect map applied late recovers relatively quickly once the links resolve again. Content that was deleted does not recover until it is rewritten, because there is nothing left to rank.

Can I change my URL structure safely?

Yes, with a redirect from every old URL to its closest new equivalent, and with the understanding that the closest equivalent is sometimes a worse match. Google documentation on canonical URLs and consolidation is the reference for how this is handled.

Is a single-page application bad for SEO?

It is a problem when the content only exists after the script runs. Server rendering or prerendering fixes it, and the test is simply whether the body is in the HTML before any JavaScript executes.

Should I keep my old pages if the new design has fewer?

Keep the ones with impressions, which your own Search Console data will tell you. Consolidating genuinely redundant pages is good practice; consolidating pages that were working is how a redesign loses a quarter of its traffic.

Sources and further reading

About to commission a rebuild?

Bring us in for the brief rather than the recovery. It is a few days of bounded work, and if your project is already too far along for it to help we will say so rather than bill for it.