
Why Does SEO Belong in Website Development?
SEO in website development means making search-related decisions before a site is built, not after launch. Choices about URL structure, rendering, templates, speed, redirects and tracking are cheap to make at the design stage and expensive to change later. Involve SEO from the first planning meeting, and test before the site goes live.
| Decision | When to make it | Cost of getting it wrong |
|---|---|---|
| Platform and rendering | Before development starts | Rebuild |
| Site structure and URLs | Design stage | Mass redirects, lost rankings |
| Page templates | Design stage | Every page of that type affected |
| Performance budget | Design stage | Slow site, redesign of components |
| Redirect map | Before launch | Lost traffic and links |
| Tracking and tools | Before launch | No baseline, blind decisions |
| Pre-launch testing | Final week | Indexing blocked or broken at launch |
This guide lists the decisions in the order a project meets them. It applies to new sites and to redesigns of existing ones.
Decision 1: Which Platform and Rendering Method?
Choose a platform that lets you control the things search depends on: titles, URLs, redirects, canonicals, structured data and robots directives. Then decide how pages are rendered.
If the site uses a JavaScript framework, make sure public pages send complete HTML from the server. Google’s JavaScript SEO basics describe server-side or pre-rendering as still a great idea, because not all bots can run JavaScript. Our React SEO guide covers the options.
Ask of any platform:
- Can each page have a unique title, description and canonical?
- Can we set redirects in bulk?
- Can we edit robots.txt and add structured data?
- Does it produce a sitemap?
- Can we export content if we leave?
Decision 2: What Site Structure and URLs?
Design the structure from keyword research, not from the organisation chart. Each main topic customers search for should have a logical home.
- Group related pages in sections that reflect how people search.
- Keep important pages within a few clicks of the home page.
- Use readable URLs: short words, hyphens, no unnecessary parameters, as Google’s URL guidance recommends.
- Choose one format and keep it: trailing slash or not, lowercase, www or not.
- Plan for growth: where will new services, locations or languages go?
For multilingual sites, decide early between subfolders, subdomains and separate domains, and plan hreflang annotations. Our SEO strategy guide explains mapping topics to pages.
Decision 3: What Goes into Each Template?
Templates multiply every decision. One flaw in a product template is repeated on every product.
Each template should provide:
- An editable title tag and meta description, with sensible defaults.
- One main heading, separate from the logo.
- A logical heading hierarchy.
- A self-referencing canonical link.
- Structured data suited to the page type, generated from the same data as the visible content.
- Breadcrumbs.
- Image fields with alt text.
- Crawlable links: real anchor elements with an href, per Google’s link guidance.
- Slots for related links to other pages.
Review designs with real content, including the longest title and the shortest description you expect.
Decision 4: What Performance Budget?
Set speed targets before design is approved. It is far easier to refuse a heavy component than to remove it later.
Use the Core Web Vitals thresholds as the budget: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less.
- Limit fonts, carousels, video backgrounds and third-party scripts.
- Serve images in modern formats, sized for the device, with dimensions set.
- Load non-essential scripts late.
- Design mobile first. Google indexes the mobile version of pages.
Want this handled for you?
Our SEO services start with a full audit and a written plan, followed by a monthly report that shows what changed and why.
See our SEO servicesDecision 5: How Will Old URLs Be Redirected?
For a redesign or migration, the redirect map is the most important document in the project. Every old URL that has traffic or links must lead to its closest equivalent.
- List all current URLs from a crawl, the sitemap, analytics and Search Console.
- Mark those with traffic or external links.
- Map each to its new URL, one to one. Do not send everything to the home page.
- Use permanent redirects. Google’s redirect guidance explains the types.
- Avoid chains, where one redirect leads to another.
- Test the map on the staging site.
- Keep redirects in place long term.
Google’s guide to site moves describes the full procedure and notes that some fluctuation during a move is normal.
Decision 6: How Will You Track Results?
Set up measurement before launch, so you have a baseline to compare against.
- Install analytics, with conversions defined.
- Verify the site in Search Console and Bing Webmaster Tools.
- Record current rankings, clicks and indexed pages for an existing site.
- Keep access to the old site’s data.
- Annotate the launch date.
Without a baseline, nobody can say whether the new site performs better or worse.
What Should Be Checked Before a Site Goes Live?
Run this checklist on the staging site, then again immediately after launch.
- Indexing is allowed. Remove the noindex and robots.txt blocks used during development. This is the most common launch error.
- Staging is not indexed and is protected by a password.
- Every template has a unique title, description, main heading and canonical.
- Canonicals point to the live domain, not the staging address.
- Redirects work, one hop each.
- The XML sitemap lists live, canonical URLs only. See our XML sitemap guide.
- Internal links contain no broken or staging URLs.
- Structured data validates.
- Missing pages return a real 404.
- Mobile pages display the same content as desktop.
- Speed meets the budget on key templates.
- Analytics and conversions fire correctly.
A full crawl of staging catches most of these. Our guide to using an SEO crawler explains how.
What Should You Watch After Launch?
Monitor closely for the first weeks.
- Day one: crawl the live site, submit the sitemap, and check the robots.txt file.
- Week one: watch the Page indexing report for errors and server logs for failed requests.
- Weeks two to eight: compare clicks and positions with the baseline. Fix any redirected URLs that return errors.
- Ongoing: look for old URLs still receiving visits, and add redirects.
Some movement is expected after a redesign. A sharp, sustained fall usually points to blocked indexing, missing redirects or removed content.
What Are the Common Mistakes?
- Launching with noindex still in place.
- Changing every URL without redirects.
- Removing content that ranked because it did not fit the new design.
- Replacing text with images.
- Navigation that needs JavaScript to reveal links.
- One title template for every page.
- Bringing SEO in the week before launch.
The last causes most of the others.
Frequently Asked Questions
When should SEO join a website project?
At the planning stage, before the platform is chosen and the structure designed. Decisions about rendering, URLs and templates are easy to get right then and costly to change after build. Bringing SEO in just before launch limits it to reporting problems nobody has time to fix.
What should be checked before a site goes live?
Confirm indexing is allowed, each template has a unique title, heading and canonical, redirects from old URLs work in a single hop, the sitemap lists only live canonical pages, internal links are not broken, structured data validates, speed meets targets and analytics records conversions.
Does changing a CMS affect SEO?
It can. A new CMS often changes URLs, templates, internal links and page speed, and sometimes drops content or metadata. With a complete redirect map, migrated titles and content, and testing before launch, rankings usually hold. Without them, traffic losses are common.
How long do rankings take to settle after a redesign?
Typically a few weeks, sometimes longer on large sites. Search engines need to recrawl pages, follow redirects and reassess content. Small fluctuations are normal. If traffic is still well below baseline after two months, look for missing redirects, blocked pages or content removed during the redesign.
Should developers or marketers own technical SEO?
Both, with clear roles. Marketers or SEO specialists define requirements and check the output. Developers implement them and keep them from breaking. Problems arise when requirements arrive after the build, or when no one checks that a release left titles, canonicals and indexing intact.
Related Guides
Want this done for you?
See what each monthly plan includes, or send us your site and questions on WhatsApp. We do not promise rankings; we show the work and the data every month.
View SEO packages Chat on WhatsAppSources
- Google Search Central: JavaScript SEO basics
- Google Search Central: URL structure best practices
- Google Search Central: Localized versions of your pages
- Google Search Central: Link best practices
- web.dev: Web Vitals
- Google Search Central: Mobile-first indexing best practices
- Google Search Central: Redirects and Google Search
- Google Search Central: Site moves with URL changes
- Search Console Help: Page indexing report



