The SEO foundation of a new site: what to get right at launch

SEO isn’t marketing you bolt on once the site is live. It’s a handful of structural decisions that either go into the build or get torn back in later, at a higher price and with a worse result. Google won’t punish you for not having a blog. But it struggles to read and index a site that was put together without a single thought for search, and a site it can’t read is a site nobody finds.

What follows is the part that actually earns its keep at launch. No tricks, no promise of “number one by Friday.” You can’t buy any of it as a standalone add-on. It lives in the code, not on a price list.

Structure and URLs: a skeleton people and crawlers can both follow

Keywords come later. First comes a structure that makes sense. Each page needs one topic and one obvious place in the hierarchy. If you can’t say in a sentence why a page exists, the search engine won’t guess it either, and neither will the visitor staring at it.

A few things matter here. URLs should be clean and readable, /services/landing/ rather than /page?id=42, and they should survive launch unchanged so links and rankings don’t break. One H1 per page, describing that page and nothing else, with H2 and H3 nested under it in a way that reflects real meaning instead of decoration. Pages should link to each other by topic, which is how a crawler learns what you care about and how authority spreads across the site.

Then the dull stuff that gets forgotten precisely because it’s dull: an XML sitemap and a robots.txt file. One hands the crawler a map. The other tells it plainly what to index and what to leave alone.

An SEO foundation is how the site is built underneath, not a layer you paint on after launch. Rebuilding the structure of a live site always costs more than getting it right the first time.

Metadata and markup: how you show up in the results

Your title and description are the line of ad copy a stranger reads before deciding whether to click you or the result below you. They don’t lift rankings on their own. They decide who gets the click out of ten near-identical blue links, which amounts to much the same thing.

Give every page its own title, around sixty characters, with the meaning up front rather than buried after your brand name. Write the description as a short promise: a reason to click, not a heap of keywords. Add Open Graph and Twitter Card tags so that when someone drops your link into a chat or a feed, it arrives with an image and a headline instead of a naked URL nobody taps.

There’s also Schema.org, structured data that labels the page for the search engine: this is a company, this is a service, this is an article, a review, an FAQ. That labelling is what wins you the rich results, the star ratings and expandable questions that catch the eye. On a properly built site, all of this goes into the templates once and runs by itself on every page you add afterwards. On a site stitched together page by page, someone ends up patching each one by hand.

Multilingual: hreflang without the headache

Run the site in more than one language and you need hreflang, and a business aiming at both the EU and Ukraine almost always runs more than one. It’s the small attribute that tells Google these pages belong together: here’s the English version, here’s the German, here’s the Croatian, separate audiences rather than copies of each other.

Leave it out and two things tend to go wrong. A German visitor lands on the English page. Or Google decides the language versions are duplicates and quietly picks one to show, often not the one you’d want. Done right, every page points to all its counterparts, the references run both ways, and the language and region codes are correct. Set up at the start, that’s a few lines in a template. Bolted onto a finished multilingual site, it becomes a project of its own, and not a cheap one.

Speed: the SEO a visitor actually feels

Speed is the one part of SEO your customer experiences directly. Google measures it through Core Web Vitals, its own scoring for how fast a page becomes usable. Picture someone on their phone tapping your product on a slow connection. The page is still thinking. After two seconds they back out, return to the results, and open whoever loaded first. You lost that sale before a single word was read.

No “speed-up” plugin fixes that. The fix is architecture:

• lean code, with no libraries dragged in “just in case”;
• images in modern formats, sized to how they’re actually shown;
• few render-blocking scripts holding up the first paint;
• caching and a CDN (servers spread across regions) so the site opens quickly from any country.

We dig into this properly in our piece on website speed and Core Web Vitals. The short version: building a light site from scratch is far easier than squeezing speed out of a bloated template after the fact.

Content: what ultimately ranks

The technical work makes a site legible to the search engine. Content is what actually ranks. And the goal isn’t a page that talks about everything at once. Aim for a straight answer to what your audience types into the search box.

Keep one intent per page, so “buy a landing page” and “what is a landing page” never share a URL, because they’re two different visitors with two different needs. Write for people, around the questions they actually ask, not as a wall of comma-separated keywords. Give images real alt text, which helps both screen readers and search. And leave yourself room to grow: an articles section planned in from the outset lets the site gain ground in search for years without anyone touching the structure.

Still weighing format and budget? It’s worth reading how much a website costs in 2026 and what actually drives the price before you commit. None of this SEO work is an extra sold on the side. It’s just part of building the thing properly.

Where to start

Stripped down, the SEO worth having on the day you launch comes to this:

1. A sensible page structure and clean URLs.
2. Unique titles and descriptions, with H1 to H3 in order.
3. Schema.org for your content type, Open Graph for social.
4. hreflang across every language version.
5. Speed that holds up to Core Web Vitals.
6. Content written for real searches, plus a sitemap and robots.txt.

We put all of this into every landing page and multi-page site we build, with no separate “SEO” line on the quote, because a site without it isn’t finished.

Planning a new site, or quietly suspecting the one you have was built on sand? Describe the project in a few sentences and we’ll tell you what belongs in the foundation now and what can wait until later without a rebuild.