A distribution business with $12 million in revenue briefs a design studio to rebuild their site, then six weeks after launch briefs an SEO consultant to work out why it still is not ranking for the terms that used to bring in enquiries. The consultant's first recommendation is to flatten a URL structure the design studio just built three levels deep. That means new navigation, new redirects and new internal links across forty pages that only just went live, on a site the business paid for twice without meaning to.
This is how a lot of website projects still get run. Design and SEO get bought as two separate purchases, from different suppliers, briefed by different people inside the same business. The design agency cares about how the site looks and how the CMS works for the marketing team. The SEO agency cares about crawl paths, keyword targeting and page speed. Nobody in the room owns both.
Site architecture, URL structure, page speed, internal linking and content hierarchy are structural choices baked into the build. Changing any of them once the site is live means rebuilding pages, redirecting URLs and re-establishing internal links, work that is slower and costlier than getting it right the first time.
The decisions that lock in before SEO gets a look
Site architecture is the clearest example. How pages nest under categories, how many clicks it takes to reach a product or service page, whether related content sits together or scattered across the site: these choices get made in a sitemap review, usually months before launch, by whoever is running the design project. Once a hundred pages have been built against that structure, changing it means redirect mapping, new internal links and a period where rankings can move around while search engines work out what changed.
URL structure follows the same pattern. A URL like /products/category/subcategory/product-name carries different signal than /product-name, and switching between the two after launch means every backlink, every bookmark and every page already indexed by Google needs a redirect that preserves the value the original URL had built up. We write these into the build from the first structure review, on both Webflow and Shopify projects, because retrofitting them later is slower and less reliable than getting them right once.
Page speed is a design decision wearing an SEO hat
Page speed gets sold as a technical fix: compress the images, defer the scripts, enable caching. Most of what determines how fast a page loads gets decided by the design itself. A hero section built from six overlapping animations, a product page loading four different apps for reviews, upsells and live chat, a font stack pulling from three different providers: these are creative and functional choices made during the build, and each one adds weight a developer has to work around later rather than avoid from the start.
On Shopify stores this compounds quickly, because apps get added one at a time over years, each one reasonable on its own and collectively heavy enough to slow the whole store down. We cover the mechanics of this in more detail in our piece on Shopify speed optimisation. Speed is close to impossible to bolt on convincingly after launch. It has to be designed for.
Internal linking and content hierarchy
A website's internal links tell search engines which pages matter most, more clearly than most other signals on the page. If your service pages, your best-performing articles and your case studies are not linking to each other in the places a reader would look, you are asking Google to guess at your priorities. Most sites make that guess by accident, through whatever order the design agency happened to build pages in.
Content hierarchy is the same problem from a different angle. Which topics get an H2 and which get buried in a paragraph, how deep a piece of content sits in a category, whether a page targets one clear topic or several loosely related ones: those choices shape how search engines read the page's purpose. Get the hierarchy wrong during the build and SEO copywriting afterwards rarely corrects it fully, because it is optimising a structure that was never built to support the content in the first place. We go into the wider pattern of ranking problems that trace back to structural decisions in why your website is not ranking.
Two agencies, two briefs, one site caught in the middle
When the design agency and the SEO agency never speak, the business becomes the only point of coordination between two suppliers who each assume the other has covered the gap. The design agency assumes SEO best practice is baked into the platform. The SEO agency assumes the site was built with their recommendations in mind, because that is how most engagements get scoped. Neither assumption holds up, and the business finds out only once rankings do not move the way the SEO invoice implied they should.
Combining both functions under one roof removes the coordination problem entirely, but that is not the only fix. At minimum, the two providers need to be talking to each other before the build starts, not after launch when the cost of change has already tripled. A sitemap and URL structure reviewed by both parties before development begins costs an afternoon. Rebuilding that structure eighteen months later, once it is indexed and ranking for the wrong reasons, costs considerably more.
This is also why the retainer question comes up so often once a site is a year or two old. A business notices rankings have stalled, hires an SEO retainer to fix it, and finds most of the recommendations point back at the site itself rather than at content or backlinks. We have written separately about when a better website beats another SEO retainer, because the two questions are not always the same one, and the answer changes which contract you should be signing next.
Ranking and converting are the same architecture problem
Structural decisions that affect ranking tend to affect conversion too, because both depend on a visitor or a search engine understanding what a page is for within seconds of finding it. A confusing hierarchy that dilutes topical relevance for Google usually confuses a human visitor in a similar way. We cover the human side of that in five seconds to trust and the conversion side in why your website is not converting.
When Clean Collective rebuilt on Shopify, addressing structure, speed and content together rather than as separate workstreams produced a 103% increase in conversion rate alongside a 28% increase in sales. Those numbers came from the same set of decisions, made once, during the build, rather than layered on afterwards by whichever specialist happened to be in the room that quarter.
What integrated looks like at Skyrocket
We build Webflow and Shopify sites for established New Zealand and Australian businesses, and site architecture, URL structure and internal linking get scoped alongside design from the first strategy conversation. On Shopify projects, theme design happens inside Shopify's own architecture at the same time as the build, which means speed and structure decisions get made with the finished store in mind rather than retrofitted once a theme already exists.
We also do real SEO work: audits, technical recommendations and implementation, rather than a packaged monthly retainer sold regardless of what the site needs. For a broader look at what optimisation covers beyond the build itself, see our guide to website optimisation in New Zealand. Once a site is live, structural and content changes are handled through website support and maintenance rather than a separate SEO contract duplicating work already done.
If you already have two separate providers
Not every business is starting from scratch, and plenty already have a design agency and an SEO consultant working independently of each other. Coordination between the two is achievable without combining the contracts, provided both parties agree on a handful of decisions before either one proceeds:
- URL structure and folder logic, signed off by both before development starts
- A shared list of priority keywords mapped to specific pages, not applied after the fact
- Page speed budgets agreed before design begins, not measured after launch
- An internal linking plan connecting service pages, articles and case studies from day one
None of this requires the SEO consultant to sit in every design meeting. It requires one structured conversation before the build starts and one review before it goes live, which is considerably cheaper than the alternative.
Common questions
Should we hire one agency for design and SEO, or keep them separate?
Either can work, provided the two functions talk to each other before the build starts. An integrated team removes the coordination problem by default. Two separate providers can still produce a strong result if URL structure, internal linking and speed budgets are agreed jointly before development begins, rather than reviewed by the SEO side after launch.
Can SEO fix a poorly structured website after it launches?
Some of it can be fixed after launch, yes. Content, metadata and on-page targeting can be adjusted without much disruption. Site architecture, URL structure and page speed are harder, because changing them means redirects, re-crawling and a period of instability in rankings while search engines process what moved. The later these get addressed, the more expensive and disruptive the fix becomes.
Does this apply to Shopify stores as much as Webflow sites?
More, if anything. Shopify stores tend to accumulate apps and third-party scripts over time, each one adding page weight that a design agency working apart from SEO has no reason to flag. Structural decisions on Shopify get made alongside the theme build, so speed and architecture need to be part of that conversation from the start rather than an afterthought once the store is trading.
How much does poor site architecture actually cost in lost rankings?
It varies by site and category, but the mechanism is consistent: a confusing hierarchy dilutes the topical relevance search engines assign to individual pages, spreading ranking potential across pages competing with each other instead of one clear target. The cost shows up as pages sitting on page two instead of page one, or traffic landing on the wrong page for the query that brought it there.
What is the first thing to check if design and SEO were handled separately on our current site?
Start with URL structure and internal linking, because both are visible without technical tools and both point to whether the two workstreams were coordinated. If your best-performing articles do not link to your service pages, and your service pages do not link to each other where a reader would expect, that usually signals the build and the SEO work happened on separate timelines.
Do you offer an ongoing SEO retainer?
No. We do audits, technical recommendations and implementation work as needed, and ongoing structural or content changes run through website support and maintenance rather than a recurring retainer sold regardless of what the site needs that month. If you are weighing a retainer against fixing the site itself, our piece on SEO retainers versus a better website covers the trade-off in more detail.
If your site was designed by one provider and optimised, or left unoptimised, by another, the fastest way to find out what that is costing you is to have both reviewed together. Get in touch and we can review both together, then tell you what actually needs fixing first.
