Newspaper Theme to Next.js: Moving a News Archive Without Losing Its Address Book

Where tagDiv keeps the front page, and where it keeps the news

A Newspaper site splits cleanly in two, which is the best news in this guide. The design lives in tagDiv Composer and the tagDiv Cloud Library: homepage zones, header and footer templates, and the single post, category, author, tag, search and 404 templates assigned across the site. The journalism, in most installs, lives in ordinary WordPress posts that those templates wrap.

Composer saves its layouts as shortcodes. A Composer page body is a chain like [tdc_zone], [vc_row] and [vc_column] wrapped around the theme's own block shortcodes. tagDiv's forum shows what happens when Composer stops working: the page prints those tags as naked text. So the templates get redrawn in code, and the articles move as data.

• Composer pages: homepage, section fronts and landing pages. Screenshot at three widths and rebuild as layouts.
• Cloud Library templates: list which template is assigned to posts, categories, authors and tags, including per-category overrides.
• Articles: export as data. Check a sample for Composer or WPBakery shortcodes pasted into the body over the years.
• Bundled extras: tagDiv Mobile Theme, Opt-in Builder, Newsletter and any Revolution Slider or WPBakery content each need their own decision.

If Composer will not open at all, our tagDiv Composer not loading guide gets the editor back long enough to record what the templates do, and the Newspaper repair hub covers the other common faults.

Years of daily posts need an import job, not an export button

The WordPress export tool writes one XML file. On a publication with years of daily posts, that file tends to time out or arrive incomplete. We pull the archive through the REST API or a copy of the database instead, in batches, and count as we go.

Cleaning is where the time goes. Old posts carry gallery shortcodes, embedded social posts, iframes from video hosts and the occasional [vc_row] pasted in by an editor years ago. Each pattern gets a rule, the rule runs across the archive, and we spot-check a random sample of articles side by side before anyone signs off. Our WordPress blog migration guide covers the cleaning rules in depth.

Section fronts, tag pages and bylines that keep their addresses

Newspaper does not invent its own URL scheme. Your article addresses follow the Permalinks setting in WordPress, whether that is /%postname%/, a date pattern or the category in the path. Next.js routes can mirror any of them, so the default plan is that every article keeps its URL exactly. The URL structure guide shows how routes are matched to permalinks.

• Categories: /category/news/local/ style paths with nesting intact. These are your section fronts and often your strongest pages after the homepage.
• Tags: /tag/ pages number in the thousands on many news sites. Keep the ones with search clicks; merge or redirect thin ones in planned batches, never all at once.
• Authors: /author/name/ pages carry years of bylines and help readers trust a story. Keep every one, including former staff.
• Pagination: /page/2/ and deeper on every archive. Paginated routes have to exist, or crawlers lose the path to older stories.
• Date archives and feeds: keep or redirect date URLs, and publish RSS at the same /feed/ addresses so aggregators and subscribers keep receiving stories.

Anything that does change gets a single 301 hop, tested in bulk before launch. The mechanics are in our redirects guide and the ranking checklist is in migrating without losing SEO.

Ad slots, redrawn so the story stops jumping

Newspaper's ad system is a list of boxes under Newspaper > Theme Panel > Ads: a header ad, sidebar ad, article top, inline and bottom ads, five custom ad spots placed with Composer or the tagDiv Ad Box widget, and an inline option that drops an ad after a chosen paragraph. Copy every snippet out, with its device settings, before anything is switched off.

In the new build each slot becomes a component with its height reserved per screen size, so a late ad fills space that was already waiting instead of shoving the headline down. Inline ads are inserted after paragraph N at render time, the same rule your editors know. The ads.txt file has to sit at the root of the new site from launch day, or programmatic buyers that check it may treat your inventory as unauthorized. Our pages on layout shift and CLS in Next.js explain why reserved space matters.

An ad that arrives late should land in an empty seat, not on top of the story.

The third option

Athena CMS, with AI agents on staff.

Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.

