An SEO-Ready Website: What Gets Built into the Code Before Any Article
17 Nov 2026
Many companies ask for “SEO” after the site is built, then find the problem is the build itself: pages that are not indexed, unclear URLs, a slow site on mobile. This guide explains what to ask your developer for so the site is ready for search from day one.
Search engine optimisation is not a service added after handover. A large part of it is decisions in how the site is built, and if they are neglected, no number of articles or ads makes up for it. A site whose pages Google cannot read, that shows the same content on ten URLs, or that opens slowly on an average phone, starts the race behind.
That does not mean every site needs a complex technical expert. It means there is a clear checklist that should be part of the delivery, and you can ask about it yourself.
Pages must be readable
Some sites are built so content appears only after scripts run in the browser. Visitors see the page, but search engines may see an empty or partial one. Ask for each page’s content to be present in the HTML the server returns, and confirm it with the URL Inspection tool in Google Search Console after launch.
Clear, stable URLs
- A URL for each page that describes its content, such as /services/web-development, not random numbers.
- One URL per page, with a canonical tag naming it when other versions appear.
- When an old URL changes, a permanent 301 redirect to the new one, never an error page.
- For bilingual sites, a separate URL per language with hreflang tags linking them.
Titles and descriptions
Each page needs its own title and description, written by someone who understands what customers search for, not the same title across the site. Just as important, you should be able to edit them yourself in the admin panel without going back to the developer. Add a share image that appears when the link is sent on WhatsApp or social media.
Speed on mobile
Most visits in Egypt come from phones, and Google evaluates the mobile version of the site. Images should be compressed and served at the right size for each screen, fonts should not delay text, and the page should not jump while loading. Ask for PageSpeed results for the main pages as part of delivery, and test yourself on a real phone on mobile data.
Structured data
Structured data describes the page in a language search engines understand: this is a business with an address and phone, this is a service, this is an article with an author and date, this is a product with a price. It does not guarantee special search features, but it helps search engines understand the site accurately. Ask for it to be generated automatically from page data, not added by hand each time.
The sitemap and robots file
A sitemap that updates automatically whenever a page is added, and a robots file that does not block important pages by mistake. This is a very common launch error: the site was built on a staging server that blocked indexing, then moved across unchanged. Check the file on day one.
After launch
Connect the site to Google Search Console from the first day, submit the sitemap, and watch indexed pages and errors. Then comes content: a page for each service that answers customers’ real questions, and articles that serve buying decisions. A good build lets that content work; a weak one buries it.
A checklist before you accept delivery
- Does the page content show in Google’s URL Inspection tool?
- Can I edit the title and description of every page?
- What is the mobile speed result for the main pages?
- Does the sitemap update automatically, and is the robots file correct?
- What happens to old URLs if this site replaces an existing one?
If you are rebuilding an existing site, read company website redesign, and to turn visits into enquiries see a business website that generates leads. Delivery is through website development.
Send your current site’s link or a description of the new one from start your project.
