The 30-second version
Our web design page promises SEO built into the foundation, and a promise like that deserves receipts. So here they are: the specific, checkable decisions that phrase covers, from semantic structure to speed budgets to town page architecture. The contrast is the industry’s default pattern, where a site gets built for looks and SEO becomes a phase 2 package sold later. Phase 2 never works the way the pitch implies, because the choices that decide rankings are load-bearing walls. You don’t add those after the house is up.
The phase 2 pattern, and why it never works
The standard sequence goes like this: a builder ships a site that looks great in the handoff meeting, then months later, when the phone hasn’t rung, sells an SEO engagement to “optimize” it. Except the URLs are a mess, the headings are decorative, the pages Google needs don’t exist, and the whole thing takes six seconds to load. Optimizing that isn’t tuning, it’s renovation: restructuring URLs (with redirects for every change), rebuilding page hierarchies, and re-doing work that was cheap at build time and expensive now.
The tell is in the incentives. A builder paid for how the site looks at handoff has no reason to sweat the invisible layer. In sites we audit, the invisible layer is exactly where the leads went missing.
Structure a crawler can read
Google reads your site as a document, and foundation SEO starts with making that document coherent. One clear headline per page saying what the page is about, subheadings that actually describe their sections rather than shouting slogans, real text instead of words baked into images, and navigation built as navigation. This is called semantic structure, and the details are unglamorous: heading tags in a logical hierarchy, content organized the way a person would outline it.
URLs belong here too. A page that lives at /services/roof-repair/ tells Google and humans what it is. A page at /page-id-2847/ tells them the builder didn’t think about it. Clean, readable, permanent URLs are a day-one decision, because changing them later means redirects, and skipped redirects are how sites lose years of rankings in a weekend.
Speed as a budget, not an aspiration
Every builder says their sites are fast. The foundation version is different: a performance budget set before design starts. Maximum page weight, maximum script count, image formats and sizes decided as policy, all measured on a mid-grade phone rather than the designer’s desktop. Design choices then have to fit inside the budget, instead of speed being whatever’s left over after the animations.
This matters because speed retrofits are miserable. A slow site is usually slow architecturally (the platform, the theme, the pile of plugins), and no caching plugin rescues a heavy foundation. Build light and stay light is a decision that costs almost nothing at the start and can’t be bought back later. We wrote up how far this goes on our own build, a site with no hosting fees and a 99 PageSpeed score, if you want the extreme version.
Schema and the town page architecture
Schema markup is structured data in the code that tells Google explicitly what it’s looking at: this is a business, here’s its service area, these are its services, these are real FAQ answers. It’s how sites qualify for richer search listings, it costs little at build time, and almost no phase 2 engagement ever gets around to doing it properly.
Architecture is the bigger one for local businesses. If you serve twenty towns, the site’s structure has to have a place for twenty town pages to live and grow, planned in the sitemap before design starts. When that architecture exists from day one, adding a town page is routine. When it doesn’t, every local expansion is a fight with the template, which is why so many contractor sites mention two towns and quietly forfeit the other eighteen.
Image discipline and the boring details
The rest of the foundation is a list of small disciplines that separately look trivial and together decide outcomes. Images compressed and sized before upload, with descriptive filenames and alt text instead of IMG_4023. Explicit dimensions so the page doesn’t jump around while loading. An XML sitemap, a sane robots file, canonical tags. And on any rebuild, the single most neglected item in the industry: a complete redirect map from every old URL to its new home, because launch day without one is how a redesign celebrates itself by deleting its own rankings.
None of this is secret knowledge. It’s just work that has to happen at a specific time, which is before and during the build, not after.
How to tell if your builder actually did this
You can audit most of this without technical skills. Run your site through Google’s free PageSpeed Insights and read the mobile score. View the page source and search for “h1”; there should be exactly one per page. Look at your URLs in the address bar and ask whether a stranger could guess the page from the address. Ask your builder three direct questions: where’s the schema markup, where’s the redirect map from the old site, and where will town pages live? If the answer to any of them is “we handle SEO in phase 2,” you have your answer about the foundation.
This checkable list is what we mean when our web design page makes the foundation promise, and it’s why our SEO work starts faster on sites we built: the renovation step is already done.
Common questions
Isn’t this just technical SEO by another name? Largely, yes, with one difference that matters: timing. The same items cost little during a build and a lot as a retrofit. Foundation SEO is technical SEO done when it’s cheap.
My site is already built. Do I need a rebuild? Not automatically. Some foundation pieces (schema, image discipline, sitemaps) retrofit fine. Others (architecture, platform-level speed) usually don’t. An honest audit sorts your list into fixable-in-place and structural, and the ratio decides.
If the foundation is right, do I still need ongoing SEO? Yes. The foundation makes effort count; it isn’t the effort. Content, local signals, reviews, and links are still the growth engine. The difference is that on a sound foundation that work compounds instead of leaking.
Why do so many builders skip all this? Incentives, mostly. The site is judged at handoff, when it’s evaluated with eyes rather than crawlers, and the invisible layer doesn’t show in the reveal meeting. It shows six months later, in Search Console, when the builder is long paid.