Before anything is built.
When we redesign a site you already have, we start by reading it.
A list of what's already working.
Before design work starts, we write down what your current site already does well, such as its wording and its best pages, and we keep those. A plan without this list fails the first check.
A design direction for your business.
We don't use templates. Each redesign starts from a written direction for that one business: who it's for, what it needs to say first and how it should feel. It's settled before the first page is built.
What your redesign is checked for.
Of the checks below, two are judgement calls: the design comparison and the logo. Scripts run the rest.
Does it look more capable than what you have now?
We show the first screen of your current homepage and of ours, with the opening of both About pages, to a separate AI that hasn't seen our plan, and ask which business looks more competent. Redesigns have been sent back and reworked on its answer.
Is every page of yours accounted for?
Every substantial page on your current site has to appear in the plan, either carried over into the new site or cut with a stated reason. A page nobody accounted for fails the check.
Does your contact form tell visitors what happened?
We test your contact form in a real browser. When a message goes through, the visitor is told so. When it can't, they're told that too and handed a ready-written email to send instead, so nobody is thanked for a message that went nowhere. Every enquiry is saved to your dashboard before it's emailed to you, so an email that goes astray doesn't lose it.
Does it fit every screen?
Every page's menu and main buttons are measured at ten screen widths, from a small phone to a wide desktop. That catches a menu that wraps onto two lines, a button whose words stack up, a phone number broken across lines, or a page that slides sideways on a phone.
Can people read it?
Each text colour is adjusted until it meets a set contrast ratio against the background it sits on.
Is it still your logo?
We use your own logo file wherever it's clean enough. Where it isn't, we reproduce it and compare the two side by side before it's used.
Can Google and AI search read it?
Your homepage carries the details search engines and AI assistants read to describe a business, and the site has a sitemap and a robots file that lets AI crawlers in. Where there's an FAQ, its structured data has to match what the page shows. More on how we get you found.
Then a person approves it.
A person on our team approves every free site before it's emailed to you.
If you don't have a website yet, there's no old site to compare against or carry over, so your first site is put together by hand from what you've told us. It's approved the same way before it's sent.
When your site goes live.
Nothing left over from the preview.
Before we ask you to point your domain at your new site, we check the live copy for anything left over from the preview, and hold that step until it's clean.
No missing files.
If a page points to a file that isn't there, such as a stylesheet or an image, the site doesn't go live. The same check runs every time a change is published.
Its own "page not found" page.
A mistyped or out-of-date link lands on a "page not found" page in your site's own design, with your menu on it.
Hosting, security certificates and backups are covered on how we host and protect your site.
When you ask for a change.
A person reads every change you ask for. Each one is built on the current version of your site, so it doesn't undo an earlier change. You can ask to see any change on a preview first and publish it yourself from your dashboard.
The checks keep changing.
We change the build process most weeks, and some of the checks on this page were added after a real build showed us a problem nothing was catching.
Who builds it.
Renie Ravin builds the pipeline. He founded IndiBlogger in 2007 and ran it for twelve years as India's largest community of bloggers and creators, and since 2021 he has been an architect on PharmacopeAI, a cancer decision-support platform built with the National University of Singapore. More about the three of us.
The way we build is ours. What we build is yours.
We don't publish how the checks work. None of that machinery ends up in your site: you get plain HTML and CSS with no proprietary format, your domain and complete code are yours, and any developer could take over tomorrow.
Questions people ask.
Is my site built by AI?
Much of it is, and that's what makes the price work. An automated pipeline writes a design direction for your business, builds to it and runs the checks on this page. A person on our team approves every free site before it's sent to you, and a person reads every change you ask for.
What happens when a check fails?
Usually the problem is fixed and the check runs again. When a check doesn't apply to a site (a form check on a site with no form, for example), the reason it was set aside is written on that build's record.
Does this mean my site won't have any mistakes?
No. The checks catch what they're built to catch, and the person who approves your site catches a lot of the rest. If something gets past both, tell us and we'll fix it.
Do sites you built earlier get new checks too?
Every new site gets the current set. Checks that run when a change is published also reach sites that are already live; the rest apply to sites built after they were added.
See what it makes of your site.
Paste your URL and we'll email you a redesign in 48 hours. It's free and needs no card. If you like it, it's $29 a month.