Abandoned site: pick up what's left and bring it back to work
Picking up an abandoned site project is first an inventory, not the code: what survived accesses, to whom the domain is registered, is there anything to recover from. Only then can you see what to do next and how much it costs. A site that hasn't been technically monitored for years almost always has silent crashes—something that has stopped working without any visible signs. In the 1,848-card catalog we measured, the analytics counter, turned off on July 1, 2023, stood for three years in a row, and there was no new property at all.
working days, the upper limit is when accesses are returned by the registrar and support
free audit of what is left, 3-7 working days
Before the estimate
a copy of the project, deployed on the test site and checked
The first technical action
asset registry, access under your control, code in Git
What is left with you?
to return the cabinet, the key to which was left in someone else's mail
What we do not promise
Free audit of the abandoned project
The first task is an inventory: what is generally on hand, what is lost, and what is still working. Only after that it makes sense to talk about the plan and money.
What we measure
What remained of accessesDomain, hosting, admin, database, mailboxes, offices of payment systems and carriers, analytics, domain registrar. Some of the accesses are usually lost, and the return of each is a separate story with its own deadline.
State of the environmentPlatform, language and database versions. Projects that have been neglected for several years mostly work on branches without support: this is both security and the impossibility of putting something new on top.
What broke quietlyThings that stopped working without visible signs. In the catalog we measured, 1,848 items in the code still had the counter of analytics turned off on July 1, 2023, and there was no new property at all - the data had not been collected for three years, and it did not show in any way on the site.
Remains of other people's settingsBlanks from templates that remained. On the directory site we measured, the sitemap line in robots.txt was commented out with the sample "# Sitemap: https://site.com/sitemap.xml" — a typical trace of an unfinished setup.
Backup copiesAre they created at all and can you recover from them? On abandoned projects, the answer "there is" often means "there is a file that no one has tried to deploy."
What works and brings moneyWhich functions are still alive: order, payment, notifications. This determines where to start and what cannot be touched during the work.
What you get
Asset register: what is there, where is it, who is the owner, what accesses are lost.
Status document: versions, silent failures, remnants of other people's settings, status of backup copies.
A plan to get back on track with priorities: what to do first, what can be postponed.
Conversation for 30–40 minutes on the document.
Timeline: 3–7 working days — longer than a regular audit, because some of the accesses have to be restored
Why is it free
Because the main value in pickup is the inventory, and you need it regardless of whether we continue to work or not. The register of assets and access remains with you.
What's next
After the audit, a plan by stages with dates and an estimate for the first stage, a contract, an invoice, an act. Often the first stage is not development, but recovery and backups.
Short form: your contact and site URL
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
European clients
Among our work — projects for Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
What affects the price
Why two seemingly identical tasks are priced differently
How many accesses are lostWhen everything is in hand, the inventory is a few days of reconciliation. When three out of ten services are live, each other means a separate recovery procedure, correspondence with support and waiting. It is this point that extends the term from a week to a month and a half.
To whom the domain and mail are registeredThe domain for the company with access to its mail is returned according to the documents. A domain for a private person with whom there is no connection is already a legal road, and it cannot be shortened by technical means.
Age of environmentThe project is fixed immediately on supported versions. An unsupported branch means a separate upgrade phase before any improvements: our measurements of other sites still show PHP 7.3.33, which has been unsupported since December 2021.
Is there anything to recover from?A working copy that has been successfully deployed removes half the risk and allows you to work more boldly. There is no copy - the first stage is slower, because every change is made carefully.
The extent of what is already brokenOne dead analytics and an empty sitemap is a few hours. The project, where the payment, mail and exchange with the accounting system were poured in parallel, is disassembled one node at a time, and each is counted as a separate line.
Who confirms the decision from your sideRegistrars and service support speak with the owner, not the contractor. If each step is agreed upon for weeks, the deadline increases not because of the volume of work, but because of pauses in confirmations.
Who it's for
Situations where this service delivers results
Scenario 1 of 4
The developer stopped responding
The letters remain unanswered for the third month, and the site is selling in the meantime. Here it is important not to pull the code until a simple thing has been clarified: to whom the domain and hosting are registered and with whose mail the payment system offices were opened. The answer depends on whether we restore access or restart services.
We'll review your situation in a free audit
Scenario 2 of 4
The full-time specialist resigned and took the passwords with him
Formally, everything is yours, in fact half of the services are tied to his personal mail and phone. Part of it is returned by support according to the company's documents, part of it is not. We go through this list to the end and write honestly what is back and what will have to be reissued.
Scenario 3 of 4
The agency has closed, the site is working, nothing can be changed
There is access to the admin, but not to the server and database. Any correction rests on the fact that no one knows exactly where the project lies and whether it is possible to roll back. It is not resolved through negotiations, but through the registrar and hosting provider according to the owner's documents.
Scenario 4 of 4
The site arrived together with the business
They bought a company, got a website and don't know what's inside: who made it, what's written on it, what's still living there. You can't trust the description - you have to check it with what the server actually gives.
What's included
Complete list of work and what you get as a result
Register of assets and access in written form - you can see what is there, where it is and to whom it is issued, even before the first edit
Return of access through the registrar, hosting and service support — the domain and mail are under your control
A backup of the entire project with a deployment check is a point you can roll back to at any time
The test site is a copy of the combat one — edits are checked there, sales do not stop
Code in Git with the first commit "as accepted" - then each change is named and reversible
List of silent failures: dead counters, empty sitemaps, template residues in robots.txt
A priority work plan divided into safety, lost money and development - you choose what to do now
Critical patching according to an agreed list and regular backups with a recovery check
Handing over: written instructions and going through admin with your manager
Terms: payment by stages, warranty period of 30 calendar days for completed works
When this service isn't right
What's not included — so there are no surprises at delivery
Access, the key to which was left in someone else's mail or phone
Restoring sources that do not exist
Liability for data lost before our arrival
Legal return of domain rights in disputed cases
Hosting, domain, acquiring
Process steps
Transparent stages with approval at every step
Total duration:7–35 days
1
Inventory
3-7 working days
We collect everything that has been preserved and bring it into one registry: domain, hosting, database, mail, service offices, analytics. Against each item - the owner, access status and what to do if there is no access.
2
Access return
3-15 working days, in parallel with the rest
Registrar, hosting provider, support of payment and postal services. We do not set the deadlines here: something is returned in a day, something in three weeks, and something is not returned at all, and the service is restarted.
3
Copy and test site
1-2 working days
We make a copy of the files and database and expand it separately - we expand it, and do not put the archive in a folder. We do not touch the combat site until the copy is up and running.
4
Technical diagnostics
2-4 working days
Environment versions, counters, sitemap, robots.txt, structured data, mail, payments. The output is a list of silent breakdowns divided into safety, lost money and cosmetics.
5
The first stage of corrections
3-10 working days
We take an agreed list of critical things: close security holes, restore measurability, fix things that directly take away orders. Each edit is first on the test, then on the combat.
6
Regular copies and transfers
1-3 working days
We set a schedule for copying and recover from it live once. Then written instructions, going through the administration with your manager and transferring access into your hands.
Did not find your case?
Describe how it works on your side — we will tell you whether “Picking up an abandoned project” fits and what it means in your situation. No brief and no call: one question, one answer.
Cases
Tasks and results in numbers — all metrics measured by us
B2B catalog of spare parts for industrial sewing equipment
Task
To accept a directory that has been working for a long time without technical support, and to understand that it broke imperceptibly.
Solution
Sitemap and speed measurement, comparison of language versions, verification of analytics and structured data counters.
Result
1,992 addresses in the site map without a single duplicate — 1,848 product cards and 138 categories. TTFB 388.1ms, full load 419.5ms, main HTML 120.2KB - the third lightest markup among the 16 sites measured. The language marks uk-ua, ru-ua and x-default are correct. Critical: The Universal Analytics counter is connected in the code, which Google finally turned off on July 1, 2023, and the GA4 property is not there at all - data was not collected for three years, and it did not show in any way from the outside. Additionally, there are zero JSON-LD and microdata blocks on the 1,848-item directory, and robots.txt doesn't declare a sitemap, even though the sitemap itself is working and complete. Measured on 07/31/2026.
Technologies & integrations
What we build on and what it connects to
Stack
OpenCart 3.x and 4.x — most of the abandoned stores come to them; under 4.x part of the Ukrainian modules is still not assembled
WordPress and WooCommerce — the code on the hosting is usually complete, but there is nothing to update paid plugins without licenses
PHP and MySQL - the version is visible from the very first server response; on abandoned projects this is often an unsupported branch
Git is the first "as accepted" commit; he will not restore the history of changes to us
The test site is a copy of the combat site - the payment gateways on it work only in test mode
Backup with recovery verification - a copy that has never been deployed proves nothing
Integrations
domain registrar
hosting panel
Google Search Console
Google Tag Manager
GA4
payment providers
carriers
SMTP
Telegram
Pick up an existing project or make a new one
How this option differs from the alternative
Development from scratchOur approach
When is it safe to change a site?months, and the old site still has to be kept alive7-35 working days, sales are going on all this time
What will happen to the accumulatedeverything moves, every address turns into a redirectaddresses, index and history remain in place
Attitude to the unknownthe unknown is left behind with the old sitefirst we measure, then we touch
Lost accessesthe new development does not bring them back — the task remainsreturn or reissue, the domain is still needed
What we need from you
We can't start without this — best to prepare in advance
1Everything that is preserved: logins, passwords, letters from the previous contractor, hosting accounts - even what seems to be no longer working.
2Contacts of the domain registrar and hosting provider and data on who the contract is for.
3Access to the mail to which the services were started, if you have it: most accounts are returned through it.
4The history of the project in human language: who did it, when they stopped, what was changed last.
5One person has the right to confirm the restoration of access - the registrar and service support speak with the owner.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ
Most frequently asked questions — with concrete answers
The developer does not get in touch - where to start?
From accesses, not from code. The domain is usually returned through the registrar according to the owner's documents, hosting - through the provider's support, service cabinets - through the recovery procedure to the company's mail. Some return in a few days, some in a few weeks, and some do not return at all, and then the service starts again. These deadlines are not set by us, therefore they are a separate line in the plan, and not within the "development".
The site has not changed for years and seems to be working - why do anything at all?
Because some things break without visible signs. In the catalog we measured, there was an analytics counter for 1,848 cards, which Google turned off on July 1, 2023, and there was no new property at all: the site sold for three years, and no data was collected. Here it is worth mentioning the limit right away - the meter itself does not improve anything, it only returns the ability to see. And even if you turn it back, you'll get a trend, not an accounting truth: blockers, consent mode, and browser cookie restrictions understate the numbers.
Where does the work itself begin?
From a copy that we expand and open, not just save. On abandoned projects, this is not a formality: it often turns out that there is no copy at all, or there is one, but no one has ever tried to raise it, and there is no base inside. Until the copy has risen on the test site, we do not touch the combat site. This is our own condition, and we do not bypass it even when we are asked to "fix one small thing quickly".
How do you even understand what the site is made of?
We see what the server gives, not what is written in the documents. The engine and theme are visible from the paths inside the HTML - in an abandoned project, this is often the only reliable source. A recent example from our own portfolio: WordPress was in the project description, and the path to the OpenCart theme was in the code. We have corrected the description ourselves, but the conclusion is broader — when picking up any description, including our own, it is impossible to believe without verification.
Is it possible to pick up the project if there are no sources?
If it is a common platform, yes: the code is on the hosting, and it is enough to continue working. We take what is there, put it in Git with the first "as accepted" commit, and continue the story normally. It is more difficult with self-written projects and with paid modules without licenses: there is nothing to update them, and part of the functions may be lost forever. This is found out during the audit, and not in the middle of the work.
What are the most common traces of previous contractors?
Unfinished settings that have remained patterned. On the directory site we measured, the sitemap line in robots.txt was commented out with the blank "# Sitemap: https://site.com/sitemap.xml" and the sitemap itself returned 200 with an empty body. A fair margin: a declared sitemap does not increase rankings or guarantee indexing - it only removes the reason why pages may not be indexed at all. It's the same with structured data: the markup gives a chance for an extended snippet, but it's up to the search engine to show it or not.
We have old hosting and an old version of the platform — is it dangerous?
Yes, and the certificate does not help here: it encrypts the channel, and that's all. It does not protect against a hole in an outdated version of the language or CMS. In our measurements of other sites, PHP 7.3.33 is still encountered - a branch without support since December 2021, that is, there are no security patches for it. On capture, we put this in the first stage next to copies: the environment update is done before the updates, not after.
How much does pickup cost?
These are at least two different amounts. The first is a return to a controlled channel: accesses, copies, inventory, correction of critical. The second is development, and it is already counted as ordinary work. We deliberately separate them in the estimate so that you can see what you are paying for now and what you can put off for later. It is honestly impossible to give a figure for the audit: the volume determines how many accesses are lost and how outdated the environment is.
How long does it take, and is it possible to run the project yourself?
7-35 working days. The lower limit is when all access is at hand and you just need to get things in order. Upper — when access is returned by registrars and service support. You can carry on by yourself: the asset register, repository, accesses and written instructions remain with you, and during the transfer we go through administration with your manager on a live task. We don't hold the project hostage - that's the difference with what you just suffered.
Write what is saved: accesses, letters, hosting accounts.
In a few days, we will tell you what is still under your control, what is being returned and in what order. If resuscitation does not make sense, you will hear it in the first email.
From measured cases1,992 addresses in the site map without a single duplicate
There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.