Websites

SEO & GEO website development

Built to rank on Google and to be the source ChatGPT, Claude, Perplexity and Gemini quote back — because ranking first stopped being the same thing as getting the click.

What is GEO, and how is it different from SEO?

Generative Engine Optimization is the work of getting an answer engine to quote your site as its source. SEO competes for a click on a results page; GEO competes to be the passage ChatGPT, Claude, Perplexity or Gemini lifts. Onpolar builds sites that do both — structured for crawlers, written for extraction.

Typical timeline
2–4 weeks to launch
Rendering
Prerendered — no JS needed to read it
AI crawlers
llms.txt plus a named allow-list
Built this way
Eesti E-pood · 3DCraft · CarFog · EcoRig

The problem

You still rank first. The clicks left anyway.

AI Overviews have cut click-through on top-ranking results by close to 60%. The query still gets answered — just above your listing, in a summary that may never name you.

Meanwhile the assistants people now ask directly cannot run your JavaScript, will not wait for hydration, and will not infer what your page means. If the answer is not in the served HTML in a shape they can lift, you are not in the answer.

So the job changed. Ranking is table stakes now, and the thing worth engineering is whether your site is the source a model reaches for.

What you get

What makes a site citable

Nine tenths of this is structural. It is also the nine tenths most sites skip.

  • Statically prerendered pages

    Every route served as finished HTML. No crawler has to execute JavaScript to read your content, because most of them will not.

  • Citation-ready structure

    One question per heading, the answer in the first sentence beneath it, and passages self-contained enough to be lifted without losing their meaning.

  • A real schema graph

    Organization, WebSite, Service, Article, FAQ and breadcrumbs joined on shared @id references — one connected graph, not six disconnected blobs.

  • llms.txt and llms-full.txt

    A curated manifest of what you publish and why, plus a full-text companion, so a model reading your site gets the guided version.

  • AI crawler allow-list

    GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended and the rest named explicitly in robots.txt rather than left to a wildcard.

  • Localised routes, not translated pages

    Keyword research per language and slugs localised down to the URL, with hreflang that names one authoritative locale.

  • Core Web Vitals in the green

    Images sized and served modern, fonts without layout shift, and the interaction budget spent on things a visitor can actually see.

  • Measurement that matches the goal

    Citations and brand mentions across generative surfaces tracked alongside classic rank data, because keyword position no longer describes the outcome.

How it works

How a GEO-first site gets built

  1. 01

    Crown keyword and question map

    One keyword the site is willing to be judged on, plus the real questions buyers put to an assistant. The question map becomes the heading structure.

    Week 1
  2. 02

    Architecture and schema graph

    Routes, locales and structured data designed together, so the URL, the heading and the schema all say the same thing about the same entity.

    Weeks 1–2
  3. 03

    Write for extraction, build for speed

    Copy written answer-first, pages prerendered, and manifests generated from the content rather than maintained by hand and left to rot.

    Weeks 2–3
  4. 04

    Verify, then watch

    Rich Results checks, rendered-HTML checks, and the prompts your buyers would actually type run against the live assistants. Then a baseline to measure from.

    Week 4

Want to know what an assistant says about you today?

We will run the prompts your buyers would type and show you what comes back — with or without your name in it. Thirty minutes.

SEO vs GEO

What changes when the answer engine is the audience

Most of classic SEO still applies. These are the places where optimising for a results page and optimising for an answer genuinely diverge.

DimensionClassic SEOGEO
GoalRank high enough to earn the clickBe the passage the model quotes
Unit of competitionThe pageThe passage — a heading and the sentences under it
RenderingGooglebot will run your JavaScriptMost AI crawlers will not; served HTML is all they see
Structure that winsKeywords, internal links, backlinksAnswer-first passages, tables, lists, plain definitions
Structured dataRich result eligibilityEntity disambiguation and extraction confidence
Crawler controlrobots.txt for search botsA named allow-list per AI crawler, plus llms.txt
Success metricPosition and click-through rateCitations and brand mentions inside AI answers

Nobody should trade one for the other. A page that cannot rank rarely gets crawled often enough to be cited.

FAQ

Questions we get asked

Does GEO replace SEO?

No. They share most of the same foundations — crawlable HTML, clean structure, real authority — and a page that ranks well gets crawled more often, which makes it likelier to be cited. GEO is the additional work of making the content extractable once a crawler arrives.

How long until we show up in AI answers?

Weeks rather than days, and it varies by assistant. The ones that search live at query time can surface a new page within days of it becoming crawlable. Models leaning on a training snapshot may take a release cycle. We set a baseline at launch and re-run the same prompts monthly, so the change is measured rather than felt.

Can you work on our existing site, or does it need a rebuild?

Often the site is fine and the work is structural: served HTML, a schema graph, heading discipline, manifests, crawler rules. We start with an audit that says which of those are missing and what each is worth. A rebuild is a recommendation we have to earn, not a default.

What is llms.txt, and does anything actually read it?

A plain-text manifest at your domain root listing what you publish, with a one-line description each. Adoption is uneven and it is not a ranking factor. It also costs almost nothing, forces you to make your own content inventory explicit, and the sites being cited today tend to have one.

Should we block AI crawlers instead?

If your content is the product you sell, sometimes yes. If your content is how buyers find you, blocking crawlers removes you from the place those buyers now ask. We will tell you which of the two you are, and the allow-list is per-crawler either way, so it is not all or nothing.

What does a site like this cost to run?

Prerendered pages on edge infrastructure cost very little to serve, and there is no CMS licence in the stack unless you want one. The recurring cost of a site like this is content, not hosting.

How many pages do we need?

Fewer than most agencies will sell you. Eesti E-pood is 84 prerendered pages because it is 13 routes across three languages — not because 84 was the target. Thin pages built to fill a sitemap actively hurt the ones that matter.

Do you write the content, or do we?

Either. If you write it, we hand over the question map and the answer-first structure to write into. If we write it, you review it for accuracy — we will not invent claims about your business, and specificity is exactly what gets a passage quoted.

Start a website build

Tell us the site, the market and the keyword you want to own. We reply within one business day.

Project details
Estimated budget
By submitting this form, you agree to our Privacy Policy.