Rebuild Your WordPress Site in Next.js: A Fresh Design That Keeps Its Rankings

A migration copies the house. A rebuild redraws the floor plan.

A straight WordPress to Next.js migration moves your site as it is: same pages, same structure, same design, much faster. That is the right job when the site works and only the platform doesn't. A rebuild starts from a different premise. The site has grown by accretion for years, a page here, a plugin there, a landing page for a promotion that ended long ago, and the structure no longer matches how customers shop for what you sell. Moving that structure into a faster framework only preserves it.

So a rebuild keeps what has value and questions everything else. The test is evidence, not taste: which pages bring visitors from search, which ones turn visitors into calls, and which ones nobody has opened since the day they were published. If you have read our page on replacing WordPress, think of this as the version with a new design and a new content plan attached.

The parts of the old site we protect

• URLs that earn traffic. Pages with search visits and backlinks keep their addresses where possible. We keep your URLs and redirect every old one that has to change.
• Content that ranks or sells. The words on your best pages are edited to fit the new layout, not thrown away. Their wording is part of why they rank.
• Search signals. Titles, descriptions, headings, structured data and internal links are carried over and improved, following our checklist for moving without losing SEO.
• Images and media, moved, renamed sensibly and resized, as described in moving WordPress images.
• Your blog archive, mapped post by post; see moving a WordPress blog to Next.js.
• Tracking and forms. Analytics, conversion tracking and form routing are rebuilt and tested before launch, so leads keep arriving in the same inbox.

Search Console and analytics write this list, not opinions. Before any design work begins, we pull every URL with impressions, clicks or inbound links, and every page that produces calls or form submissions. Anything on that list gets a home in the new site or a redirect to the closest match. Nothing that earns is left to chance.

What gets questioned from scratch

Everything that isn't on the protected list is open for redesign. In practice that is most of what a visitor experiences: how they find things, what each page asks them to do, and how the site looks on the phone in their hand.

This is also where a rebuild beats a redesign on WordPress. A new theme changes how pages look, but the content stays wherever the old builder put it, one shortcode-wrapped layout at a time. Moving to fields means the next redesign, years from now, is a change of templates rather than another page-by-page salvage job.

From the first audit to launch day

1. 1

   Audit and data pull

   Every URL with its traffic, links and conversions, plus every plugin and the job it really does.

2. 2

   Structure and sitemap

   A new page structure, with each old URL mapped to its new home or a redirect, following our notes on URL structure.

3. 3

   Design

   A mockup of key pages for your approval before development starts. Our free mockup is a good first look.

4. 4

   Content model in Athena

   Fields for each page type, shaped around how your business describes what it sells.

5. 5

   Build on a preview address

   The Next.js site is built and reviewed on a private URL while the old site keeps working.

6. 6

   Content and redirects

   Content moved and edited, and the redirect map tested against the full list of old URLs.

7. 7

   Launch and watch

   The switch happens in a quiet window, then Search Console is watched for crawl errors and ranking changes in the weeks after.

Your involvement peaks twice: approving the structure and approving the design. Between those, we need answers more than meetings. Which services matter most, which areas you serve, which questions customers ask on the phone. Those answers shape the content model, and they are the difference between a prettier copy of the old site and a site built around how you actually sell.

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

After launch, your team runs the site

A fresh design is wasted if every change needs a developer. With Athena CMS, your team edits text, images, services, offers and products in plain fields, sees a real preview before publishing, and can return to any earlier version. There is nothing to update on a Tuesday night and no plugin waiting to conflict with another. Layout changes, such as a new page type, are developer work, which is also why they arrive tested.

The AI agents keep the new structure from decaying the way the old one did. Atlas watches page depth and flags orphan and thin pages. Ariadne finds and inserts internal links. Prometheus spots customer questions the site doesn't answer and drafts the page. Picasso makes sure images are described and sized. Argus watches for broken links and failing forms. Most agents draft for your approval. More on the move itself in switching from WordPress.

The worries, answered before you ask

• Will rankings drop? Some movement is normal while Google recrawls a changed site. Keeping the earning content, redirecting every changed URL and watching Search Console after launch is how we keep that risk small.
• Will it cost more than a straight migration? Yes. Design, content work and a new structure are more work than a port. You are paying for a better site, not only a faster one.
• Will my team have to relearn everything? They will learn Athena, which has fewer moving parts than a dashboard plus a builder. Most edits are a field and a publish button.
• What happens to the old site? It stays live until launch day, and you keep a full backup of it afterward.

The bigger risk usually runs the other way. A site that grew without a plan keeps growing without one, and every year of patches makes the eventual rebuild larger. Our piece on improving an old website covers the signs that patching has stopped paying.

A smaller job might do

If the design still works and customers find what they want, a rebuild is overkill. Port the site as it is with a WordPress to Next.js migration, switch to a lighter theme through a theme migration, or simply tune it with WordPress speed and optimization. If you don't yet know what is slowing it down, a speed diagnosis or a performance consultation should come before any rebuild decision.

One more honest case: if the business itself is about to change, with a new name, new services or a merger, wait until the change settles. A rebuild designed around a structure that is about to move is money spent twice, and we would rather start a month later than redo the sitemap.

When a rebuild is right, the quote depends on the number of pages and page types, how much content needs rewriting, e-commerce or membership features, integrations, and design rounds. We start with a free site audit and a mockup, then give you a fixed quote. Website financing is available. Or call (210) 346-0848 and tell us what you would change if you could start over.