How to Run a Monthly Website Content Check

If you could check only three pages this month, which ones would cost a customer time or money if they were wrong? Start with the price, the promise, and the way to get in touch. Follow the links and try the forms as a customer would. A page can look current and still send people to last year’s order form.

A practical example

Start the monthly check at the point where an error would cost someone money or a wasted trip. For a workshop site, that might mean following a visitor from the price page to the booking form and then to the confirmation email.

A sample content-check log
What the reviewer found Who can fix it How to verify
The price page says $45; checkout says $55. The owner confirms the approved price before the editor changes either page. Repeat the booking up to payment and compare both prices.
The directions link opens last year’s venue. The event lead confirms the address; the editor updates the link. Open it from the public page and compare the destination with the booking confirmation.
The contact form says “sent,” but the test message never arrives. The site maintainer traces delivery; the editor posts a verified alternative contact. Send a new test and confirm receipt in the monitored inbox.

A working link can lead to the wrong place. Read the destination, not just the status code. Use test details, avoid unintended charges, and record the date, owner, and next check beside each finding. If you cannot establish the correct price or venue, flag it for a decision rather than guessing.

Next month, start with unresolved items and repeat one important visitor journey. Rotate less critical pages into later checks. A small check that closes real problems is more useful than a long list of pages marked “viewed.”

Start with the pages that matter most

Pick the pages that bring the most visitors, convert the most readers, or make the most important promises. For most small sites, this includes the home page, the main service or product pages, the pricing or booking page, and the three or four articles that are shared most often. Keep this list short and written down. If the list grows too long, the check will be skipped in the months when it is needed most, so it is better to start small and add pages only when a real reason appears.

Check every link on those pages

Broken links are the easiest problems to find and among the most annoying for visitors. Open each high-value page and click the links, or use a link checker that reports status codes for every address on the page. Pay attention to internal links, which you control, and to outbound links to suppliers, partners, and tools, which change without notice. Record each broken link with the page address and the destination. Fix internal links right away, since they are usually a quick edit. For external links, decide whether to replace the source, remove the link, or leave it in place with a note explaining why.

Review stale claims and dates

Links are only part of the check. Read each page for statements that may no longer be accurate. Look for prices, deadlines, opening hours, team names, screenshots of old interfaces, and phrases such as “this year” or “recently” that have quietly aged. Also check footers and copyright years. Old details are harder to spot than broken links, because the page still loads and looks finished. If a claim depends on a law, a regulation, or an official rate, confirm it against the current source before you change or keep it, and write down the date you checked it.

Log every fix with an owner

A monthly check only works if the results are recorded. Keep one simple log with four columns: the page, the problem, the fix, and the person responsible. Note the date you checked each page, even when nothing needed changing. A clean entry is useful evidence that the page was reviewed, and it helps the next person see what has already been handled. When a fix needs a developer, a supplier, or a professional review, put that in the log with a target date rather than leaving it in your memory.

Keep the check small enough to repeat

The goal is consistency. A check that takes ninety minutes every month will eventually be dropped, so set a time limit and stick to it. If you find more problems than you can fix in one session, do not expand the check to cover the whole site. Fix the most visible problems first, schedule the rest, and keep the monthly list the same so that trends become clear. After three or four months, the log will show which pages change most often. Those pages may need a shorter review cycle, while the rest can stay on the monthly schedule.

Handle fixes that take longer than a month

Some problems cannot be fixed in one session. A product page may need new photographs, a supplier may take weeks to answer a question, or a page may need a developer to repair a template that affects dozens of addresses. Do not let these items disappear from the log. Mark them as open, record who is working on them, and set a date for the next review. Review open items at the start of each monthly check, so that they do not vanish between visits. If an item stays open for three months, ask whether it still matters. Sometimes the right decision is to remove the page, redirect it to a current one, or accept the risk and note it. A visible decision, even one that says nothing will change, is better than an item that is forgotten.




