Seven Years of Platform Stewardship — Vakmangids
Since 2019, CV Infotech has been the sole technical team behind Vakmangids — a Belgian web platform built on WordPress with significant custom development. We inherited the codebase, audited and secured it, improved performance, and have continuously added features while keeping the platform stable, fast, and secure across seven years of active use.
Keeping a live platform healthy for seven years straight
Vakmangids is not a new build. It is a live platform with real users, existing content, established SEO rankings, and business processes that depend on it being available and working correctly at all times. When Steven brought CV Infotech in as the technical partner in 2019, the first job was not to add features — it was to understand what already existed and make sure it was stable, secure, and well-documented before touching anything.
Maintaining a WordPress platform over seven years is a different discipline from building one. WordPress core, PHP, plugins, and the wider hosting environment all change. Security vulnerabilities are disclosed. Performance requirements evolve as content and traffic grow. New features are requested while existing functionality must be protected. Every update carries risk — and every risk must be managed without disrupting a platform that real people rely on daily.
The Belgian market also added a layer of complexity. Vakmangids serves a Dutch-speaking audience, which means content structure, URL patterns, and SEO considerations are specific to that market. Maintaining those rankings through technical changes requires care that goes beyond standard WordPress housekeeping.
Audit first. Stabilise second. Improve continuously.
The first thing CV Infotech did when taking over Vakmangids was conduct a full technical audit. Security vulnerabilities were catalogued and prioritised. Plugin dependencies were mapped. Performance bottlenecks were identified. Database tables were reviewed for orphaned data and missing indexes. The audit produced a prioritised list of fixes — critical security items first, then performance, then code quality, then feature work.
Nothing significant goes to production without first passing through a staging environment that mirrors production exactly. This is true for WordPress core updates, for PHP version upgrades, for plugin updates, and for new feature code. Staging catches problems before users see them. In seven years of managing Vakmangids this way, we have not had a single update-related production incident.
Security patching follows a different timeline — when a CVE is disclosed for a plugin in the Vakmangids stack, the response is immediate. The patch is applied to staging, tested, and pushed to production within hours. Steven is notified when the patch is live. This is not reactive fire-fighting — it is a standing process that runs in the background continuously.
What seven years builds
The engineers working on Vakmangids today know this codebase from the first line. They know which plugins are load-bearing, which custom functions have subtle dependencies, and which database queries are sensitive to index changes. That institutional knowledge cannot be transferred in a handover document. It exists only because the same team has been here the whole time.
What platform stewardship actually looks like
Long-term platform maintenance is not a passive activity. Below is what CV Infotech does for Vakmangids on a standing basis — across security, performance, reliability, and feature development.
Security monitoring
Continuous monitoring for plugin CVEs, WordPress core vulnerabilities, and suspicious activity. Critical patches are applied to staging and pushed to production within hours of disclosure — not the next scheduled maintenance window.
Core and PHP upgrades
WordPress core and PHP version upgrades are tested in a full staging environment before touching production. Custom functionality is regression-tested after every upgrade. Seven years. Zero update-related production incidents.
Performance tuning
PageSpeed scores, Core Web Vitals, and database query performance are reviewed on a regular cycle. Caching configuration, image optimisation, and CDN settings are updated as traffic patterns change. The platform is faster today than it was in 2019.
Database maintenance
Database tables are reviewed for orphaned data, missing indexes, and slow queries. Scheduled cleanups prevent the database bloat that degrades WordPress performance over time. Backups are verified — not just created — on a regular schedule.
Feature development
Vakmangids is not a static platform. New features — directory improvements, filtering systems, user-facing tools — are developed and released alongside maintenance work. The same team handles both, which means feature work is always aware of the platform's constraints.
Backup and recovery
Automated backups run daily. Restoration procedures are tested quarterly — not assumed. In seven years of managing Vakmangids, the backup system has been invoked for testing purposes only. That is the intended outcome.
Taking over an existing platform
If you are looking for a new long-term technical partner for an existing WordPress platform, this is the process we follow. It is the same process we used when we took over Vakmangids in 2019.
Full technical audit
Week 1–2We read the codebase before we touch it. Security vulnerabilities are catalogued. Plugin dependencies are mapped. Performance bottlenecks are identified. Database tables are reviewed. The audit produces a prioritised list of issues — not a sales document, a working list.
Staging environment setup
Week 1A staging environment that mirrors production is set up before any changes are made. This is non-negotiable. Every update — critical security patch, plugin update, WordPress core upgrade, or new feature — is tested in staging first. Production only receives changes that staging has passed.
Critical security remediation
Week 2–4Security issues from the audit are addressed before any feature work begins. This is the correct order. Adding features to an insecure codebase is a compounding risk. We fix the foundation first, then build on it.
Performance baseline and improvements
Month 1–2Once the platform is secure, we establish a performance baseline — PageSpeed scores, Core Web Vitals, database query timing — and work through the improvement list. Caching, image optimisation, database indexing, and CDN configuration are the most common levers.
Standing maintenance and feature cadence
OngoingFrom month two onwards, maintenance and feature development run in parallel. Security monitoring is continuous. WordPress and PHP upgrades happen on a tested schedule. Feature requests are prioritised and developed in sprint cycles. Steven receives a brief monthly summary of what was done, what is coming, and whether anything needs his attention.
What consistent stewardship produces
7+
years active
Continuous maintenance since 2019
0
security incidents
In seven years of management
99.97%
uptime
Last 90-day rolling average
94
PageSpeed
Mobile score — up from 61 in 2019
Platform improvements since 2019
I get more quality from CV Infotech than working together with local companies. After months of working together — and now years — I can say they are very confident in their technical skills.
Steven
Vakmangids · UltimaBot · UltimaWriter · Client since 2019
Questions about WordPress maintenance
We take platforms seriously.
Whether you need a team to take over an existing WordPress platform or want a development partner who will still be there in seven years, we want to hear about it. We do not change teams between projects.