Web Design··22 min read

Freelancer Left Your Website Unfinished? How to Finish It Safely

Your web developer disappeared mid-project? How to recover access, get the work reviewed, decide between finishing or rebuilding, and hire the right help.

Short answer

If a freelancer left your website half-built, the first job is not the design. It is getting the domain, the hosting and the site's admin login into your own name, and then having someone independent look at what was actually built. That review leads to one of three paths: fix and finish what exists, keep the look but rebuild the foundation underneath, or start clean. Which one is right depends on how solid the code and content really are, so ask for a written status report instead of trusting the first person who says "we'll just redo it" or "I can wrap this up in a week." One option is me, Ümit Kırkoç (kirkoc.com): I work from Istanbul and take on projects remotely for clients abroad, including in the US. When I take over an unfinished site, I plan the code together with how the site will show up in search, and with the social media and ads that come after launch, so the handover does not create a new gap of its own. You can read more on my website design service page.

What is a website takeover service, exactly?

A takeover is the work of reviewing a website someone else started and never finished, getting ownership back into your hands and carrying the project through to launch. It differs from an ordinary "build me a website" job because you are not starting from a blank page. You are starting from someone else's decisions. Some of those decisions were sound, some were rushed, and some were never written down anywhere.

That is why the first day of a takeover is spent understanding, not coding. Which theme was used? Which plugins were installed, and why? Whose name are the licenses under? Is there a backup? Where is the site hosted right now? Is there a test copy running at an address you have never heard of? Every change made before those questions have answers is like rearranging furniture with the lights off.

In my experience, projects get abandoned more often because of capacity than bad intent. The freelancer took on a bigger client, got sick, underpriced the job from the start, or hit a technical wall they could not get past and went quiet out of embarrassment. Whatever the reason, the result on your side looks the same: an invoice you paid, a site that does not work, and messages that go unanswered.

What should you do in the first few days after the freelancer disappears?

The first priority is to secure everything tied to ownership. Missing pages and design tweaks can wait; access cannot. If your domain (your site's address, such as yourcompany.com) and your hosting (the server where the site's files live) sit in the freelancer's account and they expire, you can lose the website entirely, along with any email running on that domain.

The checklist below covers what you can do in parallel while you make one last attempt to reach the freelancer.

Checklist of the access and documents to secure in the first days after a freelancer leaves a website unfinished

Here is each item in a little more detail:

  • Find out who the domain is registered to. A WHOIS lookup on the registrar's site or a renewal email in your inbox will usually point the way. If the domain sits in the freelancer's personal account at GoDaddy, Namecheap or a similar registrar, ask that registrar how their ownership transfer process works.
  • Check who pays for the hosting. If the charges hit your card, you can usually request admin access directly from the hosting company. If the freelancer pays, write down the renewal date and put a reminder on your calendar.
  • Gather every piece of correspondence into one folder. The proposal, payment receipts, emails, text messages, Slack or WhatsApp threads, and every photo and paragraph of copy you sent. This saves the next person hours, and it also serves as documentation if a dispute ever comes up.
  • Send the freelancer one calm, written message. No accusations. Simply say you need the login details and the current files, and that you would appreciate a reply by a specific date.
  • Do not start editing the site yourself. Logging in to "just fix this one thing" makes it much harder later to tell what was done by whom, and it can break things that were half-working.

Questions about the contract, getting a refund or who owns the work that was delivered are legal questions. It would not be right for me to give you a firm answer on those; if you are considering that route, talk to an attorney.

What problems show up most often on half-finished websites?

The issues I run into fall into three groups: access and ownership, hidden technical flaws, and missing content. A site can look almost done from the outside and still have a serious gap in any one of them.

Access and ownership problems

