Skip to content
Mohammad Emmon Mohammad Emmon.

Freelancer vs Agency vs Host: Scope, Accountability, and Cost in Dubai

18 min read By Mohammad Emmon
Red flags to watch for when hiring a WordPress security expert

Quick answer

Your host may restore a backup or suspend the site, but most do not clean malware. A specialist freelancer is often the fastest and most affordable option for a full cleanup. An agency suits larger sites that need a team, reporting and ongoing support. Whoever you choose, check that they remove backdoors and fix the cause.

On this page

Your host owns the server, your agency owns the build, and a specialist freelancer owns the security work, which is why a hacked site so often sits between all three with nobody moving. That gap is the real problem, not the infection.

Each of the three can fix a hacked WordPress site, and each has a different reason not to. The host protects the platform and the other accounts on it. The agency built the site and usually never agreed to maintain its security. The specialist does the security work but needs access that the other two control. Customers struggle with this because they assume somebody in that chain already owns the problem, and usually nobody does.

The contracts say so in writing. Bluehost's own help documentation states that "Bluehost is not liable for any files or data stored on your account. You agree to be solely responsible for all files and data sent and keep all necessary backups." Meanwhile Kinsta states that "Every plan includes a hack-fix guarantee, so if your site is compromised, our security engineers will clean it up at no extra cost." Both are hosts, and their obligations are completely different. This article shows what each of the three genuinely owns, where the handover breaks down, and who to call first.

Who Is Supposed to Fix a Hacked WordPress Site?

The site owner is responsible by default, and everyone else is responsible only to the extent their contract says so. That is the uncomfortable answer, and it is the one your hosting agreement gives.

Responsibility and capability are also different things. Your host has the deepest access and the narrowest obligation. Your agency has the best knowledge of your site and often no security remit. A specialist has the right skills and no standing relationship with your infrastructure.

The system works by contract rather than by fairness. Whoever wrote a document promising to do something is the person who has to do it, and most site owners have never read the three documents that decide this.

Why Does Everyone Point at Someone Else?

Everyone points elsewhere because each party's job genuinely ends before the problem does.

The host's job ends at the platform. Their agreement covers the server, the network, and the other customers on the machine, and it explicitly puts your files and your data on you.

The agency's job ended at launch, or at the last invoice. A build contract covers building. Unless somebody signed a maintenance agreement, security was never in scope.

This problem happens when nobody wrote down who owns security after launch. The site runs fine for two years, so the question never comes up, and then it comes up on the worst possible morning.

What Does Your Host Actually Own?

Your host owns the infrastructure and whatever their agreement says beyond it, which varies enormously between hosts. That variation is the single most important fact in this article.

At one end, Bluehost's Acceptable Use Policy states that services "may be suspended or terminated with or without notice upon any violation of this AUP", and the AUP prohibits "Distributing computer viruses, worms, Trojan horses or other malicious code." A hacked site distributing malicious code is in violation, which is why suspension can arrive before help does.

At the other end, Kinsta includes a hack fix on every plan at no extra cost. In between sit hosts who sell cleanup as a product: DreamHost's Hacked Site Repair starts from 199 USD and InMotion's from 299 USD, both checked on 5 October 2026. Which one you are on is a question with a documented answer, and what your host covers and what it does not goes through how to find it.

What Are the Advantages of Going to Your Host?

Going to your host first is often correct, because they have access nobody else has.

  • Deepest access: They control the server, the file system, the logs, and the mail queue. Nobody else can see all of that.
  • It may be free: Kinsta's hack-fix guarantee costs nothing extra on any plan, which makes it the cheapest legitimate route if you are on it.
  • Server-level visibility: Cross-site contamination and server-level infections are visible to them and invisible to you.
  • Fast on their own layer: Hardware, network, and platform problems get solved quickly because that is their core business.
  • They already have your backups: Whatever retention they offer, they hold it and can restore it.

What Are the Disadvantages of Going to Your Host?

Your host's obligation usually stops where your WordPress install starts.

  • Narrow contractual scope: Bluehost's documentation states the customer is "solely responsible for all files and data sent."
  • Suspension before support: The AUP permits suspension "with or without notice", because their duty is to the whole server.
  • Limited attack coverage: Patchstack reports that traditional hosting defences block only 26% of total vulnerability attacks.
  • No Google work: Clearing a Safe Browsing warning is not a hosting function.
  • Thin backups on some plans: Bluehost documents a weekly backup on a random day that overwrites the previous one, with only one week kept.

