Before You Rebuild Your Business Website: The SEO Check That Protects Visibility

A new business website can be better in almost every visible way and still perform worse in search. The reason is often that the project treats SEO as a final check rather than as part of the rebuild itself.

When pages are moved, text is shortened, menus are changed and new templates are introduced, you also change the signals that help search engines understand the website. The consequences often become visible only after launch, when important pages lose rankings or relevant traffic declines.

The solution is an SEO change control: a consistent way to assess how each change affects technical accessibility, information architecture, search intent, internal linking, performance and content. Here is a practical model that can be used for redesigns, platform migrations and major content revisions.

Start by mapping what already works

Do not assess the existing website solely on the basis of design and editorial quality. An outdated page may still be visible for important searches, guide users to a service and contribute to enquiries.

Therefore, create an overview of all indexable pages before deciding what should be kept, merged, rewritten or removed. For each important page, you should record:

• The page URL and its position in the structure
• Which topic, product or need it covers
• Which search intent it addresses
• Whether it receives relevant organic traffic
• Which internal links point to the page
• What the user is expected to do next
• Which new page will potentially take over its role

This overview makes it harder to accidentally delete value. It also reveals pages competing for the same searches, outdated content that should be phased out and important topics that lack a clear main page.

Give each page a clear purpose

A common mistake in redesign projects is to organise the website around internal departments. Customers, however, rarely search for the organisational chart. They search for a problem, a solution, a product, a price or a supplier that suits their situation.

Therefore, define one primary purpose for each page. A service page should, for example, explain what the service solves, who it is suitable for, how delivery works and what the next step is. A guide should help the user understand or carry out something. A category page should provide an overview and lead to relevant alternatives.

If a page tries to address several entirely different intents, it often becomes unclear to both people and search engines. In that case, the content should be divided or given a clearer priority.

Three questions that clarify search intent

1. What is the user trying to accomplish? Is the goal to learn, compare, buy, book or find a particular business?
2. What information does the user need to move forward? This could be pricing factors, features, delivery time, expertise or practical implementation.
3. What is a natural next step? The page should guide the user forward without making them start their orientation process again.

This provides a better foundation for content, page type and calls to action than starting with a list of keywords.

Build an information architecture that shows priorities

The website structure should make it easy to understand which areas the business offers and how subpages relate to one another. A flat collection of landing pages can provide a short route from the home page, but often creates weak connections between topics. An unnecessarily deep structure, on the other hand, makes important pages difficult to find.

Use main areas that correspond to actual offerings and user needs. Under each main area, you can group services, products, expert articles, customer stories and questions that support the same topic.

For example, a consultancy could have a main page for risk management, subpages for specific services and expert articles explaining common challenges. This gives the user an understandable path from problem to solution, while the search engine can also see the thematic connection.

Evaluate the structure using three simple tests:

• Can a new visitor understand the main offering from the menu?
• Can editors place new content without creating random categories?
• Are commercially important pages accessible through natural clicks, not just through search or campaigns?

Create a plan for every URL that changes

Changing page URLs is one of the riskiest parts of a rebuild. Old URLs may have built up visibility, external links and internal authority. If they simply disappear, both users and search engines encounter a dead end.

Create a complete overview that connects each old URL to the correct new URL. A redirect should point to the most relevant replacement, not automatically to the home page. If three old pages are combined into one better page, all three can point to the new consolidated page. If the content has no genuine successor, it may be more appropriate to let the page disappear than to send the user to something irrelevant.

Avoid chains in which an old URL first points to an intermediate page and then to the final page. Also update internal links so that they go directly to the correct destination.

Plan internal linking as part of the content

Internal linking is often reduced to related articles at the bottom of the page. That is useful, but not sufficient. The most important links should appear where they make sense in the text and help the user move forward.

A good internal link does three things: It shows the connection between pages, describes what the destination page is about and gives the user a relevant next action. The link text should therefore be specific. Phrasing that describes the topic is more useful than generic words such as «read more».

Establish some simple editorial rules:

• New expert articles should link to a relevant service or product when natural.
• Main pages should link to important subpages and supporting content.
• Older articles should be updated with links to new, relevant pages.
• Pages with no incoming internal links should either be integrated into the structure, improved or removed.
• Links should support the user's task, not be added solely for SEO.

Check technical SEO in the templates

Many technical errors occur in templates and components, not on individual pages. One incorrect setting can therefore affect an entire content type.

Make sure the page templates allow editors to write unique page titles, descriptions and main headings. It should be clear which URL is the preferred version of a page. Pages that should appear in search must be crawlable and indexable, while internal search results and other pages without independent value should normally be excluded.

Also check that status codes, redirects, breadcrumbs and navigation work consistently. JavaScript-based solutions must not hide central content or important links from users who experience slow or incomplete loading.

Include Core Web Vitals in design decisions

Performance cannot be solved simply by compressing images just before launch. Core Web Vitals are affected by how pages are designed and built: large hero images, heavy fonts, third-party scripts, dynamic forms and elements that shift during loading.

Therefore, consider performance when components are approved. Ask whether the page displays the main content quickly, responds quickly to clicks and keystrokes, and keeps its content stable while the page loads.

Test representative page types, not just the homepage. An article template, product page, service page and contact page can have completely different problems. Measurements from the development environment should also be followed up with data from actual visits after launch.

Preserve useful content when tightening the language

Redesigns often lead to shorter texts. Short is good when unnecessary content is removed, but harmful when important explanations disappear. A polished introduction and three selling points rarely answer all the questions a potential customer has.

Preserve information that helps users evaluate the offering: who the solution is suitable for, which problems it solves, what the delivery includes, which choices must be made and how the process works. Concrete examples and frequently asked questions can make the page more useful without making it unnecessarily long.

Assess content based on decision value, not just word count. Each section should contribute to understanding, trust or progress.

Conduct a review before and after launch

Before launch, you should review the most important pages and functions in an environment that resembles production. The review must cover more than visual quality.

• Are all priority pages included in the new solution?
• Are old and new URLs connected correctly?
• Can important pages be indexed?
• Are page titles, main headings and descriptions unique and relevant?
• Do navigation, breadcrumbs and internal links work?
• Does the content address the agreed search intent?
• Have key page types been tested for Core Web Vitals?
• Do forms and other important actions work?

After launch, you should monitor whether pages are being found and indexed, whether old URLs are handled correctly, and whether organic traffic changes for important topics. Look at developments by page group and search intent, not just total traffic. An overall trend can hide the fact that valuable service pages are losing visibility while less important traffic increases.

Make SEO change control a clear responsibility

The best checklist is of little use if no one owns the decisions. Clarify who approves the new structure, URL changes, content removals, technical settings and performance requirements. SEO responsibility must be connected to design, development and content work throughout the project.

The goal is not to preserve everything old. The goal is to understand what value exists, improve it deliberately and avoid important signals disappearing during the transition. This can make the new website easier to use, easier to maintain and better equipped to be found by the right customers.