Monthly checks are suitable for areas you are still gathering information about: a future service, a seasonal category, or additional products. It is better to check an important existing page more often.
Suppose a store is preparing snow-removal equipment for winter. In spring, you can monitor queries once a month, then move the relevant phrases to a daily group after updating the product range. Choose the frequency based on how you manage the offering, not on a good-looking position in a report.
Separate a future service from an existing one
A research list can include a future service, a new category, or variations in wording that the team has not yet evaluated. But having a phrase in monitoring does not mean the company already offers that service. The website must not promise terms the business does not yet provide just to match a query.
When compiling your research, keep the original wording, the source of the idea, and the expected page. If there is no separate URL, note that. This distinguishes an honest test of a hypothesis from a report that labels any URL found as a service page prepared in advance.
Account for the limit and search engine
A reChecker project supports up to 1,000 queries: up to 50 daily, up to 150 weekly, and up to 800 monthly. A monthly Yandex run includes all groups. Google is checked against the daily set, so the monthly group alone does not provide 1,000 monthly measurements in both systems.
The number of available slots is not a recommendation to fill 800 rows right away. It is better to start with a set connected to distinct areas and pages. Duplicate phrases without distinct intent increase the amount of analysis, but do not necessarily add useful questions about the site.
Check the date of the completed check. The scheduled month and the date of the available result may differ if there is a delay or partial data collection. Use old data with its actual date; do not label it with the current month just because you opened the report today.
Record why each group is needed
| Area | Reason for inclusion | Expected decision |
|---|---|---|
| Snow-removal equipment | Preparing the winter product range | Choose pages where the terms need updating |
| Pump parts | Checking additional demand | Find queries with distinct intent |
| Garden equipment rental | Testing a new service | Decide whether a standalone page is needed |
| Lawn mower maintenance | Monitoring a seasonal service | Move important phrases to a more frequent group |
Add the search engine, region, device, start date, list versions, and selection rules to the table. These records can be kept in the team’s spreadsheet. Do not describe them as built-in automatic seasonality tracking or business planning in the dashboard.
For each phrase, specify a condition for review. For example: the area launches, a service page goes live, the product range changes, or the season begins. This keeps the list from turning into an archive of forgotten assumptions that continue to be checked without a clear purpose.
Open the page that was found
For a monthly group, it is useful to see which page was found for a specific phrase. A general article or an old section may appear for a new service instead of the intended offering. This is a reason to check the content, internal links, and technical signals, not to immediately remove competing content.
If no URL is found, record the result as no page found in the check. Do not insert a made-up URL or claim an exact position beyond the search results that were collected. Diagnose indexing for the specific page using information from the search engine.
A practical review process is described in the article about a page that is not indexed. After making changes to the site, check the page technically, then assess the next ranking measurement separately using the same settings. Waiting until the next monthly measurement should be a deliberate choice.
Decide whether to change the frequency
A monthly review ends with one of these decisions: keep monitoring, move a phrase to a more frequent group, revise the offering, or remove an irrelevant area. Record the reason for the decision. “Add daily monitoring after the service launches” is clearer than “raise priority because the position improved.”
When you change the list, keep the previous version. Related queries can continue to be monitored, but do not present an average for the new set as a continuation of the previous summary without noting the change. Unchanged rows are useful as a separate, comparable part of the research.
The groups are available in the site monitoring subscription. For assessing a longer period, see the approach to a quarterly review of site health. A good monthly group answers focused questions about products and pages; it does not promise to predict future demand or automatically choose a promotion strategy.