A good part of my activity consists of creating websites. Another part, less glorious and highly instructive, consists of repairing the ones that went wrong: the invisible website, the website held hostage by a ghost provider, the slow website, the pretty website that brings in nothing. By dint of dismantling these wrecks, I ended up drawing the map of the reefs.

Here is that map. I am an independent web developer in Hannut, and these ten traps, I watch them close on independents and SMEs across Wallonia with a regularity that commands respect. None is inevitable: each can be spotted from afar once you know it exists.

Read this list before signing a quote, or hold your current website up against it: it will cost you ten minutes and save you many. For the complete construction method, step by step, my guide to professional website creation in Belgium remains this article's companion: here the traps, there the path.

Trap 1: starting from the tool instead of starting from the goal

The original trap, the one that spawns half the others: starting with "I need a WordPress" or "someone told me about Wix" instead of starting with "I want my customers to find me and contact me". The tool is a consequence of the need, never a starting point.

The classic symptom: entire quote conversations about technology, themes and features, without a single question asked about your customers, your goals and your area. Result: a website that technically exists and is commercially stillborn, built for the provider's comfort rather than for your order book.

The antidote: first write down, on a sheet of paper, what the website must produce (calls, quotes, bookings, sales), for whom, and over what area. Then choose the provider who talks to you about that. The choice of tool will come by itself, and if the WordPress-or-custom question is on your mind, I laid out the 6 criteria to decide without tool religion.

Trap 2: design first, content never

Second trap, the one behind projects that drag on for months: choosing the colours, discussing the logo, polishing the mock-up... and discovering at integration time that nobody has written a line of text or gathered a single photo. The website waits for its content like a frame waits for its canvas, and the project bogs down.

It is more than a scheduling problem: a website designed without its real content is designed blind. Blocks are drawn for dummy text, then the real texts do not fit, the photos do not exist in the right formats, and the design is twisted to catch up. The result smells of compromise on every screen.

The antidote is counter-intuitive but unstoppable: content first. Your services described in your words, your photos gathered, your proof (reviews, past work, certifications) inventoried. The design then comes to dress real material. It is the order I gently impose on my projects, and it is why they ship on time: a showcase website is delivered with me in 7 to 14 days once the content is validated, never before it exists.

Trap 3: wanting everything, right away, in version 1

Third trap: the cathedral brief. The blog, the store, the member area, the newsletter, the booking module, the multilingual version, the configurator: everything is planned for day one, nothing is ever finished. The budget explodes, the schedule too, and the website comes out exhausted, six months late, with empty sections.

The truth the market does not like to say: the perfect day-one version is almost always a misallocation. You do not yet know what your visitors will actually use; every speculative feature is a costly bet, and the maintenance of it all adds up.

The antidote: the minimal scope that reaches the goal, delivered fast and well, then extensions guided by real usage. Five solid pages that convert beat twenty average pages. The store can follow the showcase, the blog can wait for the first customers. Gradualism is not smallness: it is management.

The filter question

For every requested feature, one question: "what happens if it is not there at launch?" If the answer is "nothing serious", it leaves version 1. You have just saved budget and weeks.

Trap 4: comparing purchase prices, never full costs

Fourth trap, the most expensive in the long run: choosing on the quote's figure without looking at what it contains or what will follow. The cut-price website without SEO, without serious mobile adaptation, without training, is then paid for every month: in customers who do not come, in invoiced repairs, in subscriptions you cannot escape.

The models to watch closely: the lifetime monthly subscription where the website never belongs to you and where three years of instalments far exceed a purchased website; the teaser quote that swells with indispensable options discovered along the way; and the "free" paid for in advertising for the provider on your own website.

The antidote: compare offers over three years, all included: creation, hosting, maintenance, routine modifications, and what belongs to you at the end. I dissected the real ranges of the Belgian market in the price of a website in Belgium: 7 real budgets: armed with that read, no quote will be able to blow smoke at you again. My own prices are public, precisely to make that comparison possible.

Trap 5: forgetting that your customers are on their phones

Fifth trap, still massively widespread: the website designed on the provider's desktop screen, vaguely adapted to mobile at the end of the project. Menus impossible to touch with a thumb, tiny texts, tables that overflow, buttons out of reach: the real experience of the majority of your visitors treated as a secondary variant.

Yet the traffic figures have been unambiguous for years: for a local shop or tradesman, most visits arrive from the phone, often in a moment of immediate need. Mobile is not a version of your website: it is your website.

