The Global Economics: Migrating a London Finance Publication from WordPress to Payload CMS & Next.js

Engagement: Platform migration & rebuild — WordPress → Payload CMS + Next.js Industry: Business & finance media / publishing Stack: Payload CMS (headless) · Next.js on Vercel · schema.org · llms.txt · Google News sitemap · RSS Result: A faster, scalable publication engineered to rank in search and be cited by AI engines

At a glance

The Global Economics is a London-based business and finance publication — roughly 2,800 articles of original journalism, a subscription print magazine, and a global awards programme, read by boards and the C-suite. Its journalism was first-class; its platform was holding it back. Years on WordPress, plus an ever-growing stack of plugins, had left the site heavy and slow — the wrong foundation for a publisher whose business depends on speed, reach and discoverability.

We migrated the entire publication onto a modern, headless publishing stack: Payload CMS for a fully-owned content model and a custom Next.js front end on Vercel's edge — then engineered it to be found by both search engines and AI answer engines.

The client

The Global Economics Limited is an established, London-based online and print news magazine, providing thoughtful, detailed analysis of the issues shaping business across the major economies of the world. Its coverage spans commercial and investment banking, wealth management and advisory — alongside the other engines of the economy: insurance, real estate, technology, energy and infrastructure.

Its audience is specific and demanding. As a subscription-based publication, its readership comprises C-level executives, boards of directors and the key decision-makers of enterprises large and small — the people who, in the publication's own words, need the story behind the numbers. The brand runs across three surfaces:

• A digital newsroom organised into clear sectors — Banking (central, commercial, digital, Islamic, private), Non-Banking, Markets, Infrastructure, Lifestyle and Feature.
• A print and digital magazine — a bi-monthly edition, available in print and as a digital flip-book, that distils the trends, deals and decisions defining global finance into a single considered read.
• The Global Economics Awards — a prestigious annual programme recognising standout performers across Finance, Banking, Real Estate, Insurance and Energy, open to organisations worldwide.

For a brand with this reach and this audience, the website isn't a brochure — it is the product. And the product had outgrown its platform.

The starting point: good journalism on a heavy platform

The Global Economics had been built, like most publishers, on WordPress. For years that was a reasonable choice. But a news operation is one of the most demanding things you can ask a CMS to do — thousands of articles, constant publishing, heavy media, complex taxonomies — and over time the familiar WordPress pattern had set in:

• Plugin sprawl. Every capability — SEO, caching, media, security, layout, forms — had been bolted on as another plugin. Each one adds code, database queries and its own update cycle. Stacked together across a large site, they make pages heavy and the whole system fragile.
• Performance drag at scale. With roughly 2,800 articles and rich imagery, the plugin-laden WordPress front end was doing far too much work on every request. For a publisher, slow pages are not a cosmetic problem — they cost readers, ad viewability, and search rankings directly.
• A maintenance and security burden. A public WordPress install with many plugins is a large, constantly-moving attack surface that needs continual patching — a real liability for a brand whose credibility is the asset.
• A ceiling on optimisation. Getting a WordPress site genuinely fast, cleanly structured, and ready for modern AI-search discovery means fighting the platform's defaults at every turn. The publication had hit that ceiling.

The journalism deserved better infrastructure. The brief to Aapta Solutions was to migrate the publication onto a platform that is fast by default, that the team fully controls, and that is engineered for how audiences — and now AI engines — actually discover content.

The decision: a headless build on Payload CMS + Next.js

We did not move the site onto a different page builder or a different WordPress theme. For a publication at this scale, the right answer is a headless architecture — separating the content from the presentation — so each side can be the best version of itself.

• Payload CMS became the content layer: a modern, developer-first headless CMS where the entire content model — articles, sections, authors, the magazine, the awards — is defined explicitly and owned by the publication, with no plugin ecosystem to manage. The editorial team gets a clean, purpose-built admin; the business gets a system it controls outright.
• Next.js on Vercel became the presentation layer: a custom-designed, component-based front end that is server-prerendered and edge-cached, so pages are assembled ahead of time and served from close to the reader. No theme, no plugin runtime — just a lean application built for this publication.