How to Find the Cause of a Recurring Customer Complaint

“I never got my download” could mean the email didn’t arrive, the button was hard to find, or the link didn’t work. Those failures need different fixes. Follow a few orders from purchase to delivery before you change the email or ask support staff to send it again.

A practical example

Five customers report “no download.” Support resends the link five times. That helps the customers who are waiting, but it does not tell you what broke. Trace one order before rewriting the instructions.

  • Did the delivery message arrive? Check the order and delivery records you are authorized to see. A sent message is not proof that the buyer saw it.
  • Could the buyer find the link? Use a test order and read the email on a phone. Record the first step that does not match the instructions.
  • Did the link lead to a usable file? Try the buyer’s route with a test account, not an administrator account. A missing attachment needs a different fix from a button the reader overlooked.

Suppose three reports concern a hidden button and two concern a file that will not open. Keep the groups separate. Change the button label for the first group and compare complaints about finding the link per completed order before and after. A quiet sales week alone is not evidence of improvement. Continue helping affected buyers while testing the cause.

Protect the customer’s privacy

When you use complaints as examples in an article, team discussion, or report, remove names, email addresses, order numbers, and other identifying details. Describe the problem in general terms. Respecting privacy also makes customers more willing to share honest feedback, which is the raw material for finding recurring problems in the first place.

Collect the complaints in one place

Start by gathering the complaints from the places where they arrive, such as email, chat, social messages, and reviews. Put them in a single spreadsheet with the date, the channel, and a short summary of the problem in the customer’s words. A single list makes patterns easier to see, and it prevents a problem from looking smaller because it is spread across several inboxes.

Group similar issues

Read through the list and sort the complaints into groups. A group might be “cannot find the download,” “file will not open,” or “charged twice.” Keep the groups broad enough to be useful but specific enough to describe one problem. Count how many complaints fall into each group. Be cautious about treating a single complaint as a trend. A pattern usually needs several examples across a period of time before it deserves attention.

Look for the moment it starts

For each group, identify where in the customer journey the problem begins. Did it happen during checkout, after delivery, during setup, or at the point of cancellation? The earliest point is often the best place to look. A confusing button on the purchase page can produce complaints that appear later as support requests about missing files, for example.

Reproduce the customer journey

Follow the same steps a customer would take. Use a test account or a private browsing window, and work from the instructions you have published. Write down each step, what you expected to see, and what actually happened. Reproducing the problem is the most reliable way to confirm the cause, because it replaces guesses with observations. If you cannot reproduce it, ask a customer who reported it to describe their steps, with their permission and without sharing private details.

Form a specific hypothesis

Write a clear explanation of the likely cause, such as “The confirmation page does not mention the email delay, so customers assume the purchase failed.” A specific hypothesis suggests a specific test. Vague explanations, such as “people are careless,” rarely lead to a useful change. Keep the hypothesis short enough that you can test it with one change.

Test one fix at a time

Change one thing, then watch what happens. If you update the confirmation page, leave the delivery email and the checkout flow as they are for the test period. Changing several things at once makes it impossible to know which one helped. Record the date of the change, the number of related complaints before and after, and any side effects you notice.

Decide what success looks like

Before the test, define a measure. For example, you might aim to cut the number of “cannot find the download” messages by half over four weeks. A clear measure stops you from declaring success too early, and it lets you decide honestly whether the fix worked. If the number does not change, review the hypothesis rather than adding more changes at once.

Document what you learned

Write a short record of the complaint group, the cause, the change, and the result. Store it where your team can find it. A record like this prevents the same investigation from starting over in six months, and it helps new team members understand which problems have already been addressed.

Check whether the cause is in your process

Some recurring complaints originate outside the product itself. A payment processor may send receipts before the download is ready, or a template may depend on a software version that many customers do not use. Ask whether the problem sits in your site, your instructions, your delivery method, or a third-party tool. Each place calls for a different fix, and the cheapest fix is often the clearest explanation. Before you change the product, see whether a better message, a clearer label, or a short video would resolve the issue for most customers.




