blizgantitvarka.com rebuildWordPress/WooCommerce → Next.js 16, nine legacy sitemaps, zero lost rankings
Rebuild of Blizganti Tvarka — Vilnius-based home-organization studio — from a crowded WordPress/WooCommerce stack onto Next.js 16 + MDX. Retired the full e-commerce surface, rewrote every SEO landing page in Lithuanian, and preserved 100% of organic equity across nine legacy sitemaps.
Visit live siteBlizganti Tvarka is a Vilnius-based home-organization studio with a high-traffic Lithuanian blog and a meaningful organic footprint across queries like namų organizavimas, kilimų valymas, and organizuoti stalčiai. After years on WordPress with a bolted-on WooCommerce storefront that nobody wanted to maintain, the brief was unambiguous: rebuild without losing a single ranking, and retire the store on the way out.
We started with the sitemap. Nine of them, actually — page, post, product, product category, product tag, category, post tag, author, and an e-landing sitemap for course content. Every URL was accounted for before any code was shipped. The rule was one 301 hop max, never chained, always direct to final destination. WooCommerce URLs redirect to a curated Amazon-affiliate editorial page; cart and checkout redirect to the contact flow; tag archives consolidate into the main blog index where they add link equity instead of fragmenting it.
On the build itself: Next.js 16 App Router with Cache Components enabled from day one, React 19.2 with native View Transitions for card → detail morphs, MDX as the content format, Framer Motion for motion, and shadcn/ui over Radix for primitives. Typography is Fraunces Variable for editorial hierarchy and Inter Variable for interface text. Static pages are fully prerendered; the two dynamic surfaces — contact form and newsletter — run as App Router route handlers with Upstash rate limiting.
The copy rewrite was the heavy lift. Every legacy SEO landing page — 800-word WP stubs at best — was rewritten as 800–1,500-word topical-authority-grade Lithuanian content, addressing the reader as tu, avoiding stock phrases, and linking into at least three supporting articles plus a service page. Gated course lessons became public teaser articles, keeping their rankings intact while CTAing into the paid course.
The result: a Lighthouse-mobile score of ≥98 across every route, LCP under 1.8 seconds on 4G-throttled Android, 100% of indexable legacy URLs resolving in one hop, and a WooCommerce surface that exited without a single 404 in Search Console. Shipped on Vercel's Frankfurt region with the full nine-sitemap redirect map documented in-repo for auditability.
Features that made the difference.
Nine-sitemap redirect map
Every URL across page, post, product, category, tag, author, and e-landing sitemaps was either preserved at the same path or 301'd to the closest canonical — in one hop, never chained.
WooCommerce retirement, no storefront regret
The store, cart, checkout, customer accounts, and product catalog were removed. Product URLs redirect to a curated Amazon-affiliate page; commerce pages redirect to the contact flow.
Rewritten Lithuanian SEO copy
Every service page and blog article rewritten from thin 200–300-word WP stubs into editorially dense 800–1,500-word Lithuanian copy. Keyword-aligned headings, internal linking, and topical authority built in.
Magazine-grade editorial shell
Fraunces Variable + Inter Variable typography, Framer Motion section reveals, View Transitions for card→detail morphs, MDX article pipeline with rehype-autolink-headings and prose-tuned Tailwind Typography.
Course teaser strategy
Rather than 301 gated course lessons to the sales page and lose their indexed content, each lesson became a public 500–900-word teaser article that ranks on its own keyword and CTAs into the paid course.
Two inboxes, one mailbox
Consultation form and designer-training inquiry form land in info@blizgantitvarka.com via Resend, with Upstash-backed sliding-window rate limits on the API route.
How it works.
Inventory every indexed URL
Pulled all nine legacy sitemaps and built a single master redirect map before a line of code was written.
Rewrite, don't port
Treated the old WP copy as a baseline to beat, not a draft to keep. Every landing page and article rewritten for 2026 search intent.
Ship Next.js 16 from day one
Committed to Cache Components, the new proxy.ts runtime, and React 19.2 View Transitions — no migration debt built in.
Deploy behind Vercel fra1
Frankfurt region for Baltic latency, edge-cached static pages, Upstash-rate-limited API routes, and GA4 behind consent.
Services used.
Let's work together.
Tell us what you're building. We'll come back within one business day with a shortlist of next steps.