Do I need to monitor sites that have no SEO or ads budget?

A lighter setup is usually enough: uptime, SSL and domain expiry, and Search Console emails. Those failures take the site offline or show browser warnings, which small business clients notice even when they don't care about rankings.

Should the client or I own the Search Console property?

The client should own it, with you added as a Full user. If the relationship ends, they keep the data and history, and removing your access is a single step in Users and permissions.

Is a staging site worth monitoring too?

Usually not for indexing, because staging should be blocked from search engines on purpose. The useful check is the opposite: make sure the staging robots rules and noindex tags don't reach production when the site is deployed.

How should I tell a client that monitoring found a problem they caused?

Describe what changed, when it was detected and the effect, without assigning blame. A short message with the affected URL and the fix you applied keeps the conversation about the site rather than about who clicked what.

Can I monitor client sites I don't maintain myself?

Yes. Checks of robots.txt, sitemaps, tags and page source only need the public site, so you can watch sites handled by another developer. Search Console data still requires the owner to grant you access.

← Back to the blog

Website Monitoring for Freelancers: A Setup That Scales

Website monitoring for freelancers is about catching the problems on client sites that you would otherwise hear about from the client first. If you look after somewhere between one and fifteen sites on your own, you can monitor client websites with a mix of free tools and a short weekly routine, and only pay for automation once that routine starts slipping.

Website monitoring for freelancers: the minimum setup

Before anything else, make sure every client site sits in a Google Search Console property you can access. A Domain property (verified through a DNS TXT record) covers every subdomain and both http and https, which saves you from missing issues on a www or shop. version nobody told you about. If the client owns the property, ask them to add you as a user under Settings, then Users and permissions.

On top of that, a freelancer needs three things running:

a free uptime monitor pinging each homepage every few minutes
Search Console emails reaching an inbox you actually read
a recurring slot in your calendar to check what those two can't see

That covers outages and the indexing problems Google eventually reports. It does not cover a title tag overwritten by a plugin update, a GA4 tag lost during a theme change, or a sitemap that shrank by half. Those are the gaps the weekly slot is for.

What you can monitor for free by hand

Search Console sends email to owners and users when it detects new issues, such as a jump in pages excluded by noindex or a spike in server errors. Check Email preferences in the Search Console settings to confirm the categories are switched on, and set up a filter so these messages don't end up buried in a promotions tab. Expect a delay: Google reports what it saw while crawling, which can be days after the change happened.

For uptime, several services have free tiers that cover a small portfolio. UptimeRobot's free plan, for example, monitors at five minute intervals, which is plenty for a brochure site. Point the alert at your phone, not just email.

The weekly slot is where the manual work happens. Thirty minutes on a Monday morning is realistic for up to about ten sites if you keep a fixed list:

Open /robots.txt on each site and look for new Disallow lines. Our guide on how to check robots.txt explains what to look for.
Open the XML sitemap and compare the URL count with last week. A spreadsheet with one column per week is enough. More on this in how to monitor sitemap changes.
View source on the homepage and one key template, and search for noindex, canonical and your GA4 or GTM ID.
In Search Console, open the Page indexing report and glance at the "Not indexed" trend.
Check SSL certificate and domain renewal dates, which you can note once in the same spreadsheet.

On WordPress sites, add a look at Settings, then Reading, to confirm "Discourage search engines from indexing this site" is still unticked. It is the single most common way a site drops out of Google after a migration, and how to catch a noindex in production covers the other ways it happens.

Where the manual routine stops scaling

The routine works until one of three things happens.

The first is volume. Each site adds a few minutes, and once you pass ten or twelve the Monday slot becomes an hour, then gets skipped during a busy week. A skipped week is exactly when a client's developer pushes a staging config.

The second is timing. A weekly check means a problem can sit for six days before you see it. For a small local business site that may be acceptable. For an ecommerce client running paid campaigns, a missing Meta Pixel for six days is money they will ask about.

The third is you. Manual monitoring depends on one person remembering, and freelancers get ill, take on a big project, or go on holiday.

When any of those starts to bite, the question stops being whether to automate and becomes how much of the list to hand over.

Monitoring when you're on holiday

Holidays are the real stress test for a solo operator. A few practical steps help:

Before leaving, run the full manual checklist on every site so you start from a known good state.
Ask clients not to schedule releases, plugin updates or redesign launches while you're away, and put it in writing.
Route uptime alerts to someone who can at least phone the host, even if that is a trusted freelancer you pay by the hour for cover.
Give that person Restricted user access in Search Console rather than your own login.

Automated change alerts matter most here, because they let you look at your phone once a day and know whether anything actually changed, instead of either ignoring work completely or checking every site from a beach.

How to price monitoring into a maintenance retainer

Monitoring is easier to sell as part of a maintenance retainer than as a separate product, because clients understand "someone is looking after the site" better than a list of technical checks. What makes it billable is being specific about scope.

Write down which signals you watch (uptime, indexing, SEO tags, tracking, SSL and domain), how often they are checked, and what response the client gets. For example: problems found are reported the same working day, and fixes that take under 30 minutes are included. Anything larger is quoted separately.

To set the price, add up your real costs per site: tool subscriptions divided across the sites they cover, plus the time you spend reviewing alerts each month. Then price the retainer on the value of avoided incidents, not the hours. Send a short monthly note even when nothing broke. Our article on website monitoring client reports has ideas on what to include.

Automating the checks with Deltio

Deltio automates the weekly list above. Once a day it reads each site's sitemap and pages, compares them with the previous check, and alerts you by email or Slack per site when something changed: noindex, robots.txt, canonical, title, meta description and H1, sitemap URLs, uptime, SSL and domain expiry, GA4, GTM and Meta Pixel, cookie consent banners, and maintenance pages left live. You can also run a manual SEO scan before or after a release.

Checks run daily, not in real time, so a change made this morning shows up in tomorrow's alert. For most freelance portfolios that is still a big improvement on a weekly manual pass.

The Starter plan covers up to 50 sites for £24, €29 or $31 per month, or £20, €24 or $26 per month billed annually. You can try it on your client sites for 14 days.

Frequently asked questions

Do I need to monitor sites that have no SEO or ads budget?: A lighter setup is usually enough: uptime, SSL and domain expiry, and Search Console emails. Those failures take the site offline or show browser warnings, which small business clients notice even when they don't care about rankings.
Should the client or I own the Search Console property?: The client should own it, with you added as a Full user. If the relationship ends, they keep the data and history, and removing your access is a single step in Users and permissions.
Is a staging site worth monitoring too?: Usually not for indexing, because staging should be blocked from search engines on purpose. The useful check is the opposite: make sure the staging robots rules and noindex tags don't reach production when the site is deployed.
How should I tell a client that monitoring found a problem they caused?: Describe what changed, when it was detected and the effect, without assigning blame. A short message with the affected URL and the fix you applied keeps the conversation about the site rather than about who clicked what.
Can I monitor client sites I don't maintain myself?: Yes. Checks of robots.txt, sitemaps, tags and page source only need the public site, so you can watch sites handled by another developer. Search Console data still requires the owner to grant you access.