A website redesign is needed when your current site loads slowly, is awkward on a phone, has no Russian or English version, or has stopped bringing in leads. To keep your Google rankings, export every URL that gets traffic before launch, map each old address to a new one with a 301 redirect, set up hreflang for az/ru/en, and watch Search Console closely for the first 30 days.
This playbook is for companies in Baku that already have a website getting at least some traffic from Google, ads and social media. The job of a redesign is to keep what works and fix what gets in the way of sales. If you have no site yet and are choosing a provider from scratch, start with the website development Baku page.
8 signs your website needs a redesign
One sign is a reason for a targeted fix. Three or more are a reason to plan a redesign.
- The site is slow on mobile. If PageSpeed Insights shows red Core Web Vitals, part of your ad traffic leaves before the first screen loads. Sometimes optimisation is enough without a redesign — see why a website loads slowly.
- The mobile experience is poor. In Azerbaijan most traffic from Instagram, Facebook and TikTok comes from phones. Tiny buttons, sideways scrolling, ten-field forms and full-screen pop-ups cost you enquiries.
- There is no Russian or English version. Buyers in Baku search in both Azerbaijani and Russian, and foreign clients and partners need English. An auto-translate widget does not create separate pages for Google and looks unprofessional.
- Traffic, but no leads. Ads bring visitors, but forms stay empty, prices and terms are missing, and the WhatsApp button is hidden or absent.
- Every change needs a developer. You cannot update a price, add a product or a promo banner yourself, the developer who built the site is unavailable, and the company has no hosting access.
- Outdated CMS and plugins. The platform and modules have not been updated for years, and there is no HTTPS or the certificate is about to expire — a security and browser-warning risk.
- No clear analytics. GA4 is not set up, the Meta Pixel is installed but sends no events, and nobody can say which campaign produced a sale.
- The site describes a different company. After a rebrand, new business lines or entering a new market, the site still shows old services, old contacts and an old visual style.
Website redesign or a new site from scratch: how to decide
In Baku, "redesign" is often used for two different jobs. The first is refreshing the design and templates on the same platform: the look, mobile layout, blocks and copy change, while the platform and page addresses stay. The second is effectively a new website: moving to a new CMS or a custom build, a new structure and often new URLs.
| Criterion | Redesign on the current platform | New site with a move to a new CMS |
|---|---|---|
| Platform and code | Stay; templates and blocks change | New CMS or custom development |
| Page URLs | Usually kept | Often change; a 301 redirect map is required |
| SEO risk | Lower | Higher, but manageable with a proper migration |
| Timeline | Shorter | Longer: structure, content, integrations, testing |
| When to choose | Platform is supported; the problem is design, speed, usability | CMS is outdated; you need new languages, CRM, payments, a client area |
A simple rule: if most of the signs above concern the "insides" — platform, languages, integrations, an awkward admin panel — a cosmetic redesign will not fix them, and you will end up paying twice.
When not to redesign
- Leads arrive but do not turn into sales. The problem is usually handling: slow replies, no CRM, managers losing enquiries. Fix that first.
- A sales peak is coming. A training centre before intake, or a developer before launching sales of a new phase, should move the launch to a quieter period.
- Nobody can prepare content. A new design with the old copy and photos achieves little.
- The goal is "just make it prettier". Without a task and a metric (leads, conversion, speed, new languages), a redesign turns into an argument about taste.
Audit before the redesign: pages with traffic, forms, analytics
The most expensive mistakes happen because nobody recorded what actually worked on the old site. Before the first mock-up, build three lists.
Pages that bring traffic
- Search Console → Performance → Pages for the maximum period (16 months): every URL with clicks and impressions. How to use the tool is covered in what Google Search Console is.
- GA4 → Landing pages: which pages receive organic, paid and social traffic.
- Search Console → Links: which pages external sites — directories, media, partners — link to. You cannot afford to lose these addresses.
- A full crawl with a crawler such as Screaming Frog: every URL, title, description, H1, canonical, status code, image and PDF.
Forms and contact channels
List every form and where its submissions go — email, CRM, Telegram, a spreadsheet. Add call and WhatsApp buttons, live chat and calculators. Send a test enquiry from each form and note who receives it.
Analytics and ad events
Record which tags are installed — GA4, Google Tag Manager, Meta Pixel and Conversions API, TikTok Pixel, Google Ads conversions — and which events they send. If your Meta campaigns optimise for the Lead event and that event disappears or gets renamed after launch, the algorithm starts learning again and your cost per lead rises.
The audit produces one table: old URL, traffic, external links, decision (keep, merge, remove) and new URL. That table becomes your redirect map. At Advertol a redesign starts with exactly this table and the event list, not with mock-ups: design changes quickly, while lost organic traffic and disrupted ad learning take a long time to recover.
SEO during migration: 301 redirects, URLs and hreflang for az/ru/en
A redesign without losing rankings rests on three things: redirects, URLs and language versions. The official instructions are in Google's guide to moving a site with URL changes.
301 redirects when the site changes
- Each old URL points to the closest matching new page, one to one.
- Use 301 (permanent) only — not 302 and not JavaScript redirects.
- Do not send everything to the homepage: Google may treat those pages as soft 404s and not pass on their value.
- No chains: the old address goes straight to the final one.
- Cover the variants: http and https, www and non-www, trailing slashes, old ad links with UTM tags, PDFs and images.
- Keep redirects for at least a year, and ideally never remove them.
Keep URLs where you can
The best redirect is the one you never need. If a page address is short and clear, keep it. If you change it, use Latin characters: transliterate Azerbaijani letters (ə → e, ş → s, ç → c), and do not use Cyrillic in Russian-version URLs — when pasted into WhatsApp or social media, those links turn into long strings of encoded characters.
hreflang for az/ru/en
Each language version needs its own address, for example /ru/ and /en/ folders, rather than switching language on one URL with a cookie or script. Every page lists all versions, including itself, plus x-default:
<link rel="alternate" hreflang="az" href="https://example.az/xidmetler/" />
<link rel="alternate" hreflang="ru" href="https://example.az/ru/xidmetler/" />
<link rel="alternate" hreflang="en" href="https://example.az/en/xidmetler/" />
<link rel="alternate" hreflang="x-default" href="https://example.az/xidmetler/" />
Common mistakes: no return link from the Russian page to the Azerbaijani one, the Russian version's canonical pointing to the Azerbaijani page, and machine-translated text instead of a real translation. Details are in Google's guidance on localized versions.
Technical pre-launch checklist
- The staging site is password-protected, and after launch the live site has no noindex and no robots.txt block.
- Canonicals point to the new addresses, not to the staging domain.
- A new sitemap.xml is ready and submitted in Search Console.
- Titles, descriptions and H1s of pages with traffic are carried over or improved, not wiped by a template.
- Structured data (organisation, breadcrumbs, FAQ, products) is carried over.
- If the domain changes, the Change of Address tool in Search Console has been used.
Structure and content: what to keep, what to rewrite
Build the structure around what customers search for, not around how the company is organised internally. Menu logic, levels and sitemaps are covered in how to plan a website structure.
Keep: pages with traffic and external links, copy the site already ranks with (do not cut it to two paragraphs for the sake of design), reviews, case studies and FAQ answers.
Merge: duplicates and thin pages with similar intent — for example, five pages about the same service in different Baku districts with no unique content. Build one strong page and 301 the old ones to it.
Rewrite: copy with no specifics — no starting prices, terms, timelines or photos of real projects. The Russian version should be written by someone who thinks in Russian and knows how Russian speakers search, not translated from Azerbaijani: people type "редизайн сайта", not a literal translation of an Azerbaijani phrase. An English version makes sense if you have foreign clients, partners or investors.
Add: pages for services and questions customers ask your managers but cannot find answered on the site. And on every screen, a clear next step: WhatsApp, a call or a short form.
Integrations: CRM, online payments, WhatsApp, ad tracking
A redesign is a convenient moment to connect the site to sales, not just to refresh the visuals.
- CRM. Every enquiry lands in the CRM with its source, UTM tags and the page it came from. Then you can see which campaign brings sales, not just clicks.
- Online payments. For online shops and service bookings, connect a payment gateway from a local bank or payment provider, accepting AZN by Visa and Mastercard. Before launch, test a payment, a refund and the customer email.
- WhatsApp. In Baku many customers would rather message than fill in a form. A button that opens a pre-filled message naming the page or product saves the manager the first clarifying question. Track clicks on it as an event. With high volumes, connect the WhatsApp Business API and a bot.
- Ad tracking. Meta Pixel together with Conversions API, GA4 events and Google Ads conversions. Keep key event names unchanged so ad algorithms do not start learning from zero.
An example from practice: for Momento Travel, Advertol built a custom CRM that brings several WhatsApp numbers, Instagram and Facebook into one sales panel (Momento Travel case). When the website feeds enquiries into a system like this, none get lost between channels.
Launch and the first 30 days
Launch day. Do not launch on a Friday evening or right before holidays such as Novruz: if something breaks, nobody will be around to fix it. Right after the switch, crawl the list of old URLs and confirm each returns a 301 to the right page. Send a test enquiry from every form and check payments and pixel firing.
Days 1–3. Submit the new sitemap in Search Console and request indexing of key pages through URL Inspection. Check the indexing report for 404 and 5xx errors.
Weeks 1–2. Compare clicks and impressions with the same period before launch. Every new 404 that had traffic is a missed redirect — add it. Confirm enquiries reach the CRM with their source.
Weeks 3–4. Track rankings for key queries in all three languages, form conversion rates and cost per lead in your ads.
Some ranking fluctuation in the first weeks after a major migration is normal while Google recrawls the site. The real warning sign is a sharp traffic drop on specific pages. The cause is almost always a missed redirect, a forgotten noindex or deleted copy that used to rank.
If you need more than a cosmetic redesign — a site connected to your ads, CRM and WhatsApp — see the website development Baku page. Advertol is a digital marketing and IT agency in Baku, Azerbaijan: Meta and Google ads, SMM and content production, websites and mobile apps, CRM systems and AI automation in one team. Book a free strategy call at /randevu: we will review your current site and traffic and work out whether you need a redesign, targeted fixes or a new website.
Frequently asked questions
How long does a website redesign take?
It depends on scope: refreshing the design on the current platform takes noticeably less time than moving to a new CMS with new languages and integrations. Content and approvals stretch timelines more than coding does. A realistic plan comes after auditing the pages and integrations.
Will I lose rankings after a redesign?
Short-term fluctuations are possible while Google recrawls the site. If URLs are kept or redirected one to one with 301s, copy and meta tags are carried over and hreflang is set up correctly, the risk of a serious drop is much lower. Nobody can guarantee rankings, but the consequences of migration mistakes are predictable and preventable.
Do I need to change the CMS during a redesign?
Not always. If the platform is supported, fast and lets you edit content yourself, updating the templates is enough. Moving to a new CMS makes sense when the current one is outdated or cannot handle multiple languages or the integrations you need.
Can I keep my old domain?
Yes, and it is usually the best choice: a domain with history and external links is an asset. Change it only for a rebrand or a move to a .az domain, and then you need redirects from every old address plus the Change of Address tool in Search Console.
What drives the cost of a website redesign in Baku?
The number of pages and languages, the amount of new content, a move to a different CMS, integrations (CRM, payments, WhatsApp API) and design complexity. SEO migration and analytics setup are separate pieces of work that should be written into the contract. That is why proposals can only be compared fairly after an audit and a brief.