A new website is in development
Page structure, URLs and the metadata model can be settled before content and migration.
Technical SEO
Technical SEO starts with site structure, not repeated keywords.
Technical SEO helps search engines discover, index and interpret a business website in Estonia. We review URLs, canonicals, multilingual hreflang, metadata, internal links, sitemaps, semantic HTML, mobile performance and the measurement foundation.
Discuss a projectWhen to review technical SEO
The website becomes multilingual
Canonicals, hreflang, language switching and the sitemap must describe the same URL model.
Indexing is unclear
Duplicates, redirects, robots rules, internal links and rendering need technical review.
Technical SEO connects content and architecture
Each search intent has an owner page
The architecture should distinguish the purpose of a service, category, product and case study. If several URLs answer the same question with nearly identical content, adding a keyword is not a solution; the site needs an owner page, useful supporting links and a coherent canonical rule.
Migration preserves valuable addresses
Before release we compare old and new URLs, search landing pages, language versions and removed content. Every old address worth retaining receives one permanent redirect to the closest meaningful replacement rather than a blanket route to the home page.
Rendering and performance affect discovery
We verify that primary content and links are present in HTML, images have dimensions and the mobile layout does not hide important material. Performance is reviewed by representative page template; one laboratory score is evidence for diagnosis, not a promise of rankings.
Technical SEO work areas
Technical SEO work areas
- Crawl, index and canonical rules
- Localised URLs, hreflang and x-default
- Titles, descriptions, heading structure and internal links
- Sitemaps, redirects and justified structured data
- Mobile performance, analytics and Search Console handover foundations
What a technical review needs
A canonical page and language plan
We need a page tree or URL list with each page’s purpose, language and content owner. A migration also requires the old URL inventory and available evidence about the most important landing pages.
Rendering and editing boundaries
We clarify which content comes from the server, which is loaded later and who can edit metadata. This separates engineering defects from editorial work and avoids multiple conflicting sources for the same field.
A measurement baseline
Where analytics or Search Console already exists, a summary of indexing issues and important pages is enough; passwords and raw exports do not belong in public documentation. For a new site we name the owner of post-launch checks.
From obstacles to implemented fixes
Indexing review
Compare canonical URLs, redirects, sitemaps and robots behaviour.
Content and structure
Confirm one owner page per intent and descriptive internal links.
Technical implementation
Correct metadata, localisation, semantics and structured-data models.
Measurement
Document checks and hand over monitoring points. Rankings, traffic and leads cannot be guaranteed.
Checks before and after release
Checks before and after release
- Canonical, hreflang and x-default target canonical URLs
- The sitemap contains only indexable pages
- An old URL reaches its meaningful replacement in one redirect
- Structured data matches visible content
- Primary content, links and metadata render as expected
Post-launch technical review
After release we sample canonical URLs, redirects, robots rules, sitemaps and language relationships. Changes visible in Search Console or analytics need time and separate interpretation. Handover distinguishes defects that should be corrected immediately from editorial work and longer-term observation.
Multilingual store URLs and content
Narva Kohvik
Narva Kohvik’s categories, products and languages show why URL structure, internal links and technical localisation must support actual shopping actions.
View case study
Technical SEO questions
Does technical SEO guarantee a Google position?+
No. It removes indexing obstacles and describes page meaning, but results also depend on content, competition, recognition and other factors.
Is an audit enough?+
An audit identifies problems and priorities. Impact requires implementing fixes in code, content or configuration and checking them after release.
Why does each language need its own URL?+
A separate URL lets search engines index each language, set its canonical and connect equivalents through hreflang.
When should structured data be added?+
Only when the schema matches visible page content and the selected type. Ratings, prices or other fields should not be added only to alter search presentation.
Technical SEO starts with site structure, not repeated keywords.
Briefly describe the goal, users, current solution and required functions. The first conversation will clarify the open questions and what discovery is needed before an estimate.