What Does an Agency Actually Own?

An agency owns what its contract says it owns, and for most Dubai businesses that means the build rather than the security. The agency designed the site, wrote the custom code, chose the plugins, and handed it over.

That knowledge is valuable during an incident. They know which plugin runs the booking form, which theme files were customised, and what the site is supposed to look like.

What they often do not have is a security remit, an incident process, or anyone on the team whose job is malware. Plenty of excellent agencies are honest about this, and the good ones say so quickly rather than experimenting on your live site.

What Are the Advantages of an Agency?

An agency knows your site better than anyone else, which saves real time.

  • Site knowledge: They know what is custom, what is standard, and what should not be there.
  • Existing relationship: You already have a contact, a contract, and a way to escalate.
  • Design recovery: If pages need rebuilding after a defacement, they can restore the look correctly.
  • Multiple people: Unlike a solo specialist, an agency has cover when one person is unavailable.
  • Continuity: They are still there in two years, which matters for the site's longer life.

What Are the Disadvantages of an Agency?

An agency's weakness on a hacked site is scope rather than skill.

  • Security is usually out of scope: A build contract does not cover incident response unless somebody added it.
  • No incident experience: Many agencies see one hacked site every few years, which is not enough to build a process.
  • Slower on emergencies: Agency workflows run on projects and sprints rather than on hours.
  • Risk of the wrong fix: The common instinct is to restore a backup, which Sucuri warns can reintroduce the infection if the copy was taken while it was present.
  • They may have built the problem: If a nulled plugin or an abandoned theme came from the build, the conversation gets awkward.

What Does a Specialist Freelancer Actually Own?

A specialist freelancer owns the security work itself: finding the infection, removing it, closing the entry point, and dealing with Google. That is the whole job rather than a part of another job.

The specialist case rests on repetition. Someone who cleans infected WordPress sites every week recognises patterns that an excellent generalist sees once a year. They know where backdoors hide, which scanner findings are false positives, and what Google's review queue actually does.

The market benchmark for an attached human with a written commitment is public. Wordfence lists Response at 1,250 USD per year with a 1-hour response time and a 24-hour time to resolution. That is the shape of what you are buying at this end, and the software alternative is compared directly in a plugin instead of a person.

What Are the Advantages of a Specialist Freelancer?

A specialist brings pattern recognition and a single point of accountability.

  • Depth on this one problem: They have seen your infection before, probably several times.
  • Entry-point focus: Sucuri found a backdoor on 49.21% of compromised sites, which makes finding the cause the main skill rather than a bonus.
  • Direct communication: You talk to the person doing the work, with no account manager in between.
  • Google handling: Search Console verification, flagged URL cleanup, and the review request are routine work rather than unfamiliar territory.
  • Flexible speed: A solo specialist can start in the next hour, which an agency pipeline rarely can.

What Are the Disadvantages of a Specialist Freelancer?

One person is one person, and that carries real risk worth naming.

  • Single point of failure: If they are ill, travelling, or unavailable, there is no second person.
  • Capacity limits: A solo specialist can only handle so many emergencies in the same week.
  • Continuity risk: Developers disappear. If the work is not documented, you are left with a site you do not understand.
  • No infrastructure control: They need access from your host, which someone else controls.
  • Verification is on you: Judging a specialist's competence before hiring is genuinely hard, which is the whole subject of red flags to watch for.

What Are the Main Differences Between the Three?

The real differences sit on seven dimensions: scope, out-of-hours response, server access, Google, entry-point closure, continuity, and cost shape.

1. Difference in Scope of Responsibility

A host's scope is the platform and is written to exclude your content. An agency's scope is the build and usually says nothing about security. A specialist's scope is the security work and nothing else.

Nobody's scope covers everything, which is why the site can sit untouched for three days. The fix is to decide in advance who owns security, in writing.

2. Difference in Who Answers at 2am

Hosts have 24-hour support, but for platform problems rather than cleanups. Agencies work business hours on business workflows.