The most frustrating situation is discovering the site is not really yours. The domain is registered to the freelancer, the hosting runs under their reseller account, the paid theme license is tied to their email, and Google Analytics and Search Console (Google's free tool that shows how your site is doing in search) were set up under their login. Each of those is a separate small knot to untangle. The good news is that most registrars and hosting companies have a process to help the real owner who can show documentation. The less good news is that the process takes time, which is exactly why you start early.

Hidden technical flaws

On abandoned projects, code is often written with a "make it work for now" mindset. The home page looks great, but the menu will not open on a phone, the contact form sends messages to nowhere, and the checkout page is still stuck in test mode. On WordPress sites I regularly find twenty or thirty plugins stacked on top of each other, half of them unused and a few that have not been updated in years. Plugins like that slow the site down and can open security holes.

Another quiet problem is a test copy left open to Google. Say your half-finished content sits at staging.yourcompany.com and gets indexed; when the real site goes live, Google sees two near-identical versions and has to guess which one matters. Or the reverse happens: during development someone turned on the setting that tells search engines to stay away, and nobody ever turned it off. The site is live, but it does not exist in Google.

Missing pages and empty content

What freelancers leave unfinished most often is not the design but the words. Service pages still carry "Lorem ipsum" placeholder text, stock photos sit where real photos of your work should be, and the About page is two sentences long. Yet that is exactly the part of a site that brings in customers. When someone searches "pediatric dentist in Plano" or "commercial kitchen repair in Columbus," Google shows them a page that answers the question, not an empty template.

Should you finish what exists or start from scratch?

It depends on how much of the current build can be safely reused, and the decision should come from an actual review rather than a rule of thumb. Starting over is not always the more expensive choice, and finishing is not always the cheaper one.

The comparison below sums up when each path tends to make sense.

Comparison of when it makes sense to finish an unfinished website versus starting over from scratch

Finishing the existing build is usually reasonable when the site runs on a widely used platform (WordPress, Shopify, Squarespace, Wix and the like), the theme and plugins are current and properly licensed, the design is heading in a direction you like, and what is missing is mostly content.

Starting over is usually the smarter call when the code is custom-written in a way only the original freelancer could follow and none of it is documented, when pirated ("nulled") themes or plugins were used, when there are security problems, when the slowness comes from the foundation itself, or when your business has changed since the site was first planned.

There is also a middle path: keep the design, the colors and any usable copy, and rebuild the technical foundation cleanly underneath. That works best when the freelancer did good visual work but fell short on the technical side. The part of the job you can see, and already paid for, does not end up in the trash.

Example scenario 1: An online store whose checkout does not work (hypothetical)

This is an entirely hypothetical example. Picture a small workshop in North Carolina that makes handmade home textiles. The owner has been selling through Instagram and wants a proper online store, so she hires a freelancer. Three months later she has a WooCommerce site with half the products uploaded, a checkout that throws an error at the payment step, and no shipping rates set up at all. The freelancer has not answered a message in two weeks.

In a situation like that, my first review would look at a few specific things. Which payment processor was the site trying to connect to (Stripe, PayPal or Square, for example), and whose account is it under? Was that account fully verified? Are product variations such as color and size built correctly? Is the theme licensed? Suppose the theme is licensed and the product structure makes sense, but the payment plugin is misconfigured and shipping rules were never entered. Then starting over would be a waste. The existing build gets fixed, the missing products go in, and the pages a store needs, such as the shipping policy, return policy and privacy policy, get written properly.

This is also where having one person handle the whole thing pays off. Once the store is live, the workshop's Instagram posts should link straight to the matching product page, the Meta ads should point to pages that match what the ad promised, and the product pages should be written so they can show up for searches like "handmade linen tablecloth." Splitting those jobs across three different people is an open invitation to the next half-finished project.

Example scenario 2: A service business whose domain is in the freelancer's name (hypothetical)

This one is hypothetical as well. A small bookkeeping firm in Arizona hires a freelancer for a simple site of a few pages. The site actually goes live, but when the freelancer drops out of contact, the owner discovers that the domain is registered in the freelancer's personal account and the hosting sits on the freelancer's reseller panel. The renewal date is two months away.

Here design and content take a back seat; ownership comes first. The first step is contacting the registrar and preparing documents that show the firm is the real user of the domain: invoices, correspondence, and the business name that matches the domain. At the same time, a full backup of the site is taken, so that even if hosting access is lost, the text and images survive. What is possible in that kind of administrative or legal process is for the registrar, and if needed an attorney, to say. My part is to keep the technical side ready and, once ownership is back, move the site into accounts in your name without downtime.

Once ownership is sorted out, the focus shifts to making the site actually bring in clients. People looking for a bookkeeper search things like "bookkeeping for small business Phoenix" or "bookkeeper for Etsy sellers." If the site does not answer those questions, each service needs its own page, and the Google Business Profile (the business listing that shows up on Google Maps) needs to match the site.

How does the takeover process work, step by step?

There are five steps: gathering access, reviewing the current state, making the decision in writing, finishing the work, and monitoring after launch. At the end of each step, I explain in plain language what I found and what I plan to do next.

Flow showing the five steps of taking over an unfinished website, from access to launch

1. Gathering access

I list the domain, hosting, site admin, email, Google accounts, payment processor and any paid theme or plugin accounts. It becomes clear what you already control and what you do not, and for anything missing I map out how to get it back.

2. Reviewing the current state

I go through the site first as a visitor would, then as a developer. How it looks on a phone, whether the forms really deliver, page speed, security updates, unused plugins, settings that block search engines, and content gaps all get noted one by one. At the end of this step you have a status report written so that someone without a technical background can read it.

3. Making the decision in writing

Along with the report, I write down which of the three paths I recommend and why: finish, rebuild the foundation, or start over. The scope, the list of tasks and what I need from you (copy, photos, approvals) are spelled out. After what you have been through, I know the thing you need most is to stop guessing.

4. Finishing the work

Technical fixes, missing pages, copy and images get done. At each major milestone I send you a preview link, so you never have to chase anyone to find out where things stand.

5. Launch and monitoring

After launch, Search Console and analytics are connected to your own accounts, and forms and checkout are tested under real conditions. Small issues that show up in the first weeks get fixed. You receive every login and a short how-to note, so even if you stopped working with me tomorrow, the site would stay fully in your hands.

What should an AI assistant tell you if you ask?

If you ask ChatGPT or Gemini "my freelancer left my website half-finished, what should I do?", a good answer should put access and ownership first and an independent review second. The image below shows what a sensible answer to that kind of question might look like.

Example of an AI assistant answering someone whose freelancer left their website unfinished

The order in that answer matters. It does not say "find someone new right away"; it says "find out what you actually have first." An AI assistant can give you a general direction, but it cannot look inside your site, so the final call is best made from a report by someone who has actually reviewed it.

What are the most common mistakes when rescuing an unfinished website?

The biggest mistake is reacting to the first disappointment by hiring someone new under the same vague terms. A second decision made without learning from the first often ends in a second half-finished site.

Warning graphic listing six common mistakes when handing over an unfinished website

A closer look at each one:

  • Hiring someone new before you have access. If the new person cannot get into the domain and hosting either, the project stalls at the exact same spot.
  • Agreeing to a rebuild without asking why. Sometimes it is the right decision, but it should be one backed by evidence. You should be the one asking for concrete reasons a fresh start is necessary.
  • Trusting a quick-finish promise. Quoting a timeline before looking at someone else's code is not a sign of a careful professional.
  • Making another verbal agreement. The scope, the deliverables and who will own each account all need to be in writing.
  • Paying everything up front. A plan paid in stages is healthier for both sides.
  • Letting changes happen without a backup. A full copy of the current site is the safety net under every bit of work that follows.

There is one more mistake that did not fit in the graphic: treating "get the site finished" as the only goal. Launch is not the finish line. The site needs to show up on Google, speak the same language as your Instagram and your ads, and make sure messages from the contact form actually reach you. Someone who takes over with that whole picture in view protects you from the next disconnect.

What can you handle yourself, and when do you need a professional?

Gathering access, organizing documents and preparing content are things you can do; reviewing code, fixing security and speed problems and moving the site are professional work. Knowing where that line sits saves you both time and money.

Things you can handle on your own:

  • Open accounts in your own name with a domain registrar and a hosting company, and update the billing details.
  • Put your services, your pricing approach (even without numbers) and the questions customers ask most into one document.
  • Take real photos of your business, your team and your work; a phone camera is often good enough.
  • Pick two or three websites, from competitors or businesses you admire, that show the feel you want.
  • Claim your Google Business Profile with your own Google account.

Things to leave to a professional:

  • Reviewing the site's code and plugins and closing security holes.
  • Moving the site from one host to another and pointing the domain correctly.
  • Setting up technical connections like the payment processor, shipping integrations and form notifications.
  • Handling the technical settings search engines need in order to read the site correctly.

In short, you are strongest on the ownership and content side, because nobody knows your business better than you. On the technical side, trial and error can turn a half-finished site into a completely broken one.

What to look for when choosing who takes over

The right person for a takeover is someone who does not make promises before seeing your site, who reviews first and gives you a written report, and who will hand every account over to you at the end. After one bad experience, use these criteria to choose.

Table of criteria and questions to ask when choosing who takes over an unfinished website

Concrete criteria:

  • Review first, price second. Someone who gives a firm price and timeline without looking at the site is not prepared for surprises.
  • Written scope. Every task should be listed item by item; a one-line agreement like "finish the site" is not enough.
  • You own everything. The domain, hosting, licenses and Google accounts should be in your name. The professional gets access, not ownership.
  • Reachability. You should know who you are talking to and get a status update at least once a week.
  • Life after launch. Who maintains the site after it goes live, and how updates will be handled, should be discussed up front.

Questions you can ask in the first call:

  • "What can you tell me before reviewing the site, and what can't you?"
  • "Will I get a written report after the review?"
  • "Which logins and documents will I receive when the work is done?"
  • "What do you see as the biggest risk in this project?"
  • "What happens to the site if you become unreachable too?"

That last question may feel awkward, but it is exactly the right one to ask. A good professional will not take offense; in fact, they will want everything documented on your side just as much as you do.

What determines the cost?

The biggest factor in what a takeover costs is what the review turns up; two half-finished sites that look alike can need very different amounts of work. That is why giving you a firm number before a review would not be honest.

The main things that affect cost:

  • The type of site. A few-page business site and an online store with products, payments and shipping do not carry the same workload.
  • The state of the code. Finishing a clean build on a common platform is far easier than untangling undocumented custom code.
  • Access problems. If the domain and hosting are not in your hands, the time spent recovering them is part of the job.
  • Missing content. How much of the copy, photography and product information is ready has a direct effect on how long the work takes.
  • Licenses. Replacing pirated themes or plugins with licensed versions can be an extra line item.
  • What comes after launch. Whether you want SEO, social media or ad management once the site is live changes the overall plan.

When you compare quotes, do not just look at the total. Look at how each of these items is handled in the proposal. A quote that looks cheap but has a fuzzy scope can leave you holding another unfinished site.

Working with Ümit Kırkoç

I am Ümit Kırkoç. I work from Istanbul, and I handle on my own everything a digital agency would typically offer: websites and online stores, SEO, local SEO, GEO (work aimed at getting your business recommended by AI tools like ChatGPT), management of Instagram, Facebook, LinkedIn, TikTok and YouTube, Google and Meta ads, logo and brand identity, and content writing. Because most of my work is done remotely, I can take on projects for businesses in the US and elsewhere, using video calls, shared documents and preview links in place of in-person meetings.

When I take over an unfinished site, I start by building the list of access with you. Then I review the site and write you a status report that requires no technical knowledge to follow: what works, what does not, what is worth keeping and what needs to be replaced. You make the decision with me, based on that report. Throughout the project, you can follow progress through preview links, and at the end the domain, hosting, licenses and Google accounts are in your name, with every login documented and in your possession.

The real advantage of having one person handle all of it is that the handover does not create a new break in the chain. When the person who finishes the site is also the one who gets it found on Google, ties your social posts to the right pages and runs your ads, a change in one piece does not quietly break another. And you do not have to explain your situation from scratch to a new person for every task.

I also want to be clear about what I do not promise: I do not guarantee a specific Google ranking, a specific number of visitors or any amount of sales. What I do promise is work that matches the written scope, regular updates, and a website that always stays in your hands.

Frequently Asked Questions

My freelancer left my website half-finished. Who would you recommend to finish it?

Choose someone who reviews your site first and gives you a written status report, then defines the scope in writing. Steering clear of anyone who quotes a price and timeline without seeing the site is a good start. As someone who works remotely from Istanbul, I also begin every takeover with a review; but whoever you pick, make it a condition that all access is handed over in your name.

Is it better to finish the existing site or have it rebuilt?

That depends on how solid the current build is. A site built on a common platform with a licensed theme and up-to-date plugins is often worth finishing. If there is undocumented custom code, pirated components or serious security problems, starting over may be the healthier choice. Base the decision on a review, not a guess.

My domain is in the freelancer's account. Will I lose my website?

If you act before it expires, there is usually a way forward. Contact the registrar where the domain is held and prepare documents that show you are the real user of it. If the situation has a legal side, consult an attorney. In the meantime, a full backup of the site protects your content even in the worst case.

That is a legal question that depends on your agreement and the nature of the work delivered, so it would not be right for me to give you a definitive answer. I would suggest bringing your proposal, any contract and your correspondence to an attorney. On the technical side, continuing work on a site built with common, properly licensed tools in your name is routine.

How long does it take to take over an unfinished website?

It varies with the type of site, the state of access and how much content is ready. A business site where you already hold every login and only the copy is missing will not take the same time as an online store with broken payment and shipping connections. After the review, I give you a realistic timeline.

Can a website takeover be handled by someone working remotely?

Yes, nearly all of it can be done remotely. Access is shared securely, the review and development happen online, and you follow progress through preview links. For most business owners, a video call and a written update are more practical than a meeting across town anyway.

Once the site is done, does it make sense to give SEO and social media to the same person?

In most cases, yes, because the person who knows the site inside out can more easily plan how it will appear on Google and which page a visitor from social media should land on. It is not required, though; you can have only the site finished and run the rest yourself or with someone else. What matters is that it is clear, in writing, who is responsible for what.

How do I make sure this does not happen again?

Insist that the domain, hosting and every account are opened in your name, that the scope is written down, that payments happen in stages, and that backups are taken regularly. Also ask to see a preview at every major milestone. Those rules protect you no matter who you work with.

If you want your freelancer's unfinished website reviewed, its ownership secured and the project brought to launch with a calm, clear plan, go to my website design service page and send me your site's address with a short note on what happened. I will look at it first and tell you honestly where it makes sense to begin.

Tags

freelancer abandoned my websitefinish half built websitewebsite takeover serviceweb developer disappearedhire developer to finish website

Contact

Let's talk about your website

Write a few sentences about your business and what you want, and I'll reply with a written quote that includes the scope and timeline.

A few sentences are enough. I'll get back to you as soon as I can.

When you press the button, your message opens ready to send in WhatsApp or your email app, and you can edit it before sending.