The CW Corner – When Someone Says Your Contact Form Never Arrived

A small business owner at her desk frowning at a laptop while investigating a missing website contact form messageThere’s a sinking feeling when a customer says, “I filled in your contact form last week and never heard back.” You may search your inbox, check your phone, and wonder what went wrong. Here’s the uncomfortable truth: a contact form can fail silently. Its confirmation message may appear, while the actual message never reaches you. You could go weeks without knowing.

The quickest way to investigate is to follow the message from the form to your inbox. Check each stop in order. That helps narrow down where the message disappeared, without changing settings blindly.

Start with one important difference

When you send an email, your email program sends it through your email provider. When someone submits a website form, your web server handles the sending. That’s a different machine, with a different sending reputation and different rules.

This single difference explains many missing form messages. Your everyday email can work perfectly while your website’s messages fail. The form might show “Thanks, your message was sent,” but that usually confirms the submission process finished. It does not prove the message reached your inbox.

First, check whether the website saved the message

Before searching more mail folders, find out whether the submission was recorded on your website. Many form plugins save entries in the website, even when sending an email notification fails.

Sign in to your website dashboard and open the form plugin’s submissions, entries, or messages area. Check any spam or junk section there, too. The exact names depend on your form plugin.

  • If the customer’s message is saved: The form received it. Focus next on email delivery.
  • If no entry exists: The problem may be with the form itself, its settings, or the submission process.

This simple check splits the investigation in two. Don’t start adjusting mail settings until you know which side needs attention.

If the message was saved, follow its path to your inbox

Check spam, junk, and quarantine

Look in the receiving mailbox’s spam and junk folders. If your hosting provider or business email service offers quarantine, check there as well.

Form messages can look unusual to filters. They may use a generic subject, such as “New submission,” and show the website’s server as the sender. That can make an ordinary customer inquiry look less familiar.

This is a useful check, but it is only one stop in the process. For a wider look at filtering, see why emails land in spam.

Confirm the destination address

Open the form’s notification settings and read the destination address carefully. A single mistyped character can send every inquiry to the wrong place.

Also ask whether the address still belongs to someone who checks it. A former employee’s mailbox or an old address may still be listed in the form settings.

Then check whether the mailbox can accept new messages. A full mailbox may reject incoming mail; our article explains what happens when your mailbox is full.

If the destination forwards messages elsewhere, test that route too. A forwarding rule may be misconfigured, or it may send messages to an address nobody monitors. See Email Forwarding Done Right for more on forwarding problems.

Check the website’s sending setup

The website’s server needs a working way to send mail. Some hosting setups restrict basic mail sending, or the website’s sending settings may have stopped working.

This can happen after an update. A form plugin or PHP (PHP: Hypertext Preprocessor) update might change or break the sending routine. Meanwhile, the form can still display a success message.

Ask your developer or hosting provider whether the website can send mail and whether recent changes affected it. If you see a bounce or error notice, keep it. Our guide to reading a bounce message can help explain what it says.

Check whether the sending server is authorized

Your website’s server is separate from the server that sends your regular email. If your domain’s email records do not authorize the website’s sender, receiving systems may distrust its messages.

SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting, and Conformance) help receiving systems check whether a message is legitimate. Your email provider or web developer can confirm that the website’s sending service is covered.

For a plain-language explanation, read SPF, DKIM, and DMARC explained. The point here is specific: make sure the website’s server is an authorized sender for your domain.

Check the reply-to address

A form email typically comes from the website’s server, not directly from the customer. The customer’s address should usually be placed in the message’s “Reply-To” field.

If Reply-To is missing or set incorrectly, pressing Reply may send your answer back to the website’s server, or somewhere else entirely. You might think you responded, while the customer never receives your reply.

Open a recent form notification and inspect its sender and reply address. If you are unsure where to find those details, ask your developer or email provider. It is a small setting with a big effect.

