Website creation and SEO: designing a site that is visible from launch

This page is for the e-commerce or SEO manager launching a new site, whether an online shop or a brochure site, who wants it to be found from day one. Getting website creation and SEO right together is not about optimising afterwards: site structure, URLs, templates, rendering and measurement are decided before the first wireframe. You will find the decisions to make and when to make them, the brief to hand to your agency and the checks to run before launch.

Why SEO Is Decided Before the First Wireframe

The cost of "SEO afterwards" comes from knock-on effects: a poorly defined URL rule leads to redirects, internal links to rework and canonicals to fix. Fixing a template after launch means fixing hundreds of pages at once.

For an online shop, the stakes are direct: category pages and product pages come from the same templates, so a design error is replicated across the whole catalogue. The ecommerce SEO guide covers optimising an existing catalogue; this page covers what is decided beforehand.

The Most Expensive Mistakes to Fix After Launch

The most expensive mistakes affect global rules and force you to rework entire templates:

There is no universal percentage for the gap between designing it in and retrofitting. You can estimate it by comparing the two scenarios template by template: effort made once at build time, versus re-coding, new checks, regression risk and the visibility lost while the fix is under way.

Integrating SEO Without Extra Cost: Decide by Template

Integrating SEO during build means doing the work at the right time and standardising it. Four methods avoid extra cost:

• Decide by template: define rules for category pages, product pages, service pages, articles and FAQs rather than page by page.
• Write acceptance criteria: each template ticket includes its indexation rules, meta fields, internal links and structured data.
• Plan measurement from the start: incomplete tracking costs more than a well-scoped tagging plan because it prevents informed decisions.
• Allocate a performance budget: image weight, third-party script limits, loading rules and Core Web Vitals targets.

Making the ALT field mandatory in the publishing interface, for example, avoids having to retrofit hundreds of media assets later.

SEO by Design: The Decisions to Make Before Development

SEO by design means locking in, before development, the decisions whose change cost skyrockets after launch. The table sorts them by timing:

Site Structure, Depth and Crawlable Navigation

A clear site structure serves both the buyer and the crawler. Three risks need to be ruled out:

• Excessive depth: a strategic category or product page more than 4 clicks from the home page is crawled less.
• Uncrawlable navigation: menus rendered only via scripts, links without a standard <a href> tag, content loaded too late.
• Orphan pages: published without a contextual link, they are poorly discovered.

A practical rule: every page that generates revenue receives a navigation link, several contextual links and a breadcrumb.

URLs, Canonicals, Facets and Redirects

URL rules are the hardest to change later. The specifications set them one by one:

• URL policy: readable slugs, stable hierarchy, editable URLs, conflict handling, a single URL per product.
• Canonical: consistent with redirects and actual indexability, never pointing to a noindex page.
• Facets, sorting and pagination: explicit rules (noindex, parameters or canonical) to prevent URL explosion and duplication.
• Redirects: a 301 redirect module in the back office from day one, so a page can be moved without loss.

Performance and Rendering: A Budget per Template

Only 40% of sites pass the Core Web Vitals assessment (SiteW, 2026): setting performance targets before development remains a differentiator.

These metrics measure loading (LCP), responsiveness (INP) and visual stability (CLS). The points to define per template, mobile first:

• Page weight budget, modern image formats, explicit dimensions, controlled lazy-loading.
• Limits and governance for third-party scripts: marketing, chat, A/B testing.
• Server-side rendering or pre-generated pages if critical content depends on JavaScript.
• Stable hosting: response time, scaling, alerts on 5XX errors.

Scoping the Project: Objectives, Personas, Site Structure and Platform

Before any technical trade-off, scoping sets what the site must deliver, for whom and against which KPIs. It then translates each search intent into a page type.

Objectives, Personas and Intent

Useful scoping brings together five elements:

