When companies start a new website project, design is naturally one of the first things they think about.
What should the colours look like?
How should the homepage feel?
Will it look more modern than the competition?
All of these matter.
But much of a successful website project is shaped by decisions made before visual design begins.
A website can look impressive and still fail because its purpose is unclear, its performance is poor, content management is difficult or SEO was treated as an afterthought.
Before starting a new project, these ten questions are worth answering.
1. Define the job of the website
“We need a corporate website” is not a complete brief.
What should the website actually do?
- Generate enquiries?
- Present products?
- Reach international customers?
- Generate demand from search?
- Support dealers?
- Build trust?
- Sell online?
A website can serve several goals, but if no priority exists, the content, design and CTA structure often become unfocused.
Start with the goal, then design the interface.
2. Plan the information architecture before the design
It is easy to begin with “Home, About, Services, Contact”.
Real information architecture goes further.
Before design begins, consider which services need their own pages, which products require detail pages, how case studies should work, whether there will be a knowledge centre, how Turkish and English pages map to each other, and which search intents deserve separate pages.
Good information architecture supports both usability and SEO.
3. Mobile should not be an afterthought
Mobile design is not simply a smaller desktop website.
On a phone, navigation, headline length, image cropping, form fields, CTA buttons, sticky elements, tables and card layouts need to be reconsidered.
A layout that looks impressive on a large screen may become unnecessarily long or difficult to use on mobile.
Mobile UX should therefore be part of the design system from the beginning.
4. SEO is not a plugin added after launch
Many important SEO decisions are made during development:
- URL structure
- heading hierarchy
- canonical URLs
- hreflang
- structured data
- internal linking
- performance
- mobile usability
- sitemap architecture
Google’s SEO Starter Guide frames SEO as helping search engines understand content while helping users discover useful information.
Source: Google Search Central — SEO Starter Guide
5. Do not leave content until the end
A common workflow is:
“Finish the design first, then we will fill the boxes with copy.”
This often creates a disconnect between design and content.
A page behaves differently when it contains a short positioning statement, a long technical explanation, a product specification table or a case study.
When content and design evolve together, the real structure of the page becomes visible earlier.
6. Define performance expectations early
Strong imagery, video and motion can give a website character.
But the way those assets are delivered matters.
Performance can be affected by image size, video bitrate, fonts, JavaScript, third-party scripts, server response and CSS architecture.
Google uses Core Web Vitals such as LCP, INP and CLS to evaluate important aspects of real-world page experience.
Website Speed and Performance Optimisation
7. Think about who will manage the website
Launching the website is not the end of the project.
Will someone inside the company need to add products, publish articles, update case studies or manage multiple languages?
These requirements should influence the content management experience.
If the backend is difficult to use, the website may eventually become a static and outdated presentation.
8. Clarify domain, hosting and code ownership
At the end of the project, you should know who owns the domain account, who controls the hosting, who has administrator access, whether source code is delivered, where backups are stored and who owns third-party service accounts.
Unclear ownership can become a serious problem when a company needs to change agency or developer.
9. Make space for real work
For B2B and professional service companies, real projects are among the strongest sales assets.
Saying “we build websites” is not the same as showing completed work.
A strong case study section should go beyond a wall of logos and show the client, challenge, approach, work delivered and real project screens.
10. Plan what happens after launch
A strong website project does not end with “the site is live”.
After launch, teams should monitor Search Console, performance, user behaviour, conversions, organic visibility, technical issues and content opportunities.
Real user behaviour often reveals opportunities that cannot be predicted during design.
A website is more than a design file
Design is an important part of a successful website, but it is not the only part.
Strategy, content, performance, SEO, technical architecture, mobile experience and ownership need to work together.
A strong website is not simply one that looks impressive. It is a digital product that serves real business goals, can be measured and can continue to improve.
—