The antidote holds in one design principle, mobile first, and one validation reflex: demand to see and handle the website on a real phone before approving anything. Not a simulation in a corner of a screen: your phone, your fingers, your 4G. Everything that annoys you in that test will annoy your customers.

Trap 6: SEO planned "for later"

Sixth trap, the most insidious because it is invisible at delivery: the website built without a second's thought for Google. Anarchic structure, missing tags, pages without coherent titles, no structured data, mute images: nothing shows to the naked eye, and the website is a ghost in the search results.

The "we will see about SEO later" is a double mistake: first because the foundations of search ranking are laid at construction and cost far more to redo afterwards, second because "later" becomes a second budget the initial quote was careful not to announce.

The antidote: demand that the SEO foundation be in the initial quote, named line by line: semantic structure, tags, speed, structured data, sitemap, Search Console. With me it is included by default, from the showcase website to the store: a website without basic SEO is not finished, it is merely switched on.

Hand tracing a route on a paper map, several pencil paths crossed out and one route marked with coral thread
Web project dead ends all look alike: fortunately, so does the right path.

Trap 7: owning nothing: domain, content, access

Seventh trap, the one that produces the most painful stories in my collection: discovering, when it is time to change provider, that nothing belongs to you. The domain name registered in the agency's name. The access credentials never handed over. The website built on a proprietary platform from which nothing can be exported. The photos and texts "included" but never assigned.

The client in that situation is no longer a client: they are a hostage. Every modification request becomes a power struggle, every desire to leave hits the wall: "you can go, but you go with nothing". I have seen businesses pay for their own website all over again to free themselves, and domain names lost after years of existence.

The antidote, non-negotiable: the domain name registered in YOUR name, the access credentials (hosting, domain, administration) handed over and documented, ownership of the content written into the quote, and a clear answer to the question "what do I take with me if we stop?". Every honest provider accepts these clauses with a smile. The one who flinches has just done you a favour: run.

Trap 8: the obese website, slow from day one

Eighth trap: slowness built in at the factory. The demo theme with its twenty animations, images dropped in at full resolution, stacked modules, the autoplay homepage video: the website is born out of breath, and every mobile visitor pays for it.

This trap is treacherous because the website looks normal on the provider's computer, on fibre with a warm cache. It is at your customers', on a phone with an average network, that the truth comes out: seconds of waiting, silent abandonments, and Google taking note.

The antidote: speed as an acceptance criterion, measured before final payment. A mobile PageSpeed test, a trial on real 4G, and thresholds agreed from the quote. I devoted an entire article to the subject, loading speed: 8 effective solutions: read it before approving a delivery, it will give you the right control reflexes.

Trap 9: skipping the Belgian legal obligations

Ninth trap, as dry as it is unavoidable: the website delivered without legal notices, without a privacy policy, without correct handling of personal data. In Belgium, a professional website must display who publishes it, company number included, and comply with the GDPR from the very first contact form.

The risk is not theoretical: inspections exist, competitors' complaints too, and the fine does not have the courtesy of waiting for the big companies. But the most immediate cost is commercial: an attentive customer who finds neither identity nor terms wonders who they are dealing with, and the large contracting clients check systematically.

The antidote: the legal pages in the quote's base scope, adapted to YOUR activity, not copied from a generic template describing another company. Legal notices, privacy, cookies handled honestly, and terms of sale if you sell: with me, all of that is part of the standard delivery, because a compliant website is a finished website.

Trap 10: launch, then abandon

Tenth trap, the most common of all: the website inaugurated with pride, then left without care or a glance for years. The outdated opening hours, the latest news from three summers ago, the form enquiries going to an email inbox nobody opens any more, no measurement of what the website produces.

An abandoned website does worse than doing nothing: it publicly documents your negligence. The visitor who lands on a dated page immediately transposes: if the shop window sleeps, maybe the workshop sleeps too. And meanwhile, for lack of measurement, nobody knows whether the website pays, so nobody invests to improve it: the circle is closed.

The antidote holds in two modest rituals: one hour per month for the basic updates (photos, news, form check), and a quarterly glance at three numbers (visits, enquiries, searches that display you, via the Google listing and Search Console). A website is an employee: recruited then ignored, it resigns in silence.

The minimal maintenance contract with yourself

One hour on the first Monday of the month, three numbers per quarter, one real update per season. This light regimen is enough to keep a website alive, credible and measured. Less than that, and you are resetting trap number ten.

