The most dangerous signs are simple: a price way below the market, a demand for 100% upfront, no written contract, and dodging your questions about access to the server and domain. If you spot even two of these at once - slow down. It does not mean the person is a scammer, but this is exactly how most of the stories begin that end with a lost deposit and a website you hold no keys to.
I have been building websites for well over a decade, and I regularly take over projects after someone vanished. Below are the specific flags I see most often - with an explanation of why each one is a problem and what to do about it.
A price much lower than everyone else
You get three quotes at 1,500-2,200 dollars and one at 300. The cheapest looks tempting, but anyone pricing a business website at 300 either pastes a ready template in an hour, or works on it after hours and abandons the project at the first tricky task. The third option: the low price is bait, and the real bill arrives later - for "extra fixes", hosting, every content change.
What to do: compare quotes that cover the same scope. Ask them to spell out exactly what the price includes. If an offer is half the price of the rest, ask outright what it is missing - usually it is missing a lot.
No contract, everything "on a handshake"
"Why a contract, we will sort it out." This is the most common trap. Without a contract you have no written scope, no deadline, no amount, and no record of who owns the code. When something goes wrong, you have nothing to stand on. From experience: people who avoid paperwork are usually the ones who later have trouble keeping to what was agreed.
What to do: no payment without a contract, even a short one. It needs to state the scope, the stage deadlines, the amount and payment schedule, the rights to the code, and what happens if either side wants to end the work.
Demands 100% upfront
Full prepayment shifts all the risk onto you. After the transfer you have no leverage - if the developer slows down or disappears, you are left empty-handed. It is a classic scenario: the deposit is paid, the first results were due "next week", and contact gets thinner by the day.
What to do: pay in stages. The standard is 30-50% at the start, the rest at each milestone, the final part on delivery. That way payment follows real progress, not a promise.
Shows no portfolio, or shows someone else's
No live examples is a red flag. The worse version - they show pretty screenshots with no links. Sometimes those are other people's work pulled off the internet, or mockups that never went live.
What to do: ask for links to working sites, not images. Open them, check they actually work. You can even message two or three clients from the portfolio and ask how the work went.
Dodges questions about access and code
You ask whether the domain and hosting will be registered to you and whether you will get the code - and the answer is fog. This is one of the more serious signs. Some firms deliberately keep the site on their own server and hand over no full access, neither to the panel nor to the database. The result: you are tied in, you pay them for "maintenance", and when you try to leave it turns out you have no way to take your own site with you.
What to do: agree at the start that the domain and hosting are under your name, and that on completion you get full access credentials and the source code. Put it in the contract. If the developer resists this - that is your answer.
Vague about deadlines
"It depends", "hard to say", "soon" - and never a single date. No specifics at the talking stage means no specifics during the work. A deadline nobody wants to write down usually does not exist.
What to do: ask for a schedule with milestones and dates. It is not about an oath to the hour, it is about whether someone is planning at all rather than improvising.
Does not ask about your business
A good developer, before naming a price, asks: who is the customer, what the site is meant to achieve, how you differ from the competition, what content you have. If someone throws out a figure without a single question about your company - they are building a template, not a site for your goal.
What to do: notice whether the questions come up at all. Prepare your answers too - a brief, a plain description of what you need helps with that.
Promises "number 1 on Google in a week"
Nobody guarantees the top spot on Google, and certainly not in a week. SEO is months of work and depends on the competition in your field. A guarantee of position is either ignorance or a deliberate hard sell - both disqualify.
What to do: treat every "guaranteed number 1" as a warning. An honest developer talks about realistic timeframes and about how the result depends on many things beyond the site itself.
A site on a closed builder with no export
Some cheap offers are built on closed platforms you cannot export the site from. As long as you pay the subscription - it works. Stop paying or want to switch developers, and the site disappears along with your access. It is lock-in baked into the product.
What to do: ask outright what the site is built on and whether you can move it elsewhere. If the answer is "you cannot do that with us" - you know where you stand.
Materials with no license
Cheaper firms will sometimes drop in stock photos and text they hold no license for - just to go faster and cheaper. The problem lands on you: you are the one who gets the demand to pay for someone else's photo on your own site.
What to do: establish where the graphics and content come from and whether you have the rights to them. Let that go into the contract too.
How to protect yourself
It comes down to four things you need to settle before the first transfer.
A written contract. Scope, deadlines, amount, rights to the code, rules for ending the work. A short contract is the minimum, without which I do not pay and would not advise anyone to.
Payment in stages. Part at the start, the rest for the following stages, the final part on delivery. Payment follows progress, not a promise.
Access under your name. Domain, hosting, panel - all under you. The source code should reach you on completion. You are the one who should own your site.
A portfolio with live links. Not screenshots, but working addresses you can check yourself. Ideally with the option to contact a few clients.
If you are torn between a single person and a firm, I lay out the pros and cons in the piece freelancer vs agency, and I have gathered the whole process of choosing a developer in the guide how to choose a web developer. If you just want to talk through a specific project - get in touch, and I cover the website development service separately.
FAQ
What should you watch out for when ordering a website? Four things at once: no contract, a demand for full payment upfront, a price well below the market, and dodging when you ask about access to the domain and code. Each point on its own can sometimes be explained, but several at once is a signal to back off.
Should you pay in full upfront for a website? No. The safe model is staged payment - part at the start, the rest at the following milestones, the final part on delivery. Full prepayment leaves you with no leverage at all if the developer slows down or disappears.
How do you vet a web developer before hiring them? Confirm they have a registered business, ask for links to working sites (not screenshots), open them and check they work. You can message a few clients from the portfolio. Also notice whether they ask about your business at all.
Who owns the website after it is built - me or the developer? It should be you. Settle before the start that the domain and hosting are under your name, that you get the source code on completion, and write it into the contract. Without that you risk being tied to one person or firm.
Is a "first place on Google" guarantee credible? No. Nobody guarantees a position on Google, and certainly not "in a week". Ranking is counted in months and depends on the competition. Such a promise is a warning, not a selling point.
What do you do if the developer took the deposit and vanished? Write down all the correspondence and proof of payment, send an official demand to deliver or refund. With no response, the civil route remains, and where there are signs of fraud - a police report. This is why a contract and staged payment matter so much: they limit the loss and give you something to lean on.
Why is the cheapest offer often the most expensive? Because a low price often means a ready template, no support, or surcharges added later - for fixes, hosting, every content change. Compare offers with the same scope, not just the figures.
