PaperTube WordPress Migration — SEO Foundation

Overview

PaperTube currently operates on Shopify. As the client has expressed interest in expanding into SEO, the existing Shopify setup presents a technical ceiling that limits what can be achieved. A migration to WordPress is the recommended path — positioned not as a redesign, but as the necessary technical foundation for the SEO work PaperTube wants to pursue.

This article captures the business case, client context, and pitch positioning developed internally before the client call in early 2026.

See also: ^[1] | ^[2]

The Problem: Shopify as an SEO Constraint

Shopify is a capable e-commerce platform, but its architecture imposes meaningful limitations on advanced SEO work:

• Limited control over site structure and URL schema — Shopify enforces certain URL patterns (e.g., /collections/, /products/) that cannot be overridden.
• Restricted templating and page-level customization — Technical SEO often requires granular control over metadata, schema markup, and page rendering that Shopify's theme system constrains.
• Plugin/app ecosystem gaps — WordPress with plugins like Yoast or Rank Math provides a more mature, flexible SEO toolchain than Shopify's native or third-party equivalents.
• Landing page friction — Jeff (developer) has been struggling to build landing pages within the Shopify environment, indicating the platform is already creating delivery friction on current work.

"I just don't think we're going to be able to help him very much with Shopify, like how they've got it set up."
— Mark Hope, internal sync

The Opportunity: WordPress as the Foundation

WordPress gives the team — and PaperTube — the flexibility needed to execute a serious SEO program:

• Full control over site architecture, internal linking, and URL structure
• Robust SEO plugin support (Yoast, Rank Math, etc.)
• Easier landing page creation and CRO iteration
• Better integration with content marketing workflows

The pitch frames WordPress not as an optional upgrade, but as a prerequisite for the SEO outcomes Parag has already said he wants.

Client Context

• Client: PaperTube (owner: Parag)
• Current platform: Shopify
• Stated goal: Improve SEO once current campaigns are running
• Current pain point: Landing page development is slow and constrained within Shopify
• Client disposition: Technical in mindset; responds better to concrete, reasoned arguments than soft sells. Karly noted she lacks the technical depth to make the case compellingly — Mark is better positioned to lead this conversation.

Pitch Positioning

Lead with the client's own goal. Parag has already said he wants SEO help. The pitch should open by affirming that goal, then explain why the current platform limits what's achievable — and what WordPress unlocks.

Frame it as infrastructure, not a redesign. Avoid language that sounds like "we want to redo your website." Instead: "To get the SEO results you're after, we need the right technical foundation underneath."

Sequence matters. The migration should be positioned as the logical next step after the current ABM campaigns are running — not a distraction from them.

Mark leads the technical portion. Given the need for technical credibility on this topic, Mark should take point on this part of the client call. Karly can set up the conversation and hand off.

Action Items (as of internal sync)

• [ ] Mark — Lead the WordPress website pitch on the upcoming PaperTube call
• [ ] Mark — Prepare technical talking points on Shopify SEO limitations vs. WordPress capabilities
• [ ] Karly — Set up the conversation and transition to Mark for the technical pitch

Related

• ^[1]
• ^[2]
• ^[3]
• ^[4]