If no message was saved, check the form itself

When there is no saved entry, start with the form’s own settings. Confirm the form is active, the required fields work, and its submission action has not been disabled.

Try the form as a visitor would. Check whether it submits, whether any error appears, and whether the entry is recorded. If it fails before saving, your developer may need to review the form plugin, its updates, or the website’s server logs.

Avoid changing several settings at once. A careful, single change makes it easier to see what solved the problem.

Test from outside your usual setup

A test from your work email on the same network may not show what customers experience. Use an outside address you control, preferably from a different email provider. If possible, test with more than one address.

Send a real test message with the details a customer might include. If the form accepts attachments, try a small photo. Note the submission time, then check:

  1. Did the form save the entry?
  2. Did the notification arrive, and where?
  3. Does the message show the expected sender?
  4. Does Reply go to your test address?

If the message arrives in one mailbox but not another, the issue may involve how those providers handle it. Share the test time and results with your developer or host. Those details are much more useful than “the form seems broken.”

Make the setup easier to troubleshoot

A dependable setup should leave you a record and make delivery failures easier to spot. Ask your developer about these practical improvements:

  • Send form notifications through an authenticated mailbox using SMTP (Simple Mail Transfer Protocol), rather than the server’s basic mail function.
  • Keep a stored copy of each submission on the website.
  • Set Reply-To to the customer’s email address.
  • Use a clear notification subject, so messages are easier to recognize.

SMTP sends through an authenticated email service instead of relying only on the website’s basic sending method. It does not guarantee delivery, but it provides a more controlled sending path. A stored submission gives you a backup if an email notification goes missing.

Give customers another way to reach you

A phone number or plain email address on your contact page gives customers a second door. Some people do not trust forms. Others may encounter a technical problem or need to reach you quickly.

Keep those details current and monitored. A second contact method can save a customer even when the form is working perfectly.

If a customer already missed a reply

Apologize plainly. You might say, “I’m sorry we missed your message. It looks like it didn’t reach us. Could you email or call me directly so I can help?”

Then follow through promptly. Don’t blame the customer’s computer or insist they did not submit the form. You may not know exactly where the message stopped, and the customer deserves a helpful next step.

Put a real test on your calendar

Test the form once a month using an outside email address. Keep the test brief, and confirm both the saved entry and the email notification. Add the check to your website maintenance routine.

A contact form nobody tests is a hole in the floor you cannot see. A calendar reminder makes it much easier to catch problems before a customer does.

Most form failures happen in a handful of places: the form, the website’s sending setup, the destination mailbox, or the route between them. A real test and a stored copy catch many problems early. Start with the saved entry, follow the message step by step, and ask for help when you reach the technical settings.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail

The CW Corner – Hiring a Web Developer? The Questions That Actually Tell You Something

A small business owner and a web developer discussing a website project across a wooden table, with a laptop and notepad between themHiring a web developeriring a web developer often happens when you are already in a hurry. A website may be down, a previous provider may have disappeared, or a needed change may be overdue.

That first conversation matters. The questions you ask can reveal how the developer works, who controls your website, and what happens when something goes wrong.

Price and timeline are worth discussing, but they only tell part of the story. Here are questions that can help you understand the working relationship before you commit.

Ask how the work gets done

“Who will actually work on my website?”

You may speak with one person during the sales call, then discover someone else is doing the work. That arrangement can be perfectly reasonable, but you should know about it first.

A good answer identifies the people or roles involved and explains how you will communicate with them. If the developer uses subcontractors, ask who manages the work and who is responsible for the result.

You are not asking to inspect an organization chart. You are making sure you know who has access to your site and who can answer your questions.

“What will you need from me, and when?”

A website project often needs your content, images, business details, and feedback. Delays can happen when the developer is waiting for something you did not know you needed to provide.

A helpful answer explains what materials are needed, when they are due, and how approvals will work. They should also be willing to help clarify what you need to prepare.

