Audit
Checking CMS, PHP, template, modules, forms, speed, SEO database, hosting and errors.
// Old website under control
Updating an old website without risk for enquiries and SEO
Audit, backup, updating CMS and PHP, transferring from designers, setting up hosting or VPS/VDS, correcting forms, speed and security. The goal is to put the website in order without chaos and loss of work enquiries.
Backup
Before edits, I note the possibility of rolling back: files, database, accesses and critical settings.
Update
CMS, plugins, modules, theme, PHP, SSL, email, cron, server settings and compatibility.
Transfer
If it is not profitable to repair the old base, you can transfer the content, addresses and SEO logic to the new platform.
// What usually breaks in old websites
The problem is rarely just in design
A website may look “just old,” but hidden underneath is often an outdated CMS, an old version of PHP, weak hosting, broken forms, insecure extensions, and lost SEO structure. Therefore, the update begins with diagnostics.
Old CMS or recorder
WordPress, Joomla, PrestaShop, old PHP code, abandoned theme, outdated modules or admin panel that is scary to touch.
Mobile version
The text is small, the buttons are awkward, the menu is broken, the forms don’t fit, and important blocks look bad on the phone.
Forms and email
Enquiries do not arrive, SMTP is not configured, letters end up in spam, there is no SPF/DKIM/DMARC, or the form appears to work, but the business is losing leads.
Security
Old extensions, unknown users, suspicious files, weak passwords, open panels and lack of regular backups.
Speed and server
Slow hosting, bad cache, heavy images, PHP errors, memory limits, VPS/VDS without maintenance and monitoring.
Constructor limits
A website on Wix, Tilda, Webflow or a similar platform is difficult to develop, expensive to maintain, or impossible to properly develop.
// Transfer from constructors and old platforms
If the constructor has become a limitation, the website can be moved to a managed basis
It is not always possible to export a website from the designer one to one. More often, it needs to be carefully reassembled: save texts, images, page structure, important addresses, SEO logic, domain, forms, analytics and basic user scenarios.
✓Transfer of structure and content while maintaining the logic of pages, menus and key blocks.
✓Setting up domain, SSL, email, forms, analytics, redirects and basic SEO check.
✓Selection of a new framework: WordPress, Joomla, PrestaShop or a custom solution if the CMS is not suitable.
Wix
Squarespace
Webflow
Tilda
Weebly
Jimdo
GoDaddy Builder
IONOS Builder
Google Sites
Strikingly
Site123
Carrd
Hostinger Builder
Framer
Readymag
// How the work goes
Safe update begins before the first “update” click
An old website cannot be treated at random. First you need to understand what keeps it working, where the risks are and how to roll back if something goes wrong.
Diagnostics
I check the CMS, custom code, PHP, hosting/VPS, forms, SSL, errors, speed and SEO database.
Backup
Files, database, accesses, current settings and a clear rollback plan to changes.
Plan
What we update, what we transfer, what we replace, what URLs we save and what risks there are.
Works
Updating, transferring, setting up the server, fixing forms, security, speed and mobile version.
Check
Control of pages, requests, redirects, meta data, indexing, errors and stability after launch.
// When it's time to update
It’s better to check the old website before it stops bringing in enquiries
- Hosting asks to switch to new PHP
- The website opens slowly
- Forms do not send emails
- No normal backups
- The website does not look good on a phone
- CMS or plugins have not been updated for a long time
- There is a suspicion of viruses or hacking
- The builder no longer allows you to develop the website
- The developer has disappeared, but the access remains
- It is necessary to transfer the website to a new hosting or VPS
// Application
It’s better to start with an audit of the old website
Send a link to the website and briefly describe the situation: old CMS, designer, self-writing, PHP, hosting, VPS/VDS, forms, viruses, speed or transfer. I'll see what's safer: upgrading, repairing, or moving.
// FAQ
Frequently asked questions about updating an old website
Is it possible to update an old website without a complete redesign?
Yes, if the technical basis is still suitable. First I check the CMS, PHP, template, plugins, hosting, forms, mobile version and security. After this, it is clear whether a careful update is enough or whether it is better to transfer the website to a new basis.
What to do if the website is running on an old version of PHP?
You can’t just switch PHP on your hosting without checking. You need to make a backup, check the compatibility of the CMS, theme, modules and code, and then update step by step. For self-written websites, sometimes code changes are needed for a new version of PHP.
Is it possible to make a copy first and check everything there?
Yes, this is the correct approach for risky updates. Work can be performed on a copy of the website or a test environment, check the result and only then transfer the changes to the working version.
What if the website is self-written and the developer has disappeared?
Such a website can first be disassembled: file structure, database, PHP version, dependencies, forms, admin panel and critical functions. After the audit, it will become clear whether it can be maintained, updated, or better gradually transferred.
Is it possible to transfer a website from Wix, Tilda, Webflow or another website builder?
Yes. Typically, a website from a website builder is not exported one to one, so it is carefully reassembled on a new platform: texts, images, structure, important addresses, SEO logic, domain, forms and analytics are preserved.
Which constructors can be moved?
You can consider transferring from Wix, Squarespace, Webflow, Tilda, Weebly, Jimdo, GoDaddy Website Builder, IONOS Website Builder, Google Sites, Strikingly, Site123, Carrd, Hostinger Website Builder, Framer, Readymag and similar solutions.
Is it possible to keep the design but update the technical part?
Yes, if the design still suits the business. You can keep the visual idea, but replace the outdated technical basis, improve adaptability, forms, speed, security and content management.
Can the update affect SEO?
Maybe if you change page addresses, structure, meta data or content without a plan. Therefore, when updating, it is important to save important URLs, set up redirects, check websitemap, robots.txt, headers, speed and indexing.
Are you running a server, VPS or VDS?
Yes, as part of the maintenance, you can check and configure hosting, VPS/VDS, PHP, SSL, email, backups, file rights, basic security, cron tasks and website stability.
When is it no longer profitable to repair an old website?
If the website is very outdated, poorly indexed, unsafe, not adapted for mobile devices, and any changes take too much time, it is more honest to consider transferring the content to a new basis. This is often cheaper than endlessly fixing an old system.