WordPress Shopify Integration: Sell on Your WP Site

Quick Match: Pick a Method in 30 Seconds

If you came here for one answer, here it is. Match your situation to a row, then jump straight to that method's section. Everything below this block is the "why" behind these picks.

Why Combine Shopify and WordPress at All

WordPress powers roughly 43% of all websitesVerified SourceW3Techs CMS UsageW3Techs · 2026View source , including most blogs, knowledge bases, and content-heavy brand sites. Shopify dominates serious commerce — over 4.6 million live stores and the highest-converting hosted checkout in the industry. The natural question for any growing WordPress business is: do I rebuild on Shopify, bolt on WooCommerce, or integrate the two?

For most teams, integration is the right answer. You already have authority, traffic, and editorial workflows on WordPress. You don't need to throw those away to start selling. You just need a clean way to expose Shopify products on the WP front-end, send shoppers to Shopify's checkout, and keep the data in sync. That's exactly what the five methods in this guide cover. If you're still weighing the platforms head-to-head before integrating, our Shopify vs WordPress comparison covers the cost and conversion math.

Three concrete scenarios where integration beats both alternatives:

• Content brand selling merch. A 5-year-old WP blog with strong rankings adds a shop. WooCommerce would dilute focus and slow the site; full migration would torch the SEO. Sell on WordPress plugin or Buy Button is the right answer.
• Agency with productized services. Marketing site on WP, but selling templates, audits, or training packages. A few Buy Buttons embedded on landing pages handle commerce in 30 minutes, no rebuild required.
• Established Shopify store launching a content arm. Reverse case — Shopify on shop.brand.com, new content site on brand.com via WordPress. Storefront API powers a "shop the look" widget on blog posts.

The 5 Integration Methods at a Glance

Before we dive into each method, here's the side-by-side that helps you skip ahead:

Editorial scoring synthesised from official Shopify dev docs and public plugin reviews.

Pick Your Method in 5 Questions

If your situation doesn't obviously match a method above, run the quiz. It weights the answers that drive most regret in WP+Shopify projects: underestimating dev cost, picking a method that breaks SEO, or paying for flexibility you'll never use.

Method 1: Sell on WordPress Plugin (Recommended Default)

Released in October 2025, the Shopify plugin for WordPress (also branded "Sell on WordPress") is Shopify's first-party answer to the integration question. It pairs a Shopify sales channel (installed in your Shopify admin) with a free WordPress plugin (installed in your WP admin). Once both are connected, Gutenberg gains three new blocks — Single Product, Product List, and Collection — and you can drop Shopify products anywhere in WordPress.

Critically, the markup is server-rendered. Google sees real HTML for product titles, prices, images, and descriptions, complete with Product schema. That makes Sell on WordPress the only zero-code method that actually preserves product-page SEO on your WP domain.

Setup in Six Steps

Method 2: Shopify Buy Button (Single Embeds)

The Buy Button channel predates Sell on WordPress by years. It's still useful — particularly when you want a single product or a small collection embedded inline within an article, not as a dedicated shop page. The setup generates a self-contained <script> tag you paste into any HTML, including a WordPress Custom HTML block, a page builder element, or even a third-party email tool.

Performance is solid: the BuyButton.js library plus its JS Buy SDK dependency load asynchronously (roughly 80 KB gzipped combined) and the card renders after first paint. Async loading means it doesn't block your LCP. The downside is SEO — because the product is JS-injected post-load, search engines see an empty placeholder. Use Buy Button for conversion, not for organic discovery.

Setup in Five Steps

The generated code looks roughly like this (truncated):

