FIELD NOTE / WEBSITE MIGRATION
A Node.js-to-PHP rebuild is a website migration. The important part is preserving the customer journey and existing useful search signals while replacing the implementation.
Export the current sitemap and inspect Search Console landing pages. Record valuable URLs, images, downloadable files, form behaviour, analytics settings and verification files. Keep a full backup and a rollback path before switching the live application.
If a service page can keep its existing URL, keep it. When a URL changes, use a permanent redirect to the closest relevant replacement. Do not send every removed page to the homepage. Keep genuinely missing pages as proper 404 responses.
Review titles, headings, descriptions, canonical URLs and main page content. PHP output should contain the essential content in the first HTML response. This is a technical choice, not an automatic ranking advantage over another framework.
A form is not complete because the browser shows a success message. Confirm a valid request is stored, invalid requests are rejected and private records cannot be downloaded publicly. Keep admin credentials and lead data outside publicly served files.
Confirm HTTPS and preferred-host redirects, sitemap access, robots directives and important pages. Use Search Console URL inspection for priority URLs. Monitor for crawl errors and unexpected traffic changes, and keep the backup until the migration is stable.
Written by One Digi Global. Further reading from Google Search Central:
SEO Starter Guide ↗Site migration guidance ↗YOUR NEXT CUSTOMER IS SEARCHING.