← All posts
5 November 2026

The frozen web: one in seven Latvian and Lithuanian footers says 2020 or earlier

Of Baltic sites that show a footer year, 14.6% in Latvia and 14.3% in Lithuania say 2020 or earlier. Four signs of an outdated website you can check yourself.

Most websites are never switched off. They stop being edited, and then they keep serving, renewing their certificate and answering visitors for years. The Baltic Web Audit, our near-census of the Latvian, Estonian and Lithuanian web in July and August 2026, put numbers on that frozen layer, and most of the signs it measured are ones an owner can check on their own site in a few minutes.

In short

Of Baltic sites that display a copyright year in their footer, the year is 2020 or older on 14.6% of Latvian sites, 8.6% of Estonian and 14.3% of Lithuanian. That is one in seven in Latvia and Lithuania. The sitemaps agree: where they carry dates, the newest entry predates 2025 on 15.8% of Latvian sitemaps, 16.5% of Estonian and 18.0% of Lithuanian. And at least one JavaScript error fires on homepage load on more than a quarter of rendered sites in every country. Four signs of an outdated website, the footer year, the sitemap date, console errors and an empty page source, can be checked without a developer; fixing what is behind the last three usually needs one.

The copyright line at the bottom of a page is the one date most sites show the public. The audit read it wherever a site displays one: on 16,698 Latvian sites, 22,790 Estonian and 34,348 Lithuanian. Every figure here is from the report’s frozen web chapter.

LatviaEstoniaLithuania
Footer year 2020 or older14.6%8.6%14.3%
Footer year 2025 or newer71.2%65.7%68.6%
Sitemap present on the live site45.9%55.4%50.3%
Newest sitemap date before 202515.8%16.5%18.0%
At least one JavaScript error on load26.9%28.8%27.9%

Estonia’s frozen layer is markedly smaller. Latvia is the most polarised of the three: it has the highest share of current footers and also the highest share of ancient ones, just ahead of Lithuania, with less in between. A Latvian site, in other words, tends to be either looked after or left alone.

An old year does not break anything. What it does is tell every visitor, in the last line they read before the contact details, that nobody has looked at the page for years.

The sitemap that stopped

A sitemap is the file that lists a site’s pages for search engines. One exists on 45.9% of live Latvian sites, 55.4% of Estonian and 50.3% of Lithuanian, and of the sitemaps that carry dates, the newest entry is older than 2025 on 15.8%, 16.5% and 18.0%. That is a site whose most recent listed content is at least a year and a half old.

The date matters more than it looks. Google’s own sitemap documentation says the lastmod value “should reflect the date and time of the last significant update to the page”, and that Google uses it “if it’s consistently and verifiably (for example by comparing to the last modification of the page) accurate.” A sitemap generated once at launch and never again either shows stale dates or, if pages did change, dates that do not match them.

The page that breaks while it loads

The neglect also shows while a page loads. At least one JavaScript error, a script on the page failing, fires on homepage load on 26.9% of rendered Latvian sites, 28.8% of Estonian and 27.9% of Lithuanian. That is out of the homepages the audit could fully load in a browser: 36,838 in Latvia, 62,883 in Estonia and 73,252 in Lithuania. The rate is almost identical in all three countries.

Many such errors are harmless. Some are the menu, the contact form or the cookie banner quietly not working, and the owner is usually the last to find out, because the browser hides the error unless someone opens the console.

The page that is not there until a script builds it

A small slice is frozen in the opposite way, too modern rather than too old. On 3.1% of rendered Latvian sites, 2.1% of Estonian and 2.0% of Lithuanian, the page a browser finally displays holds more than ten times as much as the file the server sent. The file is effectively empty and JavaScript builds the page afterwards. The report notes that such sites are largely invisible to any crawler that does not run a full browser, which includes most AI crawlers. We covered how sites end up like this in our piece on Lovable sites in production.

One relic is warmer than expected: an RSS or Atom feed is still advertised on 25.4% of living Latvian sites, 37.7% of Estonian and 34.1% of Lithuanian. That is not a defect. The report suggests platforms ship a feed by default and nobody turns it off.

What you can check yourself, and what needs a developer

Four checks need no developer:

  • Read your own footer. If the year is old, change it where the footer is edited, usually a footer setting or block in your site’s editor. If the year is typed by hand, it will be wrong again next January.
  • Open your sitemap. It is usually at /sitemap.xml on your domain, or at the address listed in your /robots.txt. Look at the newest date. If you have changed pages this year and the sitemap says otherwise, the sitemap is not being regenerated.
  • Open the browser console on your homepage. In Chrome, press Ctrl+Shift+J on Windows or Linux, or Cmd+Option+J on a Mac, then reload the page. Red lines are errors. Note how many there are and which addresses they name.
  • Check that your text is in the page source. Right-click the homepage, choose View page source, and search for a sentence you can see on screen. If it is not there, the page is built by a script after it loads.

What needs a developer is the cause behind the last three. A sitemap that does not regenerate is usually a plugin setting or a file someone made by hand at launch, and replacing it means knowing which. Console errors have to be traced to the script that throws them and checked against what they break, which may be a plugin, a theme or a third-party tag. A page that only exists after a script runs needs server rendering, which on most sites is rebuild-scale work rather than a setting. Making the footer print the current year is a one-line change for a developer and a permanent end to the stale year. Keeping a site from drifting back is what a monthly care plan is for; what one should include is written up separately, and ours are here.

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. Speed, the other thing an untouched site loses, is in the six-second web.

If you want a second pair of eyes on whether your own site has frozen, send us the address and we will tell you what we see.

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