Przemysław Zalewski

Another WordPress patch day?

Move your company site off WordPress in a few hours

Most company sites are a few pages, a contact form and a map. They do not need PHP, a database and twenty plugins waiting for patches. I move yours to static files on Cloudflare: nothing to break into, hosting that is usually free, and changes you make by asking Claude.

See price and start date → Book a free 30‑min call

Brochure site, no add‑ons: $144⁠–⁠$432 excl. VAT · 4⁠–⁠8 h Details in the configurator →

Przemysław Zalewski

Sound familiar?

WordPress problems I fix in 2026

WordPress plugin vulnerability: is my site at risk?

Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 42% more than in 2024, and 91% of them were in plugins. For heavily exploited ones, the weighted median time to the first exploit was 5 hours.

I move the site to static files on Cloudflare, with no plugins, logins or database left to attack. A brochure site usually takes 4 to 8 hours. When two critical WordPress core vulnerabilities went public in July and September 2026, I flagged each to the team the same evening, then checked whether the company site was exposed and asked for it to be updated.

No patch yet for a plugin hole on my site. What now?

The same Patchstack report found that 46% of vulnerabilities had no fix from the developer when they were disclosed. Clicking update does nothing while the vendor has not shipped one.

First aid by hand, the same day: a Cloudflare WAF rule, wp‑admin closed to the world and the plugin switched off as the advisory says. Then we migrate, so the next advisory is not your problem.

Sound like you? Book a free 30‑min call →

The plugin that sends our contact form emails got hacked

CVE‑2026‑4020 in Gravity SMTP, published on 31 March 2026, let anyone without a login download a full system report from every version up to 2.1.4, including the API keys and tokens set in the plugin, such as the key to your email provider. The plugin that delivers your leads became the way in.

Your form goes to a small Cloudflare Worker with Turnstile spam protection. Every lead is saved and sent to your email, Slack or CRM, with no mail plugin and no admin account to take over.

AI Overviews cut my traffic. Is my site still worth the hassle?

In a randomized field study reported in April 2026, run in January and February 2026 on 1,065 US desktop Chrome users, outbound organic clicks fell 38% on searches that showed an AI Overview, and zero‑click searches rose from 54% to 72%. Fewer visits means each visit and each form submission counts more.

The new site keeps every old address with a 301, adds a sitemap and llms.txt, and PostHog shows which pages people read and where they leave. I do not promise rankings; I make sure no lead is lost. In October 2026 I shipped AI Visibility Desk, which asks your customers’ questions every week and shows whether AI assistants name your brand, who they name instead and which pages they cite.

Facing one of these? Book a free 30‑min call →

Scope

What you get

The same site, as static files

Pages, images and texts moved one to one, a 301 redirect for every old address, a sitemap and llms.txt. Served from Cloudflare: no server, login, database or plugins, so nothing to attack and nothing to patch at 2 a.m.

First aid today, if you need it

If the old site is exposed right now, I patch it, add a Cloudflare WAF rule, close wp‑admin to the world and turn off what the advisory says to turn off. By hand, then we migrate.

A form that keeps every lead

The contact form goes to a small Cloudflare Worker with spam protection (Turnstile). Every lead is saved and sent to your email, Slack or CRM, so nothing gets lost in a plugin.

Analytics, replays and monitoring

PostHog on your own account: what people read, where they leave, session replays with inputs masked. Plus an alert when the site or the form stops working.

Process

How it works

  1. A 30-minute call

    We go through the site, the forms and what must keep working. You get the scope and the hours in writing.

  2. First aid, if it is urgent

    If the old WordPress is exposed today, it gets patched and locked first. Then nobody has to rush.

  3. The migration

    The site moves to a repository and a Cloudflare account owned by your company. You check a preview link, then we switch DNS with every mail record copied.

  4. 30 minutes on editing

    I show you how to change a text, a price or a photo by asking Claude, with a preview before it goes live. Optional monthly care after that.

Where it fits

  • A brochure site or company site on WordPress that nobody has updated in a while.
  • A site where every edit means logging into WordPress and hoping a plugin does not break the footer.
  • A company that wants to know where its leads come from and how many get a reply.
  • A team that already uses Claude and wants its website to be one more file it can edit.

Add-ons, priced in hours

Each add‑on is 2 to 4 hours in the configurator. Pick what you need now; the rest can come later, on the same code.

A map without tracking

An OpenStreetMap map with no API key and no tracking cookies, or a static image that opens Google Maps.

Automations after a lead

