## Marketing Website DNS

### Option 1: Shared Wordpress + Webflow domain

* **Complexity**: 3 (1-2 weeks)
* Put a frontend proxy to route traffic to either WP Engine or Webflow
* This option has a very high maintaince cost in terms of people and parts involved

**Work Required**
* Set up a proxy. Neither Wordpress nor Webflow can no longer use the supplypike.com DNS directly
* Define and maintain routings in the proxy
* Which paths needs to go to the Wordpress site? (``/blog/*, wp-content/*, /wp-login.php, /wp-admin/*``, what else?)
* Extensive testing necessary to make sure all three components actually work together. Potentially there will be unforeseen issues that are hard to resolve.


### Option 2: New domain for Webflow

* **Complexity**: 1 (1-2 days)
* Keep WP Engine on the current domain (supplypike.com)
* Webflow on a new domain (www.supplypike.com)
* If not careful, this could lead to user or SEO confusion

**Work Required**
* WP Engine: remove all non-blog pages
* WP Engine: redirect all non-blog and non-wp URLs to Webflow domain
* Webflow: redirect `www.supplypike.com/blog/*` to `supplypike.com/blog/$1`
* SEO: submit indexing of the new domain
* SEO: submit re-indexing of the current domain

### Option 3: New domain for Wordpress

* **Complexity**: 2 (2-5 days)
* WP Engine on a new domain (blog.supplypike.com)
* Webflow on the current domain (supplypike.com)
* This is the best middle-ground between technical work, isolation, and user/SEO experience.

**Work Required**
* WP Engine: remove all non-blog pages
* WP Engine: redirect all non-blog and non-wp URLs to Webflow domain
* WP Engine: migrate domain from supplypike.com to blog.supplypike.com
* Webflow: redirect `supplypike.com/blog/*` to `blog.supplypike.com/$1`
* SEO: submit re-indexing of the current domain
* SEO: submit indexing of the new blog domain