Choose a public page where it’s important to notice an incorrect response: your main service page, contacts page, or catalog. Then choose text that stays on that specific page. A fragment that’s too general may also appear on the wrong page, while a promotion date will change even when there’s no technical issue.
The important page check in reChecker uses a URL and required text. It doesn’t submit a form or place an order. To check the entire customer journey, add a separate manual check.
Choose a page based on its purpose
Start with this question: what should visitors see to continue with the action they need? For a repair shop, it might be repair terms and how to get in touch; for a store, it might be the catalog or delivery terms.
Prefer a stable URL that doesn’t require administrative access or include one-time parameters. Check that it doesn’t redirect to another page after a move. The URL used for setup must be on the same website.
Here are some sample candidates for a repair shop:
| URL | What visitors should see | Possible text |
|---|---|---|
| /repair | The main offer | Laptop repair |
| /contacts | How to get in touch | Workshop address |
| /appointment | How to start booking | Book a repair |
Check that the phrase actually appears in the response from the selected page. The text “Laptop repair” in a general menu may appear on every page and may not identify the right service. See the article about pages to monitor for additional criteria.
Choose text that won’t change every day
Don’t use the current promotional price, number of available spots, or today’s date if your goal is to monitor whether the page itself is available. That fragment may disappear during a planned update, even though the page is working correctly.
Generic text such as the website name also needs checking: it may remain on a placeholder page. It’s better to choose a stable phrase related to the URL’s purpose and note why you chose it.
If the text appears only after signing in or taking an action in the browser, first find out with your developer whether the check can retrieve it. The service isn’t assumed to click buttons or run the visitor’s entire journey. If the results differ, save the URL, time, and conditions of the manual attempt.
Fill in the fields in the “Settings” tab
In the “Site monitoring” dashboard, select a site, open “Settings”, and go to the “Important page” section. Click “Configure check”.
Fill in “Important page URL” and “Required text”. The text must be between 2 and 200 characters long. Click “Enable check”. For an already enabled setting, the buttons are called “Edit check” and “Update check”.
At first, you may see “Waiting for first check”. Later, review the actual time and result. The status “Page is available, required text is present” applies to that response, while “Important page element not found” means you should check the URL and text fragment.
The check runs on a five-minute schedule. Saving the settings doesn’t confirm a new response; wait for the actual result. Notifications depend on your channel settings, and you should confirm receipt with the recipient.
Review the settings when the page changes
If an editor replaces a heading as agreed, review the new content and update the required text with a clear reason. If a placeholder appears instead of the service, pass the issue to the person responsible rather than choosing text from the placeholder just to get a successful status.
You can add this note to the log: “04.10, /repair, required text ‘Laptop repair’; chosen as the stable service heading. We check form submission separately.” Review the URL too if the page has moved.
For the final step, follow the procedure for checking an order or inquiry. The presence of a “Submit” button confirms its text in the checked response; whether an employee receives the inquiry is a separate result.