Putting the WhatsApp Business API on your website
Cloud API versus a click to chat link, message templates, opt in, the 24 hour window and human handover, for a UAE business building WhatsApp into its site.
Read the articleWeb Services
A Joomla migration only goes wrong in a handful of predictable places. Map every URL, redirect it correctly, export the content properly, and check the things that quietly break.

A Joomla migration keeps its search rankings when every URL that mattered on the old site gets mapped to a working equivalent on the new one and redirected correctly, the content is exported without losing fields or structure, and a short list of commonly broken items gets checked before launch, not after. Rankings are lost almost entirely through missing or wrong redirects, not through the act of changing platforms itself. This guide walks through the process in the order it should actually happen.
Key points
Search rankings are attached to specific URLs, not to a website in the abstract. When a Joomla migration changes URLs without a correct redirect plan, Google eventually treats the old URLs as gone and has to rediscover and re-evaluate the new ones from scratch, which is where the visible ranking drop comes from. This is not a mysterious side effect of switching platforms. It is a direct, mechanical consequence of URLs disappearing without a signal pointing search engines to where the content moved.
The practical implication is that a Joomla migration is really two separate projects running at the same time: moving the content and design to a new platform, and preserving every URL’s search equity through that move. Most migrations that damage rankings did the first project properly and skipped or rushed the second.
Before any redirect gets built, list every URL the current Joomla site actually has, not just the ones in the main menu. Joomla’s routing generates URLs from menu items, categories and articles, which means a site often has working, indexed URLs that are not obvious from browsing the menu, including old category listings, tag pages and any URLs search engine friendly routing has generated over the site’s life. Pull this list from the site’s own sitemap, from Google Search Console’s indexed pages, and from a crawl of the live site, then combine and deduplicate them.
Once the list exists, map each URL to where its content is moving on the new platform. Most URLs map one to one. Some content gets merged or restructured, in which case it maps to the closest genuinely relevant page rather than an unrelated one chosen only for convenience. A handful of URLs may have no real equivalent at all, in which case they need a considered decision rather than a default guess, covered in the next section.
| Old URL situation | What to map it to |
|---|---|
| Article moving with the same content, new URL structure | Its direct new equivalent, one to one |
| Several old articles merged into one new page | The single new page covering that merged content |
| Category or tag listing page with real traffic | Its closest new equivalent listing, not the homepage |
| Old content genuinely being dropped, with no replacement | A relevant parent page, or a proper 410 if nothing fits |
Every mapped URL pair needs a permanent, 301 redirect from the old Joomla address to its new one, implemented at the server or platform level rather than as a manual click through page. Redirect chains, where an old URL redirects to another redirect before finally reaching the real destination, should be flattened to a single hop wherever possible, since each extra hop adds a small amount of lost signal and page load delay.
The mistake worth naming directly: redirecting every old URL to the new homepage, rather than to its actual new equivalent, is the single most damaging thing a Joomla migration can do to search rankings. A blanket homepage redirect tells search engines that dozens or hundreds of specific pages have effectively disappeared, and the ranking value those pages built rarely transfers to the homepage in any meaningful way. It looks like a shortcut that saves migration time, and it is one of the most common reasons a Joomla migration ends up losing traffic it did not need to lose.
Redirecting everything to the homepage is not a shortcut. It is the fastest way to throw away years of ranking signal in one deployment.
Joomla stores article content, categories, tags and menu structure in its own database tables, and a clean migration needs each of these pulled out in a structured, mapped way rather than copied by hand. For smaller sites, this can mean using Joomla’s own export tools where the target platform supports a compatible import format. For larger or more customised sites, a dedicated migration extension or a carefully mapped direct database export is usually more reliable, particularly where custom fields, multiple languages or third party component data are involved.
Whichever method is used, export a full checklist alongside the raw content: article body, publish dates, author attribution, category and tag assignments, featured images, meta titles and meta descriptions, and any structured data the site currently outputs. Meta titles and descriptions in particular are easy to lose in a raw content export, since they often live in different Joomla fields from the visible article body, and losing them quietly degrades how the new pages appear in search results even when the content itself imports cleanly.
| Area | What commonly breaks |
|---|---|
| Redirects | Missing entirely, or pointed at the homepage instead of the real new page |
| Meta titles and descriptions | Lost in export, replaced by generic auto generated versions on the new platform |
| Structured data | Article or organisation schema present on the old Joomla site is not rebuilt on the new one |
| Internal links | Links between articles still point at old Joomla URLs instead of the new addresses |
| Forms and analytics | Contact forms and tracking codes are not reconnected before launch, so leads and traffic data go missing |
| XML sitemap | The old sitemap keeps serving stale Joomla URLs after launch, confusing search engines about what actually exists |
None of these are complicated to fix individually. They break because a migration plan usually focuses on getting the visible site working and treats this list as an afterthought, checked briefly if there is time left before launch rather than built into the plan from the start.
Pull every indexed URL from Search Console and a full crawl, and list every custom component, form and integration the site actually uses.
Work through the full list, not just the main menu, deciding a genuine new destination for each one.
Pull article bodies, categories, tags, meta titles, meta descriptions and structured data, not just the visible text.
Check a sample of imported pages against the original Joomla articles for missing fields or formatting issues before moving on.
Check a representative sample of old URLs resolves to the correct new page with a single 301 hop, not a chain and not the homepage.
Confirm tracking codes fire, forms deliver, and the new sitemap is submitted to replace the old one.
Watch Search Console for crawl errors and indexing drops in the weeks after launch, and fix any missed redirects quickly.
Joomla’s own release news page shows an actively maintained platform, with new releases in its current 5.x and 6.x series arriving regularly. That same release history makes the risk of an old, unmaintained Joomla install clear by contrast: Joomla’s own announcement of the 4.4.9 release states plainly that it “marks the end of bug fix updates for Joomla 4.4,” with only security updates continuing for that series afterwards. A Dubai business still running an old Joomla 3 or unmaintained Joomla 4 site is not just behind on features, it is running a platform version that is no longer being actively improved, which is a genuine reason to plan a migration on its own timeline rather than waiting for a security incident to force the decision.
The weeks after a Joomla migration are not the point to relax. Watch Google Search Console for a spike in crawl errors, which usually means a redirect was missed or built incorrectly. Watch the indexed page count for an unexpected drop, which can signal that new pages are not being discovered as fast as old ones are dropping out. Spot check a sample of old URLs from before the migration weekly for the first month, since this catches missed redirects far faster than waiting for a traffic report to show the damage after the fact.
We treat the redirect and URL mapping work as the core of a Joomla migration, not an afterthought once the new site looks right. Our Joomla developer team can also assess whether staying on Joomla, properly updated, is actually the right call before recommending a move at all. Where a full platform change and redesign is the right answer, our website development service, part of the wider web services we offer, covers the build itself, and our guide on what you should own when a website is handed over covers what to check once the new site, and its accounts and logins, are in your hands.
Straight answers
It can, but the damage almost always comes from missing or wrong redirects rather than from the migration itself. If every old Joomla URL that had traffic or backlinks gets a correct redirect to its new equivalent, most of a site's ranking signal carries across.
Joomla's own release announcements confirm that Joomla 4.4 stopped receiving bug fix updates once it reached its final 4.4 release, with only security updates continuing afterwards, so an old Joomla 4 site running behind that point is a genuine security risk worth prioritising.
Redirecting every old URL to the new homepage instead of mapping each one to its actual new equivalent. A blanket homepage redirect loses almost all the ranking value the original page had built.
Joomla's own database structure stores article content in a small number of core tables, and most migrations either use Joomla's built in CSV export tools where available, a dedicated migration extension, or a direct, carefully mapped database export, depending on the target platform and site size.
Not necessarily, but every URL that changes needs an explicit redirect from its old Joomla address to its new one. Keeping the structure similar where it makes sense reduces the number of redirects you need to build and check.
It depends entirely on the size of the site and how much custom functionality the current Joomla build has, so we scope this properly against your actual site rather than quoting a generic timeframe before seeing it.
Sources
Fixed price, in writing
Got it. Your quote is being written now.
In business hours you will have it within 45 minutes. Check your inbox for the confirmation.
Keep reading

Cloud API versus a click to chat link, message templates, opt in, the 24 hour window and human handover, for a UAE business building WhatsApp into its site.
Read the article
Choosing a CMS for a UAE business by who edits it, what it integrates with and who maintains it, not by which platform sounds most impressive.
Read the article
Laravel against WordPress for a Dubai business: where a content site ends, an application begins, and what happens when WordPress is pushed past that line.
Read the article