
BrickDistrict · Full-stack web development
58x more Google impressions for a LEGO e-commerce store
- weekly Google impressions
- 137 → 8,020weekly Google impressions
- mobile Lighthouse, home page
- 60 → 98mobile Lighthouse, home page
Technical SEO
Most SEO problems are code problems: slow pages, pages Google won't index, product details it can't read. I fix them where they live, then help you publish what people actually search for. One LEGO store went from 137 to 8,020 weekly Google impressions.
Is this you?
What you get
Lighter pages that load fast on a phone. On one store the home page went from 60 to 98 on Google's mobile speed test, with its main content showing in 2.2 s instead of 9.1 s.
Sitemaps, canonical URLs, a redirect for every old link, and near-empty pages kept out of the index, so Google spends its time on the pages that matter.
Product, FAQ, article and breadcrumb data that tells Google exactly what each page is, and makes it eligible for rich results.
Product descriptions, buying guides and location pages created from your own data, and checked before they go live.
Search Console, Bing, Google Analytics and Merchant Center set up properly, with search data from several tools in one dashboard.
Proof

BrickDistrict · Full-stack web development
19
live sites from one codebase
US marketing agency · Full-stack web development
7 min read
FAQ
Regular SEO is mostly content and links. Technical SEO makes sure Google can find, load and understand every page: speed, indexing, redirects and structured data. Without it, good content can still fail to rank.
Speed and indexing fixes show up in Search Console within weeks. On one store, weekly Google impressions went from 154 to 5,280 in the three weeks after the new site went live, and kept climbing.
Yes. Every old URL gets a single redirect to its new page, the old and new sites are compared page by page before launch, and Search Console is watched afterwards. BrickDistrict moved off its page builder with all 519 pages checked.
Both. I have done technical SEO on a WooCommerce store with a custom WordPress theme, and on a Next.js platform that runs 19 sites from one codebase.
I build what makes content work at scale — descriptions generated from source data, buying guides and location pages — and check it before it is published. Your team or a writer can own the voice.
Tell me what you are building and where it hurts, and I will come back with questions or a plan.