The anatomy of a failed project: how the traps chain together

One last light before the selection grid, because the traps rarely hunt alone: they hold hands. Let us reconstruct the typical scenario, assembled from dozens of real cases I have had to repair.

It all starts with trap 1: a contract is signed for a tool praised by a salesperson, without a conversation about goals. As the content was not planned (trap 2), the provider fills in with generic text and stock images. The tight quote provided for neither SEO (trap 6) nor legal pages (trap 9): the website comes out pretty on the demo screen, obese on the phone (traps 5 and 8).

Six months later, not a single enquiry has arrived. The owner, burned, stops looking after it (trap 10). When they want to react, they discover the domain does not belong to them (trap 7) and every modification is billed at full price (trap 4). The website ends up abandoned, then with someone like me, for a diagnosis whose conclusion fits in one line: start over, properly this time.

The real cost of this scenario deserves to be laid out: the price of the first failed website, plus the months of visibility lost to better-equipped competitors, plus the price of the rebuild, plus the moral energy, because we always underestimate the discouragement a failed digital project produces. In total, the failed website commonly costs double or triple a website done right the first time. The initial saving was an advance on expenses.

The moral of this anatomy: the first trap avoided defuses almost all the others. A project that starts from the goals, with an itemised quote and guaranteed ownership, slides naturally towards good practice. The tipping point is the very beginning: before the signature, when all the options are still open.

Blank card hanging from a coral string by a wooden peg, warm bulb glowing in the dim background
Every good question asked before signing is one more thread in your safety net.

How to choose the provider who will spare you all this

The ten traps have one thing in common: a good provider naturally steers you away from them, a bad one leads you into them with a smile. Here is my selection grid, applicable to anyone, myself included.

Also beware of inbound cold-calling: the "your website is not compliant" calls, the alarmist emails about your rankings, the limited-time offers demanding a signature before Friday. The good providers of our regions rarely need to hunt by phone: their order book fills through reputation. Artificial urgency is a sales tool, never a service.

Listen to their questions before their answers: a professional starts with your goals, your customers, your area; a salesperson starts with their packages. Look at their work in real conditions: open their websites on your phone, time them, look for their clients on Google. Question ownership: domain, access, content, exit. Demand an itemised quote: every item named, the SEO foundation and the legal pages visible in black and white.

And check the human: will the person answering you be the one doing the work, and still answering in two years? Proximity helps: my clients in the Liège region and elsewhere know that a local developer who stakes his regional reputation on every project has a structural motivation to do well. Walloon word of mouth is merciless, and that is exactly as it should be.

Your anti-trap checklist, to print before signing

Let us summarise the ten traps as control questions, to run through in front of every quote. Are my commercial goals written in black and white in the proposal? Does the content plan exist before the mock-up? Is version 1's scope minimal and justified? Do I have the total cost over three years, line by line?

Will the website be designed mobile first, and validated on my own phone? Is the SEO foundation named in the quote, not promised orally? Will the domain, the access and the content be in my name, with a written handover? Is speed part of the delivery criteria, measured before payment? Are the legal pages adapted to my activity included? And is the post-launch maintenance plan defined, even a modest one?

Ten questions, ten yeses to obtain. It is not mistrust, it is project management: good providers answer this list with pleasure, because it simply describes a job well done. Keep it for your next project, or hold your current one against it.

And if your current website already ticks several boxes?

Reread the list with your website in mind: how many traps have closed? One or two can be corrected by targeted intervention: content gets rewritten, images get compressed, legal pages get added, the Google listing gets connected. It is often a matter of a few days of well-directed work.

Beyond three or four structural traps, slowness by design, total invisibility, dependence on the provider, rebuilding deserves the calculation: a new website without the traps often costs less than the piece-by-piece repair of a badly born one. An honest diagnosis separates the two paths, and it is free with me: send me your address, I look, and I tell you which of these ten traps is costing you the most right now.

And if you are in the middle of a project as you read this, no retroactive panic: take the checklist, identify the boxes still open, and ask your provider the missing questions tomorrow. A project in progress is reoriented far more easily than a delivered website is repaired: every trap defused before launch is repair budget you will never spend.

The final word, to take the drama out of it: all these traps are banal, none is shameful, and avoiding them requires neither a multinational's budget nor a technical doctorate. Just the right questions, asked in the right order, to the right person. You now have them all in hand.