Migrating more than 1,000 articles while improving search visibility and traffic

The challenge

Counselling Tutor’s library had grown to more than 1,000 articles, supported by pages and commercial content built over years in WPBakery. Readers relied on that material, but its structure no longer made the depth of the library easy to navigate, while editors had to work inside builder-specific layouts.

Rebuilding the site would only be worthwhile if it made the content easier to find, the pages faster to load and everyday publishing less laborious.

Constraints

A migration at this scale carries real risk to search visibility. Every article already had a URL, internal links and a search history, so pages earning traffic had to be identified before anything moved and redirects needed to be ready for launch.

The content also had to move out of WPBakery without leaving editors to repair more than 1,000 articles by hand. Replacing the builder was useful only if the new system gave the team a clearer and more consistent way to work afterwards.

Our approach

We started by auditing the library and looking at how readers found and moved through the material, then rebuilt the topics, navigation and internal links around those journeys. The previous structure reflected the order in which the content happened to be written.

For the migration itself, we created Gutenberg blocks and patterns for the structures that appeared repeatedly, then translated the WPBakery content into them. That made the move repeatable at scale while leaving room to check unusual articles individually.

Technical detail

The migration separated article content from the WPBakery layouts that previously controlled it. Repeated components became native Gutenberg blocks and patterns, so editors can assemble and update pages using WordPress’s standard tools while the design rules remain in the theme.

Removing builder-specific markup and assets reduced the amount of front-end code each article needed, which improved page-speed performance and made future maintenance less dependent on a third-party builder.

Before launch, we mapped existing URLs, redirects, titles, descriptions and internal links, with extra checks around pages already earning traffic. The result was a migration that improved search visibility and traffic instead of treating preservation as the ceiling.