# What makes an SEO friendly website?

> An SEO friendly website is one that search engines can find, crawl and understand, and that visitors can use quickly on any device. The technical base is speed, mobile layout, clean headings, structured data, a sitemap, canonical URLs and internal links. That base is built into the code, but rankings are earned by content that answers the question.

- URL: https://radkod.com/en/blog/seo-friendly-website
- Publisher: RadKod
- Published: 2026-09-02

## In short

- An SEO friendly website is easy for search engines to crawl and understand, and fast for people to use.
- The technical base has seven parts: speed, mobile layout, headings, structured data, sitemap, canonical URLs and internal links.
- Technical work opens the door. Content that answers the question is what earns rankings.
- SEO is built into the code, not bolted on later with a plugin.
- Check it with a list before launch and monitor it in Search Console after.

## What is an SEO friendly website?

An SEO friendly website is one that search engines can easily find, crawl and understand, and that visitors can use quickly on any device. [SEO](/en/glossary/seo) stands for search engine optimisation: the work of making a site show up for the searches that matter to it.

There are two halves. The technical half asks whether the page loads fast, works on a phone and tells the search engine clearly what it is about. The content half asks whether the page actually answers the searcher's question. Technical work gets you considered. Content gets you chosen.

This guide covers the technical half, with a pre-launch checklist at the end.

## How fast should an SEO friendly website be?

Google treats a page as good when its main content appears within 2.5 seconds. That measure is called LCP, one of the three [Core Web Vitals](/en/glossary/core-web-vitals). The other two measure how quickly the page responds to a tap (INP) and whether content jumps around while loading (CLS).

Speed is not a ranking shortcut. Google says plainly that a good page experience does not replace relevant content. But a slow site loses people before they read a word. Our guide to [site speed and Core Web Vitals](/en/blog/site-speed-core-web-vitals) covers the usual causes and fixes.

## Why does the mobile version come first?

The mobile version comes first because Google indexes sites using their mobile view. This is called mobile-first indexing. Content missing on the phone is, for Google, missing.

A layout that adapts to every screen is called [responsive design](/en/glossary/responsive-design), and it should be the default. On a real phone, check that text is readable without zooming, buttons are big enough to tap, nothing scrolls sideways and nothing visible on desktop is hidden on mobile.

## How should titles and headings be structured?

Every page needs a unique title tag, a short meta description and a single main heading, with subheadings in a logical order.

- **Title tag:** the blue line in search results. It names the topic and, where it fits, the brand. Around 60 characters avoids truncation.
- **Meta description:** the two lines under the title. It does not affect ranking directly, but it affects whether people click.
- **H1:** one per page, stating what the page is about.
- **H2 and H3:** real sections, not styling. Question-shaped subheadings show readers and search engines exactly what each section answers.

## What does structured data add?

[Structured data](/en/glossary/structured-data) is code that tells search engines, in machine terms, what a page is: an article with an author and a date, or a company with an address. It is usually written with the schema.org vocabulary in JSON-LD format.

Google may show rich results for some types, but never promises to. The real value is being understood correctly. The markup must match what the page visibly says. Marking up content that is not on the page breaks Google's guidelines. For a company site the common types are Organization or LocalBusiness, Article, BreadcrumbList and FAQPage.

## How should the sitemap and robots.txt be set up?

A [sitemap](/en/glossary/sitemap) lists the pages you want indexed. robots.txt tells each crawler where it may go. Together they shape how a search engine walks your site.

- Generate the sitemap from code so new pages appear automatically.
- Include only live, indexable pages. No drafts, redirects or noindex pages.
- Submit it once in Search Console.
- Blocking a page in robots.txt does not remove it from the index. Use noindex for that.

The classic launch mistake is carrying the staging site's "block all crawlers" setting into production. The site goes live and nobody can find it.

## Why do canonical URLs matter?

A [canonical URL](/en/glossary/canonical-url) tells search engines which address is the real one when the same content is reachable from several. Without it, the search engine picks one for you and signals get split.

Duplicates are more common than people think: trailing slash or not, www or not, tracking parameters, filter parameters. Each page should point to its own clean address, and old addresses should use a [301 redirect](/en/glossary/301-redirect) to the new one.

