Services · Website development · Perfume websites
Codeeo offers perfume website development London fragrance houses use to be found, understood and contacted. We plan, design and build brand websites for heritage perfumers around St James's and Mayfair, niche boutiques in Marylebone and Covent Garden, oud specialists and young studios in East London. The site tells your house story, explains every scent properly, sends visitors to the right boutique or stockist and turns interest into consultation requests, trade enquiries and press contacts your team can act on.
This page is about the website itself: content, search visibility, enquiries and the systems behind them. If you also sell bottles online, the shop can sit inside the same build, but the work described here is about presence and the conversations it starts.
200+ companies servedFrom a first store to an ADX listed developer
What the website covers
A London shopper can walk past dozens of perfume counters between Piccadilly and Oxford Street, so your website is rarely where they first smell your work. It is where they check who you are, read about a scent they tried on a blotter, find the nearest place to try it again and decide whether to book time with your team. Overseas visitors do the same from their hotel or after they fly home. We build for those moments: house story and perfumer pages, a fragrance library written around notes and occasions, boutique and stockist pages that rank in local search, and enquiry routes for consultations, private commissions, corporate gifting, trade and press. Everything is edited by your own staff in a CMS set up around how your house talks about fragrance, with consent, accessibility and speed handled in the build rather than added later.
Each scent gets its own page with top, heart and base notes, the perfumer's intention, how it wears through the day and which seasons suit it. Filters by family, mood and occasion help a visitor who remembers only that they liked something smoky from a shop on Jermyn Street.
Visitors find the scent they tried and understand why they liked it.
A separate page for every London boutique or counter, with opening details your team updates, nearby stations, what each location stocks and LocalBusiness structured data so Google can match a search near Marylebone or Seven Dials to the right door.
More searches for perfume shops near a London postcode land on you.
A short form for scent profiling or wardrobe consultations that asks about preferences, the preferred boutique and a time window, then routes the request to that boutique's team. Confirmation and follow up go out from your own email domain.
Consultations arrive with the context staff need before the visitor walks in.
Dedicated pages and enquiry forms for private fragrance commissions, wedding scents and corporate gifting for City firms, with clear steps, typical lead times described in words and a place to upload a brief or mood board.
High value enquiries reach a named person instead of a general inbox.
Downloadable press kits, launch notes and image libraries for fashion and beauty editors, plus a gated trade area where approved stockists find price lists, training notes and point of sale artwork.
Editors and buyers help themselves, and your team answers fewer routine requests.
Language versions such as Arabic, French or Mandarin, each with hreflang tags and translated metadata, so a visitor who discovered you in London can find you again from home and know which boutique or stockist serves them.
Interest from tourists keeps working after they leave the city.
A journal for raw material stories, perfumer interviews and seasonal edits, built with article structured data and internal links to each fragrance, so search traffic from long questions arrives on a page that answers them.
Your expertise becomes the reason people search for your name.
Every form writes to the CRM you use, tagged by boutique, enquiry type and language, with alerts to the right manager. Marketing consent is stored separately from the enquiry so PECR and UK GDPR records stay clean.
No lead sits unanswered because it went to the wrong inbox.
Launch evenings, masterclasses and in store events get their own pages with a request to attend form, capacity notes your team controls and Event structured data. Past events become journal entries, so the work behind a launch keeps bringing visitors long after the night itself.
Each launch builds the site's search value instead of vanishing from social feeds.
Image heavy perfume pages tuned for Core Web Vitals, with responsive photography, lazy loading and pages tested against WCAG 2.2 AA so visitors using screen readers or keyboard navigation can read notes and send an enquiry.
Rich visuals without slow pages or excluded visitors.
Who this is for
Perfume businesses in London range from houses with royal arcade frontage to a single perfumer working from a Hackney studio. They share a problem: the scent cannot travel through a screen, so the website has to carry the story, the detail and the next step. The four situations below are the ones we see most, and each needs a different emphasis in the build. We also look at who visits: local regulars, City workers buying gifts at lunchtime, and international visitors who return home and search for you weeks later.
Your name carries weight, but the site may still be a brochure built years ago that hides the archive and treats every enquiry alike. We give the history proper pages, separate commissions from general questions, and make each boutique easy to reach for visitors staying in nearby hotels. The tone stays restrained, and nothing on the site should feel louder than the shop itself.
Archive content often becomes the strongest search asset you own.
When you carry many independent brands, visitors need to compare scents across houses and understand why they should visit you rather than a department store counter. We build brand pages, a cross house fragrance library and a consultation flow that sells your staff's knowledge, which is the thing a West End counter cannot copy. Brand pages also help you rank when visitors search for a smaller house by name and want to know where in London they can smell it.
Customers from the Gulf, South Asia and London's own communities search in different languages and know oils, bakhoor and agarwood grades in detail. We plan Arabic pages with right to left layouts, describe oils with the precision buyers expect and give trade buyers and private clients separate routes to your team.
Arabic is planned from the first wireframe, never bolted on.
You might sell at markets, run workshops and supply a handful of stockists. The site needs to rank for your name and your craft, take workshop and commission requests, and keep a stockist list current without calling a developer. We keep the build lean so it suits a small team that edits everything itself. As the business grows, the same CMS can take a trade area, new languages or a shop without a rebuild.
How we work together
We have no London office. Our team of 80+ works across Dubai, Riyadh and Karachi and runs discovery, design reviews and sign off with London clients by video call and shared documents. Most perfume houses start with a fixed scope build for the website, then keep a monthly retainer for content updates, search work and new language versions. Groups with several brands sometimes prefer a dedicated team that works through a longer programme of sites and integrations. Whichever route you choose, you see the scope, the people involved and the decisions in writing, and staging links let your boutique managers review pages on their own phones before anything goes live.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
Usually WordPress or a headless CMS with a Next.js front end, chosen by how often your team publishes, how many languages you need and which CRM and ecommerce systems the site must talk to. Hosting sits in UK or EU data centres when your privacy policy calls for it.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
It depends mostly on content, languages and integrations.
A single boutique site with a clear fragrance list moves faster than a house with an archive, several London locations, a trade area and three languages. The slowest part is usually writing and approving scent descriptions, not code. We agree the scope and the dates in writing after discovery, and we flag early which content you need to supply so the timeline does not slip while copy waits for sign off. If you need an early version for a launch date, we can phase the build, releasing the core house and boutique pages first and adding the journal, trade area and extra languages in a second release.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio