SEO during website development: what to build in before launch and which mistakes to avoid

Разработчик и SEO-специалист проверяют структуру сайта перед запуском в студии в Ташкенте
Content

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

Разработчик и SEO-специалист проверяют структуру сайта перед запуском в студии в Ташкенте

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.

StageSEO taskWhat you get as a result
Technical briefCollect queries and describe page requirementsList of pages and sections matching demand
PrototypeCheck that each group of queries has its own page and space for textBlocks for headings, descriptions, FAQ
Design and front-endOne H1 per page, light images, mobile versionTemplates that do not get in the way of search
DevelopmentURLs, meta tags, canonical links, sitemap, robots.txtSettings you can change from the admin panel
Test copyBlock from indexing, check everything before launchChecklist of mistakes before going live in search
LaunchOpen indexing, connect analytics and Search ConsoleThe 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.

ElementWhat to build inCommon mistake
Title and descriptionA template per page type and a manual field for editsThe same title on every page
HeadingsOne H1, subheadings that follow the meaningThe H1 is taken by the logo or slogan
SpeedImage compression, lazy loading, minimal heavy scriptsVideos and sliders on the first screen of the mobile version
Mobile versionThe same text and links as on desktopPart of the content is hidden on mobile
Filters and paginationCanonical links, indexing rulesThousands of duplicates from filter combinations
System filesrobots.txt, sitemap, 404 page, HTTPSThe 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

  1. Export all URLs of the old site and the pages that bring traffic.
  2. Make a table: the old URL and the new URL for each page.
  3. Set up permanent 301 redirects using this table, with no mass redirect to the home page.
  4. After launch, check redirects and errors in Search Console.
Learn about SEO support for your launch →

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?
Yes, but part of the work will go into rework: new pages, URL changes, template fixes. The later you start, the more rework there is.
Should the test version be hidden from search?
Yes, otherwise a copy of the site at another address will get indexed. It is safer to protect it with a password and, at launch, check that the block did not carry over to the main domain.
Is a website builder suitable for SEO?
For a small site it often works. Before choosing, check whether you can change URLs, meta tags, redirects, and language versions.

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 →

6 useful guides:

increasing the number of customers and brand awareness
Download guides and implement new tools to grow your company.

Website for your business:

Fill out the brief and get a quote for your website
You receive a project implemented by experts with international experience.

How to choose an advertising agency in Tashkent without wasting your budget

A business owner in a meeting room in Tashkent compares advertising agency proposals using a printed table