Question 1

How HealMySite works

Accepted Answer

One WordPress task, US$25, and you only pay if we complete and verify it. HealMySite completes one clearly-described WordPress task for a fixed US$25. Every task runs through the same six steps: Describe the task — tell us the one change you want, with the exact wording where relevant. Check My Connection — we check your site is reachable and that the change is one we can automate. Authorize US$25 — we place a hold on your card. Nothing is captured yet. Submit access — you provide a WordPress Application Password through our encrypted vault. We make the change — our automation applies exactly the change you asked for. We verify, then charge — we re-check your live site. Only if the change is confirmed do we capture the US$25. If we cannot complete or verify the change, the hold is released and you are not charged.

Question 2

What we can and cannot automate

Accepted Answer

What each of our five services actually does, and where the line is. We are deliberately narrow: every task we accept is one we can complete and prove on your live site. Here is what that covers today, by service. Fixing a broken site: Recover a site that is down because of a plugin — we find the one at fault and disable it. Our rescue channel reaches your site even when a fatal error has taken the whole WordPress API down with it. We read the error your site already recorded, so the cause is evidence rather than guesswork. Every plugin we switch off is put back automatically if it was not the cause, so your site is never left half-disabled. Cleaning malware: Core files compared against WordPress's own published checksums, and plugin and theme files against what their authors actually published. Files that were ADDED rather than changed are found too — a dropped backdoor does not modify anything, so a checksum comparison alone would never see it. Your database checked for the hiding places a file clean always misses: unexpected administrators, hidden settings, injected scripts, leftover scheduled tasks. An executable file found where one should never be is moved out of reach and proven gone. Anything we move is moved, never deleted, so you can always get it back. Making a site faster: Before-and-after measurement of your server's response time and page weight, plus real visitor metrics where Google has them for your site. A ranked explanation of why it is slow — missing page cache, images without dimensions, render-blocking scripts. No charge unless the measurement actually improved. Changing one thing on your site: Replace exact text on one page or your homepage — give us the exact old and new wording. Replace exact text in your site footer (block themes only, e.g. a "Powered by" credit). Change a link's destination, or where one menu item points, or rename one menu item. Add a social link (X, LinkedIn, Facebook, Instagram, YouTube, TikTok) to your footer. Change your site title and/or tagline, rename a page, publish or unpublish a page. Open or close comments on one page, or delete comments already flagged as spam. Set the alt text on one image, or point one old URL at a new page (a 301 redirect). Domain, SSL and email is a free read-only check: we report what is wrong and what to change, and make no changes ourselves. What we do not do: full redesigns, multi-page projects, migrations, custom code or plugin development, full server forensics, cleaning unrelated sites in a shared hosting account, or rebuilding a slow theme. If your request is outside what we can complete and verify, we tell you before any payment is authorized — and you are not charged. The fastest, most reliable results come from naming the exact outcome, e.g. replace "Call us today" with "Book online".

Question 3

How to write a request we can complete first time

Accepted Answer

Be specific about the page and the exact wording. Our automation copies the exact text you give us, so precision gets your task done faster. Good examples: On the homepage, replace "old text" with "new text". Change the site title to "Acme Plumbing". In the footer, change "Powered by WordPress" to "Powered by Acme". Rename the menu item "About Us" to "About". Deactivate the "Hello Dolly" plugin. Close comments on https://yoursite.com/contact/ Less useful (we will ask you to narrow it): "make my homepage look better", "fix my SEO", "speed up my site". For anything involving a specific page, include the full page URL — it lets us target exactly the right page.

Question 4

I have several problems — how does that work?

Accepted Answer

Each issue is its own US$25 verified task; we can split them for you automatically. Each US$25 order covers one verified change. If you describe several separate issues, we detect that and offer to split them into separate tasks — for example three issues become three tasks at US$25 each. Each task is then handled completely independently: its own connection check, its own authorization, its own verification, and its own charge. That means you only pay for the tasks we actually complete and verify. If two succeed and one cannot be completed, you are charged for two. In your task list, tasks that came from one order are grouped together under a single heading so you can see them as one order.

Question 5

What "Check My Connection" does

Accepted Answer

A read-only safety check before any money is authorized. Before we ask for any payment we run a read-only check on your site. It confirms that: Your site is reachable from the internet. It is a WordPress site. A firewall or security plugin is not blocking us. The specific WordPress surface your task needs (a page, your menu, settings, your footer) is available to work with. If this check does not pass, we do not start an authorization and you are not charged. The message on your task explains exactly what we could not confirm. Common causes: the site is behind a firewall or under maintenance, it is not actually WordPress, or the change you asked for needs a surface your theme does not expose (for example footer text on a classic theme, where the footer lives in theme code we cannot safely edit).

Question 6

How to create a WordPress Application Password

Accepted Answer

The safest way to give us access — revocable, and never your login password. We never ask for your normal WordPress login password. Instead you create an Application Password, which you can revoke at any time without changing your own login. Log in to your WordPress admin. Go to Users → Profile (or Users → All Users → your user). Scroll to "Application Passwords". Enter a name such as "HealMySite" and click "Add New Application Password". Copy the generated password (it looks like: xxxx xxxx xxxx xxxx xxxx xxxx) and paste it into HealMySite along with your admin username. Once your task is finished you can delete that Application Password from the same screen. We also purge the stored credentials automatically when a task closes. If WordPress does not show an "Application Passwords" section, your site is not served over HTTPS or a plugin has disabled the feature — both are fixable by your host.

Question 7

How your access is stored and protected

Accepted Answer