For example, a service page may require a description of your work, contact details, and a photo. Knowing that early makes the project easier for everyone.

“What would you change about my current site, and why?”

This question reveals whether the developer has looked closely at your website. A useful answer points to a specific issue and explains how it affects visitors or your business.

Perhaps a contact form is hard to find, or important information is difficult to read on a phone. A thoughtful developer should explain the concern without making you feel foolish about the site you already have.

Be cautious if every answer is simply, “You need a complete rebuild.” Ask what can be improved, what should stay, and why.

Ask who controls the important things

“Who owns the website files, domain, and hosting account?”

Your domain is your web address. Hosting is the service where your website lives. The website files and content are separate pieces, too.

Ask whose name and account details appear on the domain registration and hosting account. Ideally, your business controls these accounts, while the developer receives appropriate access to do their work.

A clear answer should also explain how you can sign in, recover access, and see renewal notices. For more background, read Do YOU own your website? and Who owns your domain?.

“Could I move the site to another host or developer?”

You may stay with the same developer for years. Still, you should understand your options if your needs change or the relationship ends.

A reassuring answer describes what can be transferred, what files or access you would receive, and whether any software or services require separate licences. Some website platforms have limits, so ask about those before signing up.

The answer should not make leaving sound like a punishment. If you want to understand the process, see what moving your website to a new host involves.

“Can I talk to two current clients?”

References can help you learn how the developer communicates after the contract is signed. Ask for clients whose projects resemble yours, if possible.

A good developer should explain whether references are available and respect their clients’ privacy. If you speak with someone, ask whether the work matched expectations and how problems or extra costs were handled.

Client references are not the only way to judge a provider. But a real conversation can tell you more than a polished sales page.

Ask what support and pricing really mean

“How do I reach you if the site is down at 8 a.m. on a Saturday?”

This question is not a demand for round-the-clock service. It asks how support works and what the developer considers urgent.

A useful answer explains the available contact methods, normal business hours, and how urgent problems are handled. Ask what counts as an emergency. A broken payment or appointment form may matter more than a minor spacing issue.

The developer should not promise instant help unless they can explain what that commitment includes. Clear expectations now are much better than guessing during an outage.

“What is included in the monthly or hourly rate?”

A monthly fee might cover hosting, updates, backups, support, or a set amount of maintenance. An hourly rate might apply only when you request changes.

Ask what is included, what costs extra, and whether third-party services have separate charges. Request examples, such as adding a staff photo or fixing a contact form.

A good answer separates routine service from additional work. It should also explain how you will approve extra costs before the work begins.

“How do you bill for small jobs?”

A small edit can take less time than a full hour. Ask whether the developer bills by the minute, in partial hours, or with a minimum charge.

A clear response explains the billing unit and how work is recorded. If there is a minimum fee, ask when it applies.

You do not need to haggle over every small change. You do need to understand how the invoice is calculated. The older developer checklist also discusses billing practices.

“Are backups and software updates part of the arrangement?”

Ask what gets backed up, where copies are kept, and who can access them. Find out whether backups include both the website files and its database.

Also ask who handles updates and what happens if an update causes a problem. A good answer describes the routine and explains how restoration works.

A backup is more useful when it can be restored. Learn more in what website backups cover, and what they do not. For ongoing care, see a website maintenance routine you will actually keep.

Notice how they answer

A red flag is not always proof of bad intent. It is a reason to pause and ask for a clearer explanation.

Be cautious if a developer:

  • Refuses to put the domain or hosting account in your business’s name.
  • Will not provide a written scope or quote.
  • Has no phone number or clear way to reach a real person.
  • Pressures you to sign a long contract before answering basic questions.
  • Gives vague answers about who will do the work.
  • Says, “We’ll handle all that,” but will not explain what that means.
  • Offers a price far below other proposals without explaining what is included.

