How to check your own website: five minutes once a month
You probably know your site isn't new. It works, customers ring, and there's neither the time nor the spare money to rebuild it right now. An old site is like an old car: not shiny, but it runs. Still, when a warning light comes on on the dashboard, carrying on as if nothing happened stops being a good idea.
A site has only a few of those lights, and you can check them yourself in five minutes once a month. Here they are in order: first what stops people calling you, then what happens rarely but costs a lot, and last what you can safely leave alone.
First, what stops people calling
Take your phone and find your site through Google, the way someone who needs to ring you would.
- No warning instead of the page. A grey or red browser screen, or "Not secure" next to the address. A customer doesn't dig into it: they see the warning and leave. In my check of 27,591 Latvian company websites, 9.9% had this: the certificate had expired, was issued for another address, or there was no https at all. Tap the icon left of the address (a settings icon in Chrome, a padlock in Safari and Firefox): "Connection is secure → Certificate is valid" shows the date it runs until. What to do if it has expired is in the article on browser warnings.
- Can they call straight away. The number should be visible without digging through menus, and tapping it should start a call. If it's an image or tucked away on a Contacts page, here is what to fix.
- How fast it opens. If the first screen stays blank for several seconds, someone on mobile data will tap back. What exactly to measure is in Core Web Vitals explained.
If you only have time for one step from this whole article, do this one.
Then, what is rare but expensive
A hacked site usually looks the same as always. Foreign links and text are hidden in the code so that neither you nor your customers notice, but a search engine reads them: it reads the code, not the screen. Google treats hidden text and links as manipulation, and a page can drop in the results or vanish from them for it. People usually find out when a line about a casino appears under their company name in Google. I described what that looks like in the article on invisible spam.
Open your site on a computer and press Ctrl+U (on a Mac ⌥⌘U; in Safari, turn on the Develop menu in Settings first) or right-click → "View page source". Then Ctrl+F and search one by one:
- Gambling words: "casino", "betting", "slots", "poker", if your company has nothing to do with them.
displayand-9999. Search for the short form: code may saydisplay:noneordisplay: nonewith a space,left:-9999pxorleft: -9999px.displaywill have many matches; look at the ones withnonebeside it. On their own these are ordinary techniques: Google allows hiding text for convenience, in tabs for example. But if a hidden block holds links to other people's sites, somebody put them there.src=. Which addresses scripts load from: look at the matches inside<script, whereasyncanddefermay come beforesrc. Your own domain and familiar services such as analytics or maps are normal. An unfamiliar address is a reason to ask your developer.- The page description,
meta name="description". This is the line a search engine shows under the page title. If the text isn't yours, someone replaced it.
A fifth check needs no code: type site:yourdomain.lv into Google. The results are the pages of your site the search engine knows. Titles you didn't write will also be seen by a customer searching for your company name.
The code is long, and almost all of it is harmless. Ask yourself one thing: does this word, address or link have anything to do with my business? One find proves nothing yet: write it down and show it to whoever maintains the site.
If you'd rather not scroll through code, paste it here and the tool will highlight the same four signs. It runs only in your browser; the pasted text isn't sent anywhere or stored.
If the site is on WordPress: two minutes in the panel
Log in to the admin panel. If you don't have a login of your own, ask your developer for an account in your name: it's your site.
- Users → All Users. Click "Administrator" above the list; there's a number next to it. Every name should be a person you know. An unfamiliar administrator means someone has got in; what to do then is in the article on an unknown administrator.
- Posts → All Posts. Look at the Author column and the dates. Look for posts you didn't write, and check the drafts.
- Dashboard → Updates. Core, plugins and themes, inactive ones included. If many updates are waiting, write to your developer: "Please update everything waiting under Updates, and make a backup first."
- Tools → Site Health. The Status tab lists what is critical: outdated PHP, plugins without updates, automatic updates switched off. You can attach that list to the same email.
On Joomla, Drupal and site builders the screens have other names: ask whoever runs the site where the user list and the updates are.
And this you can leave
An old year at the bottom, a dated design, the latest news item from 2019. In my view it spoils the impression but doesn't stop anyone calling. The year at the bottom takes a minute to change, here's how, and it can be made automatic so you never have to come back to it. The rest can wait until there's time and money for a new site.
Five minutes a month is easy to tie to something you already do every month, such as sending out invoices.
Sources
- My check of 27,591 live Latvian company websites, September 2026: 9.9% with a broken certificate or no https. The check was automated and run once, and the certificate was read by a program; how I checked.
- Google Search Central: spam content and hidden text. Hidden text and hidden links are treated as manipulation, including text positioned off-screen with CSS. Breaking these rules can lead to a page or a whole site being ranked lower or omitted from Google Search. Hiding content for usability (tabs, accordions) does not break them.
- WordPress documentation: Users screen, Dashboard Updates screen, Site Health screen.
If something in the code or the panel puzzles you, send me a screenshot and I'll tell you whether it's worth worrying about: write to me.