Include specific actions in your maintenance proposal: when you review results, which issues you verify, what you fix yourself, and what you agree on separately. Specify your personal response hours. An automated website check every five minutes does not mean that a freelancer is on call around the clock.
For example: “On business days, by 11:00, I review new results. I verify errors on important pages and create tasks. Content edits taking up to an hour are included in the maintenance service; I estimate code changes separately. I accept urgent requests from 9:00 to 18:00.”
Specify what the service includes
List in your proposal what you personally do: review recent results, verify important findings, write up tasks, fix agreed defects, or coordinate another contractor. If fixes are billed separately, say so before the maintenance service begins.
Specify what the service covers. One homepage, a small website, and a large catalog require different levels of attention. The subscription’s daily automated audit covers up to one hundred pages, so you cannot promise a daily review of every URL on a store with thousands of products.
Specify the number of websites and the communication channels. If the client expects you to restore the site at night or on weekends, agree on that as a separate term. Check the price of reChecker itself on the pricing page; describe your own work in terms of the actions you will take.
Agree on what you can change
Before connecting the service, clarify your access to the website, the publishing method, and the actions you are allowed to take. Fixing a typo, updating a plugin, changing URLs, and restarting a server have different impacts. The client should understand what you can do on your own and when you will first present a specific task.
For changes with a wide impact, agree on pages to check and whether rollback is possible. Do not delete sections or change indexing rules just to improve a score. A technical finding may require investigation rather than simply following a brief recommendation.
Ask the client to name someone who will approve the fix. For a form, this is the person who receives the submission; a server configuration may require an administrator. Keep the agreement with the task.
Record the website’s status on the start date
Save a list of important URLs, the start date, and the first completed result. Note any known issues that predate the service. This protects both parties if an old defect is attributed to the new contractor or an existing improvement is presented as the result of the maintenance service.
Do not promise historical data for previous months if it does not exist. Search measurements and AI response monitoring apply only to available dates and settings. Missing data remains missing; do not replace it with sample figures to make the initial report look better.
One example entry: “Maintenance began on October 4; the delivery link is already broken; the issue was reported by the previous developer; the fix is not yet included in the new package.” See the pre-release checklist for help choosing the first URLs to check.
Combine findings about one issue into a single task
For maintenance, keep a log of the finding, decision, assignee, due date, and acceptance evidence. You can use your usual task management system. Specify owners and deadlines in your task tracker.
Combine recurring findings that have the same cause. If a shared template causes the same issue on dozens of URLs, start with a sample of pages to check and create one task. If the scope changes, add the new information to that task. This way, the client sees one completed piece of work instead of a long list of similar entries.
If the cause is likely to be a shared template, choose several cards with different content. The guide to template errors can help you test this assumption. After the diagnosis, tell the client what will change and how they will see the result.
Show the client the result after a fix
Suppose you fixed a broken link in the menu. After publishing, open it from the homepage and the service page. Then check the destination URL with a new audit. For a form, also run the agreed test and get confirmation from the recipient.
A brief message: “On October 4, I replaced the delivery URL in the shared menu. I checked the link from the homepage and the product card: it opens /delivery. I did not change the other menu items. The new technical report is complete, and the link is no longer flagged.”
If you are waiting for a repeat audit, say so and attach the manual check result. Later, check the date of the new report in the monitoring dashboard. In an active paid subscription, included manual local checks have no monthly run limit, but each package’s scope limits still apply. Paid plans include MCP and REST API for technical audits only. Paid AI tools are billed separately; agree on those costs before using them.
At the end of the period, review the work actually done: what was included in the maintenance service, what required a separate invoice, and how long responses took. This information will help you refine the terms for the following month.