SEO should start with web design, not after it

The order most sites follow

Here's the sequence most websites follow, and it's the sequence that's most often the reason the site isn't found the way the business needs it to be found. A design is chosen, a template is built around it, the content gets poured in, and then, if anyone thinks of it, SEO is applied to the result.

By that point, the architecture is already fixed, the URLs are already weird, the headings are already decorative, and the speed profile is already set by whatever the theme shipped with. Now the SEO has to work inside all of that, and that's why so little of it sticks. The order is the whole of the problem, and the order is the whole of the solution.

The cost of the retrofit

The cost of the retrofit is the cost that's most often missed, and it's the cost that's most often the reason the site is being replaced in the first place. The redirects to hide the URL structure the site shipped with, the duplicate content discovered and collapsed after launch, the page-speed fixes made against a design that blocked them, and the content rewrites to match an intent the page never stated.

None of that is avoidable if the order was wrong, and all of it is avoidable if the order was right. That's the whole of the cost, and it's the cost that's most often the reason the conversation about SEO starting with web design is happening in the first place.

The decisions that come first

The decisions that come first are the ones that are most often skipped, and the ones that are most often the reason the site isn't found the way the business needs it to be found. The information architecture and the URL map, the one promise per page, the semantic HTML and the heading hierarchy, the speed budget, the structured data plan, and the internal linking plan.

Each of those is a decision that's made before the first pixel is placed, and each of them is a decision that's most often the reason the site is found the way the business needs it to be found, or the reason it isn't. The decisions are the whole of the SEO, and they're the decisions that come first, and that's the whole of the case.

The design-vs-SEO myth

The myth is the one that's most often the reason the business accepts a site it can't see or a site it doesn't like, and it's the myth that's most often the reason the conversation is happening in the first place. The idea that SEO and design are in opposition, that a page built to rank will look like a brochure, and a page built to look good will be invisible to the search engine.

Both halves of that idea are wrong, and the correction matters, because it's the reason so many businesses accept a site they can't see. A search engine doesn't see beauty, it sees structure, clarity, and a match between the page and the query, and a person sees all of those things too. The design that serves the search engine is the same design that serves the visitor, and the conflict only exists in the minds of the people who design for decoration and then apologize to the search engine for it.

The whole point

The whole point is the one that's most often left out of the conversation, and it's the one that's most often the reason the site is being replaced in the first place. The SEO is not a feature that's added to the site, and it's not a service that's applied to the site. It's the architecture of the site, and the architecture is the thing that's decided before the first pixel is placed.

That's the whole of the case, and it's the case that's been made on the merits of the work, not on the hype of the moment. The site that's built with SEO in the architecture is the site that's found the way the business needs it to be found, and the site that's built with SEO bolted on after is the site that's most often the reason the conversation is happening in the first place.