The small-business website guide

Plan the SEO work before switching to a redesigned website.

The pages, URLs, and business information people already find are part of the redesign. Record them before the move so you can make deliberate changes and investigate any problems afterward.

Free preview. No card required. Publishing plans from $29.99/month.

Laptop displaying a website analytics dashboard
Illustrative stock photographImage credits

Start here

How do you reduce SEO risk during a website redesign?

Reduce redesign risk by recording important pages, preserving useful content and URLs where practical, and mapping any changed URLs to relevant destinations. Verify redirects, canonical URLs, sitemap entries, and index controls. Monitor the new site after launch. These checks reduce avoidable problems but cannot guarantee unchanged search rankings.

Start with the pages that already bring visitors.

In Search Console, review the pages and queries that receive impressions and clicks. In your analytics tool, check landing pages and the actions visitors complete. Use both views: a page with little traffic may still explain a service that produces useful inquiries.

Save the page URLs, titles, main content, and contact actions. Note external links and downloads you need to keep. Decide which pages will remain, which will be improved, and which are no longer useful. Do this before choosing a new navigation menu.

Make a URL map before you publish.

For every important old URL, record the intended new destination. Keep a working URL when there is no reason to change it. If it changes, confirm that the host or platform responsible for the old address can redirect it to the relevant new page.

A redesign preview does not configure all legacy redirects for you. Identify who will set them up and test the result. Avoid sending unrelated old service pages to the homepage by default; use a destination that answers the same customer need.

Make a URL map before you publish.
Old pagePlanned actionLaunch check
A useful service pageKeep the URL or map to its replacementPage loads and explains the service
A changed page addressConfigure a permanent redirectOld address reaches the relevant new page
A removed offerDecide whether a relevant replacement existsNo misleading or broken internal links
A booking or download linkPreserve or replace the destinationThe customer can complete the action

Check what a crawler and a visitor receive.

Public pages should load at the intended URL, describe their own content, and be available for indexing. Check for accidental noindex directives, blocked pages, incorrect canonical URLs, or links to a staging domain. Make sure the sitemap lists the public pages you want discovered.

Review the rendered page as well as its metadata. Keep headings readable, image descriptions accurate, and internal links descriptive. Structured data should reflect facts visible on the page. It does not substitute for clear content or guarantee an enhanced search result.

Watch the move with a recorded baseline.

After launch, check important old and new URLs, submit or confirm the sitemap in Search Console, and test forms on the live domain. Watch indexing reports and investigate missing destinations. Google notes that ranking fluctuations can happen while it recrawls and reindexes changed sites.

Keep search and conversion questions separate. More impressions do not necessarily mean more suitable customers; a form submission is not necessarily a sale. Compare landing pages, search queries, and qualified inquiries over time, and record the date of the redesign so changes have context.

Keep this list handy

Before the domain switch

  • Record search landing pages and useful customer actions.
  • Map old URLs to their intended destinations.
  • Confirm who will configure and test redirects.
  • Review titles, canonicals, robots rules, and sitemap URLs.
  • Test the live contact journey and monitor after launch.

Sources and further reading

Reviewed November 3, 2026.

A few more details

Common questions

Will Markio preserve my rankings automatically?

No. Markio provides website SEO foundations, but rankings depend on many factors. Review legacy URLs, content changes, redirects, and any custom integrations separately. Keep a baseline so you can investigate changes after the redesigned site goes live.

Does an XML sitemap guarantee indexing?

No. A sitemap helps search engines discover URLs, but they decide what to crawl and index. Submit canonical public URLs and check Search Console for the actual indexing status. Fix errors and make the pages useful to visitors.

Should I change all my service copy during the move?

Preserve accurate information that already answers customer questions. Improve unclear or outdated content with a specific reason for each change. Record what changed so a later search or conversion review can distinguish a technical problem from a change in the page's purpose.

Free first preview

Put your website plan into a first draft.

Paste a site you own or have permission to reuse. No credit card is required to start the preview flow.

No website yet? Describe your business instead.