Website and online shop design
Online shops, corporate sites and landing pages built for conversion.
Shopify, Next.js or WordPress, whichever fits. Structured data, Core Web Vitals in the green and analytics from day one. With the legal notice, the privacy policy and the cookie consent Spanish law requires, not bolted on at the end.
Who it is for
- Brands with an existing online shop to improve
- Consultancies that need a corporate site
- Startups with an acquisition landing page
Why it ends up being needed
Hardly any website fails because of its design. It fails because of what you cannot see: four seconds to open on a phone with average coverage, a catalogue with no structured data so Google cannot tell what you sell, a form asking for consent in the wrong place, and analytics that count visits but cannot tell a visit from a sale.
The symptom people usually turn up with is a different one: «the site is fine but nothing comes in». And it is fine, in the sense that it looks fine. What happened is that it was built once, declared finished, and since then nobody has checked whether people find it, whether it loads, or whether visitors ever reach the end of the form.
So the first decision is not what it will look like but what it has to achieve. If it is to sell, the work goes into the product page and the checkout, which is where people drop out. If it is to capture leads, into the landing page and the form. If it is to reassure people who already know you, into speed and into what can be read in the first ten seconds.
What I deliver
- UI/UX design — Laid out in Figma, with a component system.
- Front-end development — Next.js 14 or Shopify Hydrogen with SSR/ISR.
- Technical SEO — Schema.org, sitemap, robots.txt and Core Web Vitals tuning.
- Analytics — GA4, Plausible or Matomo, plus the events that matter.
- Editorial CMS — Sanity, Contentful or an integration with WordPress.
- Legal texts and forms — Legal notice, privacy policy and consent, compliant with whichever data protection law applies to you, from day one.
What is included
- Designed for you, not out of a template
- Responsive, accessible development
- Technical SEO built in
- Training so you can maintain it yourself
What gets decided before a line is written
- Shopify, Next.js or WordPress — This is not picked by taste: it is picked by who will maintain the site and by the size of the catalogue. A shop with thousands of references and a non-technical team runs better on Shopify. A corporate site that has to rank and load fast, on Next.js. WordPress when it is already there, there is content worth keeping and rebuilding does not pay off.
- Where the page gets rendered — An application assembled entirely in the browser is comfortable to build and makes a search engine work for it. With server-side rendering — SSR or ISR — the HTML arrives finished, with its title, its description and its content inside. That is the difference between Google reading your page and having to run it to see it.
- Headless or all in one — Separating the content manager from the site buys freedom and adds one more piece to maintain. It pays off when there are several channels — web, app, screens — or an editorial team publishing daily. For eight corporate pages, it does not.
- What gets measured, and with what — The analytics tool decides whether you need a cookie banner at all. With Plausible or self-hosted Matomo no third-party cookies are set and the site can work without asking permission; with GA4 you do have to ask, and you have to honour the answer. That is a product decision, not a technical detail for the end.
What is not included
- Writing the commercial copy: that is the proposals and copy service.
- Product photography and video.
- Paid campaigns or ad management.
- Migrating a catalogue from a system that will not let you export it.
- The monthly maintenance afterwards, which is contracted separately.
What you need to have
- Access to the domain and its DNS, or to whoever holds it.
- The copy and the images, or the decision to commission them separately.
- One person who can decide and sign off each delivery.
- If there is a shop: the catalogue in an exportable format and the payment gateway already contracted.
Frequently asked questions
WordPress, Shopify or bespoke?
It depends on the case, and it is decided before any design work: a shop with a large catalogue is not run like an eight-page corporate site. What I do not do is start from the tool.
Will it load fast?
It ships with Core Web Vitals in the green and structured data. That is part of the scope, not a later improvement.
Can I edit the copy myself?
Yes. It comes with the content manager and the instructions to change text and images without depending on me.
How long does it take?
Discovery and design take two weeks, and from there the work is delivered in weekly instalments. The total depends on the number of templates and on the catalogue, and it is fixed in the quote before anything starts.
I already have a site. Do you rebuild it or fix it?
It depends on what is there. If the problem is speed, structured data or the checkout, fixing what fails costs far less: that is the website review. If the foundation cannot carry what you need, rebuilding costs less than patching it forever.
Will I lose the rankings I already have?
Not if it is planned. Old addresses are redirected one by one to their new equivalent, and the ones with no equivalent are decided before going live. What loses rankings is not changing your site, it is changing it and leaving hundreds of dead addresses behind.