A very low price may leave out important work, support, or maintenance. Compare what each proposal actually covers, not just the total.

Make the conversation easier to compare

Before calling, write a one-page brief. Include what your business does, what you want the website to accomplish, what is currently frustrating, and any important features.

Talk to two or three developers and ask each the same questions. That makes it easier to compare their answers, not just their personalities or prices.

Then ask for the scope and price in writing. The scope should explain what the developer will do, what you need to provide, and what costs extra. Keep the written agreement somewhere you can find it later.

You can also begin with one small paid job before handing over the whole site. For instance, ask the developer to review a form or make a specific update. Notice how they communicate, explain the work, and handle billing.

If you are replacing someone, do not cancel the old arrangement immediately. First, make sure the new person has the needed files and domain access. Confirm that a backup exists and has been tested. Otherwise, you could lose access before the transition is ready.

Choose someone whose answers you can rely on

The goal is not to find the cheapest developer or the fastest promise. It is to find someone whose answers you can hold them to later.

Good questions do not make you difficult. They help both sides understand the work and avoid preventable surprises. A developer who welcomes these questions is usually the right kind.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail

The CW Corner – Hardware Security Keys: The Little USB Key That Stops Phishing

A person holding a small black hardware security key in front of an open laptop on a wooden desk, with a phone and notebook nearbyHardware security keys are small devices that give your important accounts a strong, physical check at sign-in. You plug one into a computer or tap it against a compatible phone. Think of it as a small key that helps prove you are really you.

For most accounts, the security key is a second step after your password. Some services also let you use a key to sign in without entering a password. Either way, it can make fake login pages much less effective.

What is a hardware security key?

A hardware security key is a small device that connects through a Universal Serial Bus (USB) port or communicates wirelessly with a phone. During sign-in, you may need to touch its button or tap it against your device.

The key works with your browser and the service’s sign-in system. It helps confirm that you are signing in to the real website, not a convincing imitation.

Some keys include a fingerprint reader. Others ask you to touch a button. Either style can work well. Choose a method that feels comfortable and suits the accounts and devices you use.

You may also see keys described as supporting Web Authentication (WebAuthn) and Fast Identity Online (FIDO) standards. Those standards let websites and security keys work together for secure sign-ins. Check that the services you rely on support them.

Why does a key stop many phishing attempts?

A password or code can be copied. If a fake website tricks you into entering a password or a temporary code, the attacker may use it on the real account before it expires.

A hardware security key works differently. During sign-in, the browser and key use the website’s identity to check that the request is for the right service. A key registered for your real email provider will not answer a lookalike site pretending to be that provider.

Picture a key cut for one particular lock. A copied key shape may look convincing, but it will not turn the real lock. A security key uses a similar idea, with digital information instead of metal teeth.

This protection is why keys can resist phishing better than codes you type into a webpage. It does not make every account or device invulnerable. Use the key only on websites you opened yourself, and protect your devices, passwords, and account recovery options.

For another passwordless sign-in option, see Passkeys Explained: Signing In Without a Password. To compare common second-step methods, read Authenticator Apps vs. Text Codes: Which Two-Factor Sign-In Is Safer?.

What should you look for when buying one?

Start by checking that the key supports WebAuthn and FIDO standards. Well-known brands make these devices, but focus on compatibility rather than choosing based on a logo.

Consider how you will connect the key. A model with both a computer connector and a phone-friendly option can be useful if you sign in from both. Check your computer and phone ports before buying.

Buy two keys: one for regular use and one as a spare. Store the spare somewhere safe and separate from your everyday key. A backup does not help much if both keys live on the same key ring.

Some keys have a button you touch during sign-in. Others include a fingerprint reader. Either can be a practical choice. Follow the maker’s setup instructions, and keep the key protected from damage or loss.

Which accounts should you secure first?

