Website Development SEO Basics: What to Build In
A large share of SEO is not marketing at all — it is decisions made during website development that are cheap at build time and expensive later. URL structure, rendering strategy, internal linking and editable metadata all fall into that category.
This guide covers what to build in from the start, in rough order of how painful it is to add afterwards.
Make sure the site can be crawled and indexed#
Everything else is irrelevant if search engines cannot reach or read your pages. This is also where launch-day mistakes cluster.
- robots.txt on production allows crawling. The staging copy must not be deployed with it.
- No stray noindex meta tags carried over from staging.
- Every page has a self-referencing canonical URL, and there is one canonical hostname.
- Content is in the HTML, or server-rendered. If it only appears after JavaScript runs, indexing becomes slower and less reliable.
- An XML sitemap listing only indexable, canonical URLs — not filtered or paginated variants.
- Every indexable page has at least one internal link. Orphaned pages are barely crawled.
- Consistent status codes: 200 for real pages, 404 for missing ones, 301 for moved ones.
The single most common launch failure in this list is the staging robots.txt reaching production. Check it from outside your network on launch day.
Structure that search engines can read#
Structural decisions are the ones that are painful to change later, because changing them means redirects and losing accumulated signals.
| Decision | Build it as | Cost of changing later |
|---|---|---|
| URL pattern | Short, lower case, hyphenated, stable | High — redirects and lost signals |
| Heading hierarchy | One H1, no skipped levels | Low |
| Internal linking | Hubs linking to detail pages and back | Medium |
| Pagination | Crawlable links, not JavaScript-only | Medium |
| Faceted navigation | noindex on filter combinations | High — index bloat is slow to clear |
| Language versions | Prefix URLs plus reciprocal hreflang | Very high |
Metadata your team can actually edit#
A common build failure is generating titles and descriptions from a template with no way to override them. Six months later marketing needs to change one page's title and the answer is a developer ticket.
- Editable title tag per page, with a sensible generated default.
- Editable meta description, with a visible character counter in the CMS.
- Editable Open Graph title, description and image for shared links.
- Structured data on the templates that support it: Article, Product, FAQ, Breadcrumb, Organization.
- A per-page noindex switch for pages that should exist but not rank.
- Automatic canonical, with a manual override for the rare case that needs one.
Only mark up what is actually visible on the page. Structured data describing content a visitor cannot see is a policy violation, not a shortcut.
Speed and stability as build requirements#
Page experience is part of the build, not a later optimisation project. Retrofitting speed onto a finished site usually means undoing decisions rather than adding code.
| Metric | Target | Built in by |
|---|---|---|
| Largest Contentful Paint | Under 2.5s | Prioritising the hero image, avoiding render-blocking assets |
| Cumulative Layout Shift | Under 0.1 | Width and height on images, reserved space for embeds |
| Interaction to Next Paint | Under 200ms | Less JavaScript, and not blocking the main thread |
| Page weight | As low as the design allows | Modern image formats, no unused libraries |
| Time to First Byte | Under 800ms | Caching, a CDN, and sensible database queries |
Frequently asked questions
Should SEO be in the development brief?
The technical parts, yes — crawlability, URL structure, editable metadata, structured data, performance targets and redirect mapping. Content strategy and link building are separate work with a different skill set. Putting the technical requirements in the brief means they are quoted rather than discovered after launch, which is when they cost several times more.
Does a JavaScript framework hurt SEO?
It can, if pages are rendered only in the browser. Search engines can execute JavaScript but do so on a delay and not always completely, so client-only rendering makes indexing slower and less reliable. Server-side rendering or static generation removes the problem. For a content site the simplest answer is usually to put the content in the HTML.
How long after launch before I see search traffic?
For a brand-new domain, typically weeks for indexing and months before meaningful rankings — new sites do not rank quickly regardless of technical quality. For a relaunch of an existing site with clean redirects, expect two to six weeks of fluctuation before things settle back around the previous level.
Do I need an SEO plugin?
On a CMS, a plugin is a convenient way to give editors control over titles, descriptions, canonicals and sitemaps. It is not a strategy, and its default output is not a substitute for someone deciding what each page should be about. On a custom build the same functionality is usually written directly and is lighter for it.
website development seoseo basicstechnical seoseo for developerscrawlabilityon page seo
