I Paid for a Website That Brings Nothing: Can a Consultant Save It?
You paid for a website — maybe more than once — and it sits there like a framed certificate: official, silent, useless. No calls come from it, no forms, no orders. And now someone suggests paying again, this time for a consultant. Understandably, everything in you resists.
Here is the honest reframe: the question is not “should I spend more on this site?” The question is “why exactly does this site bring nothing — and what is the cheapest fix?” Those are diagnosis questions, and diagnosis is precisely what a website consultant sells first.
In this guide we separate the three reasons sites fail, draw the rescue-versus-rebuild line with real criteria, and show what a rescue actually looks like week by week.
Did the Money Really Go to Waste?
Let’s set the account straight first. The feeling of “I got nothing back” is real; but what does the number say? Sometimes the site is guilty; sometimes its abandonment is.
Four questions clarify the picture:
Rescue or Rebuild — Who Decides, and How?
The line between rescue and rebuild is not a matter of taste; it follows a few concrete criteria.
Four of them:
What Exactly Does a Website Consultant Do?
The title is vague; the job isn’t. Draw the borders and the value gets visible.
Four borders:
How Does a Rescue Proceed, Step by Step?
Rescue is not one dramatic weekend; it is a scheduled recovery.
The stops:
Is Rescue Cheaper Than a New Site?
Usually, clearly — but the comparison must be done honestly, with all lines on the table.
Four lines:
The Meeting Test: Four Questions Before You Sign
BU BÖLÜMÜN ÖZETİ
- “What will you base the rescue-or-rebuild call on?”
- “Which of your services do we NOT need?”
- “Which number will we watch, and when?”
- “If we start small, what do we get?”
Close with the door-specific test. Four questions, and the sound of good answers:
Ask them in order:
“What will you base the rescue-or-rebuild call on?”
Good answer: named criteria — platform health, structural editability, cost comparison — and a diagnosis before the verdict. Bad answer: a verdict in the first five minutes, in either direction. Speed of verdict is inverse to its worth.
“Which of your services do we NOT need?”
The exclusion test, unchanged from the main guide. A concrete answer — “you don’t need a redesign; you need counting and three fixed pages” — signals a real diagnosis in progress. “It all works together” signals a menu, not a doctor.
“Which number will we watch, and when?”
Good answer: monthly inquiries from the site, read monthly on one page, first honest reading at a named date. If the proposed measures are traffic and prettiness, the phone will stay quiet and the reports will stay colorful. You are buying the phone, not the colors.
“If we start small, what do we get?”
The diagnostic session: your site examined, the three-way diagnosis made, a one-page state report with priced paths. Bring your last three months’ numbers — even rough ones — to a preliminary assessment, and pair this read with the /en/website-consulting/ service page. The kin topics are close by: the patch-cost guide and the brand guide.
Field Notes
· The most frequent diagnosis is the third one — nobody counts: the site was neither guilty nor innocent, just unread. Counting alone changes the conversation within a month.
· Rescues that assign an internal owner hold their gains; ownerless rescues drift back within a year, whoever did the fixing.
· Rebuild verdicts given in the first meeting almost never survive a real diagnostic; the ones given after it almost always do.
Quick Glossary
Leak lines: The three silent losses: unsearched content, mobile breakage, missing next step.
Diagnostic session: The paid single session producing a one-page state report with priced paths.
Internal owner: The person on your side who feeds and reads the site weekly after rescue.
Quick Summary
· Most sites are rescuable; rebuild is the exception and must be proven by inspection, not declared at hello.
· Diagnosis separates three failures — arrival, conversion, counting — and starts from the cheapest cure.
· Watch one number: monthly inquiries. Keep the domain, the access and an internal owner on your side.
Next Step
Tonight, answer one question: how many inquiries did the site bring in the last ninety days? Bring that number — or the fact that it’s unknowable — to a preliminary assessment. Either way, it is the first line of your diagnosis.
Frequently Asked Questions
My site was built by a relative and nobody has the passwords. Can it still be rescued?
This is common and usually solvable: hosting and domain access can be recovered through the registrars with ownership proof, and the diagnostic starts right after. It also becomes lesson one of the engagement: every credential gets documented in your name, so the next transition — whoever it involves — costs a phone call, not a hostage negotiation.
Do I need ongoing consulting after the rescue, forever?
No; the healthy pattern is intensive at setup, then sparse. Once the leaks are fixed, counting runs and your internal owner has the routine, the consultant’s role shrinks to periodic checkups — quarterly or on demand. Open-ended dependency is a design flaw in this series’ book, not a service model.
Would adding ads help before the rescue?
Usually the reverse: ads multiply whatever the site does, including its leaks. Sending paid traffic to a page that breaks on phones or hides the next step is buying waste at scale. Fix the leak lines and install counting first; then ads amplify a working machine — and their own audit has its dedicated guide in this series.
Sık Sorulan Sorular
The measure is plain: in the last three months, how many calls, forms and quote requests came from the site? If you don’t know that number, the problem starts not in the site but in the absence of counting. An unknown number cannot be managed; the first job is to count.
Three usual suspects: content written for phrases nobody searches, pages that break on phones, and design that never tells the visitor what to do next. None of them appears on an invoice, yet each loses customers monthly. Usually it is not the whole site that’s wasted — it’s these three lines.
The honest question: after launch, who looked after it? Was content added, were calls counted, was anything tested? If the answer is no, the site may be innocent; an unattended shop doesn’t sell. Then the cure is not a rebuild but an owner.
No, and knowing that matters. Most small businesses get no regular work from their websites; the site sits like a business card. You are not in an embarrassing situation; you are inside a common mistake — and common mistakes come with tested cures.
Its foundation stands: the platform is maintainable, the structure editable, the content salvageable. Most “dead” sites are exactly this — neglected, not broken. Rescue means fixing the three leak lines and installing an owner; it costs a fraction of a rebuild and shows results sooner.
When the foundation itself fights you: an abandoned or locked platform, code nobody can safely touch, a structure where every small fix costs like surgery. Then patching is the expensive path, and a rebuild — with the old content rescued into it — is the thrifty one. The point is: this verdict comes from inspection, not from a salesperson’s convenience.
Traffic and its sources, phone behavior, page speed, what visitors do and where they leave, whether counting works at all. The output is one readable page: what works, what leaks, what it costs. That page is yours regardless of who you hire next — which is exactly why it’s worth paying for.
You — on the consultant’s evidence. A proper consultant presents both paths with prices and expected outcomes and lets the numbers argue. Beware the reflex answer in either direction: “always rebuild” serves builders, “always patch” serves maintainers. Evidence serves you. The selection principles live in the main guide.
The designer’s question is “does it look right?”; the consultant’s is “does it earn?” Looks are one input among several — speed, findability, clarity of next step. A beautiful site that doesn’t ring the phone fails the consultant’s exam; a plain one that rings it passes.
The agency executes at scale; the consultant diagnoses and directs. In a healthy setup the consultant writes the prescription and supervises whoever fills it — an agency, a freelancer, your own team. Prescription and pharmacy in one hand is possible, but then ask who checks the prescription.
Diagnosis, priority plan, fixing the leak lines — content direction, mobile and speed, next-step design — installing counting, and coaching an internal owner. Everything measured, everything scheduled. The running theme is turning a neglected asset into a managed one.
An honest consultant names their borders: they don’t do every technical task themselves, don’t spend your ad budget, don’t promise the impossible. Advertising is its own discipline — that door is covered in the Ads audit guide. An expert who knows their border is always safer than one who promises without borders.
The cheapest, highest-impact fixes ship first: counting installed, mobile breakage repaired, the next step made visible on key pages. Nothing glamorous — and that is the point. Early wins fund patience for the slower work behind them.
One main counter, agreed in the diagnosis: inquiries per month from the site — calls plus forms plus quote requests. Traffic and rankings are supporting actors; inquiries are the headline. A single honest number beats a dashboard of decorative ones.
Two things no consultant can outsource: your expertise — the raw material of content — and your decisions. Expect to answer questions, approve directions, and assign an internal owner an hour or two a week. A rescue where the owner stays absent relapses; the consultant should say so out loud.
Leak fixes show within weeks; visibility work breathes in months. The honest consultant gives each fix its own date and reads them with you on schedule. Anyone promising everything in two weeks is selling weather, not climate — and your site’s problem was always climate.
Diagnosed scope: which leaks, how many pages, what technical debt. That is why a serious rescue quote arrives after the diagnostic session, never before. A price named at hello is a guess wearing a suit.
Add the hidden lines to the rebuild column: content migration, new-site teething, the months of ranking reset, your team’s onboarding hours. Rebuilds are sometimes right — but they are never as cheap as their first quote. Compare totals, not headlines.
Possibly, and you should ask: licenses, hosting corrections, extra development if debt runs deep. The right expert lists them up front; every later surprise erodes trust, and good consultants know it. One line is non-negotiable: your domain stays registered in your own name — the official registry framework can be verified through BTK.
Always — that’s the design of this whole series. The small entrance here is the diagnostic session alone: one fee, one readable report, full freedom afterwards. Buy the diagnosis, read the page, then decide about the room. No good consultant fears that sequence.