A reply to the customer, a task in your CRM, a message in Slack, a row in a spreadsheet. The start of the bigger automations.

Languages and a blog

More languages generated from one source and blog posts kept as Markdown files, with the old addresses redirected.

A git-based CMS

For a team that wants a panel instead of Claude: a light editor (Pages CMS or Decap) on top of the same repository.

Track record

Proof

The first two cases are this offer in practice: a WordPress help center moved into a repository, and same‑day patching when a critical advisory lands. More on Cloudflare and PostHog.

Help center moved from WordPress into the repo as docs-as-code

The problem
An unmaintained WordPress help site: red in audits, no sitemap, expiring certificates, plugins nobody understood.
What I did
Markdown in the repo, versioned with the product, all languages generated automatically, interlinking, 301 redirects for every old address, help added to the Definition of Done.
Result
One machine less to break during holidays, docs that match the product, better SEO and GEO, context agents can read.

docs‑as‑code 301s i18n

See also: Cloudflare · Next.js

Same-day response to React2Shell and other advisories

The problem
Critical advisories in React, Node.js, WordPress and OpenSSH land without warning and proof‑of‑concept scanners follow within days.
What I did
A fixed pattern: official source, patch the same day, WAF mitigation, a regex sweep of our own code for the same vulnerability class, hardening flags for Node.js, reading material for the team.
Result
React2Shell patched the day the advisory went out, days before public scanners went live.

same‑day patch WAF code sweep

Taking over growth: SEO, GEO and dashboards leadership reads

The problem
Organic acquisition was close to zero and nobody could say which feature moved which number.
What I did
A tracking plan per feature, PostHog KPI dashboards, SEO and GEO work on landing pages and help, with help, changelog and landing pages treated as one body of context for people and bots.
Result
Organic acquisition grew from near zero: in one 28‑day window organic clicks rose 116% and impressions 2.5×. Leadership gets its numbers from dashboards, not from asking. Numbers stay relative on purpose.

PostHog SEO + GEO

Want the number before the call?

Brochure site, no add‑ons: $144⁠–⁠$432 excl. VAT · 4⁠–⁠8 h

See price and start date → Book a free 30‑min call

Good to know

WordPress facts worth knowing before you stay or leave

PHP 8.2 loses security fixes on 31 December 2026

Many WordPress hosts still run PHP 8.2, which stops getting security fixes at the end of 2026 (PHP supported versions).

WordPress still runs on end-of-life PHP

WordPress works with PHP 7.4, which is past end of life, and its own requirements page warns that such versions may expose the site (WordPress requirements).

Plugins do not update themselves by default

Automatic background updates cover minor core releases; plugins and themes update automatically only in special cases (WordPress docs).

WP-Cron runs only when someone visits

WP‑Cron is triggered on page load, so on a quiet site scheduled posts and backups run late (WordPress docs).

Keep redirects for at least a year

Google advises keeping redirects for at least a year after a move. A same-domain platform change does not use the Change of Address tool (Google Search Central).

Cloudflare caps _redirects at 2,000 rules

A _redirects file holds 2,000 static and 100 dynamic rules, and redirects win even over an existing file. A blog with thousands of old URLs needs rules in a Worker (Cloudflare docs).

FAQ

Questions

