Own your website, domain, and logins again.

No. Recovery depends on the provider and on the proof you have that the business is yours. Registrars, hosts, Google, and website builders each have their own process and their own rules. I follow those official processes with your authorization, and I do not try to get around them. Some accounts cannot be recovered. When that happens, we open a new account in your name, rebuild what we can, and I tell you plainly what will not carry over.

No. They are all good tools, and each one is fine for a small business site. The problem is not the tool, it is not owning the account. Often the fix is to get the existing account, or the site inside it, into your name and keep using it, when the provider allows that. We only switch platforms if the current one cannot do what you need or the site cannot be moved to you.

We ask in writing first and stay polite. If they do not reply, we use the provider's own recovery process with your proof of ownership. If they refuse and say the domain or site belongs to them, that is a legal question, and I will tell you to talk to a lawyer before we go further. I never threaten anyone or log in to an account without permission.

The plan is to avoid that. The old site stays live until the new setup is checked. Before anyone touches DNS, I copy every existing record, including the ones that make your email work, so nothing gets left behind. DNS changes can take time to spread, so I make them at a quiet time and test email before and after.

Yes. First we stop the damage: change every password, remove logins nobody recognizes, and take the site offline for a moment if it is sending visitors somewhere bad. Then I restore a clean backup or remove the bad code, update the site software, and ask Google to review the site if it flagged it. I tell you what I found and what likely let them in. Cleanup is priced on its own, agreed before I start, and I cannot promise it never happens again.

Because some steps wait on the provider. A Google ownership request, a registrar's recovery review, or a domain transfer each has its own steps and waiting periods. For example, under ICANN's current transfer rules, changing the owner details can lock a domain against moving to a new registrar for 60 days (some registrars let you opt out first). ICANN is updating those rules, so I check what applies to your domain at the time. Often the domain does not need to move at all: it can stay with its current registrar, in an account in your name. I tell you which pieces are waiting and on whom.

It depends on the provider. Useful things include your business registration, invoices or card statements that show you paid for the domain or site, access to the business email or phone on the account, and your ID. We gather what you have on day one, before any request goes out.

No. Accounts end up under your email, with two-factor on your phone or an authenticator app. If I need access for later work, you add me as a user you can remove at any time. The who-owns-what sheet lists accounts and login emails, never passwords. A password manager is the right place for those.

It depends on how many accounts are involved and whether we fix the current site or move it. We agree on the scope and the price before work starts. If you only need one password reset, I will say so on the intro call and point you to the provider's own help page.

Yes. Most of this work happens online, in English or Spanish. I can also meet Tampa-area owners in person when it helps to sit down and go through the accounts together.