## How should internal links work?

Internal links should connect related pages with descriptive anchor text. Search engines discover pages mostly by following links, and visitors find their next answer the same way. Every article should link to its service page and the service page back to its articles. No page should be an orphan, and broken links should be checked regularly.

## Where does content fit in?

Content sits at the centre. A technically perfect page that does not answer the question will not rank. Google's own guidance asks for helpful content written for people first. First-hand experience, your own process and your own numbers are the things nobody else can publish, and they carry the most weight. If you also want that content cited by AI assistants, read [how to show up in AI search](/en/blog/show-up-in-ai-search).

**Pre-launch checklist for an SEO friendly website**

| Check | How to verify | Why it matters |
| --- | --- | --- |
| Crawlers are allowed | Read robots.txt and look for noindex tags | A leftover staging setting keeps the site out of search |
| Unique title on every page | View source on a few pages | Identical titles make pages indistinguishable |
| One H1 per page | Count headings in developer tools | The topic is clear |
| Works on a phone | Browse every page type on a real device | Google indexes the mobile view |
| Core Web Vitals are good | Test the home page and an inner page in PageSpeed Insights | Slow pages lose visitors |
| Structured data is valid | Use the Rich Results Test or Schema Markup Validator | Broken markup is ignored |
| Sitemap is clean | Open it and look for drafts or redirects | Only real pages are submitted |
| Canonicals are correct | Check the canonical tag in the source | Signals consolidate on one address |
| Old URLs redirect | Open the old site's key URLs one by one | Existing search traffic is kept |
| Images have alt text | Check image tags in the source | Screen readers and search engines understand images |
| HTTPS is enforced | Try the http address and look for the padlock | Browser warnings drive visitors away |
| Search Console is set up | Verify the property and submit the sitemap | You see problems first |

## What should you ask a web agency about SEO?

Ask which of the items above are built into the code and happen automatically. Can you edit each page's title and description in the admin panel. Does the sitemap update itself. Which structured data types are included. How will old URLs be redirected. Will they measure speed before launch and show you the result. And in whose name is the Search Console account.

We write these items into the quote and into the [definition of done](/en/glossary/definition-of-done). On launch day every row of the checklist must be ticked, or the job is not finished. Search Console and analytics accounts are opened in your name from day one, like the domain and hosting.

See our [web design](/en/services/web-design) service for what a company site includes, and [maintenance and support](/en/services/maintenance-and-support) for how we keep the base healthy after launch.

## Frequently asked questions

### Does an SEO friendly website guarantee first place?

No. The technical base makes sure the site is crawled and understood. Rankings depend on content, competition and trust. Be careful with anyone who guarantees a position.

### Is an SEO plugin enough?

A plugin can add title and description fields. It cannot make a heavy theme fast or fix a broken heading structure. The base belongs in the code.

### Does the meta description affect ranking?

Not directly. It affects click-through, because it is the text people read in results. Google may also show its own snippet instead.

### Will structured data give me star ratings?

Not guaranteed. Google shows rich results where it sees fit. The main benefit is that the page is understood correctly.

### How long until a new site appears in Google?

Indexing can take days to a few weeks. Settling into competitive rankings takes months. Submitting a sitemap in Search Console speeds up discovery.

### How often should I repeat the keyword?

There is no number. Use it naturally in the title, the first paragraph and one subheading. Forced repetition hurts readability and does not help.

### Does SEO cost extra?

Basic technical SEO should not be a separate line item. Titles, sitemap, canonicals and structured data are part of building the site properly. Writing content and migrating an old site are separate work.

## Sources

- [SEO Starter Guide: The Basics](https://developers.google.com/search/docs/fundamentals/seo-starter-guide), Google Search Central
- [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), Google Search Central
- [Mobile-first indexing best practices](https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing), Google Search Central
- [Introduction to structured data markup in Google Search](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data), Google Search Central
- [What is a canonical URL](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls), Google Search Central
- [Learn about sitemaps](https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview), Google Search Central
- [Schema.org](https://schema.org/), Schema.org

**A site with SEO built in** [Get a quote](https://radkod.com/en/get-a-quote)
