Viralistic
Strategic call

WordPress Agency in Amsterdam: An Honest Guide to Choosing One

Choosing a WordPress agency in Amsterdam? An honest guide to costs, maintenance, security, speed, and the cases where WordPress is the wrong platform.

MK
20 August 2026 · 16 min read
WordPress Agency in Amsterdam: An Honest Guide to Choosing One

WordPress agency in Amsterdam: the short answer

A WordPress agency in Amsterdam designs, builds, secures and maintains sites on the WordPress CMS for local businesses. Expect roughly €500 for a template build and €25.000 or more for a custom platform, based on prices Amsterdam agencies advertise. The right one will also tell you when WordPress is the wrong platform.

5.0 ★

Viralistic on Google, 30 reviews

43%

of all websites run on WordPress (W3Techs)

91%

of 2025 WordPress vulnerabilities sat in plugins (Patchstack)

46%

of WordPress origins pass Core Web Vitals (HTTP Archive)

Here is the awkward part of this article. Almost every page competing for your attention on this topic is published by a shop that only builds WordPress. Their honest answer and their commercial answer are the same answer, which makes both harder to trust.

Ours are not. The site you would hire us to replace or rebuild, viralistic.nl, runs on WordPress. The blog you are reading right now runs on Astro, a static framework, behind a Cloudflare Worker. We ship in both every week. That gives us no reason to talk you into a platform and every reason to tell you where each one costs you.

What a WordPress agency actually does

A WordPress agency takes responsibility for the whole lifecycle of a site built on WordPress: strategy, design, theme and plugin development, content migration, hosting, security patching and ongoing maintenance. A freelancer usually covers two or three of those. An agency is what you buy when you need all of them to hold together for years.

Design and build

Custom theme development, or a hardened commercial theme configured properly. The good ones write their own blocks instead of stacking a page builder on a page builder.

Integrations

Bookings, CRM, payments, PIM, WooCommerce, marketing automation. This is where WordPress projects quietly become software projects.

Maintenance and security

Core, theme and plugin updates on a schedule, staged and tested before they touch production. Backups you have actually restored from at least once.

Amsterdam companies search for this in two languages. In English they type wordpress agency amsterdam or wordpress development amsterdam; in Dutch they type wordpress website laten maken amsterdam. The results are largely the same eight or nine firms, plus two directory pages. Volume for each phrase is modest, which tells you something useful: this is a small, high-value market where reputation and referral do most of the work, and the SERP is a shortlist rather than a marketplace.

What running WordPress and Astro side by side taught us

Two things, and they are not the ones a WordPress-only shop tends to lead with.

First: WordPress is a content problem solved, not a performance problem solved. Our marketing site sits on WordPress because non-technical people at Viralistic need to change a headline on a Tuesday afternoon without opening a pull request. That is a real, recurring, expensive problem, and WordPress solves it better than almost anything else. We are not being polite about that. It is the reason we did not migrate.

Second: the speed ceiling is lower and you feel it later. This blog runs on Astro and ships almost no JavaScript, so it is fast by construction rather than fast by optimisation. On WordPress we reach the same place, but we get there by managing things: caching layers, image handling, deferred scripts, a plugin budget. That management never ends. It is a running cost, not a one-time fix.

The question that separates good agencies from average ones

Ask a prospective agency: which parts of this site will my team edit, and how often? If the honest answer is “the homepage hero, twice a year,” you may be paying a WordPress tax for flexibility nobody uses. If the answer is “landing pages, weekly, by three different people,” WordPress is probably right and a static build would be a mistake.

When WordPress is the right call

WordPress wins on four things, and they are worth real money.

  • Editorial independence. Your team publishes without a developer. Over three years this saves more than the platform costs.
  • Ecosystem depth. Whatever you need to integrate, a mature plugin or a documented API path probably exists. Building the same thing from scratch is rarely cheaper.
  • No lock-in and no licence. It is open source. You own the database and the files, and you can move to another agency without asking anyone’s permission. That is a genuine commercial advantage over Webflow, Wix or a proprietary CMS.
  • A hiring market. If we vanished tomorrow you could hire a competent WordPress developer in Amsterdam within a fortnight. Try that with a bespoke framework.

W3Techs puts WordPress at roughly 43 percent of all websites, and around 59 percent of sites running a known CMS. That is not fashion. That is infrastructure, and infrastructure is the right thing to be boring about.

When WordPress is the wrong call

We turn WordPress down in four situations, and any agency worth hiring will name its own list.

The site is really an application

Dashboards, complex user state, real-time data, heavy custom logic. You can force this into WordPress. You will then spend years fighting the parts of WordPress that assume you are publishing pages.

Performance is the product

Publishers monetising on ad viewability, or storefronts where every 100ms moves revenue. A static or headless build removes a whole class of performance work rather than managing it forever.

Nobody will ever edit it

A five-page brochure site nobody touches does not need a CMS, a database, a login screen or a monthly patch cycle. It needs a fast static site and a small maintenance retainer.

