Migrating ~1,000 articles without SEO loss
Every article had accumulated search equity over years. Migrating meant URL mapping, redirect planning, metadata preservation, and structured content migration with zero tolerance for 404s or ranking drops.
Case study - WordStream - completed 2023
WordStream’s PPC platform, migrated without SEO loss.
WordStream is one of the most-trafficked PPC education platforms on the web: over a thousand articles, a suite of marketing tools, and an editorial team that needed an admin they could actually use. The platform had outgrown its stack. RTW was brought in to migrate the entire property to WordPress, redesign the frontend, and build the admin tooling layer the team had been working around for years.
Completed - 2023
wordstream.com ->
SAAS MARKETING - 2023
CASE STUDY - COMPLETED
Articles migrated
SEO-safe
~1,000
Every article moved to WordPress with URL mapping and redirect rules verified before cutover.
Platform scope
full rebuild
full redesign
Homepage, blog, PPC tools, landing pages - the entire WordStream web presence rebuilt end-to-end.
Custom admin tools
editorial efficiency
custom built
Mega menu, category filtering, content widgets - none of it existed before the engagement.
Delivery timeline
completed
2022-2023
Phased migration and build. Every phase signed off before the next began.
// 01 - the brief
What the work required.
WordStream built its reputation as a reference destination for PPC marketers: a content library of over a thousand articles covering Google Ads, paid search, and digital marketing, backed by free tools that drove organic traffic and lead generation. The problem was the platform running underneath it. A legacy stack with an admin interface that required workarounds for basic editorial tasks, limited flexibility for promoting the marketing tools, and a blog experience that made content hard to find.
RTW was brought in to do three things at once: migrate the full content library to WordPress without losing page search ranking, redesign the frontend experience for readers, and build the admin tooling the editorial and marketing teams had been working around for years. The migration alone - roughly 1,000 articles, years of accumulated SEO equity, landing pages, and tool integrations - required careful URL mapping, redirect planning, and content structure decisions before new code was written.
The result is a platform the editorial team can actually manage. A custom WordPress build with a mega menu, category-based blog filtering, and content promotion widgets designed around how WordStream's marketing team actually works. The blog redesign improved content discoverability. PPC tool pages were rebuilt around clear conversion paths, and the frontend was brought up to the standard readers expect from a modern marketing platform.
// 02 - the challenge
What could not break.
Rebuilding the platform UX on a legacy foundation
The frontend was outdated in design and technology. Rebuilding it meant balancing SEO, readability, conversion paths, and development velocity alongside the active migration.
Improving admin workflows for a non-technical editorial team
The existing admin required daily workarounds. The new interface had to make content creation, tool promotion, and category management faster against how the team actually worked.
Enhancing content discoverability across 1,000+ articles
Readers needed to find articles by topic, intent, and format without paginating through results. A category-based filtering system had to be designed from scratch.
Redesigning marketing tool integration within content
PPC tools were embedded in the content experience. The redesign had to improve conversion paths without disrupting editorial flow or making tool promotion feel bolted on.
Ensuring SEO integrity across the entire migration
Search visibility was the platform primary traffic driver. Any missing redirect, changed URL pattern, or stripped metadata field was a direct revenue event.
// 03 - approach
How we handled the migration.
A phased migration built around the one thing that could not be undone.
The stakes of a content migration are asymmetric. You can redesign a page. You can improve an admin tool. You cannot unlose organic traffic. The engagement was structured around that reality: SEO mapping first, migration second, redesign third, admin tooling fourth.
A
SEO-safe migration
Every article URL was mapped before content moved, and redirect chains were confirmed from old addresses to new destinations.
B
Modular WordPress development
The custom theme was built as a component system so new widgets and page types could be added without modifying core theme logic.
C
UX-first design approach
Design decisions were reviewed against actual editorial and marketing workflows, not abstract admin conventions.
D
Close stakeholder collaboration
Editorial, marketing, and tech teams reviewed each phase before the next began. No migration batch ran without content review.
PHASE // 01
Discovery
Platform audit, SEO mapping, and stakeholder alignment
Audited content structure, URL patterns, SEO performance, and admin workflows. Mapped every article URL to its new destination before development began.
content audit
URL mapping
redirect plan
workflow analysis
PHASE // 02
Architecture
WordPress setup, custom theme planning, and content modeling
Set up the WordPress environment, planned the custom theme architecture, and defined article types, taxonomy structure, PPC tool templates, and admin capability requirements.
WP environment
theme architecture
content model
taxonomy structure
PHASE // 03
Migration
~1,000 articles migrated, SEO-safe, content verified
Ran migration in batches with redirect verification at each stage. Content, metadata, URLs, and internal links were checked before each batch was cleared.
content migration
redirect validation
metadata check
link audit
PHASE // 04
Frontend
Frontend redesign, responsive build, and PPC tool integration
Built the new frontend across homepage, blog, PPC tool pages, and category pages, with improved typography, responsive layouts, and contextual tool CTAs.
homepage
blog redesign
tool pages
scroll effects
PHASE // 05
Admin tooling
Custom WordPress admin, mega menu, filtering system, and content widgets
Built the admin experience the editorial team needed: mega menu controls, category-based blog filtering, and content promotion widgets configurable without developer support.
mega menu
filtering system
promo widgets
admin UX
PHASE // 06
QA + Launch
Cross-team QA, SEO verification, redirect audit, and launch
Joint QA with WordStream teams, full redirect audit, SEO metadata verification across the article library, performance testing, and launch with no P1 incidents.
QA pass
redirect audit
SEO check
performance test / launch
// 04 - stack
The exact tools we used.
Backend
[01]- PHP language
- WordPress CMS
- Custom themes built from scratch
- Custom plugins extensibility
- Radix UI primitives
Frontend
[02]- HTML5 / CSS3 markup
- JavaScript interactions
- Scroll effects engagement
- Responsive layouts mobile-first
CMS tools
[03]- Custom admin UI editorial
- Mega menu navigation
- Content widgets promotion
- Capability design workflow
Content
[04]- Migration scripts custom-built
- ~1,000 articles migrated
- SEO mapping URL plan
- Redirect rules verified
Design
[05]- Adobe XD design tool
- UX audit workflow analysis
- Wireframes admin + frontend
- Component system shared UI
QA / Ops
[06]- Redirect validation every URL
- SEO verification metadata
- Phased rollout batch delivery
- Launch monitoring live ops
// 05 - what we built
Three things worth showing.
Feature 01 / 03 - scale + SEO
Content migration system, ~1,000 articles with zero SEO loss.
The migration was the highest-stakes part of the engagement. WordStream traffic depended heavily on organic search, so every URL was mapped before migration began, every article moved in verified batches, and every redirect was tested before the corresponding content went live.
- ~1,000 articles migrated to WordPress with content structure, metadata, and internal links preserved.
- Every source URL mapped to its destination before migration ran.
- Migration executed in batches with redirect validation at each stage.
- SEO metadata checked and confirmed for every article in the migration set.
MIGRATION - ~1,000 ARTICLES
Feature 02 / 03 - discovery
Advanced blog filtering, built for 1,000+ articles.
A content library of that size needs a filtering layer or it becomes effectively unsearchable. RTW built category-based filtering so readers could narrow by topic, channel, and content type without leaving the blog index.
- Category-based filtering system built from scratch for a 1,000+ article content library.
- Readers filter by topic, PPC channel, and content type without leaving the blog index.
- Filter interactions are fast and stateful for longer research sessions.
- Editorial team assigns categories and tags from the custom admin without developer involvement.
BLOG - CATEGORY FILTERING
Feature 03 / 03 - admin tooling
A custom admin experience shaped around the team’s workflow.
The editorial team interacted with the admin every day. RTW built a custom WordPress admin experience from workflow analysis: mapping what editorial and marketing actually needed to do and designing tooling around those tasks.
- Custom mega menu for editorial navigation across content and tool pages.
- Content promotion widgets let marketing feature tools and resources contextually within articles.
- Admin capability design driven by real editorial workflows.
- New content types and promotion modules can be added without modifying the core theme.
ADMIN - CUSTOM TOOLS
// 07 - gallery
What it looks like in the wild.
01 / Blog homepage - redesigned content discovery
02 / Category filtering - 1,000+ articles organized
03 / PPC tool pages - improved conversion paths
04 / Custom admin - mega menu + content widgets
05 / Mobile layout - responsive blog experience
06 / Article page - redesigned reading experience
// large-scale platform migration?
We migrate platforms that cannot afford to break.
A thousand articles, years of SEO equity, a team that uses the admin every day: you do not get a second chance at the cutover. If your platform has outgrown what it is running on, we would like to hear about it.
