Your Website, Protected · No. 29

Someone else is running your website: the first hour

A strange page or a wrong number on your site is not the moment to start deleting. Here is the first hour in a fixed order, and the note to hand whoever fixes it.

Three rounded red bars rising inside a pale pink circle, with a dot grid and small yellow and blue dots on a light background.

A customer texts you a screenshot of your own website. It shows a page you never made, or a phone number you have never seen, and the message says "is this still you?" You are on a job with your hands full, and the first thing you feel is the urge to fix it right now.

If your website is hacked, spend the first hour stopping the damage and writing down what you see before anyone deletes or rebuilds anything. Do it in order: record, reach the host and the builder, change the logins you control, put up a holding page, then plan the rebuild.

The first hour, short version

  • Record first: dated screenshots and a plain note, before anything changes.
  • Reach your host and whoever built the site, in writing.
  • Change the logins you control.
  • Put up a holding page or take the site offline, then plan the rebuild. This order is our advice.

Stop the damage before you fix anything

Stopping the damage means keeping the problem from spreading or getting worse while you figure out what happened. That usually means changing nothing on the site itself yet, so the evidence stays intact. Your first moves are small and outside the site: a few screenshots, a note of the time, and a message to the people who can act.

The obvious first move is to start deleting the odd pages, or to call a developer and say "just rebuild it." In our view that is the wrong first move. Deleting wipes out the only record of what changed, and a rebuild on top of an unknown problem can bring the same problem back. The first hour is about stopping the damage and writing down what you see. Everything else can wait for the second hour.

The first urge

  • Delete the odd pages
  • Ask for a rebuild right away
  • Wait and hope it clears up

The first hour

  • Screenshots and a dated note
  • Host and builder told in writing
  • Logins changed, holding page up

How it happened can wait. If you want that story later, there is a plain guide to the usual ways in and a note on why a scary headline may not be about your platform. When a headline names a flaw, the first question is whether your site runs that part, and an owner who has written down what the site runs on can answer it in a minute.

Write down what you see

Take screenshots and write a dated note before anything changes. Capture the strange page, the wrong phone number, the address bar and the time you looked. Whoever fixes the site will want exactly this, and it is the one thing you cannot recreate after the pages are deleted.

The table below is an invented example of the note to hand whoever fixes the site.

An example incident note with made-up entries. Yours holds what you saw.
FieldExample entry
First seenJust after lunch, when a customer texted me
Told byA customer, by text, with a screenshot
PagesHome page and contact page
DevicesMy phone and a friend's laptop
Changed sinceNothing yet
Host and builderThe names of both, if I know them

Check more than the home page. Open the site on your phone, then on another device that has never visited it, and try a search for your business name. Look at each one and write down what you see before you move on. Note anything odd: pages you do not recognize, a redirect that sends you elsewhere, a warning message. Do not click anything on the strange pages, and do not enter a password on them. If you have Google Search Console set up, a look at its messages is worth a minute.

Put a copy of the note in an email to yourself as well, so the time stamp is on record.

What you might see, and how to capture it
  • Strange page On a small phone A page you never made
    Strange page Check it yourself Screenshot it with the web address showing
  • Wrong number On a small phone A phone number that is not yours
    Wrong number Check it yourself Screenshot it and note which page it was on
  • Redirect On a small phone Tapping a link sends you somewhere else
    Redirect Check it yourself Write down the page you tapped and where you landed
  • Anything else On a small phone Something else that looks off
    Anything else Check it yourself Screenshot it and note where you were

Four things worth capturing, and one way to capture each.

Keep your notes somewhere you can open from a phone, because you may be on a job when it starts. None of this needs a technical background, only a notebook and a few calm minutes.

If you cannot tell whether something is wrong, write it down anyway. A strange page that turns out to be harmless costs you one line. A missing detail can cost the person fixing it an hour, and they may not be able to ask you while you are on a job. Do not try to guess the cause. A note that says what you saw is worth more than a theory about why.