• Primary objective: purchase, quote or demo request, appointment booking.
• Secondary objectives: CTA click, add to basket, download, all of them instrumented.
• Personas: roles, maturity level, frequent objections, buying context.
• Constraints: GDPR, integrations, publishing governance, multilingual.
• Success criteria: conversion volume and quality, mobile performance, time to update.

The reference deliverable is an "intent → page type → primary KPI" matrix. An informational intent calls for a guide, a comparison intent for a category page, a transactional intent for a product page. The query classification method is detailed in the guide on search intent. Each page carries one dominant intent and one primary call to action.

Choosing the Platform on SEO Criteria

No platform is the best in absolute terms: Shopify, WooCommerce, PrestaShop, Magento or Webflow are separated by questions to ask before signing:

Non-SEO trade-offs still have to be made, but a platform that answers no to any of these questions creates debt from day one.

The SEO Brief to Hand to Your Agency or Team

A useful SEO brief describes testable rules, tied to templates, with a verification method. At a minimum, it contains:

• Scope: page types, volumes, languages, GDPR constraints, tech stack.
• Site structure and intent → page matrix, validated before wireframes.
• Template rules: URL, title tag and meta description, indexability, internal linking, structured data, performance.
• Cross-cutting rules: robots.txt, XML sitemap, canonicals, redirects, HTTPS.
• Tagging plan: primary and secondary conversions, GA4 events, consent.
• QA plan and post-launch monitoring: reference pages, tools, thresholds, Search Console routine.

Testable Rules, Template by Template

Each rule is written as "expected evidence + how to verify". For example: "the sitemap contains only indexable URLs", verified by a crawl and in Search Console. For metadata, rather than asking for "customisable meta tags", the brief specifies:

• Editable fields per page type, with their default values.
• Allowed variables (product name, category, brand) and length rules.
• Interface alerts: title empty, duplicated or too long.
• Where structured information is displayed on screen: price, availability, reviews, FAQ.

Structured data follows the same logic: schemas per template (Product, Offer, AggregateRating, BreadcrumbList, FAQPage, Organization), entered in the CMS and consistent with visible content. Since 2023, Google has restricted FAQ rich results to authoritative sites.

Turning the Brief Into Tickets and Acceptance Criteria

SEO by design connects product, development and editorial. Without organisation, you end up with a site that is technically clean but empty, or content-rich but invisible.

Each role decides within its own scope, on a single backlog: product prioritises pages, development ensures rendering and performance, SEO sets indexation, structure and internal linking, content produces to templates. SEO involvement is non-negotiable at four moments: scoping, template design, specifications and pre-launch checks. A recommendation becomes a ticket when it specifies the template, expected impact, solution, validation criteria and regression risk.

The SEO "Definition of Done"

A template is only delivered once it passes testable criteria, for example:

• The page returns a 200 code, is not noindex and appears in the sitemap.
• The H1 is unique, the title tag is filled in, and the canonical points to the final URL.
• Navigation links are <a href> tags visible without interaction.
• LCP, INP and CLS meet thresholds on mobile for strategic pages.

Reviews are carried out per template, with non-regression tests on the sitemap, robots.txt and reference pages at every deployment.

Ready for Generative Engines From Launch

Generative Engine Optimization (GEO) aims to get your pages cited in AI answers. At the time of writing, AI Overviews and AI Mode have been available in France since summer 2026 and cite sources, as do ChatGPT and Perplexity. They cite pages that are indexed, structured, up to date and attributable, which a new site can be from day one:

• Structure: hierarchical headings, lists, tables and direct answers at the top of each section.
• Entities: brand, products and organisation named consistently, marked up as Organization and Product.
• FAQ: buyers' real questions, planned in the templates.
• Attribution: customer reviews, cited sources, an identifiable brand.
• AI crawlers: GPTBot, PerplexityBot and Google-Extended not blocked by mistake in robots.txt.

Google does not penalise AI-generated content as such: it judges its usefulness. The principles and how to track visibility in AI answers are detailed in our GEO guide.

