← All articles

SEO & Project Planning

When to Bring SEO Into a Website Redesign

Resolve search-related content and URL decisions before they become expensive redesign changes. Includes a phase-by-phase responsibility table.

By , Co-Founder & CEOUpdated 3 min read
A fault specimen, replacement fitting and separate inspection gauge sit in a milestone tray.

The redesign is nearly finished when someone notices that a high-value service no longer has its own page. The developer can restore it, but the change affects the menu, layout, copy, and testing.

That is a project-sequencing problem. The service decision needed to happen before the team treated the page list as final.

Bring the right decisions forward

Google’s guidance on hiring SEO help identifies a redesign or new site as a useful time to involve an SEO. The practical reason is that search, content, and site structure affect decisions other people will build on.

Use this planning table before approving the project schedule:

Stage Decision due People who need to resolve it Cost of finding it late
Scope Which existing pages still perform a business job? Business owner, marketing, SEO Deleted pages must be restored
Templates Which offers need different information? Service owner, writer, designer Finished layouts need rework
Build estimate Are URLs, CMS, domain, or connected systems changing? Project owner, developer, SEO Migration work appears outside the estimate
Launch approval Who can resolve a failed release check? Developer, content owner, approver The team finds issues without a decision-maker
After launch Who handles defects and ongoing improvements? Project owner and support provider Findings sit outside anyone’s active scope

This is an example responsibility structure. Use the roles your business actually has rather than creating a committee for each row.

Separate different offers before choosing the layout

Imagine a company sells both emergency repair and annual maintenance. The repair buyer needs urgency, coverage, and a contact path. The maintenance buyer may need plan scope, exclusions, and scheduling details.

Resolve those differences before insisting that every service page fit the same short template. The design can stay consistent while allowing enough room for each buying decision.

That discussion is easier while layouts are sketches than after the team has approved finished pages.

Define what “redesign” includes

A visual refresh, a CMS replacement, and a domain move involve different work. Ask which changes are necessary for the business outcome and which can happen later.

Google’s site-move guidance recommends changing major elements separately where practical. The team also gains a clearer explanation of what changed if a problem appears.

Set a release gate before the launch meeting

Before development begins, ask the team to identify the pages that must survive the redesign and the tests required for launch. That gives the designer room for useful service content and gives the developer an agreed redirect list.

SEO decisions belong at specific project stages. Scope: Assign service and article owners; Design: Preserve useful content space; Build: Map redirects and canonical URLs; Launch: Accept routing and inquiry checks
SEO decisions belong at specific project stages. Original planning aid from The Ops Guide. Any example figures are illustrative unless this article identifies a source.
Scope
Assign service and article owners
Design
Preserve useful content space
Build
Map redirects and canonical URLs
Launch
Accept routing and inquiry checks

For a hypothetical launch, the owner may accept the visual design while holding release for a broken service URL. Make that authority explicit. After launch, use the same URL list to inspect the public site and investigate changes in search exposure without confusing them with new-page performance.

Check this before you proceed

  • Assign an owner to the old-URL inventory.
  • Include routing checks in launch acceptance.
  • Set a dated post-launch review.

Download this article’s editable worksheet (CSV). Add your evidence, owner, and review date. For the next related decision, read Website Redesign SEO Checklist: Preserve the Pages People Find.

Put release checks in the plan, not in someone’s spare time

Reserve time and people to respond to failed checks. Our redesign preservation checklist covers the URL and content checks themselves; the project plan needs to say who acts on the findings and who can delay a release.

Separate fixing a launch defect from commissioning a new content program. Both may be necessary, but combining them under “SEO later” makes responsibility hard to pin down.

If a redesign is approaching, The Ops Guide can help connect SEO with the project plan before the expensive decisions are locked in.

SEO growth

Want this done for your business?

See how the SEO Growth Partnership works — we audit your site, improve listings, and publish content for the services and locations you want customers to find.

Luke Thompson

About the author

Luke Thompson

Co-Founder & CEO, The Ops Guide

Luke Thompson is Co-Founder and CEO of The Ops Guide. He writes about practical uses of AI, workflow automation, custom software, and SEO for growing businesses.

About The Ops Guide

The Ops Guide helps businesses improve how work gets done through custom software, workflow automation, AI systems, and SEO services.

The Ops Guide Brief

Get AI news you can use.

The developments worth your attention, what they change at work, and what to do next. Choose a daily briefing or a weekly selection.

Free to subscribe. Confirm by email. Unsubscribe any time.