01
Technology and current condition
We document the CMS or framework, versions, themes, plugins, source code and setup. Known issues and important visitor journeys are recorded so it is clear what can stay and what needs attention first.
Website takeover
Your website was built by another agency, or your current developer is no longer available. Jordy investigates how it runs, what access is available and what can responsibly be taken over. We then agree on management, maintenance and any improvements.
01
We document the CMS or framework, versions, themes, plugins, source code and setup. Known issues and important visitor journeys are recorded so it is clear what can stay and what needs attention first.
We identify who manages the domain, hosting, repository and external accounts. Your authority and available rights are checked. Missing access or licences are discussed before responsibilities are accepted.
We review available backups and what is needed to roll changes back. A restore test or separate test environment is included when feasible within the agreed scope and technology.
Taking over management does not automatically require moving your hosting. If a move is needed, we review DNS, mailboxes, certificates and external integrations and agree the steps and responsibilities in advance.
Pages, URLs, images, forms and existing measurement are documented. We agree which visitor journeys will be checked after handover and how any URL changes will be handled.
You receive a summary of the current setup, outstanding access questions, risks and recommended next steps. The initial takeover, recurring maintenance, hosting and new development are scoped separately.
A takeover starts with a review. This helps identify unknown dependencies or missing access before changes begin. If a component cannot responsibly be supported, we discuss the available options first.
These pages address the same underlying question and help you choose the right project scope.
Codegenie takes over technical website maintenance and targeted changes for businesses that want a clear owner for an existing site. The first step is to determine what can be taken over safely and which follow-up is genuinely needed.
View serviceYou want to explain your services, sell products or improve an existing WordPress site. As a WordPress expert, Jordy helps you with structure, development and technical decisions. Discuss your needs directly with the developer behind Codegenie.
View serviceDoes your site load slowly, respond late to clicks or shift its content on mobile? Jordy investigates where your website loses time and implements agreed improvements. You receive baseline measurements, clear priorities and follow-up checks, directly from the developer behind Codegenie.
View serviceA slow, dated or confusing site does not automatically need rebuilding. Codegenie reviews the content, technology and enquiry journey before defining the smallest worthwhile improvement.
View serviceOur approach
Scope and responsibilities are clarified first. We then build and verify the solution in controlled steps.
Share your website address, its technology if known and why you want to switch. Describe what is not working well today.
We examine the available information and access. You receive a proposal for takeover, necessary fixes and any further support.
Accounts, licences, backups and contact with the current manager are coordinated. Any migration and rollback approach are planned separately.
We check the agreed pages, forms and integrations. You receive the responsibilities, checks performed and outstanding items.
Yes, if you are authorised to transfer management and the technology can responsibly be supported. We begin with the website, accounts, available source code and arrangements with the current provider.
Not automatically. We assess whether the existing environment supports the agreed work. If a migration is needed, hosting, DNS, mailboxes and responsibilities are reviewed first.
Yes. We review the WordPress installation, theme, plugins, versions, licences and backup options. This determines a suitable takeover and follow-up scope.
Explain which accounts you do and do not manage. We identify the access needed and who can transfer it. Missing access can block parts of the takeover, so we agree how to address it first.
The initial takeover and recurring maintenance each have a defined scope. Updates, backups, monitoring, small changes and any response times are included only when agreed.
It depends on the technology, available access, current condition and any migration. The review leads to a defined proposal. Hosting, licences, remedial work and new features are listed separately.
Send your website address and describe the current situation and support you need. Mention missing access, but do not share passwords or customer data.