How do I edit the site without a developer?
You ask Claude: “change the opening hours on the contact page”. The change lands as a pull request. Every change gets its own preview link from Cloudflare (or Vercel on its Pro plan), and you publish it with one click. If your team prefers a panel, a git‑based CMS is an add‑on.
What about my plugins, Rank Math and IndexNow? Do I have to do that myself?
No. What plugins did on every page view now happens once, when the site is built and deployed: titles and descriptions, Open Graph, schema, sitemap, robots.txt, llms.txt, redirects and compressed images. After each deploy the changed addresses are sent to IndexNow automatically. Ongoing SEO, audits and internal links are work for Claude with open skills such as marketingskills. And with no plugins there is no plugin update that can bring malware in.
What does it cost?
A brochure site with no add‑ons is 4 to 8 hours. Pick the size and the add‑ons in the configurator to see the price and the start date before we talk.
Is updating WordPress not enough?
It is the minimum, and I can do it as first aid. But every patch is a race against the next exploit. In October 2026 two critical flaws were found in PHP itself, and exploits were shown on current WordPress, Drupal and phpBB before the fix was out. A static file has no PHP to exploit. Making WordPress faster does not change that.
Will search rankings drop after the move?
Every old address gets a 301 redirect to its new page, titles and descriptions move with it, and you get a sitemap. Static pages also load faster, which search engines measure.
Do you run security audits or scans?
No scanners and no security audits as a product. I remove the attack surface by moving the site, and in an emergency I patch and lock the old one by hand. If you want a person to read your code, that is the one‑week code audit on pricing.
What about WooCommerce or a members area?
Out of scope for this offer. A shop or logins is a separate project, and we can talk about it on the call.
Our WordPress may already be infected. Does the backdoor move with it?
No. I export the content only: texts, images and addresses. No PHP, theme or plugin is carried over, so whatever was planted stays on the old server, which is switched off after the move.
What happens to our email?
Mailboxes stay where they are. I copy every DNS record (MX, SPF, DKIM, DMARC, autodiscover), keep the mail records unproxied and send a test message before and after the switch.
WordPress has a plugin for everything. What do we lose?
A company site usually needs a form, analytics, SEO tags, a map and maybe search. All of that works without plugins. Bookings go through a calendar such as Cal.com. A shop, a members area or a large editorial team are a fair reason to stay on WordPress, and then first aid and monthly care still make sense.
We have a blog with several authors. What about roles, approval and scheduling?
Accounts, login and roles come from GitHub: each person has their own account and access to the repository, and every change has an author and can be reverted. A site’s code is public anyway, so the repository can be public too, and then even the free plan lets you require an approval before anything is published. A private repository needs GitHub Team for that. A post with a future date goes live on the next scheduled build. Decap CMS adds a draft, review and ready workflow in a panel. For a newsroom publishing all day, WordPress may still be the better tool, and I will say so.
Can whoever has access to Claude change the whole site?
Access is granted and taken away on GitHub, person by person. Changes from Claude arrive as a pull request, and nothing goes live until someone approves it. The CMS panel can only edit the content fields I give it, while the layout and code stay protected.
Will it look the same as in Elementor? Can I still move blocks around?
The look is rebuilt one to one, or refreshed if you want. Texts, prices and photos you change yourself. New sections and layout changes are a request to Claude or to me, so drag and drop is gone, and that is what keeps the site fast.
What if you disappear? Are we locked in?
The repository, the Cloudflare account and PostHog belong to your company. The site is plain HTML and Markdown, so any developer, or Claude, can keep working on it without me.
What about cookies and GDPR?
PostHog can run in its EU cloud and count visits without cookies until someone consents. The map uses no tracking cookies. If you use other tools that need consent, the banner stays.
What comes after?
Often the next problem: quotes that take a day to write, an internal app without company login, a form that should start an automation. See quote automation and company login.
Do I have to upgrade PHP for WordPress in 2026?
If your host runs PHP 8.2 or older, security fixes stop on 31 December 2026 or have stopped already (PHP). WordPress itself will keep running, so nothing forces the upgrade except risk (WordPress requirements).
Is hosting a static site on Cloudflare free?
Requests to static assets on Workers are free and unlimited (Workers pricing). The limits that matter are file counts per version and the 2,000‑rule cap on _redirects (Cloudflare docs).
WordPress plugin vulnerability: is my site at risk?
Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 42% more than in 2024, and 91% of them were in plugins. For heavily exploited ones, the weighted median time to the first exploit was 5 hours. I move the site to static files on Cloudflare, with no plugins, logins or database left to attack. A brochure site usually takes 4 to 8 hours. When two critical WordPress core vulnerabilities went public in July and September 2026, I flagged each to the team the same evening, then checked whether the company site was exposed and asked for it to be updated.

In 30 minutes you will know if we are a fit

You bring the problem, I bring the questions. Want a number first? The configurator shows hours, a price range and the start date.

or write to ciunkos@gmail.com

After you book you get a calendar invite. Nothing else to fill in.

My pledge

  • Reply within 24 hours. I reply within 24 hours on working days, personally, not a bot. Weekend messages: by Monday noon.
  • Late means free. If I am late, the first hour of work is free. You do not have to ask.
  • Scope in writing within 24 hours. A free 30‑minute call with no company deck, then the scope and the price in writing within 24 hours. You decide.
  • The person who does the work. You talk to the person who does the work. No sales layer, no handoff.
  • Follow‑up only with news. I follow up only when I have something new for you. Never a “did you see my offer”.
  • Honest “not a fit”. If I am not the right person, I say so on the call and point you to someone who is.

Calls this week · work can start now · B2B contract · Wrocław, Poland (CET), remote

You own the code, domain and accounts from day one. Nothing is held hostage.