Services
SEO Services Social Media Website Development AI Automation About Reviews Portfolio Blog Contact Free SEO AuditMost builds hand a finished design to an SEO afterwards and hope. These were built the other way round — structure, content architecture and technical groundwork planned together, which is cheaper than fixing it later and considerably less painful.
Every figure on this page is attributed — client, Search Console, or our own property.
Most agency portfolios show percentages with nothing behind them. Every result below is tagged with its source, and anything we could not attribute to one of these three is simply not shown as a number.
Builds where the search groundwork went in from the start — including this site, which you are reading and can inspect completely.
Legal tech · UK
A complete site built for the business rather than a template dressed up — structure, content architecture and the search groundwork done as one job instead of handing a finished design to an SEO afterwards.
Static PHP with shared includes. No React, no build pipeline, no CMS carrying three hundred plugins — because the site needs to be fast, crawlable and still editable in five years by whoever is here then. Every page is checked by a script that reads the rendered HTML, not the source.
What was hard: Rendering the pages found copy being HTML-escaped twice, so an apostrophe printed as raw entity text in 65 places — on pages that validated perfectly. Reading the markup would never have caught it.
Check this yourself: View source on this page, then run it through Google’s Rich Results Test. Every claim about how it is built is inspectable in two minutes.
Website work is the hardest kind to publish, because a build is usually delivered and then handed over. The client redesigns, rebrands or moves platform, and a portfolio entry from three years ago no longer looks like anything we did — while still carrying our name.
Rather than pad this page with sites we would no longer recognise, we add builds as clients approve being named and while the work is still live. If you want to see more before deciding, ask on a call and we will walk you through work we cannot publish but can show you directly.
This website is static PHP with shared includes. No React, no build pipeline, no content-management system carrying three hundred plugins. That is not nostalgia — it is the choice that makes a site fast, fully crawlable, and still editable in five years by whoever is here then.
Every page is checked by a script that renders it and reads the output rather than the source: schema validity, FAQ markup matching the visible text, heading order, tag nesting, internal links that resolve, images that exist. It runs across all 25 pages and currently reports zero failures.
It also catches what code review does not. Rendering the pages found that author-written copy was being HTML-escaped twice, so “Joe’s Blooms” was printing the raw entity as visible text in 65 places — on pages that validated perfectly and looked entirely correct in the markup.
You do not have to take any of that on trust. View source on any page here and check it.
The fastest way to judge a web developer is to look at their own site — not how it looks, but whether it is fast, crawlable, and built to be understood by whoever comes next.
Every build covers the same ground. What changes is scale, not which parts you get.
Sitemap, URL structure and content architecture agreed first, because moving a page after launch costs redirects and rankings.
Semantic markup, clean heading order, schema and Core Web Vitals treated as build requirements rather than a post-launch cleanup job.
Pages written to answer real search intent, not lorem ipsum with a promise to fill it in once the site is live.
Old URLs mapped and redirected before launch. This is the step where most rebuilds quietly lose the traffic they already had.
Hosting, domain, analytics, repository and accounts in your name. No hostage arrangement and no rebuild fee for leaving.
Documentation written for whoever maintains it next — including if that turns out not to be us.
Real clients, quoted in their own words — one of them named on the work above.
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
“Working with Ghalib has been an outstanding decision for our company.”
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“It was a pleasure working with Ghalib and his team.”
“Working with Ghalib resulted in a boost in our organic traffic.”
“Highly professional and dedicated to achieving results.”
All of them, in full, on our reviews page.
Static PHP includes, no framework, no build step and no JavaScript framework at all. Thirty pages, hand-built. That is the same stack we would hand a client, and the reason it is listed here is that you can verify every claim about it by viewing source.
Because it decides who can maintain the site after us. A page built from plain HTML, CSS and PHP can be picked up by any developer; one built on a framework needs somebody who knows that framework and the version you are on. Leaving us should always be possible and never expensive.
The figures quoted are from measurements anybody can repeat — run the page through PageSpeed Insights or Lighthouse yourself. We have deliberately not published field data, because this site has not had the traffic to produce a stable field measurement yet.
Both, and which one is right is usually decided by the platform rather than the code. If the existing site can be fixed we will say so, because a rebuild that was not needed is the most expensive thing on our price list.
Free 30-minute audit · No obligation · Response within 24 hours
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.