What SEO-Friendly Web Design Means — And What It Does Not
One of the most common lines in a proposal is "your site will be SEO-friendly." Most of the time that sentence says nothing, because the term has no agreed definition. SEO-friendly web design is not a feature bolted on afterwards; it is a set of decisions made at the design stage that become expensive to reverse later.
Start with what it is not. It is not sprinkling a keyword across the page twenty times. It is certainly not hiding text at the bottom of the page. And it is not installing a plugin until the light turns green — those plugins keep a checklist, they do not make the decision.
What it actually is: how a page is divided, which text is a heading, how heavy the images are, how the navigation is built, and how the content is delivered to the browser. All of these are design decisions, and all of them affect search results directly. Saying "now let's do the SEO" after the design is signed off is like adding load-bearing columns after the building is finished.
Six Decisions Made at the Design Desk
There are six things we settle before design begins. We do not draw a single pixel until they are agreed.
- Page purpose: each page does exactly one job. If two pages do the same job, neither ranks — they suppress each other. A navigation draft is really a search decision.
- URL structure: short, readable, permanent. An address that changes later loses the value it accumulated; redirects rescue some of it, never all.
- Content density: how much room does the design leave for text? A design made purely of imagery looks beautiful and gives a search engine nothing to read.
- Heading structure: which text is the H1 and which are H2s. This is a document-structure question, not a font-size question.
- Image budget: total kilobytes of imagery per page. If this ceiling is not set at the start, it cannot be imposed later.
- Mobile behaviour: what gets hidden on small screens. Hidden content is still evaluated, but hidden content does not reach the visitor — the designer sets that balance.
The Designer Decides the Heading Hierarchy
This is the mistake we see most often in practice. A page ends up with three H1 tags because the designer wanted large type in three places. Or the real heading is baked into an image, so as far as the crawler is concerned the page has no heading at all.
The correct approach: every page has exactly one H1 and it states what the page is about. Sub-sections are H2, and their children are H3. The sequence is never skipped — you do not jump from H2 straight to H4. You can style them at any size you like; the skeleton of the document and the size of the type are separate matters.
That skeleton is also how AI-driven search systems read a page. Systems that summarise a page and present it as an answer look at this hierarchy first. We covered that side in our article on visibility in AI search.
Speed Is a Design Decision
Page speed is usually assumed to be a server question. In our experience most of the slowness is created at the design stage.
A full-screen video background, six different font families, animations firing in every section, uncompressed imagery, three separate tracking scripts. Each looks harmless on its own; together they sink the site. And they cannot be removed after the design is approved, because by then they are the design.
Our practical benchmark is simple: a page should paint its first meaningful content on mobile in under two and a half seconds. If the design breaks that, the design changes — not the server. We listed the other sources of slowness in our site speed article.
Mobile: Rebuild, Do Not Shrink
The majority of visitors to corporate sites now arrive on a phone, and Google evaluates your page in its mobile form. Despite that, most designs are still drawn on desktop and squeezed down afterwards.
Here is what squeezing produces: tap targets collide, tables scroll sideways, forms stretch on forever, and the most important button falls inside a collapsed menu. The visitor leaves. The search engine sees them leave.
The right method is to build the important pages on the narrow screen first. A layout that works narrow will work wide; the reverse is almost never true.
The Cost of Fixing It Afterwards
Here is the real reason for this article: a share of the work that reaches us arrives as "the site just launched, now let's get some SEO done." At that stage, part of what needs doing cannot be done without breaking the design.
If the URL structure is wrong, bulk redirects are required. If there is no heading skeleton, the template files have to be opened. If the imagery is heavy, all of it gets regenerated. If the navigation architecture is wrong, pages must be merged. Together these cost nothing on a project started correctly, and become a separate project when retrofitted.
In short: SEO-friendly design is not the expensive option. Retrofitted SEO is. We describe how we run the process in our SEO method article.
Pre-Handover Checklist
Ask for these before you accept delivery of a site. Every item can be checked individually and none of them require technical knowledge.
- Does every page have its own non-repeating title and description?
- Does every page have exactly one H1, and is it written as text rather than baked into an image?
- Are the alternative texts on images filled in?
- Does the first paint on a phone happen in under three seconds?
- Are the addresses sensible and readable, rather than ending in a string of digits?
- Do a sitemap and a robots file exist, and have they been submitted to the search console?
- Is the same content reachable at two different addresses anywhere?
- Are the contact and quote pages reachable from every page?
A handover that cannot answer yes to all eight is technically incomplete. Our SEO service begins with a setup covering every one of them.
What would this cost if we did it? We can tell you free of charge how many of these items your current site is missing. If you are considering a new build, select what you need and see an instant figure with our price calculator.