You have no maintenance budget

An unmaintained WordPress site is a liability with a countdown on it. If nobody will own updates, choose a platform where updates are somebody else's job.

If two or more of those describe your project, read our note on custom website development and why we build with Astro before you commission anything.

What a WordPress website costs in Amsterdam

Prices advertised on the Amsterdam search results span two orders of magnitude, which is exactly why buyers find this so hard.

Build typeIndicative rangeWhere this number comes from
Template or near-template sitearound €499 to €799entry prices advertised by Amsterdam website builders on the live search results
Custom design on WordPress, standard integrationsmid four figures to low five figuresthe gap between the two advertised anchors, so treat it as a band and get a written quote
Custom WordPress platform with integrationsfrom €25.000one Amsterdam WordPress agency states this as its published starting price

Treat all three as market ranges, not quotes. What actually moves the number is scope: page count, how much of the design is bespoke, how many systems the site has to talk to, and whether anyone is migrating content. Two agencies quoting the same site can differ by a factor of ten because one is styling a theme and the other is building software.

For the wider view across platforms, see how much a website costs.

Your maintenance bill is decided at build time

This is the most expensive thing nobody tells you before you sign. The recurring cost of a WordPress site is set almost entirely by decisions made during the build, and by then it is very hard to reverse.

Three build decisions drive it:

  1. Plugin count. Every plugin is a dependency you now patch, test and eventually replace. Twenty plugins is not twenty times the maintenance of one; it is worse, because they interact.
  2. Page builder dependency. A site built inside Elementor or Divi is portable in theory and welded shut in practice. Leaving means rebuilding the pages.
  3. Custom code quality. A well-written child theme survives a decade of core updates. Functions bolted into the theme by four different freelancers will break on one of them, usually on a Friday.

Ask any prospective agency for the intended plugin list before you sign, and ask what happens when one of them is abandoned. A good website maintenance arrangement is not an upsell here; it is the thing that keeps the asset alive.

Security: the risk is plugins, not WordPress

WordPress core is not the weak point. In Patchstack’s State of WordPress Security report covering 2025, 91 percent of the 11,334 newly disclosed vulnerabilities in the WordPress ecosystem sat in plugins and 9 percent in themes. Core itself accounted for a negligible share. The report also found that around half of high-impact vulnerabilities are exploited within 24 hours of disclosure.

That reframes the whole conversation. You are not choosing whether to trust WordPress; you are choosing how disciplined your agency is about third-party code. Practically, that means a short plugin list, a patch window measured in hours rather than weeks, staged updates, real backups, and a named person responsible. Every serious wordpress agency will describe this process without being asked. If yours cannot, that is your answer.

Performance and Core Web Vitals on WordPress

WordPress can hit good Core Web Vitals. Most WordPress sites do not, and the honest version of that sentence is useful to you.

HTTP Archive’s Core Web Vitals Technology Report put WordPress at roughly 46 percent of origins passing all three Core Web Vitals in its late-2025 data, well behind fully managed platforms such as Duda at around 85 percent. The interesting detail is where the failure sits: WordPress interaction responsiveness is strong, at roughly 86 percent passing INP. The problem is loading, measured as Largest Contentful Paint. That is what happens when themes ship heavy CSS, plugins queue their own scripts, and somebody uploads a hero image straight off the camera.

None of that is a flaw in WordPress. All of it is a flaw in how a specific site was built. A disciplined build with a lean theme, a strict plugin budget, proper image handling and edge caching passes comfortably. It just does not happen by default, and it degrades every time someone installs one more plugin. If speed is a commercial priority for you, start with Core Web Vitals and technical SEO.

WordPress, headless, or a static custom build

Classic WordPressHeadless WordPressStatic or custom build
Editing experienceExcellent, familiarGood, needs preview workDepends entirely on the CMS you attach
Speed ceilingGood with disciplineVery goodHighest
Build costLowestHighest of the threeMiddle to high
Maintenance surfaceLargest, plugin-drivenTwo systems to patchSmallest
Best forContent-led marketing sitesLarge content operations feeding apps and sitesPerformance-critical or application-like products

Headless is genuinely powerful and routinely oversold. You keep the WordPress editor and render the front end separately, which buys you speed and flexibility. It also costs you a second codebase, a second deployment pipeline, and a preview problem somebody has to solve. Headless is the right answer for a large content operation and an expensive answer for a fifteen-page site. We cover the tradeoff properly in headless CMS, and if you are weighing a shop specifically, in Shopify vs WooCommerce.

Getting found by AI search on WordPress

The platform barely matters to AI answer engines. What matters is whether your pages state answers plainly, load quickly, and carry structured data that reflects what is on the page. WordPress handles all of that well, when somebody bothers.

The practical work is the same on any stack: put the direct answer in the first two sentences of a page, keep headings honest, mark up your organisation and services, and make sure the pages an AI engine would cite actually render fast for a crawler. This is what we mean by earning the cited answer rather than gaming it. WordPress plugins will happily generate schema for you; almost none of them will tell you when the schema no longer matches what is on the page. That is the part a person has to own.