Start with accounts that could unlock or disrupt many other parts of your life or business:

  • Your email account. Password-reset links for many services arrive in your inbox. That makes email a kind of master key.
  • Your domain registrar. Someone with access may be able to change where your website address points.
  • Your web hosting account. Access could allow changes to your website or its hosting settings.
  • Your bank and payment accounts. Protect accounts that handle business funds or personal savings.
  • Your password manager. It may hold the sign-in details for many of your other accounts.

A password manager can help you use a different password for every service. Learn more in Password Managers: One Key for a Whole Ring of Locks.

If your email account is compromised, the damage can spread quickly through password resets. Our email account recovery walkthrough explains why that inbox deserves special attention.

How do you set up a key?

The exact wording varies between services, but the process is usually straightforward:

  1. Open the service’s official website or app yourself. Avoid starting from an unexpected email link.
  2. Sign in and open the account’s security or sign-in settings.
  3. Choose the option to add a security key, then follow the instructions.
  4. Give the key a name you will recognize, such as “Office key” or “Backup key.”
  5. While you are still signed in, add your spare key in the same session.
  6. Test that both keys work before closing the settings page.

Adding the spare right away matters. You may not remember to do it later, and recovering an account can be much harder if your only key disappears.

If the service offers recovery codes, print them and store them somewhere secure, away from your keys. Treat those codes like spare keys to the account. Do not leave them beside your computer or save them in an inbox that the account itself can unlock.

Can your phone act as a security key?

Modern phones can take part in secure sign-ins. Some can approve a login on another device, while many also store passkeys for accounts that support them.

Passkeys are related to security keys, but they are not exactly the same thing. A passkey is a digital sign-in credential stored on a phone, computer, or supported account service. A physical security key is a separate device you carry and connect when needed.

A phone that receives a text message is not the same protection as a physical security key. Text codes can be intercepted or stolen through phone-number scams. Learn about that risk in our article on SIM swap scams.

What are the trade-offs?

You need to have the key with you when signing in, unless you use another supported method. Some services limit how many keys you can register. Others do not support security keys at all.

Losing every registered key can lock you out. That is why you should set up a spare and save recovery codes before trouble starts. Check each service’s recovery process while you still have access.

A key also cannot protect an account if someone has already gained access another way, such as through an open sign-in session. Keep devices updated, watch for unexpected account alerts, and remove keys you no longer use.

A small-business security step worth planning

If employees or contractors can change your website, pay bills, or access customer information, consider issuing keys to those people. Keep a simple record of who holds each key and which accounts it protects.

When someone leaves, remove their key from the relevant accounts the same day. Treat it like a building key: record who has it, and collect or disable access when their work ends.

For a handful of accounts that could ruin your week if they were taken over, hardware security keys are worth considering. Start with your email, domain, hosting, banking, and password manager accounts. Add a spare, save recovery codes, and ask for help if setup gets confusing.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail

The CW Corner – Moving Your Website to a New Host: What’s Actually Involved

Small business owner at a desk reviewing migration notes next to a laptop while planning to move her website to a new hostMoving your website to a new host can feel like a risky technical project. With a little preparation, it’s usually a series of manageable steps, not a reason to panic.

You might be changing hosts because costs have climbed, support is hard to reach, or your site feels slow. Perhaps you have security concerns, or the developer who managed everything has disappeared. Those are understandable reasons to review your hosting.

But “the grass might be greener” isn’t much of a plan by itself. First, name the problem you want to solve. Then check that the new host can address it. A clear reason helps you compare providers and avoid moving the same problem somewhere new.

Keep your domain name

The decision that matters most is often the simplest: keep the same domain name. Your domain is your web address. Hosting is where your website’s files and related services live. Email is another service, even when it uses the same domain.

These pieces are connected, but they aren’t one thing. In many migrations, you change where the website lives without changing the address customers type into their browsers.

You usually do not need to transfer your domain registration to a new company just to move hosting. Keeping the domain where it is can reduce unnecessary changes. For more on protecting domain access, read why your domain lock matters.

