Critical error on every page
A business site was offline after an update. Root cause isolated, offending component replaced, back live the same morning — no full restore required.
Read the caseAbout
I’m Sahed Rana Neka. I build and repair WordPress sites — and this site exists for the repair half, because it is a different job with different expectations.
I started in full-stack development and design: PHP, MySQL, JavaScript, interfaces. WordPress became the recurring platform because it is where businesses actually live — and because it is where things break in interesting ways. Fifteen years later, the pattern has not changed. Most “WordPress problems” are not WordPress problems. They are a version mismatch, a server limit, a plugin nobody audited, or a backup nobody tested.
For a long time that work sat inside a general portfolio at sahed.dev, mixed in with new builds, design and e-commerce. This site separates it for a reason: when a site is down, you do not want a design agency. You want someone who will read the error log, tell you what it means, and fix it without turning the conversation into a redesign proposal.
The work here is deliberately narrow. WordPress, WooCommerce and Elementor repair, malware cleanup, performance, migrations, and the monthly maintenance that stops the next emergency. If you need a new site, a custom application or a Shopify store, that lives on the portfolio — I will point you there rather than stretch this service into something it is not.
Diagnosis before action. The error log, the server log, the access log and a snapshot — in that order. The instinct to deactivate plugins until something loads is understandable and almost always a waste of the first hour.
Evidence before confidence. If I cannot reproduce a fault, I say so. If a fix is a workaround, it is labelled as one, with the durable option and its cost. The written summary at the end is not paperwork; it is the reason the next person does not have to start from zero.
No lock-in. You keep the access, the documentation and the decisions. Care plans exist because they are useful, not because leaving should be hard.
ProofRecent repairs
Each case on the portfolio records the symptom, the diagnosis and the fix — including the ones where the obvious answer was wrong.
A business site was offline after an update. Root cause isolated, offending component replaced, back live the same morning — no full restore required.
Read the caseThe regenerating dropper was found, the entry point closed, and the stack hardened without restoring an infected backup.
Read the caseEvery URL returned a 500 and wp-admin was unreachable. The fault was split between server and application layers, then fixed without a rebuild.
Read the caseDirect
The person who reads your first message is the person who fixes the site. That is the whole model.
Or email hello@wordpressfixe.com — first reply within 1 business day.