WordPress Technical Support and Troubleshooting

// Who is WordPress technical support for?

WordPress technical support is for businesses whose site is down or unstable and who cannot locate the cause themselves. The fault usually comes from a single plugin update or a server setting, while the symptom shows up somewhere completely different, which is why first attempts fail. If any of the following sounds familiar, you are on the right page.

• The site shows a blank white screen or you cannot log in to the admin panel
• A feature broke after an update and you do not know which plugin caused it
• Form submissions or order emails never reach the customer
• The site returns intermittent 500 or 502 errors and the host says everything is fine

We use the same method on a one-page brochure site and on a 40-plugin online store; only the diagnosis time changes.

// What is included and what is not

Technical support can be bought as a one-off intervention or as part of a monthly maintenance plan. The table below lists what a one-off intervention includes and what is planned separately. We write the exclusions up front so there are no surprises at the quote stage and so it is clear which job belongs to which service.

Hacked site recovery is a different process; the symptoms look similar but the method is not. For that we point you to WordPress security and recovery.

// How does it work and how long does it take?

The process has four steps, each with a known duration. Urgent cases get a first response within 4 hours; a typical diagnosis and fix is completed the same business day. If the problem spans several layers it can stretch to 2 business days, which we tell you in writing after the first review; every delivery carries a 7-day recurrence guarantee.

// How is the price determined?

Three variables set the price: how many layers the problem touches, how plugin-heavy the site is, and whether the intervention is urgent. A white screen caused by a single plugin and a fault spread across server, theme and database do not take the same time, so instead of a fixed list we quote after a pre-check. The pre-check is free and the quote is fixed once it is done.

The price does not rise during the intervention. If we cannot fix it, we do not charge. For customers on the monthly maintenance plan, technical support is included and never billed separately.

// Results we have delivered

The three cases below represent different symptoms and different causes. We do not share client names without permission, so sector and scale are given instead. In all three the symptom and the source were in different places, which is why they had not been solved at first attempt and reached Zep Bilisim only after several tries.

• Education provider, 60 pages — The white screen came from a caching plugin update incompatible with the PHP version; fixed in 2 hours
• Online store, 200 products — Order emails were not sending; the server was mailing without SMTP, and authenticated SMTP took delivery to 100%
• Architecture practice — Intermittent 502 errors came from the memory limit; the limit and image-processing setting were corrected and it did not recur in 3 months

Removing the symptom and removing the cause are different jobs. Clearing the cache brings the site back from a white screen; the next update brings the white screen back.

// The team behind the work

The work is carried out by Caner Zep Çelik, founder of Zep Bilisim. As founder and technical consultant he has worked on WordPress infrastructure, server configuration and incident response since 2020 and has been involved in more than 120 projects. He reads the server and error logs himself and does not outsource the diagnosis.

Every intervention closes with a root-cause report: what was found, why it happened and what was done to stop it recurring. The document stays with you even if you later work with another team.

// When is it not needed?

Not every error calls for paid intervention and we do not sell unnecessary work. A display glitch that clears with a cache purge, a conflict that disappears when one plugin is disabled, or an outage on the hosting provider's side do not justify a paid callout; we say so in the pre-check and describe the step you can take yourself.

If the problem keeps recurring, a maintenance plan is cheaper than repeated one-off callouts; in that case we point you to WordPress maintenance and updates.

For scheduled care see WordPress maintenance and updates, and for speed problems see speed and performance optimization. If a backup is needed to roll back after a failure, backup and restore explains the process. WordPress's official debugging guide walks through the first checks you can run yourself.

// Frequently Asked Questions