SEO-friendly website: how to build technical SEO in from day one

The new website was beautiful, quick to click around and approved by the whole management team. Three weeks after launch, traffic from Google had halved. Nobody had set up redirects from the old URLs, every page had the same title, and a setting left over from the staging server was still telling Google to stay away. All three mistakes take minutes to avoid and months to recover from. This guide is about avoiding them, and about the choices that make a website easy for Google to understand from day one.

What makes a website SEO-friendly?

An SEO-friendly website does three things well. It makes it easy for Google to find every important page. It makes it easy to understand what each page is about and how the pages fit together. And it gives the visitors Google sends a fast, good experience. Everything in this guide falls into one of those three boxes: discovery, understanding and experience.

How should the site structure and URLs be planned?

Structure is the first thing Google uses to understand you, and the hardest to change later. Start with a list of the topics customers search for and give each topic one page. A carpenter has a page about roof replacement, one about windows and one about extensions, rather than a single “services” page. Then group the pages in a logical menu where no important page is more than three clicks from the homepage.

• Short, readable URLs containing the keyword, such as /services/roof-replacement.
• Lowercase letters and hyphens only, with Danish æ, ø and å written as ae, oe and aa.
• No dates or ID numbers in URLs for pages meant to last.
• One URL per page: choose with or without a trailing slash and redirect the other.
• Breadcrumbs showing where the page sits in the structure.
• A 404 page that helps people on to the most important pages.

Internal links: how the pages connect

Internal links show Google which pages matter most and how topics relate. Link from guides to the services they discuss, and from services to relevant case studies and guides. Use descriptive anchor text such as “what a new website costs” rather than “read more”. A page no other page links to is hard for Google to find and is often judged less important. The text around the link matters too, which we cover in website copywriting.

Which technical SEO elements must be built in?

How fast does an SEO-friendly website need to be?

Google measures speed and stability with three Core Web Vitals, based on data from real users in Chrome. A page is rated good when at least 75 % of visits fall within the thresholds below. Speed is one of many signals in Google, but it also directly affects how many people stay on the page and take action.

The usual culprits are large images without modern formats, late-loading fonts, heavy page builders, chat widgets and tracking scripts that all run before the page is ready. We have collected measurement methods and the fixes that pay off most in website speed and Core Web Vitals.

Server rendering: the content must be in the HTML

What is schema markup, and which types do you need?

Schema markup, or structured data, is a small block of code that tells Google in a fixed format what the page contains: a business, an article, a product with a price or a breadcrumb trail. It can give richer display in search results and helps search engines and AI services understand you correctly. Google has limited some displays over time, such as FAQ results, so treat structured data first and foremost as a tool for understanding. Stars and extra lines are a bonus when they appear. These types cover most business sites:

• Organization or LocalBusiness on the homepage with name, logo, address and contact details.
• BreadcrumbList on all subpages, so the path shows in search results.
• Article on guides and blog posts with author and date.
• Product and Offer on product pages with price and stock status.
• Service or FAQPage where the content really is a service or a list of questions.

How do you set up hreflang for Danish and English?

If the website has several languages, Google must know which pages are versions of each other, so a Danish searcher gets the Danish page and an English searcher the English one. That is what hreflang does. The rules are simple, but they must be followed precisely, and it is one of the things most often set up wrong on plugin-built sites.

• Each language version points to all versions, including itself.
• References must go both ways. If the Danish page points to the English, the English must point back.
• Use language codes such as da and en, and consider x-default for the version shown when no language fits.
• Each language version has its own fixed URL, for example with /da or /en, that Google can crawl.
• Translate URLs, titles and descriptions so they match the keywords in each language.

How do you make sure Google finds and indexes the pages?

1. Generate the sitemap automatically, so new pages are added and deleted ones disappear.
2. Reference the sitemap in robots.txt.
3. Create and verify the domain in Google Search Console and Bing Webmaster Tools.
4. Submit the sitemap, and check the indexed pages report after a week.
5. Remove noindex and password protection from production, and make sure the staging server itself is hidden.
6. Follow errors such as 404s, redirect chains and pages marked “discovered, currently not indexed”.

If the new website replaces an existing one, the redirects are the single most important task. We have a step-by-step plan in website migration without losing SEO.

What does it cost to build SEO into a new website?

When technical SEO is planned in from the start, it is a small share of the budget, because most of it is about doing things right the first time. Afterwards it gets expensive, because structure and URLs have to change on a site already in use. The table shows where the money typically goes.

At Ceptiv, technical SEO is part of all our web packages, from Small at DKK 18,000 to Large at DKK 54,000. We build in Next.js, where static generation, sitemaps, hreflang and image optimisation are part of the foundation. See the packages under pricing, or read why we chose the technology in Next.js vs WordPress.

How do we build SEO into a project step by step?

Which myths about SEO-friendly websites can you ignore?

• That you must repeat the keyword many times. Google understands synonyms and context.
• That an SEO plugin makes the site SEO-friendly. It helps with titles, but can’t fix structure and speed.
• That you must submit the site to Google every time it changes. An updated sitemap is enough.
• That more pages is always better. Many thin pages can drag down the whole domain.
• That the meta description is a ranking factor. It affects clicks, and clicks are what you want.

What should you check before the new site goes live?

1. Does every page have a unique title and description?
2. Does each page have one H1 with the primary keyword?
3. Have noindex and password protection been removed from production?
4. Do all 301 redirects from the old URLs work?
5. Is the sitemap generated and submitted in Search Console?
6. Does hreflang point both ways between language versions?
7. Has the structured data been validated without errors?
8. Are Core Web Vitals within the thresholds on mobile?
9. Do all images have alt text and a modern format?
10. Is there a helpful 404 page?

The full launch checklist with legal points, analytics and testing is in website launch checklist. And if you want a website where all of this is included in the price, get a fixed price within 24 hours.