Inventory every indexed URL first
Sitemaps, Search Console and crawl data combined into one list before anything is designed. You cannot preserve what you never wrote down, and this is the step that gets skipped.
Migration
The traffic drop after a redesign is not bad luck. It is what happens when URLs move without redirects, metadata is rewritten by someone who never saw the old titles, and nobody crawled the site before it was replaced.
What is wordpress migration at The Cubas?
The Cubas migrates WordPress sites to Next.js without losing search rankings. Every indexed URL is inventoried and mapped one to one, metadata and structured data are matched or improved, and crawls are compared before and after launch to confirm nothing dropped.
When people call us
Plugin sprawl, a page builder that makes Core Web Vitals unreachable, a security update that broke the layout, or hosting costs that keep rising to compensate for a site that should not be slow.
Built by
Ashraful Islam Hridoy, Lead Engineer
Ashraful builds the systems behind The Cubas engineering work, from typed REST APIs and data models to the React interfaces on top of them. His focus is the part most builds skip: secure access, reliable background jobs, and what happens to a system after launch.
What people search before they call
We rank for these ourselves. That is the shortest demonstration available that the search side and the build side are the same team.
How we approach it
Four decisions that separate a build which holds up from one that needs rescuing inside a year.
Sitemaps, Search Console and crawl data combined into one list before anything is designed. You cannot preserve what you never wrote down, and this is the step that gets skipped.
Every old URL resolves to its closest equivalent with a single permanent redirect. No chains, no bulk redirect to the homepage, which search engines treat as a soft 404 rather than a move.
Titles, descriptions, heading structure, internal links and structured data carried across deliberately. A rewrite is fine, an accidental change is not, and telling them apart requires having recorded the original.
A full crawl before launch and another after, diffed. Anything that changed unintentionally is found in days rather than discovered in a ranking report a month later.
Deliverables
No tiered packages with features withheld to force an upgrade. Every engagement covers what the project genuinely requires.
Stack for this work
Questions
Not if the migration is planned around preserving them. Losses come from moved URLs without redirects, lost metadata and missing structured data. Each is preventable, which is why the URL inventory is the first deliverable rather than a launch week task.
A brochure site with a defined page set typically runs three to five weeks including the redirect work. Sites with large archives or custom post types take longer, mostly in content mapping rather than in building.
Yes. Depending on who edits and how often, that means a headless content system, a git based workflow, or structured content files. We choose based on your team rather than defaulting to the option that is easiest for us to build.
Other engineering services
Send the brief, the existing codebase or just the problem. We will tell you what it takes, what it does not need, and whether we are the right people for it.
Prefer to skip the form? Message us on WhatsApp or email yousuf@thecubas.com