How to Write a Clear Delivery Email for a Digital Product

A customer who just paid for a worksheet shouldn’t have to scroll past a thank-you speech to find the file. Put the download link where they can see it, name the file, and tell them what to do if it won’t open. Then add any setup instructions they need.

A practical example

Here’s a delivery email for a budgeting worksheet. The bracketed text stands for the buyer’s download link; replace it with the actual link before sending.

Subject: Your monthly budget worksheet (order 1042)

Hi Sam,

Thanks for your order. [Download your monthly budget worksheet]

The file is called Monthly-Budget.xlsx. Open it in Excel and start on the tab marked Monthly Bills. The example figures are there to show how the totals work; replace them with your own.

If the link doesn’t open, reply to this email with order number 1042 and tell me what you see.

Jo

What changes with the product?

For a PDF, the file name and download link may be enough. For a course, the first useful action may be signing in rather than downloading anything. In that case, label the link “Open lesson one,” say which email address to use, and explain when the next lesson arrives. If access expires, give the actual deadline and tell the buyer how to request help afterward.

Keep the support route as specific as the download instructions. “Reply to this message” works only if someone reads the inbox. If replies go nowhere, give the buyer a monitored address instead. Leave promotions out: the person searching their inbox next month needs to recognize the purchase, not remember what else was on sale.

Try to collect the order yourself

Place a permitted test order with a buyer account, not your store administrator account. Open the message on your phone. Follow the link, sign in if required, and open the file. Does its name match the email? Can a first-time buyer find the tab or lesson you named? Send a reply through the support route and check that it arrives. Fix the first step that fails before adding another paragraph of instructions.

Put access first

Open with the most important information: how to access the product. Include a direct link, the file name, and any login step the customer needs. Keep the first paragraph short. A customer who arrived from a checkout page is usually eager to start, and a long introduction only delays the answer. If the product requires a password or a specific app, mention it near the link so the customer does not have to search for it.

Confirm the order details

Briefly restate what was purchased, the order number if you use one, and the date. This helps customers match the email to their purchase, especially if they bought several products. Keep the summary to a few lines. It should reassure the customer without repeating the whole receipt.

Explain what to expect next

Describe the steps after the download. For example, a template might include a short setup guide, or a course might send the first lesson by email on a set day. If the customer will receive more messages, say what they are and when they will arrive. Clear expectations reduce confusion and prevent customers from thinking the delivery failed when the next step simply has not happened yet.

Give simple instructions for opening the file

Some customers are unfamiliar with certain file types. Name the format, such as PDF or a zipped folder, and say which program opens it. If a zipped folder must be unpacked first, explain how in one or two sentences. Avoid assuming technical knowledge. A customer who cannot open the file is the most likely person to request a refund.

Offer one support path

End with a single, clear way to get help, such as a support address or a contact form. Giving several options can make customers unsure where to go. Include the expected response time if you can state it honestly. If a common problem has a quick fix, you may mention it in one line, but keep the main support message simple.

Separate delivery from marketing

A delivery email is a transactional message. It should contain what the customer needs to access their purchase, not a promotion for something else. If you want to send marketing messages, ask for consent separately, and do not place a sales pitch in the delivery message. Check the consent rules that apply to your audience and location, because they vary. Keeping the two types of message apart protects customer trust and reduces the chance of unsubscribes from important messages.

Write in plain, friendly language

Use short sentences, clear headings if the email is long, and a warm but direct tone. Avoid jargon. Phrases such as “Here is your download” or “You can open the file in any PDF reader” are easier to follow than technical descriptions. A friendly voice makes the purchase feel finished and supported.

Check the wording of each step

