Hi there, my first topic!
We are in the works of moving our website from Wordpress to Webflow.
The problem: we have a hard deadline of Feb 14 launch and not all the new pages are ready to go live.
We plan to go live with some pages (homepage, pricing pageā¦) and redirect the rest of the pages to the āoldā website on wordpress. Then, continue to build and complete the migration.
Is this a reasonable solution? should we use 301/302 redirection to ALL the pages on the wordpress site?
If youāre using a new domain name for the new site, this is a possibility and you wonāt cause too much SEO damage because the old site will effectively be unchanged.
If you are trying replace the old site with your new Webflow one using the same domain name, that wonāt be an option with redirects.
The only options;;
Renegotiate your launch date
Accelerate your build schedule
Build a reverse proxy that consolidates both sites under the same domain name
Iād only recommend the r-proxy as a last option here, because without knowing more about both your old and new site structures, page counts, SEO, tech infrastructureā¦ this approach could range from moderately-complex to massively-complex, which wouldnāt be cheap.
I build reverse proxies regularly, so if options 1 and 2 arenāt possible, drop me a direct message with both published sites and I can give you an estimate.
Thanks @memetican . Yes, we are keeping THE SAME url and moving the old site from wordpress to a new webflow site. If that is the case we canāt do any redirects? The only option will be reverse proxy? can you share a bit more about this process?
If you move domain.com from site A to site B, then site A is now inaccessible.
You could register a new temporary domain like olddomain.com and apply it to your old site A, but that will be messy, confusing for users, and will break your SEO.
A reverse proxy is a new system that is built to intercept the requests for your domain.com. It can then respond to them specially like pulling the appropriate page from site A or site B, depending. However itās a fair bit of work to build correctly and there are a few tricks to make it work with Webflowās SSL certificates.
In your case the āsite mergeā would require not just the URL rewriting, but also canonical fixes and a rebuilt sitemap - and thatās the simplest situation. If have other featuresā¦ referrer tracking, user accounts, ecommerceā¦ there are other things to consider.
@Idan_Lasser Weāve built a no-code reverse proxy tool which can solve this for you. In this case, you can work under a unified domain while using Webflow and WordPress at the same time. For more information Connectify.tech | Reverse proxy for Webflow