Encrypted at rest, used only for your task, then purged. Access you submit is encrypted immediately using envelope encryption (a unique key per submission, itself encrypted with a key held only in our server environment). It is never written to logs, events, or support tickets in plain text. The credentials are used only to perform the specific change you approved, and only against your own site. All of our outbound requests are restricted to public internet addresses over HTTPS. When your task closes, the stored secrets are purged automatically. You can also revoke the Application Password yourself at any time from WordPress.

Question 8

When am I charged?

Accepted Answer

A hold at authorization; the charge only after we verify the change. Authorizing a task places a US$25 hold on your card. That is not a charge — no money moves at this point. We only capture the US$25 after our automation has made the change and independently verified it on your live site. You are not charged if: The connection check does not pass. The change is not one we can automate. The requested change was already in place, so there was nothing to do. The automation cannot complete the change, or verification does not confirm it. You cancel before we start work. In those cases the hold is released. Depending on your bank, a released hold can take a few business days to disappear from your statement.

Question 9

My task says "Already up to date"

Accepted Answer

The change was already in place — nothing was altered and you were not charged. This means we checked your site and the exact change you asked for was already present — for example the title was already the value you requested, or the text had already been updated. We deliberately do not make or charge for a change that would have no effect, so nothing was altered on your site and the hold on your card is released. If you expected something to change, it is usually because the wording did not match exactly. Start a new task with the precise current wording and the new wording you want.

Question 10

What if your work breaks my site?

Accepted Answer

We save a restore point before we touch anything, and you can put your site back. This is the fairest question to ask before letting anyone near your site, so here is the whole answer. Before we change anything, we save a restore point. It happens the moment your site confirms our plugin can reach it — before any of our work begins — on every task, not only the risky ones. A restore point holds: The content we might touch — your posts and pages as they were. The files that could not be downloaded again from anywhere else, such as your wp-config.php and your uploads list. A fingerprint of every plugin, theme and core file, so we can tell you exactly what changed. It deliberately does not copy WordPress core, plugins or themes published on wordpress.org. Those are already available from their authors byte-for-byte, so copying them would spend your bandwidth duplicating something nobody can lose. If something looks wrong afterwards, you can open your task and: See exactly what changed, file by file, compared to the restore point. Undo our changes. Put back individual pages you did not want altered, one at a time rather than all or nothing. Download the restore point itself, so you hold your own copy. Two honest limits. Restoring files does not roll your database back, so anything written since — a new order, a new comment — stays. And we do not restore users, comments or orders, because someone asking for their About page back has not asked us to touch any of that. The restore point is encrypted with a key unique to it, held for 30 days, and copied to a second machine so one failure cannot lose it. We ask you to approve deleting it once your task is done; if you never answer, it is deleted automatically when the 30 days are up. We also check our own restore points regularly by opening them, because a backup nobody has ever opened is a promise rather than a fact.

Question 11

Can I cancel a task?

Accepted Answer

Yes — any time before we start making the change. You can cancel a task from your task list at any point before our automation begins making the change. Cancelling releases any authorization hold and closes the task with no charge. Once the automation has started applying a change we do not cancel mid-way, because stopping half-way could leave your site inconsistent. If something looks wrong at that point, use "Contact support" on the task and we will look into it.

Question 12

My task says "Needs attention"

Accepted Answer

Automation could not finish it. You are not charged, and reporting it is one click. This means our automation could not complete or verify the change safely, so it stopped rather than risk your site. The authorization is released and you are not charged. Use the "Report this issue" button on the task. It opens a support request with the task's details — task number, your site, the current state, and what went wrong — already attached, so you do not need to explain the technical side. Common causes: WordPress rejected our access, the exact text we were asked to replace was not found (or appeared more than once, making the change ambiguous), or your host blocks the WordPress API.

Question 13

"WordPress did not accept the access" or the host blocks the API

Accepted Answer

Usually a wrong password type, or a host stripping the authorization header. There are two different causes and the message on your task tells you which one it is. 1. The credentials were rejected. Make sure you used an Administrator username plus an Application Password (six blocks of four characters), not your normal login password. Re-submit access from your task. 2. Your host is blocking the authorization header. Some shared and sandbox hosts strip the HTTP Authorization header before WordPress can read it, so WordPress never receives the Application Password at all. This must be fixed on the hosting side — usually by enabling "CGIPassAuth" or adding a SetEnvIf Authorization rule in .htaccess. Your host's support team will know it. Once that is in place, re-submit access. In both cases nothing was charged.

Question 14

The free Site Check

Accepted Answer

A read-only report on your site — no account, no charge. The Site Check at /site-check runs a free, read-only look at your public site and reports on reachability, basic SEO signals, obvious security exposure, and broken links. It never changes anything and needs no account or payment. When it finds something worth fixing you can carry those findings straight into a task — we pre-fill the description for you. It is a starting point, not a full security audit: it only sees what any visitor can see from outside your site.

Question 15

What happens when you contact support

Accepted Answer

Your first reply is usually automatic and clearly labelled. Reply to it and a person takes over. When you open a support ticket, HealMySite looks at your ticket straight away rather than leaving it in a queue. Before answering anything it gathers the facts: your recent tasks and what happened on each one, step by step a read-only check of your site — whether it responds, whether it looks like WordPress, and whether the WordPress API is reachable the help articles that match what you described If your question is a straightforward one — how something works, or what to do about site access — you usually get an answer within a couple of minutes. That first reply is sent automatically and says so at the bottom. Nobody read your ticket personally before it went out. Anything to do with money, or anything where the evidence does not clearly explain the problem, is never answered automatically. A person reviews it, and they can see everything that was gathered plus the suggested answer before they reply. You can always reply to any message on your ticket. A reply always reaches a person, and once a person is involved the automatic answers stop. What we never do automatically: charge you, refund you, release a hold, retry a task, or change anything on your site. Those are decisions a person makes.

Help & Support

Getting started

Your tasks

Access & security

Billing

Troubleshooting