Sometimes a client comes to a studio with a request like: “I want to add functionality – but something isn’t right.” We start digging, and the usual picture appears: the site was built on a website builder, “translations” are handled by an auto-translator, payments are connected through a strange mix of widgets, and most importantly – the site isn’t indexed, there’s no organic traffic, and there’s no reliable tracking.
The problem isn’t a specific platform or “bad design.” The problem is that the project started with visuals instead of a launch plan: goals, structure, SEO foundations, data, consent, and ownership of access.
Below is a clear roadmap you can use as a step-by-step process before launching almost any website (B2B, services, content sites, lead generation, e-commerce).
STEP 1
Website Goal, KPIs, and 3 Key Conversions
STEP 2
Geography and Languages: Which Markets the Site Serves
STEP 3
Domain Name and TLD: A Choice Without Surprises
STEP 4
Keyword Research → Page Map (The Foundation of Structure)
Step 1. Website Goal, KPIs, and 3 Key Conversions
Before any wireframes or CMS choice, write down (in 5–10 lines):
- the website goal: leads / sales / bookings / quote requests / brand;
- 3 key conversions (example): contact form submission, phone call, brief/meeting request;
- KPIs: lead conversion rate, CPL/CPA, share of organic traffic, lead quality, speed (CWV).
Why this matters: if success isn’t measurable, the team will argue about “looks good / looks bad,” not about outcomes.
Step 2. Geography and Languages: Which Markets the Site Serves
Decide upfront:
- regions: city / country / multiple countries;
- how many languages you can realistically support with content;
- how the URL architecture will be built:
- subfolders (/lv/, /en/) – often the best starting point,
- subdomains (en.site.com) – sometimes justified,
- separate domains – more expensive and harder to maintain.
If you don’t lock in languages and regions early, you’ll later face issues with hreflang, duplicates, and canonicals.
Step 3. Domain Name and TLD: A Choice Without Surprises
Check:
- readability and how easy it is to dictate/spell;
- legal risks (similar names/trademarks);
- domain history (reputation and potential penalties);
- domain ownership (the domain must be registered to the business owner).
A domain is an asset. Losing control of it is easier than it seems.
Step 4. Keyword Research → Page Map (The Foundation of Structure)
This is the most underestimated step.
Instead of “we’ll just make a Services section and that’s it”:
- collect service/product topics + customer pains/tasks;
- gather queries and group them into clusters;
- build a page map: 1 cluster = 1 landing page;
- prioritize: what belongs in the main menu and what can go into the blog.
Result: you know exactly which pages you need – you’re not guessing.
STEP 5
Website Structure and Prototypes (Wireframes) – Before Design
STEP 6
Technology and CMS Choice: Not “What’s Trendy,” but What Can Scale
STEP 7
Integrations and Data Logic: Forms, CRM, Email, Payments (If Any)
STEP 8
GDPR and Google Consent Mode v2 – Before Analytics and Pixels
Step 5. Website Structure and Prototypes (Wireframes) – Before Design
Based on the page map, create wireframes for key templates:
- Homepage;
- service page (as a product/service landing page);
- case study page;
- contacts / lead-gen page;
- blog/article page.
The goal of a wireframe is not beauty – it’s logic: sections, arguments, CTA, navigation.
Step 6. Technology and CMS Choice: Not “What’s Trendy,” but What Can Scale
This phrase is the perfect selection criterion. Before deciding “we’ll build it on X,” verify:
- SEO control: URLs, metadata, canonical, redirects, hreflang, schema, sitemap;
- multilingual support (fully indexable versions, not “auto-translation”);
- integrations: CRM (including custom-built), forms, email, chat, BI;
- speed and stability (CWV, caching, CDN if needed);
- security and updates;
- content editing usability (marketing must be able to update the site without pain).
If the platform can’t scale, “adding just a bit of functionality” turns into an expensive rebuild.
Step 7. Integrations and Data Logic: Forms, CRM, Email, Payments (If Any)
Describe upfront:
- which forms are needed and which fields (no excess – but enough to qualify a lead);
- where the lead goes (CRM, email, Telegram/Slack – with clear rules);
- notifications and SLA for processing requests;
- if payments exist: flow, statuses, errors, confirmations, refunds, funnel analytics.
This reduces the risk of “weird integrations” that nobody can maintain later.
Step 8. GDPR and Google Consent Mode v2 – Before Analytics and Pixels
Define:
- which cookies/scripts will be used;
- what loads before consent and what only after;
- Privacy Policy / Cookies Policy texts;
- requirements for the consent banner and preference center.
Consent is architecture – not “a banner at the bottom.”
STEP 9
Website Goal, KPIs, and 3 Key Conversions
STEP 10
Geography and Languages: Which Markets the Site Serves
STEP 11
Domain Name and TLD: A Choice Without Surprises
STEP 12
Keyword Research → Page Map (The Foundation of Structure)
Step 9. Technical SEO Before Launch: Indexing Without Surprises
The minimum list that must be included in the technical spec:
- sitemap.xml (preferably auto-updating);
- Robots.txt;
- Canonical;
- hreflang (if multilingual);
- redirects (http→https, www/non-www, trailing slash rules, page migrations);
- proper 404/410 handling;
- internal linking and breadcrumbs.
Plus decide in advance what must not get indexed (utility pages, internal search results, parameters, etc.).
Step 10. Structured Data (Schema.org) and Content Standards
Plan the minimum schema set:
- Organization / LocalBusiness
- Service (service pages)
- Article (blog)
- BreadcrumbList
- FAQPage (where relevant)
And block standards for service pages:
- a short top summary/positioning;
- benefits and differentiators;
- process, timelines, what’s included;
- cases/proof;
- FAQ;
- a clear CTA.
This helps both SEO and AI systems “read” your content.
Step 11. Analytics and Ownership of Access: So the Project Is Manageable
Before launch, verify:
- GA4, GTM, and Search Console are created in the owner’s account;
- pixels and conversions are documented;
- domain/DNS/hosting are controlled by the owner;
- there is a list of all scripts, events, and goals.
This protects you from the situation where “everything belongs to the contractor and the business has no access.”
Step 12. Design and Template – Only After Structure and Requirements
Now design becomes efficient:
- it’s built on an approved structure,
- it accounts for SEO, analytics, and consent,
- it doesn’t require redesign “because something important was missed.”
Pre-Launch Checklist: What to Verify in 30 Minutes
- The site opens on a single canonical version (https, www/non-www) and all redirects are correct (301).
- There is no accidental noindex on key pages.
- robots.txt does not block important sections.
- sitemap.xml exists and includes the right pages.
- For multilingual sites, hreflang is configured and there are no duplicates.
- Canonical is correct on key pages.
- Forms work: submit → notification → lead recorded in CRM.
- Consent banner works: nothing unnecessary loads before consent; required scripts load after.
- GA4 and GTM receive key conversion events
- Search Console is connected and owner permissions are correct.
- A 404 page exists and does not return 200.
- Mobile speed is at least “not terrible” (quick basic check).
Let’s Walk Through This Roadmap Together
If you’re launching a new website or want to “grow” an existing one, the fastest way to save budget and nerves is to go through this pre-design roadmap with a specialist.
In a 60–90 minute consultation, we will structure your project end-to-end:
- Goal, KPIs, and 3 key conversions (what exactly we consider success)
- Markets and languages + correct URL architecture (so indexing doesn’t break)
- Demand-driven page map (keyword research → which service/landing pages you actually need)
- Structure and wireframes for key pages (what belongs in the menu vs. content)
- CMS/technology “for growth” (SEO control, multilingual, integrations, speed)
- Technical SEO before launch (robots/sitemap/canonical/hreflang/redirects)
- GDPR + Google Consent Mode v2 (so analytics and ads remain correct)
- Ownership of access and data (domain, hosting, GA4/GSC/GTM – all under the owner)
Consultation outcome: you get a clear action plan and a requirements list for your developer/studio – without “patchwork” fixes, auto-translation hacks, or indexing surprises.
To book a session, leave a request via the contact form on the website and write in your message:
“Website Launch Roadmap” – we’ll get back to you and schedule a convenient time.