Read the email as a customer would, one sentence at a time. Look for instructions that assume prior knowledge, such as a reference to a “dashboard” the customer has never seen, or a file name that does not match the link text. Confirm that the subject line makes the purpose obvious, so the customer can find the message again later. A small change, such as renaming a button from “Access” to “Download your guide,” can remove a source of confusion without adding any length to the message.




How to Handle a Client Request Outside the Original Scope

A client who asks for “just one more thing” is not necessarily acting in bad faith. Requests grow because people see new possibilities as the work unfolds, or because they assume a small addition will not affect the schedule. The challenge for a freelancer is to respond without sounding defensive and without quietly absorbing the extra work. The approach in this guide is simple: restate the request, explain the tradeoffs, and record the agreed change. Each step keeps the focus on the work rather than on blame.

A practical example

“Could you also make the guide into slides?” is a reasonable question from a client. It is not necessarily a small change. Check the agreed deliverable before answering: correcting a mistake in your guide is different from producing a second format.

“The editable guide and its revision are included. Slides would be a separate deliverable. I can finish the guide on Friday as planned and quote the slides for next week. If the slides are more urgent, I can price a switch and confirm what happens to the guide. Which would help most?”

If the work was already promised, say so and do it. If the brief is ambiguous, show the client the relevant wording and clarify what each of you understood before discussing a fee. For genuinely new work, specify the extra price, the revised date, what is no longer included, and who can approve the change. A request is not approval to send a larger invoice.

Decline when the change does not fit

Sometimes the best answer is no, or not yet. If the request would compromise the quality of the agreed work or the timeline is fixed, say so politely and propose a later phase. You do not need to justify every boundary in detail. A clear explanation and a constructive alternative are enough.

Once the client decides, add the agreed change to the working brief and send both parties the same version. If the client declines the extra work, confirm the original deliverable and carry on. There is no need to renegotiate the whole project.

Restate the request in your own words

Begin by confirming that you understand the request. A short summary such as “You would like the pricing page to include a comparison table, and you want it ready before the launch on Friday” shows that you listened. It also gives the client a chance to correct any misunderstanding before you discuss effort or cost. Restating is especially useful when the request arrives in a quick message or during a call.

Avoid responding immediately with a price or a refusal. A brief pause to restate the request keeps the conversation calm and gives you time to think.

Compare the request with the agreed scope

Check the request against the brief, the quote, and any earlier emails. Is the new work already covered, partly covered, or outside the agreement? Be honest with yourself. Some requests are small clarifications that fit the scope, while others change the deliverables in a meaningful way. Making this comparison privately before you reply helps you respond consistently.

Explain the tradeoffs

Describe what the change would affect. Extra work may require more time, which can delay another deliverable. It may also change the quality of the rest of the project if the schedule becomes tight. Present these tradeoffs as facts rather than complaints. For example, “Adding the comparison table would take about three hours, which would move the final review to Wednesday” gives the client a clear choice.

Offer options where you can. You might suggest adding the table as a separate task with its own quote, or including a simpler version within the current scope.

Offer a clear set of choices

Most scope changes can be handled in one of three ways: the client accepts a revised timeline, the client approves an additional fee, or the client chooses a smaller version that fits the existing agreement. Name the options in a short list. Clear choices make it easier for the client to decide, and they keep the conversation productive rather than adversarial.

Record the agreed change in writing

Once the client chooses, confirm the decision in writing. Describe the new deliverable, the updated date, and any change in price. Ask the client to reply with approval. A short email is usually enough, though a formal change request may be better for larger projects. Written records protect both parties and prevent later disagreement about what was agreed.

Update the brief and invoice

Update the project brief so it reflects the agreed change, and send the revised version to the client. If the change affects payment, include the adjustment in the next invoice and refer to the change request. Keeping the documentation current makes the final project easier to close, and it helps you remember the reasons for each decision later.

Keep the tone factual

Avoid language that assigns blame, such as “You keep adding work” or “This was never included.” Instead, describe the situation neutrally: “This request is outside the original scope, so here are the options.” A calm tone helps the client accept the change without feeling criticized. It also protects the relationship, which may lead to future projects.




