Here’s what happens on most website projects.
Designer builds the site. Developer codes it. SEO person gets called in two weeks before launch.
Then the SEO person opens a 30-item fix list. URL structures that need rewriting. Images with no alt text. Headings in the wrong order. Pages that don’t exist for the keywords that matter.
Half the list won’t get done because the launch date can’t move. The other half gets patched over the next 6 months.
This is the normal way to build a website. It’s also the most expensive way.
What goes wrong when SEO comes last
The problem isn’t that SEO people are slow. It’s that most SEO fixes aren’t actually SEO problems. They’re design decisions that nobody made with SEO in mind.
A few examples we see every week:
- Service pages designed as pretty one-pagers with no H2 structure, so Google can’t tell what each section is about
- A top navigation that has 11 items, which splits the site’s authority across too many pages
- Blog category URLs that go /blog/post-123 instead of /blog/category/post-title, so there’s no topic grouping
- Product pages that use the same meta title template for every product
- Images that are 2MB each because they weren’t compressed in the design handoff
- Mobile menus that hide important internal links behind clicks, so link equity doesn’t flow
None of these are “SEO work.” They’re design and build choices. But they cost you traffic for years if you get them wrong.
7 decisions that are design decisions AND SEO decisions
If you’re planning a new site, these choices need SEO input before they get locked in:
- URL structure. Flat or nested? Keyword-based or ID-based? Change it later and you’re redirecting hundreds of pages.
- Page templates. How do service pages, blog posts, category pages differ? Each template needs its own meta logic, heading hierarchy, and schema markup.
- Navigation. Which pages go in the top menu? Which get surfaced from the footer? This decides where your link equity flows.
- Image strategy. Compressed webp or raw jpg? Lazy-loaded or not? CDN or self-hosted?
- Page speed targets. Carousel in the hero? Video background? Fancy animations? All of these have a page speed cost.
- Content modeling in the CMS. Can editors add alt text? Meta descriptions? Schema? If not, every page launches with gaps.
- Internal linking patterns. Related posts, breadcrumbs, in-content links. Design decisions, all of them.
How to actually bring SEO into design
You don’t need a full-time SEO person on the project. You need SEO input at three specific moments:
Before wireframes. Review the sitemap, URL structure, template plan.
During design. Review heading hierarchy, meta title and description logic, image strategy, mobile layout.
Before launch. Run a technical audit, check indexation, redirects, schema, speed.
That’s it. 3 touchpoints, usually a day or two of work each. Spread across a 2-month project, it’s barely visible to the design and dev team.
Compared to retrofitting after launch? Easily 10x cheaper.
The real win
The biggest cost isn’t the fix list after launch. It’s the traffic you don’t get for the first year because the site wasn’t built to rank.
A site that launches with good URL structure, clean templates, fast pages, and clear navigation starts earning organic traffic from month one.
A site that launches without those things earns traffic maybe from month six, after someone has gone back and fixed everything.
That’s a 5-month gap. For most ecom businesses, that’s real money.
Technical SEO isn’t something you bolt on. It’s a set of choices you make while you build. Make them early and you save yourself the cleanup.
