How to Use Sitechecker to Catch Client Site Problems Early

The short answer: for an agency running 20 client sites on the Standard plan (pricing page), the work is one careful set-up per site and then alerts: create a project with Google connected, set the crawler's limits, leave Site Monitoring on, verify your email and route alerts to Slack, add each site's revenue keywords to Rank Tracker in groups, share projects with view rights, and brand the reports.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job here is simple to state. When a developer pushes a theme update on a Friday and the checkout page drops out of the index, you want to know on Friday, not in next month's report. Sitechecker is built for that kind of watch across many sites; the Sitechecker glossary entry covers what it includes and costs.

Settle three things before the first project:

1. Budget the keyword limit. Rank Tracker counts every setting: one keyword in 2 countries on desktop and mobile is 4 keywords, per the Rank Tracker guide. Standard's 2,500 keywords over 20 sites is 2,500 / 20 = 125 a site, which is 31 keywords each if every site tracks two countries on two devices (125 / 4 = 31.25).
2. Collect access you already have. For each site, a Google account with access to its Search Console and GA4 property, or the ability to add an HTML tag for ownership verification, as the project guide explains.
3. Agree what counts as an incident. Pick the alerts someone will act on within a day, such as broken pages or pages that became non-indexed, and log the false alarms over the first two weeks. That log tells you whether the set-up works.

1. Create one project per site

Click Create project and enter the domain, then connect your Google account so Google Analytics and Search Console data come in, per the project guide. Connecting Google also verifies ownership automatically; the alternative is an HTML tag or file on the site. Both steps can be skipped, at the cost of the Search Console reports and the custom crawler rules later.

2. Tell the crawler what to read

In the Site Audit step you choose the sitemaps, how many pages to crawl and whether to follow subdomains or nofollow links. Sitecheckerbot respects robots.txt by default, and once ownership is verified you can write local rules for it without touching the live file, according to the Site Audit guide. Lower the number of parallel requests if the site responds slowly or the crawl triggers 5xx errors.

3. Leave Site Monitoring on

Monitoring starts as soon as the project exists and tracks titles, descriptions, H1s, indexation, robots.txt, and new, broken, orphan and deleted pages, per the Site Monitoring guide. How often it rescans depends on the plan: weekly on Basic, daily on Standard and every 12 hours on Premium, on the pricing page. The timeline view is where you will check every alert later.

4. Make sure alerts reach a person

Verify your email address first. Sitechecker's getting started list says unverified accounts receive no product notifications, and that the confirmation mail from notifications@sitechecker.pro can land in spam. Then choose your alerts in Account Settings: Site Monitoring sends a change digest plus triggered alerts when pages break, indexed pages become non-indexed or robots.txt changes, per the notifications guide. The project's Alerts and Reports step also connects Slack, so alerts land in a channel the whole team reads.

5. Add the keywords that bring in business

Click Add in the Rank Tracker header, paste keywords one per line, pick Google, Bing or Yahoo, the countries (cities become available when you track one country), the devices, and optionally a group or target URL, as the Rank Tracker guide describes. Keywords from a connected Search Console can be imported from the project settings' Keywords tab. Groups pay off later: the Groups tab compares topics once a project has at least two.

6. Add the competitors

Enter competitor domains in the project's Competitors settings, or accept the ones Rank Tracker suggests from your keywords. Every plan compares against 15 competitor websites, according to the pricing page.

7. Let an assistant draft the Monday summary

Sitechecker runs a hosted MCP server that lets Claude, ChatGPT, Codex or Claude Code read your projects' audit, monitoring, Search Console, GA4, ranking and AI visibility data, signed in through OAuth with no API key, per the MCP introduction. It is read-only, limited to 10 tool calls per second per connection, and works on paid plans but not in the trial.

Ask it each Monday for the past week's new critical issues and ranking drops across all projects, grouped by site. Before anything goes to a site owner, the account lead opens each flagged change in that site's Site Monitoring timeline and confirms it happened.

8. Share and report

Share a project by email with View or Edit rights. Edit users can do everything except add users, delete the project or manage notifications, per the project guide. Rank Tracker exports a PDF for any period up to 12 months, with your logo. PDF branding is on Standard and above, while a branded app, a custom domain and your own sender address need Premium, according to the white label guide.

A monitoring tool earns its renewal by sending you things, so its defaults lean towards telling you more. Switching off the alerts nobody acts on is part of the set-up, not a loss of coverage.

What Sitechecker's help pages warn about

• Alerts in the spam folder. The monitoring guide asks you to find the notification mail and move it to your inbox.
• Invitees without an account. The person you share a project with must be registered, on any plan including free, per the Site Audit guide.
• Gaps in ranking data. When Google blocks collection for some keywords, Rank Tracker shows the last positions it has and marks the chart, says the Rank Tracker guide. Check for that marker before you report a drop.
• One logo for everything. The PDF logo, the app logo and the favicon need different image sizes, per the white label guide.
• Issues that do not apply. Use the Ignore button to hide them, and restore them from the project's Site Audit settings if you change your mind.

FAQ

How often can I recrawl a site?

As often as you like on a paid plan, since every plan lists unlimited recrawls on the pricing page. On the free trial, the getting started list allows a manual recrawl once every 24 hours.

Do invited clients see Sitechecker's name?

On Premium and Enterprise, invited users can register on your branded domain, where the sign-up page says "Welcome to SEO platform" and pricing, upgrade prompts and the Help Center are hidden, per the white label guide. Notifications for invited users start switched off.

Which alerts matter most for a client site?

The ones that cost traffic within days. The pricing page lists alerts for pages that become broken or non-indexable, robots.txt changes, an invalid SSL certificate, removed tracking code such as GA4 or Google Tag Manager, and domain expiry 90, 30 and 7 days ahead.