Pre-Launch QA: Checks and Criteria

Before launch, each template goes through a series of checks on a sample of strategic pages. The table gives the tool and acceptance criterion for each:

Pre-Production: Protect It, Then Lift the Protection

Pre-production stays out of the index, through authentication or noindex, and this block is lifted on launch day: a pre-production noindex left in place blocks the entire site.

Launch and Measurement: The First 90 Days

Going live opens the period in which design decisions are put to the test, by comparing each page with itself against a baseline set before launch.

On Launch Day

A few actions determine how the site is discovered:

• Declare the site and submit the sitemap in Google Search Console.
• Check that the pre-production block has been lifted and that HTTPS is active on all address variants.
• Inspect a few strategic URLs per template: category, product page, article.

Tracking the First 90 Days

No indexing timeframe is guaranteed. Indicators are tracked per template rather than page by page:

• Indexed pages and crawl errors, in Search Console.
• Impressions, clicks, CTR and positions by page type.
• Organic sessions, conversions and value, in GA4 and the CRM.
• Brand citations in AI answers to your key questions.
• Performance regressions after each deployment.

Search Console counts AI Overviews and AI Mode impressions without separating them: citations are tracked separately. A change should be read as a correlation with a deployment, never as a cause. If the new site replaces an existing one, URL migration falls under an SEO redesign with a redirect plan.

Depending on Your Situation

Depending on where you are, the next step is covered elsewhere:

• You are building an online shop: the full method for a catalogue is in the ecommerce SEO guide mentioned above.
• Your new site replaces an existing one: prepare the migration with the redesign guide mentioned above.
• Your site is already live and underperforming: start from the method to optimise an existing website.
• Your doubts concern rendering, crawling or performance: see the guide to technical SEO.
• You are looking for outside support: see how to work with an SEO agency.

To publish launch content without re-entering it, the CMS integration module of Incremys, the GEO & SEO platform, sends written pages to your CMS; each page is then compared with itself before / after.

FAQ: Website Creation and SEO (SEO by Design)

Should you think about SEO before building a site?

Yes. Site structure, URLs, templates, rendering and the tagging plan determine crawling, indexation and measurement. Changing them after launch means reworking global rules, with redirects and re-coding. Deciding them at scoping takes an effort made only once.

Which CMS is best for SEO?

No CMS is the best for SEO in absolute terms: the right one is the one that lets you control your rules. Check that it lets you edit URLs, title tags, meta descriptions and canonicals per template, control robots.txt, the sitemap and facets, produce structured data and serve content in the initial HTML.

How long before a site is indexed and ranking?

No timeframe is guaranteed. Indexation depends on how pages are discovered (sitemap, internal linking, Search Console), on rendering and on published content; ranking also depends on competition. A site designed with crawlable, ready pages starts without any technical backlog to catch up on.

What does an SEO brief for a web agency contain?

It contains the scope, the validated site structure, template rules (URLs, metadata, indexability, internal linking, structured data, performance), cross-cutting rules, the tagging plan and the QA plan. Each rule specifies the expected evidence and how to verify it.

Which SEO elements should be planned from the wireframes onwards?

Heading structure, with a unique H1 and logical H2s and H3s, content slots (proof, reviews, FAQ), internal links and breadcrumbs, CTAs aligned with intent, and accessibility. The wireframe also sets the weight of media and third-party scripts, and therefore part of the performance.

What are the most expensive SEO mistakes to fix after launch?

Unstable URLs, which force a wave of redirects, duplication through parameters and facets, JavaScript hiding content and links, mobile performance dragged down by media and third-party scripts, and incomplete measurement. All of them affect entire templates, and therefore hundreds of pages at once.

How do you measure the ROI of a website built with SEO baked in?

Set a baseline before launch with Search Console, GA4 and your CRM, define conversions and their value (lead, order, margin), then track changes per template. Compare each page with itself before / after, reading changes as correlations and without limiting yourself to last click.