Make an inventory before the move

Before anything changes, write down what your website depends on. You don’t need to understand every setting. You do need a list someone can check.

Include these items:

  • Domain and access: Which company is the registrar? Who controls its login and recovery email?
  • Domain Name System (DNS) records: Where are the current records managed? Ask for a copy of the full set.
  • Email: List mailboxes, forwards, aliases, and whether email is included with your current hosting.
  • Website data: Note the files, databases, and any special configuration your site needs.
  • Secure Sockets Layer (SSL) certificate: Confirm how the new host will provide and install the certificate.
  • Scheduled tasks: Ask whether any recurring jobs run behind the scenes. These are sometimes called cron jobs.
  • Connected services: List payment processing, contact forms, newsletters, analytics, bookings, and other outside accounts.
  • Paid themes and plugins: Record their names and check whether licences are tied to the old host or a particular account.

A hosting control panel may show some of these services. If you’re unsure where to look, see what your hosting control panel actually does. A simple inventory can prevent a small forgotten setting from becoming a very inconvenient surprise.

Take your own backup first

Before anyone touches the live site, make a full backup and copy it somewhere you control. Ideally, keep it somewhere separate from both hosting accounts.

Don’t rely only on the new host’s migration tool. Those tools can be useful, but your own copy gives you another way back if something goes wrong. Check that the backup includes both the website files and its database.

Ask how the backup can be restored, too. A backup is much more reassuring when you know it can actually be used. Our guide explains what website backups cover, and what they don’t.

Test the new copy before changing DNS

Ask the new host or developer to provide a temporary or preview address. This lets you inspect the migrated website before visitors are sent to it.

Check more than the homepage. Try important pages, images, logins, contact forms, and any checkout or booking steps. Forms may look fine but fail to deliver messages. A checkout may load but not complete correctly. Images might be missing because their files didn’t make the trip.

Think through a real customer visit. Can someone find a service, fill out your form, and receive a useful response? Find problems on the private copy, not after the public switch. If testing could trigger real orders or messages, ask how to avoid duplicate notifications or charges.

Lower the DNS timer ahead of time

About a day before the planned switch, ask whoever manages your DNS to lower the records’ time to live (TTL) value.

TTL is a cache timer. It tells internet services how long to remember where your website lives before checking for updated directions. A shorter timer can help more visitors pick up the new server sooner after the change.

This step doesn’t move the website or guarantee an instant switch. It simply reduces how long some services may keep using older directions. If you’re unsure which records to adjust, ask your host or developer. Avoid changing unrelated records.

Point the domain to the new server

When the new copy is ready, the person managing DNS changes the relevant records so they point to the new server.

For a while, some visitors may reach the new site while others still see the old one. That can happen because internet services update their stored directions at different times. It’s usually temporary.

Keep this period in mind if your site accepts orders, bookings, or other information that changes often. Ask your developer whether new activity needs to be paused or copied over during the switch. Don’t assume both copies will automatically stay in sync.

Give email special attention

Email is the part people often forget. Mailboxes, saved messages, forwards, and aliases do not always move with the website. If you use hosting-based email, the mail service may be changing too. If your email uses a separate provider, it may need to remain untouched.

Before the switch, confirm which company hosts each mailbox. Ask who will recreate the accounts, whether existing messages will be copied, and how to check both sending and receiving. Include shared addresses such as info@ and addresses that forward to staff.

Mail-related DNS records need careful handling. Mail exchange (MX) records direct incoming email. Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting, and Conformance (DMARC) records help other providers verify email sent from your domain.

If these records are missing or copied incorrectly, messages may fail or land in spam. Ask for the existing email-related records to be copied exactly unless your email provider gives different instructions.

Losing access to a working mailbox during a website move is one of the most common self-inflicted problems. Confirm the email plan before the switch, not after an important message goes missing.