This split is the heart of the rebuild. It removes the WordPress bloat, gives the team a content model that matches how a finance publication actually works, and puts a fast, fully-custom front end in front of the reader — one we can optimise without limit for speed, search and AI discovery.

The migration: moving ~2,800 articles without losing the archive

A publisher's archive is its equity. Roughly 2,800 articles represent years of reporting, accumulated search authority, and inbound links from across the web. The migration's first rule was simple: lose none of it.

That meant treating the move as a content-engineering project, not a copy-paste:

• Modelling the content properly in Payload — articles, sectors and sub-sectors, authors, media and the magazine mapped into explicit, structured fields, so the archive becomes clean, queryable data rather than a tangle of theme-specific markup.
• Preserving the things search engines remember — URL structure, titles, metadata and images carried across so that the authority built up over years transfers to the new platform intact, with redirects where paths needed to change.
• Rebuilding discovery infrastructure from the ground up — sitemaps, feeds, structured data and an AI-readiness layer (below), designed in rather than bolted on.

The outcome is an archive that is not just preserved but upgraded — the same journalism, now sitting on a foundation that makes it faster to serve and easier for both people and machines to find.

Faster and lighter — by construction

The old WordPress front end did an enormous amount of work on every page load. The new one does very little, because most of the work already happened before the reader arrived.

On the Next.js build, pages are prerendered and cached at Vercel's edge, so a reader opening an article is served a ready-made page from a nearby location rather than waiting on a database and a stack of plugins. The front end is a lean, custom application — there is no theme to parse and no plugin runtime to execute. For a global readership opening stories on everything from office desktops to phones on the move, that speed is felt on every visit, and it feeds directly into the two things a publisher cares about: reader retention and search ranking. (The same Core Web Vitals discipline underpins every build we ship — see our note on website speed optimisation.)

Engineered for AI search (GEO & AEO)

This is where the rebuild goes beyond a normal redesign — and where it matters most for a publisher today. A growing share of the C-suite now starts its research not in a search box but in an AI assistant. If ChatGPT, Gemini, Perplexity or Google's AI answers summarise a topic in global finance, The Global Economics should be among the sources they read and cite. We built the site to make that as easy as possible for the engines — an approach we set out in full in our Generative Engine Optimization (GEO) 2026 guide.

Concretely, the new site ships with:

• An llms.txt file — a concise, machine-readable guide, served at the site root, that tells AI models what the publication is, how its coverage is organised, and where to find its sections and latest articles. It's the emerging standard for helping LLMs understand a site, and most publishers don't have one.
• Rich schema.org structured data — the site describes itself to machines as a real publication: a WebSite with a SearchAction (which also powers a Google sitelinks search box), ItemList and CollectionPage markup on its sections, Article and ImageObject data on its stories. This is the difference between an engine guessing what a page is and being told.
• A Google News sitemap alongside the standard XML sitemap, plus RSS feeds — so both news crawlers and aggregators can discover new reporting within minutes of publishing.
• Clean, semantic, server-rendered HTML — because an AI crawler reads the markup, content that is present and well-structured in the server response (not assembled later by scripts) is content an engine can actually use.

Put together, these make the publication legible to machines — not as an afterthought, but as a core design goal. You can measure any site's AI-readiness the same way we do, with our free GEO readiness scanner.

Engineered for search engines, too

The AI layer sits on top of fundamentals that are stronger than a plugin-driven WordPress site could reach:

• A Google News-ready sitemap so fresh reporting is surfaced quickly in Google News and Top Stories — essential for a news publisher.
• Structured, crawlable sections (Banking, Non-Banking, Markets, Infrastructure, Lifestyle, Feature) that map cleanly to how readers and search engines think about the subject.
• Fast, prerendered pages that satisfy Core Web Vitals, which Google treats as a ranking input.
• Clean canonical URLs, metadata and structured data on every article, applied consistently by the system rather than left to a human to remember per post.

Built to scale with the newsroom

