Host choice and site moves
A managed WordPress host, or AWS when you want the server in your own account. We copy the site, test it on a temporary address, then switch DNS with no lost orders or form entries.
WordPress hosting and security · WordPress · Los Angeles
Most hacked WordPress sites weren’t targeted. They were simply left alone too long.
Keeping a WordPress site safe means four quiet jobs done every week: a firewall in front, updates applied without breaking pages, backups you have actually restored, and someone told the minute the site stops answering. Our Glendale-led team picks or moves your host, hardens the install, then runs those jobs on a monthly care plan for US businesses, with alerts and care requests flowing into Zoho.
01Should you hand this off?
Any site that takes leads, orders or bookings is worth guarding, because an hour offline costs real inquiries. A care plan makes the most sense when nobody on staff owns updates and backups today. If you already have a developer who patches weekly and tests restores, you may only need a hardening pass. Here’s how we sort it.
Dozens of pending plugin updates and an admin login that three former staff still know. This is the most common starting point we see.
Downtime during a sale, or a card-skimming script in the checkout, is far more expensive than a monthly plan.
We clean it, find how the attacker got in, close that door, then keep watch so it doesn’t come back next month.
Moving to a managed WordPress host or to AWS is a good moment to rebuild the security layers properly.
A static site or Zoho Sites may be simpler than paying to look after WordPress at all. We’ll say so if that’s your case.
We harden and maintain WordPress. Audited frameworks for your whole company need a dedicated compliance firm alongside us.
02Hosting and security services
The work splits into a one-time setup (host, hardening, backups) and the ongoing care that keeps it true. You can take the setup alone, but most US clients keep us on afterward, since a hardened site drifts back to risky within a few months of nobody minding it.
A managed WordPress host, or AWS when you want the server in your own account. We copy the site, test it on a temporary address, then switch DNS with no lost orders or form entries.
Web application firewall, login rate limits, two-factor for every admin, the file editor switched off, XML-RPC closed when nothing uses it, and file permissions set the way WordPress recommends.
Daily copies of files and database stored away from the host, kept for a set number of days, and restored to a scratch server on a schedule so we know they work.
Core, theme and plugin updates go to a staging copy, get a quick visual and form check, then go live. Anything that breaks is held back with a note on why.
An outside check pings the site around the clock, a scanner looks for changed core files and injected code, and alerts go to a named person on our side and yours.
Remove the malware, close the hole it came through, reset every credential, then ask Google to review the warning. We write up what happened in plain words for your records.
03One month on a care plan
Mostly calm, with a few nights that would have gone badly without anyone watching. This is a sample October for a dental group’s WordPress site in Orange County, CA. Every green dot is a nightly off-site backup; pick a marked day to read what happened.
OctoberSample site
Updates
All seven went to the staging copy at 7 AM. The booking form and the location pages were compared side by side with the live site, then the updates went live before lunch.
Uptime
The uptime check failed twice in a row and paged our on-call engineer. The host’s PHP workers had stalled; a restart through the host panel had the site back in under ten minutes, with a note sent to the host’s support.
Updates
Core applied the security release on its own, as minor updates do by default. We checked the forms and the appointment widget afterward anyway.
Security
A public advisory named the version this site ran. The firewall already had a rule for it; we still patched on staging and pushed the fix live the same afternoon.
Security
Thousands of login attempts from rotating addresses, mostly for the username “admin”, which doesn’t exist here. Rate limits and two-factor meant none came close.
Updates
A slider plugin’s new version broke the homepage layout on staging. We pinned the old version, told the plugin’s developer, and logged it for next week.
Review
Last night’s backup was restored onto a scratch server. Pages loaded, the database matched and a test booking went through. Then the scratch copy was deleted.
Updates
The developer shipped a patch. It passed on staging, went live, and the pin came off.
Security
Two admin accounts belonged to people who had left the practice. Both removed, and an editor who only writes blog posts was moved down from administrator.
Review
One page for the office manager: uptime, what was updated, what was blocked, the restore drill result, and anything we want a decision on next month.
Sample practice, location and events. Your plan’s check times, backup retention and report format are written into the BRD.
04Try it · sample scoring
Flip the switches to match your WordPress site, or load one of the three starting points. The score weighs each defense by how often its absence causes trouble in the sites we take over, and the replay shows seven sample incidents being stopped, recovered from or getting through.
Sample month replay
Fix these first
Sample scoring and incidents for illustration. The weights are our own rule of thumb, not an industry standard, and a high score lowers risk without promising a site can’t be breached.
05WordPress care + Zoho
Into the tools your team already opens every morning. A downtime alert buried in someone’s inbox gets read at lunch; the same alert in a team channel gets read in minutes. These are the three links we set up on most care plans.
Down, back up, and “new admin user created” alerts land in a Zoho Cliq channel where your office manager and our engineer both see them, with the time and the page that failed.
“Can you change the holiday hours?” becomes a Zoho Desk ticket with an owner and a due date, so small edits on your care plan never get lost in a thread.
Honeypot fields and a challenge on suspicious submissions stop junk before it reaches Zoho CRM. We test the form after every update so leads keep flowing, and Zoho Forms is an option when you’d rather not host the form at all.
06Hosting and security costs
In layers, like the protection itself. WordPress costs nothing, so your bill is the host, an optional firewall or CDN service, a security plugin licence if you want the paid tier, and backup storage. Each vendor sets its own rates and changes them, so we price your exact stack in writing rather than print figures here.
Managed WordPress hosts charge per site plan, scaled by visits, storage and staging copies. On AWS you pay for the server, storage and data transfer you use; our Amazon EC2 page explains how that bill is built.
Cloudflare has a free plan that already puts a CDN and basic protection in front of a site, with more firewall controls on its paid plans. Many managed hosts include a WAF in the plan.
Wordfence and similar plugins have a free version; the paid tier is a yearly licence per site that gets new firewall rules sooner and adds support.
Usually a few gigabytes a month. Kept in your own Amazon S3 bucket it costs very little; see our Amazon S3 page for how storage is billed.
For our side, the host move and hardening are one fixed figure in a signed BRD, and the care plan’s monthly fee and what it covers (check times, backup retention, edit hours) sit in the same document. Talking it through on the first call is free; a hacked-site cleanup is quoted the day we see the damage.
07Hosting and security questions
Hosts, firewalls, backups, hacked sites and what a care plan covers. If your site is showing a warning right now, say so when you book and we’ll look first.
Every week we run updates on a staging copy before they touch the live site. Each night a backup leaves the host, and on a set schedule we prove one restores. On top of that come firewall and malware scanning, round-the-clock uptime checks with alerts to a person, a user audit, small content edits and a one-page monthly report. The exact check times, retention and edit hours are written into the BRD.
For a site that brings in leads or sales, usually yes. Managed WordPress hosts tune the server for WordPress, isolate sites from each other, and often include staging, a firewall and daily backups. Cheap shared plans put many unrelated sites on one server, which makes slowdowns and cross-site infections more likely.
Yes. We are an AWS Partner and can run WordPress on Amazon Lightsail or Amazon EC2 in your own AWS account, with backups stored in Amazon S3 and CloudFront in front when it helps. It suits teams that want the server under their own account or already run other systems on AWS.
Yes. We take a copy for evidence, remove the malicious code and any backdoor accounts, replace core and plugin files with clean versions, reset every password and key, then find and close the way in. If Google shows a warning, we request a review once the site is clean, and we watch it closely for the following weeks.
They work at different points. Cloudflare filters traffic before it reaches your server, a host firewall works at the server, and Wordfence runs inside WordPress where it can see logins and file changes. Most sites do well with an edge filter plus one plugin; we avoid stacking several security plugins, since they slow the site and conflict.
Daily for most business sites, and more often for busy WooCommerce stores. Backups belong away from the host, so a server failure or a hacked hosting account cannot take them too. A backup only counts once it has been restored successfully, which is why our plans include restore drills.
Occasionally an update does break something, which is exactly why we apply them to a staging copy first and check key pages and forms before going live. When an update misbehaves we hold it back and keep the current version until the plugin’s developer fixes it. Skipping updates altogether is the riskier choice.
No one honestly can. What we can do is remove the common ways in, such as outdated plugins, weak or shared logins and unmonitored servers, and make sure that if something does get through it is spotted fast and a clean backup is ready to restore.
Normally not. We copy the site to the new host, test it on a temporary address, lower the DNS time to live a day ahead, and switch during a quiet hour. For stores and booking sites we pause new orders for the few minutes of the final sync so nothing is lost between the two servers.
Moving and hardening the site is quoted once, as a single fixed amount written into the signed BRD, and the monthly care plan fee and its scope are in the same document. Hosting, firewall and plugin licences are billed to you by those vendors. A hacked-site cleanup is quoted once we have seen the infection.
08How a care plan starts
Four steps take a site from “nobody knows who updates this” to a signed care plan. A single site can often be read on the first call; a hacked install or a portfolio of sites can need a paid forensic look first, and we name that fee before doing any of it.
Care plans run remotely, whether your site serves Texas, Ontario or Mexico City. Clients near Glendale are welcome to sit down with us and walk through their dashboard in person.
Once signed, the host move and hardening follow our usual dated delivery plan. See how we work →
09Let’s talk
Book a free consultation with Elite Tech Global. We review your Zoho, AWS, Shopify or WordPress setup, show where AI / SI agents can save time, and agree the next step. If we work together, every requirement and a fixed price go into a signed BRD before the build starts.
Real people, one team. Led by co-founders Ikramul Karim and Khris Kakosimidi, and a 40+ member team across Zoho, AWS and AI.
Thanks, we’ve got it.
We’ll review your request and email you to set up your free consultation. Prefer to pick a time now?
Book a call