Web design or SEO first is the question that decides whether the most common and most expensive mistake in a website project happens to you: treating search as something you add at the end. A design is approved, a developer builds it, the site goes live, and only then does somebody ask why it is not ranking.
By that point the decisions that determine whether the site can rank have already been made, usually by people who were not asked to think about them. Fixing them means rebuilding parts of a site that was signed off three weeks ago.
The answer to web design or SEO first is that they are not sequential. Search work belongs at the start, alongside the brief, and its output is one of the inputs to the design.

What has to be decided before anyone designs anything
What the site is supposed to rank for
Keyword research is not a task for after launch. It tells you how many pages the site needs, what each one is about, and what people call the thing you sell. Businesses routinely name their services internally in language nobody searches for, and discovering that after the navigation is built is painful.
A keyword map produced before design is a list of pages with a purpose attached to each. That list is the sitemap. Designing a sitemap without it is guessing.
The URL structure
URLs are cheap to decide and expensive to change. Get them right at the start and you never think about them again. Get them wrong and every fix afterwards involves redirects, lost signals and a period of instability.
Shallow, readable, lowercase, hyphenated, no dates on evergreen pages, no parameters where a clean path would do.
How much text each template holds
This is where design and search collide most often. A minimal design with forty words per section looks superb in a mockup and gives search engines almost nothing to work with. A design that only accommodates short copy forces either a bad page or a redesign.
The fix is simple and has to happen early. Write the content, or at least the outline and approximate length, before the layout is finalised. Designers work better with real content anyway, and the result is a template that fits what the page actually needs to say.
The platform
Most platforms can be made to rank. They differ in how much work that takes. Anything that renders content only through JavaScript, blocks you from editing titles and meta descriptions, or generates URLs you cannot control will cost you either flexibility or money later. Establish what the platform allows before committing, not after.
Web design or SEO first: the order that works
Research first. Keywords, competitors, what the market searches for and how they phrase it. This produces the page list.
Structure second. Sitemap, URL scheme, navigation and internal linking logic, built from the page list rather than from an org chart.
Content third, at least in outline. Headings, the argument each page makes, the rough length. This is what the design has to accommodate.
Design fourth, with the content in hand. Now the templates are shaped by what the pages need rather than the other way round.
Build fifth, with the technical requirements written into the brief. Clean HTML, real headings, fast loading, proper image handling, structured data where it applies.
Launch sixth, with redirects mapped if there was a previous site, tracking verified before the switch and Search Console ready.
Ongoing SEO after that, on a foundation that does not have to be rebuilt.
If the site is already built
Most businesses reading this are not at the start of a project. They have a site that looks fine and does not rank.
In that situation the work is triage rather than sequencing. An audit establishes which problems are structural and which are cosmetic. Some are fixable within the existing build, such as titles, headings, content depth, internal links and page speed. Others, such as a URL structure that buries important pages or a template that cannot hold enough content, are decisions baked into the build.
Knowing which category each problem falls into is the difference between a productive year and an expensive rebuild. It is worth finding out before you commission either.
The conversation to have with your web designer
Settling web design or SEO first before the brief is written saves both sides from redoing work once the site is live.
Ask three things before the project starts.
Can I edit the title tag and meta description on every page without a developer? A surprising number of builds say no.
Will the content be in the HTML, or rendered by JavaScript after load? The second is workable but adds risk and cost.
Who is responsible for redirects if we are replacing an existing site? Somebody has to own this, and if nobody does it will not happen.
A good web design company in Dubai will have clear answers and will not be offended by the questions. One that treats them as interference is telling you something useful.
Google’s SEO Starter Guide is a useful checklist to hand a web designer who has not built a search-ready site before.
Getting the sequence right
If you are planning a new site, bring search into the brief rather than the launch. If you already have one, find out which of its problems are fixable before deciding whether to rebuild.
Either way, the free website audit gives you a picture of where the site stands today, and technical SEO covers the structural side of the work. If a rebuild is on the table, get in touch before the design is signed off rather than after.