Keep the old host as a fallback

Don’t cancel the old hosting account as soon as the new site appears to work. Keep it available while you check the new setup and confirm that nothing still depends on it.

Give the new site time to run cleanly for a couple of weeks before cancelling the old service. The right timing can depend on your setup, so ask your host or developer what they recommend.

Check the site after the switch

During the first days, test the parts your customers rely on:

  • Submit forms and confirm messages arrive at the right address.
  • Check logins, images, and important pages.
  • Test email sending and receiving from each relevant mailbox.
  • Review notices in Google Search Console, if you use it.
  • Visit the site using its secure address and check for browser warnings.

Your site should show a working padlock and certificate on its secure pages. If you see a warning, contact your host or developer rather than telling visitors to ignore it. Learn more in our plain-language guide to the SSL certificate and padlock.

If something looks wrong, record what you saw and when. Our calm first-hour website outage checklist can help you gather useful details before contacting support.

Keep a record and ask clear questions

Write down what changed and when. Keep the important logins and provider details together in a secure place, with access for the right person in your business.

If your current developer holds the keys, request a written handover of the domain and hosting accounts before you start. You should know who controls each account and how your business can regain access.

Finally, ask the prospective host what its migration help actually covers. Does it include email? Testing? DNS changes? Fixes if a feature fails? Clear answers make it easier to plan a calm, careful move. You don’t have to do every technical task yourself, but you should know what is being moved and who is responsible for each piece.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail

The CW Corner – Your Website Was Hacked: A Step-by-Step Recovery Plan

Woman at a wooden desk looking worried at a laptop showing a red security warning about her website

A website hacked warning can turn an ordinary workday into a stressful one. Take a breath: a hacked site is a fixable problem, not the end of your business. Don’t delete the site or wipe everything in a panic. First, preserve what you have, then work through recovery in order.

How you might discover a hack

Sometimes Google shows a warning beside your website in search results. Your hosting provider might email you about suspicious activity. Or a customer might say your site sent them somewhere unexpected.

Other clues can be less obvious: unfamiliar administrator accounts or files, pages you never wrote appearing in search results, or a site that suddenly feels slow. Some hacks are silent. You may hear about the problem from someone else before noticing anything yourself.

Google’s guide, How do I know if my site was hacked?, explains that harmful changes can be hidden from site owners. So, a normal-looking homepage is not proof that every page is clean.

Step 1: Take a snapshot before changing anything

Before you start cleanup, ask your host or developer to save a full copy of the website files and a separate copy of the database. The database holds your posts, pages, settings, and other site information.

Write down the exact date and time of the snapshot. Keep this copy separate from the live site, and label it clearly as a snapshot of the site as found. Do not treat it as a clean backup.

Why bother keeping a copy of a compromised site? It can help show what changed and when. It may also help a technician identify how someone got in. A backup created after the break-in can carry the problem forward, so don’t restore it as if it were known-good.

For more on what backups contain, read What Website Backups Actually Cover (and What They Don’t).

Step 2: Close the way in

Once the snapshot is safely kept, change the passwords connected to site access. This includes your hosting control panel, WordPress administrator accounts, file transfer accounts, and database.

File Transfer Protocol (FTP) and Secure File Transfer Protocol (SFTP) are methods for accessing website files. If you use either, change its password too. Coordinate the database password change with your host or developer, since the website may need updated settings to connect afterward.

Sign out active sessions where you can. Review the list of WordPress administrators and hosting file transfer accounts. Remove any account you do not recognize, but record its details first.

Make password changes from a clean, trusted device. If an account or computer may also be compromised, ask a qualified technician for help before entering new credentials.

Step 3: Find the entry point honestly

Cleanup is not complete if the way in remains open. Common causes include outdated WordPress software, plugins, or themes; weak or reused passwords; and stolen logins from a phishing page or infected computer.

