WordPress Maintenance & Development
April — July 2026
Contents
Headline numbers across the four-month period.
Weekly Wordfence scans, plugin updates, hardening.
Clean-up of an infection and reduction of the account behind it.
Design, build, domain migration and three language versions.
A multilingual landing-page builder inside the dashboard.
kemroc.com/us — US units, isolated database.
Testimonials page & Rank Math SEO editing.
What the hosting reported vs. what we asked for.
What we recommend for the coming period.
Period summary
Everything delivered between 1 April and 31 July 2026.
01 · Ongoing maintenance
The routine work that keeps the site online, patched and protected — carried out continuously across all four months, alongside every development track.
A full malware and integrity scan is executed every week across core files, themes and plugins. Findings are triaged the same day, and anything flagged is either cleared or resolved before the next cycle.
Plugins are updated on a controlled schedule rather than automatically, so every update is verified against the live design and functionality before it stays in place.
Wordfence firewall rules are reviewed as part of the same cycle — including the false-positive rule that was blocking legitimate SEO edits from the dashboard.
01 · Ongoing maintenance
Maintenance ran continuously throughout. April and May produced the first landing pages by hand; June and July replaced that approach with a system.
Bars indicate relative activity across the period, not billed hours. Striped bars run continuously.
02 · Incident
An infection introduced through a previous user account was identified and removed, and that account's permissions were reduced.
Wordfence scanning surfaced files that did not match the official WordPress and plugin distributions.
The infection was traced back to activity from a previous user account rather than to a hosting-level breach.
Malicious files and injected code were cleared and the affected files were restored to clean versions.
The account itself was kept, but its role was lowered so it no longer holds the permissions that allowed the infection in.
03 · April — May
Before any system existed, the landing page was designed, built and shipped by hand. This is the work that proved the concept — and revealed what it would cost to repeat.
The landing page interface was designed from scratch — layout, hierarchy, typography and the KEMROC brand treatment, shaped around a page built to convert.
The approved design was developed into a working page and checked across screen sizes and browsers before anything went near the live site.
The page was moved off the development domain onto the main KEMROC domain, so traffic and search value land on the live site rather than a staging URL.
A designed, developed and published landing page running on the main domain — the reference every later version was built from.
03 · April — May
Using WordPress pages and a page builder, three versions of the landing page were produced across Italian and English.
Three separate versions of the page, each published and maintained as its own WordPress page.
Content prepared per version so each market reads the page in its own language.
Each version was assembled visually in the page builder — the standard WordPress approach, and the quickest route to the first few pages.
Three pages were manageable. Every further market would mean another hand-built page to lay out, translate and maintain separately.
04 · Flagship delivery
A purpose-built system that lets KEMROC create a complete, on-brand landing page for any market or language — entirely from the WordPress dashboard, without a page builder and without a developer.
04 · Landing System
04 · Landing System
A custom post type powered by JetEngine, with every piece of page content stored as a structured field.
“Landings” — a dedicated content type registered with JetEngine, listed in the dashboard like posts or pages.
Eleven tabs of fields — hero, applications, products, catalogue, testimonials, job reports, contact, form, configuration, footer and section visibility.
A single hand-coded template renders those fields. The design is locked, so no entry can break the layout — regardless of language.
Published in any language, LTR or RTL, with its own contact form — created without touching code or a page builder.
04 · Landing System
Each landing page is its own entry with its own language content, while the layout, spacing and brand treatment stay identical everywhere.
A single toggle — landing_configuration_language_direction — flips the entire page to right-to-left for Arabic and other RTL languages.
All copy, images, videos, links and contact details are plain dashboard fields. No Elementor, no shortcode hunting, no HTML.
Eight independent switches under “Sections Display” turn each section on or off per page, so no two markets need the same page structure.
Applications, products and job-site reports are repeaters — items are added, duplicated, reordered or deleted with a click.
Each page points at a JetFormBuilder form ID. Ready-made LTR and RTL forms are supplied to duplicate and reuse.
04 · Landing System
Everything visible on a landing page maps to a tab in the dashboard.
Title, description, background video and thumbnail.
Title, description, CTA and a repeater of application areas.
Title, description and a repeater of KEMROC solutions.
Cover image, description and a download call-to-action.
Rich-text success stories plus video and video thumbnail.
Repeater of real job-site reports with CTA to the full archive.
Sales representatives — name, role, phone, mail, location, photo.
Section heading, intro copy and the form ID rendered on the page.
RTL toggle, header menu labels and the JetFormBuilder form ID.
Footer description and every quick-link label.
Eight on/off switches controlling section visibility.
04 · Landing System
The Middle East pages need Arabic. Rather than maintaining a second design, the template mirrors itself.
landing_configuration
_language_direction
04 · Landing System
Built with JetFormBuilder and connected to each landing page through a form ID.
One left-to-right and one right-to-left, both already styled to match the landing design.
The team copies the matching master form for a new market instead of building fields from zero.
Only the field labels and messages change — structure, validation and notifications stay intact.
The landing_form_id field connects the form to the page. Nothing else is required.
04 · Landing System
Every editing tab delivered to the KEMROC team. Click any screen to enlarge.
05 · Development
Built as a proving ground for regional websites — US measurement units only, with its own isolated data.
kemroc.com/usInstalled as a directory on the existing domain, so the US site inherits the domain authority already earned by kemroc.com instead of starting from zero.
The US install runs on its own database. Content, users and settings are fully isolated — nothing done there can affect the global site.
Specifications, dimensions and performance figures are presented in imperial units, so US customers read numbers in the form they actually work with.
This version validates the regional-site model — content structure, unit handling and maintenance overhead — before it is rolled out more widely.
05 · Development
The directory-plus-separate-database approach proved the concept. The next generation moves to a proper network.
06 · Corrections
The testimonials page was not behaving correctly for visitors, affecting one of the strongest trust signals on the website.
The cause was identified and corrected, and the page was verified across devices. Customer success stories now display as intended.
SEO fields could not be saved. Wordfence was treating legitimate Rank Math requests as suspicious and blocking them, so titles, descriptions and keywords could not be updated from the editor.
The blocked requests were traced in the Wordfence logs and the firewall rule was corrected — without weakening the site's overall protection. Rank Math now saves normally, restoring day-to-day SEO control.
07 · Infrastructure
We audited the hosting environment and submitted a formal upgrade request. Below is what the server reported at the time of the audit, against what we asked for.
| Setting | Value at audit | Value we requested |
|---|---|---|
| Web server | Apache | LiteSpeed / optimised stack |
| PHP version | 7.4.33 end of life | 8.2 or 8.3 |
PHP memory_limit | 256M | 512M |
WP_MEMORY_LIMIT | — | 256M |
WP_MAX_MEMORY_LIMIT | 256M | 512M |
upload_max_filesize | 80M | 256M |
post_max_size | 80M | 256M |
max_execution_time | — | 300+ |
max_input_vars | — | 5000+ |
| Server-side caching | Disabled | Enabled |
Summary
The three April–May pages each needed design and development time. A page for a new region now needs neither — the marketing team publishes it directly, and the Middle East page is the first live proof.
Every market gets the same locked design. Language changes, the presentation does not.
Malware removed, weekly scanning in place, plugins patched, and the firewall tuned so protection no longer blocks legitimate work.
The US build validates the approach for future markets, and points the way to a multisite network that scales without multiplying maintenance.
Content, visibility, contacts, forms and language direction are all controlled from the dashboard by the KEMROC team.
Looking ahead
In priority order, for the coming period.
Use the system for the remaining target markets. Each new page is content entry rather than development, so the marketing team can publish without a build cycle.
Action: KEMROC marketing · Hive Studio supportConvert the regional-site model to a WordPress Multisite network once the US version's evaluation is complete — including a check on how premium plugin licences apply across a network.
Action: Hive StudioWeekly Wordfence scans, controlled plugin updates, user-access review and post-release verification — plus following up on the server values still short of the request.
Action: Hive StudioApril — July 2026
We're glad to keep building on this platform with the KEMROC team.
Report prepared by Hive Studio · WordPress maintenance & development partner