Skip to content

01.01 / Build

Websites.

Marketing and multilingual websites pre-rendered to static HTML, with technical SEO, hardened forms and analytics built in. The repository, Supabase and Vercel are in your name.

indexable URLs, Spanish and EnglishHotel Talavera
16
translation keys present in each of the three languagesEstepona Golf
536/536
languages live on the site, Spanish and EnglishGlobal Dynamic Security Group
2
A golf club's new website on a desktop screen by a window: the course photo on the home page and, beside it, the green fee booking panel with the free tee times.

In detail

What you should know.

Two hotel staff review a new website before launch: the mobile version on her phone, the room page and a speed report on his monitor

For example: 16 indexable URLs, Spanish and English. Hotel Talavera

What it is

A marketing website in which every page is a static HTML file. Polargate builds these with Vite, React and vite-react-ssg: each route is pre-rendered at build time, so the text, the headings, the structured data and the links are already in the HTML the server sends. A search crawler, a screen reader and an AI assistant all read the same thing, without waiting for JavaScript.

That matters more than it used to. GPTBot, OAI-SearchBot, Claude-SearchBot and PerplexityBot fetch raw HTML and do not execute JavaScript. A site that paints its content in the browser after hydration does not exist for them, however good it looks to you.

How we do it

We start from your content, not from a template. One page per real question a buyer asks: rooms, restaurant, events, how to get there, contact. Each page gets a single H1 that states plainly what it is, a direct answer in the first paragraph, and headings phrased the way people actually search.

Multilingual sites are pre-rendered per language, with self-referencing hreflang, x-default and translated URLs, not a language switch that swaps strings in the browser. We ship a robots.txt with explicit groups for the search and answer crawlers, a sitemap built from the same route list as the site, and schema.org JSON-LD generated from one data file, so the markup can never drift from the visible text.

Forms run server-side on a Supabase Edge Function with honeypot, timing check, validation and a rate limit per IP address, and go out through Resend on a dedicated subdomain, leaving your corporate mail untouched. Analytics arrive with consent denied by default, and third parties (maps, chat) load only after consent.

Before launch the site goes through an audit loop: several review passes over correctness, accessibility, performance, security and SEO, with every finding verified before it is fixed. On a recent hotel site that loop produced 48 confirmed findings, all fixed, in a single maintenance round.

What you get

What you take away.

Everything is written down before we start, and everything stays in accounts your company owns.

01Deliverables

  1. 01

    Static pre-rendering of every route with vite-react-ssg, so all content sits in the served HTML

  2. 02

    Page architecture built around the questions buyers actually ask, one H1 and a direct answer per page

  3. 03

    Multilingual delivery per language: translated URLs, self-referencing hreflang, x-default, metadata and sitemap entries per locale

  4. 04

    Technical SEO: sitemap generated from the route list, robots.txt with explicit search and answer crawler groups, schema.org JSON-LD from a single data source

  5. 05

    Contact and enquiry forms on a Supabase Edge Function with honeypot, timing check, server-side validation, rate limiting and delivery through Resend on your own subdomain

  6. 06

    Security and privacy: security headers, Content Security Policy in enforce mode, row level security on the database, consent-gated maps and chat

  7. 07

    Analytics setup: GA4 with Consent Mode, Google Tag Manager and Search Console, plus server-side visibility of AI crawler traffic

  8. 08

    Multi-pass audit before launch (correctness, accessibility, performance, security, SEO) with every finding verified before it is fixed

02How it runs

  1. 01 · Week 1 to 2

    Discovery Sprint

    Interviews with the people who will use the thing, an audit of the systems you already run, a data model, an architecture decision and a scope written in plain language. It ends with a fixed price and a delivery plan, and the document is yours whether or not you continue.

  2. 02 · Week 2 to 4

    Foundations

    Design direction, database schema with row level security from the first migration, environments, continuous integration and the first screens in a place you can open. Nothing is built on a platform you cannot leave: the repository, the backend and the hosting are created in your accounts.

  3. 03 · Week 4 to 8

    Build to the first shipped iteration

    Weekly deployments, a short written update with each one and a running list of decisions. The goal of this stage is a version in production with real data where someone can finish an actual task, not a demo. Scope changes are priced before they are built.

  4. 04 · Week 8 onwards

    Audit, launch and handover

    Several review passes over correctness, architecture, accessibility, performance and security, with every finding checked by a second reviewer before it counts as real. Then the launch, the handover pack and, if you want it, a move to the CARE retainer for maintenance and evolution.

For example: 536/536 translation keys present in each of the three languages. Estepona Golf