A compromised account on shared hosting can also create problems for neighboring sites. Your provider can help investigate whether the hosting environment is involved.

Look for evidence with your host or developer. That may include unfamiliar accounts, unexpected files, unusual site changes, or activity in available logs. A log is a record of events on your website or server.

Don’t settle for removing the strange page you can see. The visible symptom may be only one sign of a deeper problem. Our older article, Best Practices for Mitigating Website Hacks, covers ways to reduce the risk of another incident.

Step 4: Choose between a clean restore and cleanup

The right recovery method depends on what happened and what backups are available. If you have a verified, known-good backup from before the intrusion, restoring it may be the clearest route.

But first, close the entry point. Restoring an old copy without fixing the cause can simply reopen the same hole. Check that the backup is trustworthy and does not include the attacker’s changes.

If no suitable backup exists, a qualified professional may need to clean the site in place. This means inspecting and repairing the files and database that make up the current site. Malware can hide in places a basic scan misses, and injected content may live in the database, not just website files.

Google’s Security issues report guidance also recommends fixing the issue throughout the site, not just on example pages. If the work is beyond your comfort level, get help. Guessing at unfamiliar code can make recovery harder.

Step 5: Request removal of Google warnings

After the site has been cleaned or safely restored, check Google Search Console’s Security issues report. It may identify examples of affected pages and explain what Google detected.

Fix all the listed issues, then request a review through the report. Describe what you found and what you changed. Google needs to review the site before removing its warning.

A website that looks normal to you may still have a warning in Google results or browsers. The warning will not necessarily disappear just because the site appears fine now. Google’s review process can take time, so check the report for updates.

If you need an introduction, see our guide to Google Search Console.

Step 6: Tell customers plainly

If customers may have seen redirects, suspicious pages, or a browser warning, send a short, honest note. Silence can leave people confused and make them wonder whether you know about the problem.

For example:

We recently discovered unauthorized changes to our website. We have secured the site and are investigating how the changes occurred. If you visited during this period and entered information, please contact us using the details below. We’ll share relevant updates as we learn more.

Adjust this wording to match what you know. Don’t claim customer information was exposed unless that has been established. Don’t blame an unnamed “third party” as a way to dodge responsibility. Be clear about what happened, what you did, and what customers should do.

Step 7: Report the incident where it matters

Tell your hosting provider about the intrusion. Share relevant details and ask whether they see activity affecting your account or hosting environment. Depending on what happened, you may also need to contact your payment provider, insurer, or other relevant reporting channels.

If customer data or payment details might have been exposed, this becomes a different conversation. Notification and legal duties can depend on the information, location, and circumstances involved. Get qualified legal advice rather than guessing about what you must do.

Step 8: Reduce the chance of a repeat

Once recovery is underway, keep future care practical and manageable. Keep WordPress, plugins, and themes updated. Use unique, strong passwords and two-factor authentication (2FA) for administrator access.

Remove plugins and themes you no longer use. Keep regular backups in a separate location, and test a restore before an emergency. For more prevention guidance, see our article on mitigating website hacks.

The business cost of a hack

A hack can cost more than cleanup time. Customers may hesitate to visit or submit a form. Search warnings can interrupt new enquiries, and your staff may spend valuable hours answering questions instead of serving customers.

That is why the awkward customer email is often cheaper than silence. A clear update gives people a reason to trust your next message. A site you cannot restore to a known-good state can also cost far more than a sensible backup routine.

Recovery is easier when you know who to call, where your backups live, and what they include. Ask your host or developer those questions before a crisis, not while one is unfolding.

Work through the steps, and ask for help

A website hack is upsetting, but you do not have to solve everything at once. Preserve a snapshot, close the way in, investigate the cause, and choose a careful cleanup or restore.

Write down what you do and when. Get help early rather than guessing, especially if you cannot confirm the site is clean. A calm, documented recovery is a much better plan than a rushed wipe.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail