SEO in Web Development: What to Plan Before You Build

Build first, fix later

This post is for business owners and the people who build their sites. Most projects follow one order: develop the site, write the SEO plan, then rebuild what the plan says is wrong.

Some things are cheap to change later: a headline, a meta description, an image. Other things are set in the first weeks of a build, and everything sits on top of them:

• URL structure: how every page address is written
• Site hierarchy and page types: which pages exist and where they sit
• Category structure: how products or services are grouped
• Internal links: how pages connect to each other

When SEO arrives after development, it has to ask for changes in exactly these places. That means rework and redirects, and every URL change carries risk.

What SEO-last costs

Google says something similar in its guidance for site moves: if you redesign content and URL structure together with a move, expect some traffic loss while Google reassesses your pages (Google, Change of Address tool).

So the cost of SEO-last is not a fixed number. It is the work of changing structure after launch: new URLs, redirects, and a check that nothing that ranked was lost. Plan the structure first and there is less of this to do.

Both sources describe redesigns and site moves, not every project. Read them as strong signals, not as a controlled study.

Strategy first, development second

1. Segment: decide who the site is for.
2. Concerns: list the questions, doubts and needs customers have before buying.
3. Keywords: match each concern to what people search, grouped by intent.
4. Site map: define page types, hierarchy, URL patterns and internal links. On an existing site, add a redirect map for every URL that will change.
5. Design and flows: answer each concern in the content, the design and the user flow.
6. Build: develop exactly what the map says.
7. Audit: save a baseline from Search Console and Analytics, then crawl the staging site before it goes live. Check that pages load, render and can be indexed.

The order is not strictly linear. Keyword research can change the segment or the site map. If it does, go back before design starts.

From concerns to flows

Most SEO plans stop at keywords. Go one level deeper. For each segment, write down the real concerns (the questions and doubts customers have before they buy), then answer each one in three places: the content, the design and the flow.

This helps SEO in a direct way. A page that answers a real concern matches search intent. A clear flow creates clean internal links. And a better experience turns the traffic you earn into leads and sales.

One honest note: better UX alone does not lift rankings. Google's John Mueller has said Core Web Vitals are a signal, but one that will not make your rankings jump (Search Engine Land). SEO brings the right visitors. UX and flow decide what they do next.

When to be careful

This model fits new builds best, and rebuilds where the URL map is planned and tested. If your site already has traffic, protect it. Google advises changing one thing at a time, so do not change domain, platform and layout in one release (Google, How to move a site). Ahrefs adds:

• Keep the old URLs unless you are sure you need to change them.
• Keep the pages that already rank and bring links.
• Change top ranking pages as little as possible.
• Test the staging site for mobile and Core Web Vitals.
• Run a site audit before and after launch.

For a small site of a few pages, do not over-build the plan. One page of notes is enough: who the site is for, the main search for each page, and the URL list.

Strategy first does not mean change everything. It means decide everything with a plan.

Example: ecommerce category structure

Category pages are the main SEO pages of a store, so category structure is the biggest decision in the plan.

On Shopify this matters even more. Store URLs follow this structure: /products/, /collections/ and /blogs/ (Shopify). You can edit the handle at the end of each address, and you can create a redirect from the old address to the new one (Shopify Help Center). What stays in your hands is the collection hierarchy, the handles, the navigation and the internal links. Those are the things to plan before the build.

Technical basics for the build

The plan also needs a few technical decisions, made with the developer before the build starts.

• Content that renders: key text, headings and links must be visible in the rendered HTML. Google cannot index content that is not there, and it recommends server-side or pre-rendering for JavaScript-heavy pages (Google, JavaScript SEO basics).
• One preferred URL per page: when pages are duplicate or very similar, say which URL you want Google to treat as the main one (Google, canonical URLs).
• An XML sitemap that lists the pages you want found (Google, sitemaps).
• Speed and mobile: test the staging site for mobile and Core Web Vitals before launch.

SEO checklist for web development

1. Target segment and their main concerns.
2. Keyword research grouped by search intent.
3. Site map with page types and a URL pattern.
4. Redirect map for every old URL that will change (existing sites).
5. Baseline from Search Console and Analytics saved before launch: clicks, rankings and top pages. See SEO KPIs for what to track.
6. A plan for how each concern is answered in design and flow.
7. Staging site behind a password or set to noindex, with a reminder to remove it at launch.
8. Technical basics checked on staging: rendered content, preferred URLs, sitemap, mobile and Core Web Vitals.

If you can tick all eight, development becomes a build, not a guess.

Frequently asked questions

Should SEO be involved before a website redesign starts?

Yes. URLs, site hierarchy, categories and internal links are set early in a build and are costly to change later. See what SEO-last costs.

Does a website redesign hurt SEO?

It can. Google says to expect ranking fluctuation, and some traffic loss if you redesign content and URL structure together with a move. See when to be careful.

What should be ready before design and development start?

A segment and its concerns, keyword research by intent, a site map, a redirect map, a baseline, the technical basics and a protected staging site. See the checklist.