A specialist's availability depends on the arrangement you made. A retainer with a stated response time answers at 2am. A cold enquiry does not, whoever you send it to.

3. Difference in Server-Level Access

Only your host sees the whole server: the mail queue, the logs, the neighbouring accounts. Cross-site contamination is one of Sucuri's five named reinfection risks and it is almost impossible to diagnose without that view.

Agencies and specialists work with whatever access you grant. On a shared host, that is not enough to rule out a server-level cause, which is why the best outcome is usually the specialist and the host talking to each other.

4. Difference in Who Handles Google

Hosts do not handle Google. Agencies usually have not done it before. Specialists do it as routine work.

This matters because the Google side runs on its own clock and its own rules. Google publishes review times of about one day for phishing, a few days for malware, and up to several weeks for hacked with spam, with removal within 72 hours of approval. If nobody owns who talks to Google about the warning, the warning simply stays up.

5. Difference in Entry-Point Closure

Hosts remove the violation so the server is safe. Agencies often restore the site so it looks right. Neither is the same as finding the hole.

Closing the entry point is the difference between a fix and a delay. Google reports that 20% of hacked sites are hacked again within one day, and closing the entry point explains why that figure is the one to judge any provider by.

6. Difference in Continuity If They Disappear

Hosts have the strongest continuity, because they are companies with contracts. Agencies are next. A solo specialist is the weakest on this dimension, and that is a fair criticism of the route I work in.

The answer is documentation and handover rather than reassurance. Written findings, a record of what was changed, and credentials you control mean the work survives the person. If a provider cannot offer that, continuity is a real risk.

7. Difference in Cost Shape

A host is either free or a fixed product. Kinsta includes the fix. DreamHost charges from 199 USD, InMotion from 299 USD, both as one-time fees with 30-day terms.

An agency bills hours or a retainer, usually at build rates rather than security rates. A specialist charges per job or per month, scoped to the site. The whole ladder sits in what each route costs in Dubai.

Where Does the Handover Usually Break Down?

The handover breaks down in four predictable places, and all four are about authority rather than skill.

1. The Host Suspends and the Agency Cannot Reach the Files

The host suspends the account to protect the server, which is their documented right. Bluehost's AUP permits suspension "with or without notice" on any violation, and a site distributing malicious code is a violation.

Now the agency or specialist cannot reach the files to clean them, because the account is offline. The work stops until somebody with the hosting login talks to support, and that person is usually you.

2. Nobody Owns the Search Console Property

Google notes that a hacker typically adds themselves as a property owner in Search Console. That means the attacker may hold a verified claim on your search presence while three legitimate parties argue about the files.

Meanwhile nobody on your side is sure who owns the property. The agency verified it during the build with their own account, that employee left, and the login is gone. Checking and cleaning that owner list is part of the job, and who owns your Search Console property covers how to do it.

3. The Agency Built It and Will Not Touch Security

The agency responds honestly that security is not in their contract, which is usually accurate. They are not refusing to help. They genuinely never agreed to this work.

The frustration is understandable and misplaced. The time to settle this was at launch, with one line in the contract naming who owns security and patching afterwards.

4. Three Parties Hold Credentials and None Hold Accountability

By the second day, the host has the server, the agency has the dashboard, and a specialist has partial access. Everybody has a piece and nobody has the job.

The fix is to name one owner for the incident, give them the access they need, and let the other two support them. One owner, written scope, one clock. Without that, the site stays broken while three competent parties wait for each other.

Who Should You Call First?

Call your host first to find out what they cover, then decide based on the answer. That single question costs you ten minutes and can save you the entire fee.

The question to ask, in writing, is simple: does my plan include cleaning a hacked site, and if not, do you offer it as a paid service. The answer puts you in one of three positions immediately.

When Is Your Host the Right Call?

Your host is the right call when they publish a hack-fix guarantee, and you should use it rather than pay anyone else. Kinsta states that every plan includes one and that its engineers will clean a compromised site at no extra cost.

That is the honest answer even though it costs me work. If you are paying for a host that includes cleanup, you have already bought this service.

Your host is also the right first call for anything server-level: a suspension, a mail queue full of spam, or signs that the infection is spreading between accounts. Those are their layer and nobody else can see them properly.

When Is Your Agency the Right Call?