Not sure WordPress is the right platform for you?

We build on WordPress and on Astro, so we have no stake in the answer. Book a free orientation call and we will tell you honestly which one your project needs, and where the money goes either way.

How to judge a WordPress developer before you hire

Ask these seven questions. The answers separate a WordPress developer from a supplier of WordPress sites.

  1. Which plugins will this site depend on, and why each one? A short, reasoned list is a very good sign. Vagueness here becomes your maintenance bill.
  2. Do you build with a page builder, and what happens if we leave? Neither answer is disqualifying. Not having thought about it is.
  3. Who patches this site, on what schedule, and how are updates staged? You want a named process, not “we keep an eye on it.”
  4. Show me a site you built three years ago. Anything looks good at launch. Three-year-old work shows whether it was built to last.
  5. What is your Core Web Vitals field data on that site? Field data, not a Lighthouse score from their laptop.
  6. When do you tell a client not to use WordPress? If the answer is never, they are selling, not advising.
  7. What exactly do we own, and how do we get it? Database, files, repository access, domain, hosting account. Get it in writing before the build starts, not after a disagreement.

A wordpress agency that answers all seven crisply is worth paying more for. One that deflects on numbers four through seven will cost you the difference later.

Where we fit

Viralistic is a digital agency on the Herengracht in Amsterdam, rated 5.0 stars on Google across 30 reviews. We bring SEO and AI visibility, web design and custom development, branding, and workflow automation together under one strategic lead, so you are not translating between a designer, a developer and a marketer who have never met.

Our work with SilverDrive, a chauffeur service operating from Amsterdam across Europe, is the clearest example of what we mean. We built the website and the systems behind it, and the business grew internationally on organic findability. In the client’s own words, in the original Dutch: “Viralistic begeleidde SilverDrive naar een internationaal gericht bedrijf dat volledig draait op organische vindbaarheid. De website en alle systemen besparen ons enorm veel tijd.” — Joshua Faerber, SilverDrive. Translated: Viralistic guided SilverDrive toward becoming an internationally focused company that runs entirely on organic findability, and the website and systems save the team an enormous amount of time.

If you want the design-led view of the same market, read website design in Amsterdam and custom websites in Amsterdam.

Frequently asked questions

Is WordPress outdated in 2026? No. W3Techs still puts WordPress on roughly 43 percent of all websites, and the block editor has changed the platform substantially in recent years. What is outdated is a specific way of building on it: heavy page builders, thirty plugins, and no maintenance plan. The platform is fine; the habits date badly.

Why are people moving away from WordPress? Usually for three reasons: performance ceilings on content-heavy sites, maintenance fatigue from plugin sprawl, and a preference for platforms where hosting and updates are somebody else’s problem. Teams that move for the third reason often trade one cost for another, since managed platforms charge a licence and limit what you can build.

What is the downside of using WordPress? The recurring maintenance surface. Core, themes and plugins all need patching, and Patchstack recorded 11,334 new WordPress ecosystem vulnerabilities in 2025 with 91 percent of them in plugins. WordPress also has a lower default performance ceiling than a static build, so speed has to be actively managed.

How much does it cost to build a site on WordPress? Amsterdam agencies advertise entry builds from around €499 to €799 and custom platforms from €25.000. Most business sites land between those anchors. Scope drives the number: page count, bespoke design, integrations and content migration. Always ask for a written quote that names the plugin list and the hosting arrangement.

Do I need a WordPress agency, or can I build it myself? You can build it yourself. Whether you should depends on what the site has to do. Marketing pages with a commercial theme are genuinely DIY-able. Payments, bookings, multilingual content, CRM integration or anything carrying real revenue is where a wordpress agency earns its fee, mostly by preventing decisions that are expensive to undo.

Can ChatGPT build a WordPress website? It can generate code, copy, and configuration, and it will speed up an experienced developer meaningfully. It cannot decide your information architecture, judge your plugin risk, or take responsibility when an update breaks checkout. Use it as an accelerator, not as a supplier.

What does WordPress maintenance include? Core, theme and plugin updates on a schedule, staged and tested before production; security monitoring and patching; backups that have been restored from at least once; uptime checks; and periodic performance review. Ask what the response time is when a critical vulnerability is disclosed, since roughly half of high-impact ones are exploited within a day.

Can an agency take over an existing WordPress site? Yes, and it is common. Expect a paid audit first: plugin inventory, theme quality, code added outside version control, hosting setup and backup status. A good agency will quote the takeover only after that audit, because the honest number depends on what the previous team left behind.

Talk to a team that builds on both

We run WordPress and Astro side by side every week, which means our advice is not a sales pitch for one stack. Tell us what your site has to do and we will tell you what it should be built on.

Explore this topic

This article in context: linked and related posts — drag the dots or click to keep reading.

Marrallisa Kreijkes WhatsApp