What to Put in a Simple Client Brief

When a client asks for “a short guide,” you might picture a two-page handout while they expect a designed booklet. Put the deliverable, format, reviewer, and due date on one page before either of you starts work. That brief gives you something to check when the feedback arrives.

A practical example

Before work begins, send the client the page you would want to find if you had to take over the job halfway through. Here is a sample for a small writing project.

Job: A two-page guide that helps first-time workshop leaders set up the room without calling the organizer.

Delivery: One editable document, written from the organizer’s room plan and checklist. One round of consolidated comments. Design, translation, and printing are outside this job.

Timing: The organizer sends the approved room plan on Monday. The writer sends a draft on Thursday. The organizer returns one set of comments by the following Tuesday; final copy follows on Friday.

Approval and fee: The event lead approves the wording. The agreed fee is $480; payment timing is in the accepted quote. The writer will ask for approval before taking on additional work.

Still open: Which entrance is available before 8 a.m.? The organizer will confirm before the draft is due.

Notice what the open question does. The writer can start, but nobody is authorized to invent a door number. If the answer is essential before work can begin, move it out of “still open” and make it a start condition.

Ask the client to correct the brief, especially who can sign off and who collects feedback. Keep the agreed version with the quote. If the deliverable changes, date the revision and confirm any new cost or deadline in writing; don’t quietly overwrite the original agreement.

Capture the desired outcome

Start with the outcome. Ask the client what should be true once the project is finished. Perhaps a new landing page should explain the service in under a minute, or an onboarding guide should reduce the number of support questions. Write the outcome in one or two sentences, using plain language. A clear outcome gives every later decision a test: does this choice help us reach the goal?

If the client names several goals, ask which one matters most. A project with one priority is easier to scope and easier to finish well.

Describe the audience and context

Add a short section about who the work is for and how it will be used. Note the intended readers or users, where the material will appear, and any constraints you already know about, such as brand guidelines, existing files, or a platform the client uses. Context prevents wasted effort. A design that looks excellent in isolation may fail if it does not fit the client’s website or the people who will read it.

Define the deliverables

List each item you will deliver, with its format and the number of revision rounds included. For example, “one blog article of about 1,000 words, delivered as a document, with two rounds of revisions” is specific enough to check. Avoid vague items such as “support” or “content.” If a deliverable depends on the client providing something, name that dependency and its due date.

State the exclusions

Exclusions are as important as deliverables. Say what is not included, such as hosting, translation, photography, social media posting, or updates after launch. Clear exclusions prevent later disagreement about whether a request was part of the original agreement. You can phrase them politely: “Publishing and scheduling are not included in this project, but I can provide a separate quote if you want them.”

Set a timeline with checkpoints

Add the main dates for the project, including the start, the review points, and the final delivery. Mention what happens if feedback arrives late. Many delays come from slow approvals rather than from slow production. A timeline that names checkpoints makes it easier for the client to see when they need to respond, and it gives you a clear basis for discussing schedule changes.

Agree on sign-off

Decide who approves each stage and how approval is given. A simple rule works well: approval is confirmed in writing by the named contact, and work moves forward after that confirmation. If the client wants several people involved, ask who has the final decision. An unclear approval process is one of the most common causes of repeated revisions.

Record the budget and payment terms

Include the agreed price, the payment schedule, and what happens if the scope changes. You do not need to write full legal terms in the brief. A reference to your quote or contract is enough. The purpose is to keep the commercial basics visible alongside the creative or technical goals, so that both parties can see the full picture in one place.

Keep the brief short

A brief that runs to ten pages will not be read. Aim for one page, with clear headings and short sentences. Use bullets for deliverables and exclusions, and put the most important decisions near the top. A short document is easier to review, easier to update, and more likely to be used during the project.




How to Price a First Freelance Project

