--- title: ECOM | How to configure your Content Website for ECOM integration description: This step by step guide will walk you through how to configure your existing Wordpress, Duda, Webflow or Squarespace content website for integration with ECOM --- [Skip to content](https://support.blaze.me/hc/en-us/articles/how-to-configure-content-website-for-ecom#main-content) [![BLAZE-Logo-Blue (2)](https://support.blaze.me/hs-fs/hubfs/BLAZE-Logo-Blue%20(2).png?width=140&height=37&name=BLAZE-Logo-Blue%20(2).png)](https://support.blaze.me?hsLang=en) - [BLAZE US Knowledge Base](https://support.blaze.me/hc/en-us/articles) Open main navigation Close main navigation - [BLAZE US Knowledge Base](https://support.blaze.me/hc/en-us/articles) Welcome to the Blaze US Knowledge Base! Find helpful reference by searching here... - There are no suggestions because the search field is empty. 1. [BLAZE US Knowledge Center](https://support.blaze.me/hc/en-us/articles?hsLang=en) 2. [BLAZE ECOM](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en) # ECOM | How to configure your Content Website for ECOM integration ## This step by step guide will walk you through how to configure your existing Wordpress, Duda, Webflow or Squarespace content website for integration with ECOM BLAZE ECOM is a unique cannabis ecommerce solution that allows for indexable menu pages for all of your products, categories and brands. This results in these individual page urls being directly connected to your main domain and are fully crawl-able by search engines; resulting in Google indexing these pages and assisting with the building of SEO and your domains online presence. **BLAZE ECOM is integrated to your domain and content website through a proxy, which allows for the native connection between the ECOM menu and domain.![DIAGRAM2](https://support.blaze.me/hs-fs/hubfs/DIAGRAM2.png?width=670&height=470&name=DIAGRAM2.png) Please see the details below on how to configure your Wordpress, Duda or Squarespace site for the ECOM DNS proxy. Jump to: \- [Wordpress Configuration](https://support.blaze.me/hc/en-us/articles/how-to-configure-content-website-for-ecom#:~:text=For%20Wordpress%20Content%20Sites%3A) \- [Webflow Configuration](https://support.blaze.me/hc/en-us/articles/how-to-configure-content-website-for-ecom#:~:text=For%20Webflow%20Sites%20%2D%20DNS%20Proxy%3A) [- Squarespace Configuration](https://support.blaze.me/hc/en-us/articles/how-to-configure-content-website-for-ecom#:~:text=For%20Squarespace%20and%20Duda%20Sites%20%2D%20DNS%20Proxy%3A) \- [Duda Configuration](https://support.blaze.me/hc/en-us/articles/how-to-configure-content-website-for-ecom#:~:text=For%20Squarespace%20and%20Duda%20Sites%20%2D%20DNS%20Proxy%3A)** ### **For Wordpress Content Sites:** The steps below are a summary of the details outlined further in the kb article of how to configure your existing **Wordpress** content site for this proxy integration. Your duplicated Wordpress site should be placed on a subdomain content domain url **content.rootdomain.com** (example: **content.blaze.me**), with an SSL issued to it and no redirects configured. This may require adding a domain in your hosting platform temporarily. - Create a complete duplicate (or brand new) version of your Wordpress site in the same or any Hosting environment. - Create a **content.** subdomain in your domain host (content.rootdomain.com) - Connect duplicated website to content.rootdomain.com - Remove any redirects from content. to main domain (website should load on that content domain - Issue SSL to the content domain and send to Onboarding Coach or [ECOM Support](mailto:ecomsupport@blaze.me) - **Note: Once launched, content updates will be made on the content.rootdomain.com/wp-admin website, which will then populate on the root domain.**  - **REQUIRED****: Configure content.rootdomain.com Wordpress site to "NOINDEX"** via these **[instructions.](https://yoast.com/help/how-to-noindex-an-entire-site/)** - This will prevent the content domain (content.rootdomain.com) from being indexed by Google and search engines permanently. - **REQUIRED:  Install the Tymber Shop Plugin on content.rootdomain.com**. Download the install Zip File by [clicking this **link**](https://support.blaze.me/hubfs/wp-tymber-shop-v1.0.2.zip?hsLang=en). - - This plugin wil**l** auto-configure all links as Relative on the content.rootdomain.com site (required for proxy). - - Relative links are the url pathname only, without the root domain included: **/menu** versus **rootdomain.com/menu** - **Note**: If using the Yoast SEO plugin, the Relative links will cause a conflict. You must **Enable** the **Disable Relative URL on Admin Dashboard **setting. - Tymber Shop Plugin also includes a Short Codes feature, which can be configured with the assistance of the ECOM Support team. - **[Configuring the Short Code feature](https://support.blaze.me/hc/en-us/articles/shortcode-feature?hsLang=en)** - **Please email ecomsupport@blaze.me for assistance and API token (not required for ECOM Proxy)** - **ECOM Support will need the WP Admin Site Address to pair with the API token:![](https://support.blaze.me/hs-fs/hubfs/image-png-Aug-05-2024-07-00-02-4598-PM.png?width=670&height=473&name=image-png-Aug-05-2024-07-00-02-4598-PM.png)** - Once configured and plugin installed, send the **content domain (content.rootdomain.com)** to your ECOM Onboarding Coach.  **Launching Content Domain and ECOM:** - Our ECOM Support team will coordinate the launch of your content site and proxied ECOM menu(s) with your Onboarding Coach. We highly recommend granting DNS access to your domain so our team can white glove the launch for you. - **[How to grant access to your domain's DNS Settings](https://support.blaze.me/hc/en-us/articles/granting-dns-access?hsLang=en)** - **For Self Launches Only (Not recommended):** - If you prefer launching the ECOM yourself, the records needed for the proxy to work accordingly are viewable in these kb articles - **[How to update your DNS records for ECOM Launch](https://support.blaze.me/hc/en-us/articles/launch-dns-settings?hsLang=en)** - **[Understanding your DNS records for ECOM Launch](https://support.blaze.me/hc/en-us/articles/understanding-dns-settings-after-launch?hsLang=en)** - When we launch the ECOM, the content on the content domain will be placed onto the root domain via two DNS records. - Before the ECOM is live, edits to the content site should be made to both versions to ensure they are both up to date. **Post Launch Tips:** - - **Do not alter/remove the ECOM DNS records from your domain's settings without confirming with ECOM Support (ecomsupport@blaze.me) first.** - After the ECOM is live, edits to the content site will be made on the content url site: [content.rootdomain.com](http://content.rootdomain.com/) - After creating the content domain, you'll need to request it's removal from Google Search Console to prevent indexing: - **[How to Remove Content Domain from Search Results](https://support.blaze.me/hc/en-us/articles/remove-content-domain-from-search-results?hsLang=en)** - **If using WP Rocket Caching Plugin, ALWAYS complete the cache purge in the plugin settings after completing any content site updates.![](https://support.blaze.me/hs-fs/hubfs/image-png-Jun-20-2024-04-34-44-7702-PM.png?width=670&height=329&name=image-png-Jun-20-2024-04-34-44-7702-PM.png)** - Once the ECOM has been launched, the previous domain/site may be deleted to free up account space/seats. All future content updates will be made on content.rootdomain.com, which will populate on the main domain via the DNS Proxy. **For Webflow Sites - DNS Proxy:** The steps below are a summary of the details outlined further in the kb article of how to configure your existing **Webflow** content site for this proxy integration. Your duplicated Webflow site should be placed on a subdomain content domain url **content.rootdomain.com** (example: **content.blaze.me**), with an SSL issued to it and no redirects configured. This may require adding a domain in your hosting platform temporarily. - Create a complete duplicate (or brand new) version of your content site in the same or any Hosting environment. This complete content site version should be placed on a subdomain content url [content.rootdomain.com](http://content.rootdomain.com/)(example: [content.blaze.me](http://content.blaze.me/)), with an SSL issued to it and no redirects configured. - **Note: Once launched, content updates will be made on the content.rootdomain.com website, which will then populate on the root domain.**  - Once configured and plugin installed, send the **content domain (content.rootdomain.com)** to your ECOM Onboarding Coach.  **Launching Content Domain and ECOM:** - Our ECOM Support team will coordinate the launch of your content site and proxied ECOM menu(s) with your Onboarding Coach. We highly recommend granting DNS access to your domain so our team can white glove the launch for you. - **[How to grant access to your domain's DNS Settings](https://support.blaze.me/hc/en-us/articles/granting-dns-access?hsLang=en)** - **For Self Launches Only (Not recommended):** - If you prefer launching the ECOM yourself, the records needed for the proxy to work accordingly are viewable in these kb articles - **[How to update your DNS records for ECOM Launch](https://support.blaze.me/hc/en-us/articles/launch-dns-settings?hsLang=en)** - **[Understanding your DNS records for ECOM Launch](https://support.blaze.me/hc/en-us/articles/understanding-dns-settings-after-launch?hsLang=en)** - When we launch the ECOM, the content on the content domain will be placed onto the root domain via two DNS records. - Before the ECOM is live, edits to the content site should be made to both versions to ensure they are both up to date. **Post Launch Tips:** - - **Do not alter/remove the ECOM DNS records from your domain's settings without confirming with ECOM Support (ecomsupport@blaze.me) first.** - After the ECOM is live, edits to the content site will be made on the content url site: [content.rootdomain.com](http://content.rootdomain.com/) - After creating the content domain, you'll need to request it's removal from Google Search Console to prevent indexing: - **[How to Remove Content Domain from Search Results](https://support.blaze.me/hc/en-us/articles/remove-content-domain-from-search-results?hsLang=en)** **For Squarespace and Duda Sites - DNS Proxy:** 1. Squarespace and Duda content sites have a built-in domain, which the content lives on automatically. We'll just need that built-in domain for the proxy integration, along with DNS access.  1. URLs are automatically configured as Relative for Squarespace content sites. 1. For Squarespace content sites, be sure to disable any **/menu or /shop** pages within the CMS if using those pathnames for an ECOM menu. 2. URLs will need to be full domain.com/pathname in Duda CMS links 2. Please refer to the screenshots below: **Squarespace:** **![iScreen Shoter - Google Chrome - 240116165729](https://support.blaze.me/hs-fs/hubfs/iScreen%20Shoter%20-%20Google%20Chrome%20-%20240116165729.png?width=670&height=279&name=iScreen%20Shoter%20-%20Google%20Chrome%20-%20240116165729.png)** **Duda:** **![iScreen Shoter - Google Chrome - 240116165316](https://support.blaze.me/hs-fs/hubfs/iScreen%20Shoter%20-%20Google%20Chrome%20-%20240116165316.png?width=670&height=409&name=iScreen%20Shoter%20-%20Google%20Chrome%20-%20240116165316.png)** **Launching Content Domain and ECOM:** Our ECOM Support team will coordinate the launch of your content site and proxied ECOM menu(s) with your Onboarding Coach. We highly recommend granting DNS access to your domain so our team can white glove the launch for you. - **[How to grant access to your domain's DNS Settings](https://support.blaze.me/hc/en-us/articles/granting-dns-access?hsLang=en)**  - **Do not alter/remove the ECOM DNS records from your domain's settings without confirming with ECOM Support (ecomsupport@blaze.me) first.**   3\. If existing content site is not built on any of the CMS platforms listed above, we can skip the site configuration above and place the ECOM onto a subdomain. - **[How to configure a subdomain ECOM on your domain](https://support.blaze.me/hc/en-us/articles/launching-ecom-menu-on-subdomain?hsLang=en)**   - [BLAZE Retail](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#main-content) - [FAQs](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#faqs) - [Ecommerce](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#ecommerce) - [Transactions](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#transactions) - [Loyalty / Marketing](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#loyalty-marketing) - [Members](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#members) - [Integrations](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#integrations) - [Reporting](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#reporting) - [Metrc](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#metrc) - [Delivery & Dispatch](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#delivery-dispatch) - [Getting Started](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#getting-started) - [BioTrack](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#biotrack) - [Promotions](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#promotions) - [Point of Sale (POS)](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#point-of-sale-pos) - [Purchase Orders](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#purchase-orders) - [Insights](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#insights) - [BLAZEPAY](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#blazepay) - [Compliance & Taxes](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#compliance-taxes) - [Inventory Management](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#inventory-management) - [Hardware & Labels](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#hardware-labels) - [Web POS App](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#web-pos-app) - [State Limits](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#state-limits) - [New Mexico S2S](https://support.blaze.me/hc/en-us/articles/blaze-retail?hsLang=en#new-mexico-s2s) - [BLAZE ECOM](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#main-content) - [ECOM Mission Control](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#ecom-mission-control) - [Ecommerce](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#ecommerce) - [Onboarding](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#onboarding) - [Website Content](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#website-content) - [Mobile Apps](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#mobile-apps) - [SEO](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#seo) - [General](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#general) - [Promotions, Discounts & Rewards](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#promotions-discounts-rewards) - [Integrations](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#integrations) - [WordPress](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#wordpress) - [Order Notifications](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#order-notifications) - [Online Store Configuration](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#online-store-configuration) - [Customization](https://support.blaze.me/hc/en-us/articles/blaze-ecom?hsLang=en#customization) - [BLAZEPAY](https://support.blaze.me/hc/en-us/articles/blazepay?hsLang=en#main-content) - [Cashless ATM](https://support.blaze.me/hc/en-us/articles/blazepay?hsLang=en#cashless-atm) - [BLAZE Growth](https://support.blaze.me/hc/en-us/articles/blaze-growth?hsLang=en) - [Ecommerce](https://support.blaze.me/hc/en-us/articles/ecommerce?hsLang=en#main-content) - [Online Store Configuration](https://support.blaze.me/hc/en-us/articles/ecommerce?hsLang=en#online-store-configuration) - [Mobile Apps](https://support.blaze.me/hc/en-us/articles/mobile-apps?hsLang=en#main-content) - [Go To Market](https://support.blaze.me/hc/en-us/articles/mobile-apps?hsLang=en#go-to-market) - [Troubleshooting](https://support.blaze.me/hc/en-us/articles/mobile-apps?hsLang=en#troubleshooting) - [Push notifications](https://support.blaze.me/hc/en-us/articles/mobile-apps?hsLang=en#push-notifications) - [Onboarding](https://support.blaze.me/hc/en-us/articles/mobile-apps?hsLang=en#onboarding) - [Payment Integrations](https://support.blaze.me/hc/en-us/articles/payment-integrations?hsLang=en#main-content) - [Birchmount](https://support.blaze.me/hc/en-us/articles/payment-integrations?hsLang=en#birchmount) - [BLAZE Sites](https://support.blaze.me/hc/en-us/articles/blaze-sites?hsLang=en#main-content) - [SEO](https://support.blaze.me/hc/en-us/articles/blaze-sites?hsLang=en#seo) - [General](https://support.blaze.me/hc/en-us/articles/blaze-sites?hsLang=en#general) - [Widgets](https://support.blaze.me/hc/en-us/articles/blaze-sites?hsLang=en#widgets) - [BLAZE Widgets](https://support.blaze.me/hc/en-us/articles/blaze-sites?hsLang=en#blaze-widgets) - [3rd Party Apps](https://support.blaze.me/hc/en-us/articles/blaze-sites?hsLang=en#3rd-party-apps) - [Company Products](https://support.blaze.me/hc/en-us/articles/company-products?hsLang=en) - [SSO(Single Sign-On)](https://support.blaze.me/hc/en-us/articles/ssosingle-sign-on?hsLang=en) - [BLAZE Brands](https://support.blaze.me/hc/en-us/articles/blaze-brands?hsLang=en) - [Product Catalog](https://support.blaze.me/hc/en-us/articles/product-catalog?hsLang=en) - [Compliance](https://support.blaze.me/hc/en-us/articles/compliance?hsLang=en#main-content) - [New Mexico](https://support.blaze.me/hc/en-us/articles/compliance?hsLang=en#new-mexico) [![BLAZE-Logo-Blue (2)](https://support.blaze.me/hs-fs/hubfs/BLAZE-Logo-Blue%20(2).png?width=140&height=37&name=BLAZE-Logo-Blue%20(2).png "BLAZE-Logo-Blue (2)")](http://blaze.me) BLAZE US Help Center Copyright © 2026, BLAZE Solutions Inc.