What to build into a site before launch so you do not have to rework it for search later: structure, page URLs, meta tag templates, speed, mobile version, language versions, and migrating an old site.
KelyanMedia editorial team · Updated November 13, 2026

Many search requirements are easier to meet at the design stage than to fix on a live site. Changing a heading template in a mockup is easy, while reworking the URLs of hundreds of pages after indexing takes long and risks losing traffic.
Below we cover what to discuss with your developer and SEO specialist before launch and which mistakes happen most often.
In short: what you need to know
- WhenSEO requirements are needed at the brief and prototype stage, not after launch.
- WhatStructure based on queries, clear URLs, meta tag templates, speed, mobile version, and language versions.
- RiskMost traffic is lost when an old site is migrated without a 301 redirect map.
Where SEO fits into development
Each development stage has its own SEO task. If you skip it, you will have to fix it at the next stage, and that costs more.
| Stage | SEO task | What you get as a result |
|---|---|---|
| Technical brief | Collect queries and describe page requirements | List of pages and sections matching demand |
| Prototype | Check that each group of queries has its own page and space for text | Blocks for headings, descriptions, FAQ |
| Design and front-end | One H1 per page, light images, mobile version | Templates that do not get in the way of search |
| Development | URLs, meta tags, canonical links, sitemap, robots.txt | Settings you can change from the admin panel |
| Test copy | Block from indexing, check everything before launch | Checklist of mistakes before going live in search |
| Launch | Open indexing, connect analytics and Search Console | The site starts getting indexed |
← Swipe to scroll the table →
We explained how to write these requirements into a document for the developer in the article how to write a technical specification for a website.
Site structure and page URLs
Site structure is built around how people search, not around how your sales department is organised.
- each service or product category with its own demand needs its own page, not one shared section;
- URLs in Latin letters, short and readable: /uslugi/remont-kondicionerov/, with no parameters or numbers;
- nesting that follows meaning: a service inside a section, a product inside a category;
- breadcrumbs and menus that let you reach an important page in a few clicks;
- URLs do not change after launch unless necessary.
Meta tag templates and the technical foundation
On sites with a catalogue, meta tags are filled in with templates, and important pages are edited by hand. Both options should be available in the admin panel.
| Element | What to build in | Common mistake |
|---|---|---|
| Title and description | A template per page type and a manual field for edits | The same title on every page |
| Headings | One H1, subheadings that follow the meaning | The H1 is taken by the logo or slogan |
| Speed | Image compression, lazy loading, minimal heavy scripts | Videos and sliders on the first screen of the mobile version |
| Mobile version | The same text and links as on desktop | Part of the content is hidden on mobile |
| Filters and pagination | Canonical links, indexing rules | Thousands of duplicates from filter combinations |
| System files | robots.txt, sitemap, 404 page, HTTPS | The noindex rule was left over from the test copy |
← Swipe to scroll the table →
Language versions and migrating an old site
Sites in Uzbekistan often need Russian, Uzbek, and English versions. Each version needs its own URL and links to the others through hreflang.
Language versions
- a separate URL for each language, for example /uz/ and /en/, without switching the language only through cookies;
- on each page, hreflang tags for all language versions, including the page itself;
- translation of meta tags and URLs, not just the page text.
Migrating an old site
- Export all URLs of the old site and the pages that bring traffic.
- Make a table: the old URL and the new URL for each page.
- Set up permanent 301 redirects using this table, with no mass redirect to the home page.
- After launch, check redirects and errors in Search Console.
Important
A sound technical foundation does not promise rankings: results depend on the niche, competition, and content. But mistakes at launch can delay indexing for a long time, so it is cheaper to rule them out before launch.
FAQ
Can SEO be added after the site launches?
Should the test version be hidden from search?
Is a website builder suitable for SEO?
Next steps
Planning a new site: see website development.
Your site is already live or moving: learn about SEO promotion.
Want to see examples: open our websites.
Still have questions: call +998 33 339 33 34.
Discuss website development →
