
Website development on Next.js, with the technical SEO included
I build websites on Next.js, Sanity and WordPress and handle their technical SEO myself — Core Web Vitals, structured data and crawlability decided during the build rather than retrofitted afterwards.
What you get with a site built this way
One person writes the code and runs the SEO
You brief me and I build it. No account manager relaying requirements to a developer who never spoke to you, and no separate SEO invoice arriving three months later for work that should have been done during the build.
Next.js, Sanity or WordPress — chosen for the job, not for habit
Next.js with a headless CMS where speed and scale matter, WordPress where the team needs a familiar editor. I tell you which one your project actually needs and why, including when the cheaper option is the right one.
Multilingual from the first line of code
English, Polish and Russian in one codebase, with hreflang, per-language URLs and a CMS where an editor can work in their own language. Retrofitting this into a single-language site later costs more than building it in from the start.
Core Web Vitals treated as a requirement, not a nice-to-have
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift measured against real field data, not a lab score screenshotted once on launch day.
Structured data so machines can read what you sell
Schema.org markup describing the organisation, its services and its location, rendered in the server HTML. This is what search engines and AI assistants read when deciding whether your business answers someone's question.
I build websites on Next.js, Sanity and WordPress, in English, Polish and Russian, and handle their technical SEO myself.
That combination is the point. Most projects split the work: an agency builds the site, an SEO specialist arrives afterwards and finds decisions already baked in that cannot be undone cheaply — a URL structure that cannot carry three languages, a rendering approach search engines struggle with, a CMS that makes structured data impossible. When the same person does both, those decisions get made once and correctly.
Working directly with me also means no agency overhead and no intermediaries: the person who answers your first message is the person who writes the code and the person you call when something breaks a year later.
Problems I solve when developing websites
Builds in several languages
Roughly half of what I build runs in more than one language, and the technical setup for it is decided at the start rather than added later: per-language URLs, reciprocal hreflang, and a CMS where each language is a document an editor can work on independently.
That work has its own page, with the pricing, the failure modes I get called in to repair and a case running in four languages: multilingual website development.
| Problem | Solution |
|---|---|
| Your website loads slowly and loses visitors | I optimize code, images, and hosting so it ranks in the top 3% for Google PageSpeed |
| You don’t get clients from your website | I structure and optimize your content for conversions and SEO |
| Template builders limit your flexibility | I develop fully custom websites, scalable and editable without constraints |
| Your site isn’t mobile-friendly | I design and code with a mobile-first mindset for all screen sizes |
| You need a website built to evolve and scale alongside your business | I create modular, scalable architectures powered by Headless CMS solutions and cutting-edge web frameworks. |
Why a professional build instead of a website builder
Platforms like Wix or Squarespace are perfect for launching quickly, and if that is genuinely what you need, use one. They fall short when the site has to carry several languages, rank for competitive terms, integrate with systems you already run, or survive three years of growth without a rebuild.
Most of my clients come to me after trying a builder and finding that templates cannot solve business problems. Builders limit control over rendering, URL structure, markup and page weight — which is to say, over most of what determines whether search engines and AI assistants can use your pages at all.
What a custom build gives you that a template cannot
- Control over rendering and page weight, which is where Core Web Vitals are won or lost
- A URL structure and hreflang setup that carries every language properly
- Schema.org structured data describing your organisation and services in the server HTML
- Integrations with the CRM, payment and booking systems you already use
- A codebase that can grow instead of being replaced
How the development process works, step by step
Brief and analysis. Your niche, audience and goals, plus what the site has to do in your sales process. If you have an existing site, this is where I look at what is worth keeping.
Structure and wireframes. The user journey, the core sections, the URL structure, and — for multilingual projects — which languages each page exists in.
Development. Next.js, Sanity or WordPress, chosen in the previous step rather than assumed. Structured data and hreflang go in here, not afterwards.
Testing and optimisation. Responsive behaviour on real devices, Core Web Vitals measured properly, markup validated, and the whole thing checked against how a search engine and an AI assistant actually read it.
Launch and support. Deployment, search console setup, sitemap submission, and guidance for running it. I stay reachable afterwards, because the person who built it is the person who knows why it was built that way.
Specialised builds follow the same process: multilingual sites, catalogues with filters, sites with online booking, and platform migrations that keep the SEO traffic intact. All of them are listed on the full services page.
Some industries have a page of their own: a photographer website, an accounting firm website, an architecture studio website, a language school website, a recruitment agency website, a travel agency website, a cleaning company website, a restaurant website, a veterinary clinic website and a website for models.
Built and shipped: an investment platform with AI-guided learning, a digital agency website and a personal website with SEO.
When a site already exists and has rankings worth keeping, the work is a redesign without losing rankings rather than a build from scratch.
After launch the site does not look after itself: updates, fixes and small changes are covered by website maintenance and support.