• PPicassoImages
• AApolloSite analysis
• AAresCompetitor watch
• PPrometheusContent holes
• AAtlasPage depth and structure
• DDelphiAI search visibility

ZDAOAand 12 more agents. Two come with Athena; the rest are monthly add-ons.

Meet the agentsTake the Athena tour

PPicassoWeekly · ImagesAApolloWeekly · Site analysis

AMP pages and the separate Mobile Theme

Newspaper bundles the tagDiv Mobile Theme, a lighter layout for phone visitors, and tagDiv's documentation explains how to pair it with an AMP plugin. Not every site did. Check Search Console and your plugin list for an AMP plugin and for indexed /amp/ or ?amp addresses.

• AMP found: redirect each AMP URL to its canonical article. The responsive Next.js page replaces it.
• Mobile Theme settings: note what it hid or simplified on phones, because readers and editors are used to that version.
• Menus: mobile menu items configured separately get folded into one responsive navigation. If the mobile menu has been failing already, say which behavior you want kept.

One responsive build means one set of templates to maintain instead of a desktop theme, a mobile theme and an AMP layer that each update on their own schedule.

A decade of uploads, sorted by month

A news site's media library is the largest thing it owns. WordPress stores uploads in year and month folders and makes several resized copies of each one, and every image size a theme or plugin registers adds another. Open one month's folder and count the files per original; that ratio tells you how much of the library is copies.

We move originals only. next/image builds the sizes each layout needs, in modern formats, as readers request them. Old image URLs are kept reachable or redirected, because image search traffic and syndication partners still link to them. Missing alt text, common on wire photos and quick posts, gets filled in as part of the move. Details are in migrating WordPress images to Next.js, and the speed side is covered on our Newspaper speed page.

The cutover plan for a newsroom that never stops publishing

1. 1

   Crawl and benchmark

   Export every URL with status codes, plus Search Console clicks by page. Record article counts by category, tag and author as the baseline.

2. 2

   Record templates and ads

   Screenshot each Composer page and Cloud Library template at three widths, and copy every ad snippet from the Theme Panel.

3. 3

   Pull the archive in batches

   Extract posts, terms, authors, comments and media through the API or a database copy, logging counts for each batch.

4. 4

   Clean the content

   Run shortcode and embed rules across the archive, then compare a random sample of articles side by side.

5. 5

   Build the layouts

   Homepage, section front, article, author and tag templates become Next.js components, with ad slots sized in advance.

6. 6

   Map every URL

   Match articles, archives, pagination, feeds, images and AMP addresses. Test the full redirect list on staging.

7. 7

   Run a delta sync

   On launch day, import stories published since the main export so no article is lost in the gap.

8. 8

   Switch and monitor

   Move DNS, submit fresh sitemaps, confirm ads.txt and feeds, and watch crawl errors and traffic by section daily.

What makes a publisher's move longer, and what editors use after

Archive size sets the import time, but the clean-up sets the schedule. These drivers shape the fixed quote we give after a free site audit:

• How many years of posts, and how many shortcode patterns hide inside them.
• The number of Composer pages and Cloud Library templates, including per-category overrides.
• Ad stack complexity: direct-sold slots, header bidding, sponsored post formats.
• Paywall or newsletter subscribers in the Opt-in Builder that need to keep their access.
• Tag pages, author archives and date archives to keep, merge or retire.

See migration timelines and what drives migration cost for the phases.

Editors land in Athena CMS: plain fields for headline, deck, body and byline, a real preview and every version kept. Subscriber areas move to Athena's membership features, with login levels and Stripe subscription billing. Ariadne suggests internal links to older coverage, Iris drafts search titles and social cards, Calliope drafts articles for an editor to approve, and Argus flags broken links and slow pages. A one-person blog happy on its $59 license should stay put; a newsroom fighting update problems and slow article pages is a different story. Our Newspaper vs Next.js comparison weighs the choice, the migration hub collects the guides, and our Next.js rebuild service handles the move.