<div id="product-component-XXXXX"></div>
<script type="text/javascript">
  (function () {
    var scriptURL = 'https://sdks.shopifycdn.com/buy-button/latest/buy-button-storefront.min.js';
    if (window.ShopifyBuy) {
      ShopifyBuyInit();
    } else {
      loadScript();
    }
    function loadScript() {
      var script = document.createElement('script');
      script.async = true;
      script.src = scriptURL;
      (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(script);
      script.onload = ShopifyBuyInit;
    }
    function ShopifyBuyInit() {
      var client = ShopifyBuy.buildClient({
        domain: 'yourstore.myshopify.com',
        storefrontAccessToken: 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
      });
      ShopifyBuy.UI.onReady(client).then(function (ui) {
        ui.createComponent('product', {
          id: '1234567890',
          node: document.getElementById('product-component-XXXXX'),
          // ...options
        });
      });
    }
  })();
</script>

Method 3: ShopWP Plugin (Shortcodes & Power Users)

ShopWP (formerly WP Shopify) is the most established third-party Shopify-WordPress plugin, in active development since 2017. Its appeal is breadth: you get shortcodes for every page builder, dynamic collection pages with sorting and filtering, customer accounts inside WordPress, and template overrides for every product element.

The trade-off is performance. ShopWP renders heavier React components than the Sell on WordPress plugin, and its initial bundle is the largest of any method covered here. Median LCP impact in our testing was ~410 ms — three times the Sell on WordPress plugin. Mitigate this with WP Rocket or similar caching, and lazy-load product grids below the fold.

Setup in Five Steps

Method 4: Headless via Storefront API (Maximum Control)

The headless route is what serious dev teams pick when none of the above is flexible enough. Instead of relying on a plugin to render product cards, you write your own queries against the Storefront API and inject the data into WordPress templates (PHP), a Gutenberg block (React), or a separate front-end framework like Next.js that renders WordPress + Shopify together.

Why pay for that complexity? Three reasons: complete control over markup (good for unusual layouts and accessibility audits), server-side rendering on whatever stack you choose (better LCP than any plugin), and the ability to mix Shopify product data with WordPress custom fields, ACF data, or external APIs in the same template.

Setup in Six Steps

A minimal GraphQL query looks like this:

query ProductByHandle($handle: String!) {
  product(handle: $handle) {
    id
    title
    descriptionHtml
    priceRange {
      minVariantPrice { amount currencyCode }
    }
    images(first: 4) {
      edges { node { url altText } }
    }
    variants(first: 10) {
      edges {
        node {
          id title availableForSale
          price { amount currencyCode }
        }
      }
    }
  }
}

Method 5: Subdomain Hybrid (Two Apps, One Brand)

The subdomain hybrid is technically not an integration — it's a deliberate split. Your WordPress site at yourdomain.com handles content, blog, and SEO. Your Shopify store at shop.yourdomain.com is a full Shopify Online Store 2.0 with theme, collections, search, and checkout. The two share a brand and navigation but render entirely separately.

Why pick this over the integration methods? Because you avoid every plugin's limitations. You get full Shopify SEO (collections, faceted search, blog if you also run one in Shopify), full theme freedom, and zero performance overhead on either side. The cost is brand fragmentation: visitors notice when shop.brand.com looks slightly different from brand.com, and analytics requires cross-domain tracking.

Setup in Four Steps

Video Walkthrough: Sell on WordPress in Action

For a visual walkthrough of the official Sell on WordPress plugin from install to first sale, this 12-minute tutorial covers exactly what we describe in Method 1:

Cost Calculator: What You'll Actually Pay

The interactive calculator below estimates your monthly Shopify costs based on revenue, plan, and order volume. Add your WordPress hosting (typically $5–$30/mo for managed) and the one-time cost of your chosen integration method to get total Year-1 spend.

For a stacked view of Year-1 TCO across all five methods at the same revenue level:

Assumes Basic plan ($39/mo), $15/mo managed WP hosting, and one-time dev costs. Excludes transaction fees and ad spend.

Performance Impact on Core Web Vitals

Adding a commerce layer to WordPress always carries some performance cost. The numbers below come from lab measurements with WebPageTest on a 4G profile, averaging three reference WordPress themes (Astra, Kadence, GeneratePress) loading a single product card above the fold.

Lab-tested median LCP impact, 4G throttling, mobile viewport. Lower is better.

Three concrete things to do regardless of method:

• Lazy-load product blocks below the fold. If a product appears in the second viewport or lower, defer its render until the user scrolls. Sell on WordPress supports this in block settings; Buy Button needs the loading="lazy" pattern.
• Use a managed WordPress host with edge caching. Kinsta, WP Engine, and Cloudways all serve cached HTML from the edge. This eliminates the dynamic PHP cost so Shopify's contribution becomes the only variable.
• Cache Storefront API responses. If you go headless, cache GraphQL responses for 5–15 minutes via WordPress transients or your CDN. A second request for the same product should never hit Shopify.

SEO: Don't Lose the Traffic You Already Earned

WordPress SEO is its own discipline — you have Yoast, Rank Math, schema plugins, and a decade of practice. None of that goes away when you add Shopify. What changes is product-page indexability, and the answer depends entirely on the integration method.

Tax, Shipping & Checkout: Who Owns What

This split is non-negotiable because Shopify's checkout is a closed system. You can apply your branding via Checkout Extensibility, you can add scripts on Shopify Plus, but you cannot embed checkout in a WordPress iframe or process payments on the WP server. PCI compliance and chargeback liability stay with Shopify, which is exactly what you want.

B2B, Subscriptions, Memberships and Multi-Currency

WordPress sites rarely sell only simple physical products. If your catalogue includes any of the four models below, the default Sell on WordPress plugin is not always enough. Here is how each maps to the integration methods covered above.

For B2B specifically, do not try to retrofit B2B logic onto a Sell on WordPress block. Shopify Plus B2B brings company accounts, customer-specific catalogs, NET payment terms, and quote requests — none of which surface through the WordPress plugin. Either use the subdomain hybrid (B2B portal at b2b.yourdomain.com) or build a headless front-end that queries the Storefront API with company-specific authentication.

Page Builders: Elementor, Divi, Bricks, Beaver Builder

Most WordPress sites in 2026 still run on a page builder rather than pure Gutenberg. Compatibility with your editor of choice can be the deciding factor between two otherwise equal methods.

Migrating from WooCommerce to a WordPress + Shopify Setup

This is the most common entry path into WordPress + Shopify integration: a site that started on WooCommerce, hit performance or feature limits, and now wants Shopify's checkout while keeping the WordPress brand and SEO equity. The migration itself is well-trodden, but the order of operations matters.

Common Pitfalls and How to Avoid Them

Eight failure modes that come up over and over in WP+Shopify projects, with the fix for each:

Troubleshooting: When the Integration Breaks

Before contacting support or rebuilding the integration, walk this checklist. It catches roughly 90% of post-launch issues that look like bugs but are actually configuration drift.

Stay Hybrid or Migrate Entirely?

The Bottom Line

For 80% of WordPress sites adding Shopify in 2026, the right answer is the Sell on WordPress plugin. It's free, it's official, it gives you SEO, and it solves the integration in under an hour. Start there. Upgrade only when you hit a specific limitation that another method solves. For non-WordPress sites following the same playbook, our add Shopify to an existing website guide covers Buy Button and Starter-plan setups.

Whichever method you pick, the integration will only ever be as good as the operational discipline behind it. Cache aggressively, monitor checkout abandonment after the redirect, and revisit the choice every six months. Methods that fit at $5K/month often break at $50K — that's a feature of growth, not a flaw of the integration.

Frequently Asked Questions