Your agency is the right call when the damage is to the build rather than the system. Defaced pages, broken layouts, and content that needs rebuilding are agency work and they will do it faster and better than a security specialist.

They are also the right call when the site has heavy custom code, because they know what is supposed to be there. A specialist cleaning an unfamiliar custom build spends real time learning it first.

Ask them one direct question before handing it over: have you dealt with a hacked site before, and will you be finding the entry point. A good agency answers that honestly and sometimes recommends a specialist themselves.

When Is a Specialist the Right Call?

A specialist is the right call when the site has been hit before, when Google has flagged it, or when your host says the hack is your problem.

A repeat infection is the clearest signal. It means the cause was never closed, and closing causes is the specialist's actual job rather than a side task. A Google flag is the second signal, because the review process is its own skill with its own timings.

Before you hire anyone, run the questions. The questions to ask first is the full list, and it works whoever you are evaluating.

How Do You Get Accountability in Writing?

You get accountability in writing by naming four things before work starts: scope, clock, reinfection terms, and access.

Scope means a list, not a label. Files, database, users, scheduled tasks, entry point, Google, hardening. Each item confirmed or excluded explicitly. If you are not sure what belongs on that list, what website security covers sets out every layer a written scope should name.

The clock means a response time and a completion target, with a stated start point. The market measures these differently, so pin it down. DreamHost's turnaround runs "once payment is received", and InMotion advertises 24 and 48 hours while its FAQ says the work typically takes two to three business days depending on when credentials arrive.

Reinfection terms mean a number of days. Thirty is the market standard, and both DreamHost and InMotion use it. Access means a list of what you granted, to whom, and when it gets revoked. Written down, those four items turn three willing parties into one accountable one, and that accountability is most of what WordPress security services actually give you.

Accountable WordPress Security in Dubai by Mohammad Emmon

How Mohammad Emmon Works With Your Host and Your Agency

I work alongside your host and your agency rather than around them. The host has access I do not have, and the agency knows your build better than I will on day one. Fighting that wastes your time.

My part is the security work and the accountability for it. I clean the infection, close the entry point that let it in, handle the Google side, and then keep it clean with hardening and monitoring if you want that. You get a written finding, so the work survives me and your agency can read it. The full scope of that work is on my WordPress malware removal and security service page.

I will also tell you to go elsewhere when that is right. If your host includes a hack fix, use it. If the damage is a broken layout rather than an infection, your agency will do it better. Emmon's own figures, which he confirms before publishing, put his client return rate at 96% across 745+ clients, and those are his own claims rather than independently audited numbers.

Dubai Business and Hospitality Site Coverage

I work with businesses across Dubai and the wider UAE, including hospitality, restaurants, professional services, retail, and online stores. The three-way standoff in this article is something I see most often with Dubai businesses whose site was built by one agency, moved to a new host, and maintained by nobody. The local detail is on my pages for WordPress security in Dubai and WordPress security in Abu Dhabi.

All the work is remote, so nothing waits on travel or office hours. Clients in the UAE, UK, USA, Canada, and Australia get the same approach: name the owner, agree the scope, do the work, document it. That is what hiring a WordPress security expert in the UAE should look like, whoever you choose.

Get a Free Security Check from Mohammad Emmon

The free security check tells you who actually needs to act. I look at what is on the site, whether anything is already inside, who holds your Search Console property, and what your host's position is likely to be. You get a written finding you can forward to your host or your agency.

Message me on WhatsApp or book a call, whichever is easier. If the finding says your host should handle this free, that is what it will say. Contact Mohammad Emmon today for a free security check and find out who really owns the fix on your site.

Free security check

Worried your site is infected?

Get a free security check — I'll tell you if your WordPress site is compromised and exactly what it needs. No obligation.

Related

Take it further.

Mohammad Emmon

Written by

Mohammad Emmon

WordPress Malware Removal, Security, Ongoing Security Monitoring And Website Development

I'm a WordPress malware removal and security specialist — I've cleaned and secured over 10,000 sites. Once a site is safe, I can also build, run and automate the whole thing. Based in Dhaka, working worldwide.

  • 15,000+ sites secured
  • 745+ businesses
  • 96% come back

Worried about your site?

Think your WordPress site is hacked? Let's check it.

Google Business Profile

Find me on the map

Open in Google Maps