The report below is an invented example of what to list from your checks.

Example

An example of what to list from your checks

Page Size Result
Home page Phone screen Fail
Contact page Phone screen Fail
Home page Laptop screen Pass
An example with invented pages. Pass means it looked normal and fail means it showed something wrong. Yours lists what you saw.

Reach your host and whoever built the site

Contact both, in writing, as soon as your note is done. The host may be able to restore a clean copy or lock the site down, and the builder knows how it was put together.

Write the message once and send it to both, so neither is guessing. Say what you saw, attach your screenshots, and ask two questions: is there any change you did not make, and can the site be put in a safe state while it is checked? Keep the tone calm and factual. If you cannot find who built the site, search your old emails for the first message about the project, since that thread usually names them.

Who you reach, and what each can do

  • You, on the job

    Take the screenshots, write the note, send one message

  • Your host

    May be able to lock the site or restore a clean copy

  • Whoever built it

    Knows how the site was put together

While the site is in trouble, customers still look for you on the map. Google Business Profile is the map listing for your business, and in our view it is where people can still find your real number while the site is down. Open it and look for edits you did not make. If the listing needs tidying afterward, this setup guide for service area businesses gives the order.

Change your logins, then put up a holding page

Change the passwords you control: your email, your host and the site's own login. Use a new, long, different password for each, and turn on a second check if the service offers one. Do this from a device you trust. Then ask the host or builder to put up a plain holding page, or take the site offline, so customers stop seeing the strange version.

The first hour, in order

  1. Record

    Dated screenshots and a plain note, before anything changes.

  2. Reach

    One written message to your host and to whoever built the site.

  3. Change logins

    Your email, your host, then the site.

  4. Holding page

    A plain page or the site offline, so the strange version is gone.

  5. Plan the rebuild

    Only after the first four are done.

Start with your email, because if it can reset your other logins, it is the one to secure first. Then change your host login, then the login to the site itself. Write down what you changed, and when, as you go. If a login will not accept your old password, tell the host at once and say so in your note.

A holding page is better than a strange site, and it takes the pressure off the rest of the hour. If the host or builder can do only one thing quickly, ask for that. Share the new passwords by phone or a password manager, never by text or email.

Plan the rebuild only after the site is safe

Once the site is offline or on a holding page, and your logins are changed, you can decide how to rebuild. A cleaned copy of the same site and a fresh build are two different jobs, and the person fixing it should say which one they recommend and why. Ask for the reason in plain words before you agree.

Before the site goes back up, ask to see proof. A site approved on a laptop has not been proven at phone size, and your customers may be on phones, so ask for a phone test of the call button and the pages that matter. In our view the builder should pass a pre-launch check and show you the result before you approve anything. Ask, too, who will have access afterward and how you will know if something changes.

Keep your note going after the site is back. Write down what was found, what was changed and who did it, so the next person to look at the site starts with facts instead of guesses. Check your phone, your Business Profile and your Search Console messages once more a few days later, and again after a while. A problem that came back is easier to spot when you know what normal looked like. A dated note, a clean list of logins and a host you can reach by phone put you ahead of where you were when the first text arrived.

Stop the damage and write down what you see before anyone deletes or rebuilds anything.
Our rule for the first hour

If you would rather have a site built to be checked, with a pre-launch audit the builder must pass and show you, our web design service is the place to start. The better use of the first hour is the one you spend before anything goes wrong: write down what your site runs on, who your host is and who built it, and keep that note where you can reach it from a phone.

Your first hour

All done

Talk to Offer before you decide anything.

You'll talk with Offer, not a sales rep. A short call, no pitch deck.

Talk to Offer

This post was drafted with AI tools from our own project records, anonymized, and checked by us before it published. Read our editorial standards.

Related Articles

Want to talk through your marketing?

Tell us where things stand and we'll tell you plainly what we'd do next.