Who it is for

We don't take every project.

We would rather tell you now than halfway through. If you recognise yourself on the left, let's talk.

It fits if

  • You need a website, a portal or an app that does not exist yet, or one that has run out of road
  • You want the code, the data and the hosting in accounts your company owns
  • You prefer a fixed price before work starts to an open hourly bill
  • Someone on your side can decide and give the project a few hours a week
  • You care that Google and AI assistants can read it from day one

It is not for you if

  • You are after a cheap template or a site put together over a weekend
  • You want it to live on a platform you cannot leave later
  • Nobody on your side can review screens or make decisions
  • You need people to bill hours without a clear goal

For example: 2 languages live on the site, Spanish and English. Global Dynamic Security Group

Timing and budget

How we quote.

No price list and no hourly billing during a build. After a short call you get a written quote for your project.

Timeline
Typically four to six weeks from kickoff to launch for a standard multilingual site. Branding, a large amount of new content or a booking engine integration extend it. A paid Discovery Sprint of two weeks comes first and fixes the page map, the content plan and the price.
Team
Our team defines and builds the site, including brand design, photography and copy when the scope calls for it. Pedro Ciordia, founder and CTO, sets the architecture and reviews every page before it goes live. You talk to the people building it, and there is no handover to a junior team after the kickoff.
How the price is set
Fixed price per project, quoted privately after a first call. What moves it: languages, brand identity, content and photography to produce, and integrations. You get the figure in writing before anything starts.
The stack
ViteReactTypeScriptTailwind CSSshadcn/uiReact RouterSupabaseVercelResendGitHubGA4Search ConsoleVitest

For example: 27 published FAQs with FAQPage schema. Hotel Talavera

FAQ

What people ask us.

How much does a custom website cost?
It depends on the number of languages, whether brand identity (logo system, brand book, photography direction) is part of the scope, the content to produce and the integrations. Polargate quotes a fixed price, agreed in writing before the build starts, after a short call and a paid Discovery Sprint. Hosting and the database are separate and run at real cost, usually tens of euros a month, billed to you directly rather than marked up. Tell us about your site and you get a private quote.
How long does it take to build a website?
Four to six weeks from kickoff to launch for a standard multilingual site. Branding, a lot of new content or a booking engine integration extend that. The Discovery Sprint before the build takes two weeks and produces the page map, the content plan and the fixed price, so the build phase starts with no open questions and no scope discussions halfway through.
Why build a site as static HTML instead of WordPress?
Static pages are faster, have far less surface to attack and are readable by machines that do not run JavaScript, which includes most AI crawlers. There is no plugin stack to patch every month and no page builder licence. The trade-off is that a content change goes through a build, so when you edit often we add an admin panel wired to your own database.
Will my website show up in ChatGPT and other AI assistants?
Nobody can guarantee a citation, and Polargate does not sell one. What we do is remove the technical reasons you would be excluded: real HTML on every route, a robots.txt that allows the search and answer crawlers, no bot challenge blocking them at the edge, indexing in Bing as well as Google, accurate structured data and a direct answer near the top of each page. The rest depends on your content and your reputation.
Can I update the content myself?
Yes, where it is worth it. Pages that change rarely we edit in the repository, which keeps the site simple and fast. For news, offers or listings we build a small admin panel on your own Supabase project, with login and roles, like the news manager on the Estepona Golf site. You edit, and the page rebuilds and deploys itself.
Do you build multilingual websites?
Yes. Polargate works natively in English, Spanish and Dutch, and has shipped sites in Spanish, English and French. Each language is pre-rendered as its own set of pages, with translated URLs, self-referencing hreflang and x-default, its own metadata and its own sitemap entries. We do not redirect visitors by IP address or browser language, because that hides the other languages from crawlers.

For example: 48 audit findings confirmed and fixed. Hotel Talavera

Get started

Tell us what you want to build.

Websites, apps, custom systems and AI for companies that need them in production in weeks. Fill in the form or book a 30 minute call: a senior engineer answers within 48 business hours with a first take on scope, timeline and price.

What do you need?
Budget
When

At least ten characters.

Answer in writing within 48 business hours. No newsletter, no automatic sequence.

Rather answer the full brief?

First step

Discovery Sprint

Two weeks to close scope, architecture and price before anything is built.

No price list. You get a private quote, in writing, after a short call.

Then, to build, always at a fixed price

Not ready yet?

AI-native digital studio for mid-market companies

POLARGATE, S.L. · CIF B24895005
Calle Electrónica 6, 28027 Madrid, Spain