WordPress
An open-source CMS written in PHP, installed on hosting with a MySQL or MariaDB database. You pick a theme, add plugins (forms, WooCommerce shop, SEO, caching) and edit pages from a dashboard.
Guide · Web technology · Updated November 2026
WordPress works very well for an editorial site or a blog your team updates on its own every week, on a tight budget with standard needs. A custom Next.js website fits better when the site must be fast, light on security upkeep, and do more than show pages: calculated quotes, bookings, a customer area, a link to your app or your tools. Both can rank well on Google; the difference lies in maintenance, security and what the site will need to do in two years.
Start a project →See pricing →
The two are often compared as competing products. That is not quite right: WordPress is a ready-made content management system, Next.js is a tool developers use to build a custom website.
An open-source CMS written in PHP, installed on hosting with a MySQL or MariaDB database. You pick a theme, add plugins (forms, WooCommerce shop, SEO, caching) and edit pages from a dashboard.
An open-source framework built on React. Developers write the site in code; pages are generated ahead of time or on the server and sent as HTML. Content is edited from a back office or a connected CMS, planned from the start.
On WordPress, Elementor is used by 31.5% of sites (W3Techs). It lets you compose pages without code, at the cost of heavier markup and one more plugin to maintain.
Both technologies can produce a good website. This table shows where each one takes more effort.
| Criterion | WordPress | Custom Next.js website |
|---|---|---|
| Launching a simple site | Fast with an existing theme | Longer: design and pages are developed |
| Changing a text or a photo | From the WordPress dashboard | From the back office or CMS planned in the project |
| Specific features (quotes, booking, customer area) | Plugins, or custom PHP development | Built into the site, like the rest |
| Day-to-day security | Updates to core, theme and every plugin | No public third-party plugins; dependencies updated by the tech team |
| Speed | Depends on the theme, plugins and caching | Prerendered pages, little unused code |
| Hosting | PHP 8.3+, MySQL 8.4+ or MariaDB 10.11+, HTTPS (WordPress recommendations) | A Node.js server, or static files on a CDN |
| Finding a provider | Very easy, many freelancers | Narrower: React and Next.js developers |
| Sharing code with a mobile app | No | Yes with React Native: same language and business rules |
WordPress requirements: WordPress.org “Requirements” page, read on 20 November 2026.
WordPress remains a good answer in many cases. We do not advise rebuilding a WordPress site that works well.
WordPress core is well maintained: Patchstack recorded only 6 core vulnerabilities in 2025, all low priority. The risk comes from plugins and themes: 11,334 new vulnerabilities in the WordPress ecosystem in 2025, up 42% in a year, 91% of them in plugins and 9% in themes.
The same report says 46% of those vulnerabilities had no fix when they were disclosed, and that the most exploited ones were mass-attacked within a median of 5 hours. A WordPress site is not dangerous in itself, but it needs constant watching.
A custom site also has dependencies to update (Next.js, React, libraries). The difference: less third-party code, no standard public admin like /wp-admin, and updates done by the team that knows the code.
Google does not favour a technology. It reads your pages’ HTML, measures their speed and judges their content. WordPress with an SEO plugin and a good theme ranks very well; so does a Next.js site, provided pages are rendered on the server or generated ahead of time, which is Next.js’s default. Google says so itself: server-side or pre-rendering is still a great idea, because it makes the site faster for users and crawlers, and not all bots can run JavaScript.
What makes the difference on Google in Morocco is useful content, pages per service and per city where you have real clients, a complete Google Business Profile, reviews and links from other sites. Changing technology replaces none of these.
This is the question to ask before any other. With WordPress, the dashboard comes with it: you edit pages, publish posts and change photos yourself.
With a custom site, the editing tool has to be part of the project: a connected CMS (often called “headless”) or a back office built for your content. If you change your texts twice a year, asking the provider is often cheaper than a CMS. If you publish every week, the editing tool must be in the quote, and you should be able to try it before delivery.
WordPress is available in Arabic and handles right-to-left writing; the quality of the result depends on the theme and plugins, not all of which are built for RTL. With a custom site, each language gets its own layout from the mockups: menus, icons, arrows and forms are designed for both directions. Either way, plan Arabic from the start: adding it later costs more.
The build price is not the total cost. Compare over three years, listing the same lines for each option.
For amounts in dirhams, see our guide to website cost in Morocco.
Export all indexed URLs, from the sitemap and Google Search Console, with their traffic.
Keep the same URLs when you can; otherwise, a permanent redirect (301 or 308) from each old page to the matching new one.
Titles, descriptions, texts, images with their alt text: nothing should disappear without a decision.
Check redirects, internal links, forms and speed on a test address.
Submit the new sitemap in Search Console and watch for error pages for several weeks.
We build custom websites: the site you are reading is built with Next.js and prerendered, and the 2STM platform uses Next.js for its interface. The code, designs and content belong to the client.
We also audit existing WordPress sites. If yours works and your team uses it well, we will say so; if plugins, speed or security are a problem, the audit prices both options: fix or rebuild.
Real projects, with their screens and their status.
Neither in absolute terms. WordPress is faster to set up and easy to edit for a standard editorial site. Next.js fits a fast site with business features or a linked mobile app, and less day-to-day security upkeep.
Not by nature. Google favours no technology. Next.js helps with speed and prerendered HTML; WordPress ranks very well with a light theme and a good SEO plugin. Content, your Google profile and reviews matter more.
Yes, if a back office or CMS is part of the project. Ask to see it before signing and to try it before delivery.
No, but it needs constant watching. Core is well maintained; most vulnerabilities come from plugins and themes (91% and 9% of those disclosed in 2025, according to Patchstack). Fewer plugins and regular updates cut the risk sharply.
Only if it holds your business back: slowness, repeated breaches, features that cannot be added cleanly, or a need to share data with an app. Otherwise, fixing what exists is almost always cheaper. An audit settles it.
To build, often yes, because the design and pages are developed. Over three years the gap narrows: a WordPress site pays plugin licences and update hours. Compare total cost, not just the first quote.
We build custom websites; vctrum.com is built with Next.js. We also audit WordPress sites and tell you whether keeping the existing one is the better option.
Describe your site in two minutes. Within 24 hours, we tell you which option fits your project and what it costs over three years.