← All posts
15 November 2026

How many pages should a website have? In the Baltics, about 40

Among Baltic sites with a sitemap, half list 37 pages or fewer in Latvia, 35 in Estonia and 44 in Lithuania. What that means when you scope a new site.

Every website quote starts with the same question: how many pages? Owners often do not know, and the quote is built on a guess. The Baltic Web Audit, our near-census of the Latvian, Estonian and Lithuanian web in July and August 2026, can answer it with a measurement instead of an opinion, because a sitemap is a site’s own list of its pages and we read every one we found.

In short

Among Baltic sites that publish a sitemap, half list 37 pages or fewer in Latvia, 35 in Estonia and 44 in Lithuania. A quarter list 10 or fewer, and one in ten lists just 2. Only about half of live sites publish a sitemap at all, and those tend to be the better-built half, so the typical Baltic website is about 40 pages, and probably smaller. That is a benchmark, not a target: the right number for a site is one page for each distinct question a buyer needs answered before they get in touch. You can count your own pages in a minute from your sitemap; the redirects in front of your homepage are the part that usually needs whoever runs your hosting.

The typical Baltic website, measured

Every figure here is from the report’s chapter on site size.

LatviaEstoniaLithuania
Median pages listed in the sitemap373544
Homepage weightabout 73 KBabout 73 KBabout 85 KB
Average detected technologies per site6.57.37.6
Average addresses before the homepage arrives2.192.052.07
Sites with a chain of three or more redirects11,41312,88915,090

The report’s own summary is the most useful line in it: the typical Baltic website is a forty-page brochure with a two-hop front door. Its handful of detected technologies is the usual kit: a CMS, a theme, a few plugins, an analytics tag.

Two cautions on the page count. A sitemap lists whatever the site’s software puts in it, which on a site with a blog includes every post, so a forty-page sitemap can be a handful of designed pages and a few years of news. And the sites without a sitemap are not counted at all. They tend to be the less looked-after half, which is why the report says the typical site is probably smaller than the median.

What Google calls a small site

Google’s sitemap documentation gives the one external yardstick worth knowing here. It says you might not need a sitemap if your site is “small”, and adds: “By small, we mean about 500 pages or fewer on your site.” The same page sets two more conditions: that the site is comprehensively linked internally, and that it does not have many media files or news articles you need to appear in search.

By that definition the typical Baltic site is small, at under a tenth of Google’s threshold. So at this size the page count is not what decides whether search engines can find a site; how the pages link to each other and what is written on them does. The report found no meta description, the summary a site writes for its own search result, on 44.0% of Latvian homepages, 49.9% of Estonian and 45.1% of Lithuanian (covered in Latvian here). That is a bigger gap than any missing page.

How many pages your site should have

Start from what a buyer has to find out before they contact you, not from a number. For most businesses that is a short list:

  • What you do, one page per service a buyer would compare separately. Two services that are always bought together can share a page.
  • Who has bought it, a page of work or clients, with enough detail to be believable.
  • What it costs or how it is priced, even if the answer is a range or the factors that move the price.
  • Who you are and how to reach you.
  • The questions you answer on every sales call, each as its own page or as an article, because those are the pages people search for.

Without the last item, that list is often ten pages or fewer, which is where a quarter of the Baltic web sits. The last item, articles and answers, is what takes a site towards the median and beyond, and those are also the pages that earn search traffic over time. A site with fewer pages than services is usually missing something, and a buyer who cannot find their exact service tends to assume you do not offer it.

For a quote, the total matters less than the number of different kinds of page. Forty pages built from five templates is a smaller build than fifteen pages that are each laid out differently. Our cost calculator takes a page count and gives a first range; when you send a brief, list the kinds of page as well as the total.

The two-hop front door

The audit also measured what happens before a homepage appears. On average, a visitor is bounced through about two addresses before the page arrives: 2.19 in Latvia, 2.05 in Estonia, 2.07 in Lithuania. Chains of three or more redirects run on 11,413 Latvian, 12,889 Estonian and 15,090 Lithuanian sites.

A redirect is usually the site moving the visitor from http to https, from the bare domain to www, or from one language path to another. Each one is harmless on its own and each one costs time. Chrome’s own performance guidance is direct about it: “Redirects slow down your page load speed”, because the browser has to make another request at the new address before it can load anything, and its document latency check flags a page whose first request “was redirected one or more times”. Search engines will follow a chain, Google’s crawlers up to 10 redirect hops by default, but a visitor on a phone pays for every hop before seeing anything. Speed on a phone is its own story, told in the six-second web.

What you can check yourself, and what needs a developer

Two checks need no developer:

  • Count your pages. Open /sitemap.xml on your domain, or the address on the Sitemap: line of your /robots.txt. If it is an index pointing to other sitemaps, open each one. Count the addresses, then count how many of them are pages you designed and how many are posts, tags or archives. If there is no sitemap at all, most website platforms can generate one from a setting or a plugin. While you are in it, look at the newest date, which our frozen web piece explains.
  • Count your redirects. Run your homepage through PageSpeed Insights, typing the address the way an old link or bookmark might carry it, for example http:// and without www. If the Document request latency insight says the request was redirected, your front door has at least one extra hop. Try the other variants too: each one should land on the final address in a single step.

What needs a developer is fixing the redirects. The usual cause is two rules applied one after another, one for https and one for www, where a single rule should send every variant straight to the final address. That rule lives in the server configuration, the hosting panel or the CDN, and changing it on a live site means knowing which of those is answering first. Adding pages is the other half: deciding which ones a buyer actually needs is a scoping conversation, and that is the work we do at the start of every build.

Why we can say any of this

The figures come from a near-census rather than a sample. We measured 293,806 of the 306,872 Baltic domains in our frame across July and August 2026, from one fixed location, with a crawler that identified itself honestly on every request. Everything is published as an aggregate and no individual site is named beside a weakness.

If you are scoping a new site and want a second opinion on what it needs, send us the address of the current one and we will tell you what we would keep.

Tell us what’s broken.
We’ll tell you the truth.

Book a free call →
Reply within one business day · EN / LV
↑↓ navigate · ↵ open · esc close