Because the content model lives in Payload and the front end is componentised in Next.js, the publication can grow without the platform fighting back. New sections, new article formats, the magazine's flip-book, the awards programme, reader accounts and alerts all sit within one coherent, owned system — not a patchwork of plugins each going its own way. The next 2,800 articles will sit on the same fast foundation as the first.

Outcome — before and after

The publication moved from first-rate journalism on a platform that was slowing it down, to the same journalism on infrastructure engineered for speed, discovery and scale.

The takeaway

For a publisher, the CMS is a strategic decision, not an IT detail. WordPress will get you started, but at the scale of a real newsroom — thousands of articles, constant publishing, an audience that expects speed and engines that now read your markup to decide whether to cite you — its plugin-driven model becomes the ceiling. A headless build on Payload CMS and Next.js lifts that ceiling: it turns a heavy archive into a fast, owned, future-ready asset that competes for both the Google result and the AI citation.

That is the migration we delivered for The Global Economics — and the same modern-stack thinking runs through our rebuilds for The Platos School, Arun Sharma Guruji and Epic Gymnastics Academy.

If your publication or content business has outgrown WordPress, let's talk about a migration, or get a tailored quote.

Frequently asked questions

What platform is the new Global Economics website built on?

It's a headless build: Payload CMS manages the content (articles, sections, authors, the magazine and awards), and a custom Next.js application on Vercel renders the front end — server-prerendered and edge-cached for speed. This replaced a WordPress site that had become heavy and slow under a large stack of plugins.

Why move a publisher off WordPress?

WordPress is a fine starting point, but a news operation pushes it hard: thousands of articles, constant publishing, heavy media and complex taxonomies. Over time the plugin stack that powers SEO, caching, security and layout makes the site slow, fragile and expensive to maintain. A headless architecture removes that bloat and gives the publication a content model it fully owns and a front end with no performance ceiling.

Why Payload CMS specifically?

Payload is a modern, developer-first headless CMS where the entire content model is defined explicitly in code and owned by the publication — no third-party plugin ecosystem to manage. That gives The Global Economics a clean, purpose-built editing experience that matches how a finance publication actually works, and complete control over its own data.

Did the migration affect SEO or the article archive?

Protecting the archive was the first priority. Roughly 2,800 articles — and the search authority and inbound links they carry — were migrated with their URL structure, titles, metadata and images preserved, and redirects applied where paths changed. The goal of the migration is to carry years of accumulated authority onto the faster platform intact, not to start over.

How is the site optimised for AI search?

In several concrete ways: it serves an llms.txt file that tells AI models what the publication is and how its coverage is organised; it ships rich schema.org structured data (WebSite, SearchAction, ItemList, CollectionPage, Article, ImageObject); and it exposes clean, server-rendered, semantic HTML that AI crawlers can actually read. Together these make the journalism easy for engines like ChatGPT, Gemini and Perplexity to understand and cite.

Is the new site faster than the old WordPress one?

Yes, by design. Pages are prerendered and served from Vercel's edge, and the front end is a lean custom application with no theme or plugin runtime to execute on each request — so readers get a ready-made page from a nearby location instead of waiting on a database and a plugin stack.

Does the new platform support the print magazine and the awards programme?

Yes. The headless content model covers the full brand — the digital newsroom, the bi-monthly print-and-digital magazine, and The Global Economics Awards — within one coherent system the team owns, rather than a set of disconnected plugins.

Can you migrate my WordPress site to a headless stack?

Yes — moving a content-heavy WordPress site to a headless Payload CMS + Next.js build is exactly this kind of engagement. We handle the content modelling, the migration with its redirects and SEO preservation, the custom front end, and the search and AI-discovery layer. Get a tailored quote or read about an ongoing technology partnership.

Project credits

Built by Aapta Solutions · Founder: Dharmendra Asimi · Bengaluru & Hyderabad, India

Visit the live site: www.theglobaleconomics.com

Thinking about moving off WordPress? Talk to us or run a free GEO readiness scan on your current site to see where you stand today.