Before quoting a price, describe the point at which the job is finished. One draft and one revision is a different commitment from “until everyone’s happy.” Estimate the time for the whole job, including meetings, revisions, and delivery, before you put a number in front of the client.

A practical example

Imagine a client wants a two-page guide. Before putting a price beside “write guide,” list the jobs the client will not see: collecting the source material, resolving conflicting comments, and handing over the final file.

Illustrative estimate for one guide
Work included Hours
Briefing and source review 2
Writing and editing 4
One consolidated revision 2
Communication and delivery 1

Nine hours at an internal target of $50 an hour gives $450. Add $30 for an agreed project expense and the illustrative quote is $480, before any applicable taxes. The rate is an assumption, not a market benchmark. At eleven hours, the same fee leaves $450 after the expense, or about $41 per hour before overhead and taxes.

“$480 covers one two-page guide using the source material you provide, one round of combined feedback, and delivery of an editable file. Interviews, design, and further revisions are not included. I’ll quote any extra work for approval before starting it.”

If you cannot tell whether the sources are usable, ask to see them before offering a fixed fee. You can also quote a short discovery phase rather than padding every line to cover an unknown. After delivery, compare the actual hours in each row with your estimate. The row that ran over is the one to investigate next time.

Define the scope before you price

A price is only meaningful when both sides agree on what it covers. Write down the deliverables, the number of revisions included, the platforms or formats involved, and the dates that matter. Then list what is excluded, such as hosting, content writing, or training after launch. A short scope statement turns a vague request into a set of items you can estimate one by one.

If the client cannot describe the outcome, ask them to describe a finished project in plain terms. You can then propose a scope that matches that picture, and the quote will be easier to defend.

Estimate the effort for each task

Break the scope into tasks and estimate the hours for each one. Include discovery, planning, production, review, and handover. Many beginners price only the visible work and forget the time spent on messages, file transfers, and revisions. A simple way to test your estimate is to imagine doing the work on an ordinary week. Would the schedule hold, or would the project spill into the following month?

For example, an illustrative project might include four hours of planning, twelve hours of production, and three hours of review. Those hours give you a starting point before you consider risk.

Add a margin for uncertainty

First projects carry more risk than repeat work. You may not know the client’s approval process, the state of their existing files, or how long their feedback will take. Add a margin to cover that uncertainty. Some freelancers add a fixed percentage, while others add a contingency for specific risks, such as unfamiliar software or a tight deadline. Whichever method you choose, make the margin visible enough that you can explain it if asked.

Avoid padding the price so heavily that the client cannot justify it. The aim is a fair estimate that accounts for what you genuinely do not know.

Turn hours into a price

Choose a rate you can defend, then multiply it by your estimated hours. Suppose your target rate is forty dollars an hour and your estimate is nineteen hours. The base price would be seven hundred and sixty dollars before any margin. Adding a fifteen percent contingency brings it to about eight hundred and seventy-four dollars. These figures are only an example. The point is to show how each assumption affects the final number.

Consider whether a fixed price or an hourly rate suits the project. A fixed price can work well when the scope is clear. An hourly rate may be safer when the client is still deciding what they want.

State your assumptions in the quote

A quote should say what it assumes. Examples include the number of revision rounds, the client providing content by a certain date, and the use of a specific file format. If an assumption changes, the price can change with it. Writing assumptions protects both sides, because the client can see what they are buying and the freelancer has a clear basis for any change request.

Explain the quote simply

When you send the quote, explain how you reached it in a few sentences. You might describe the main deliverables, the phases of work, and the number of revisions. Avoid a long justification. A clear, short explanation builds confidence, and it invites the client to discuss which parts matter most to them.

Check the numbers after the first project

Once the project is finished, compare the actual hours with your estimate. Note which tasks took longer and which were quicker than expected. Use those notes for your next quote. Your first project is the start of a record, not a final verdict on your pricing. Over several projects, your estimates will become more reliable.