How to Request a Website Update

Make the change easy to find.

“Can you update the website?” is a useful opening. The work becomes much easier to understand when the next message says which page, what should change, and what the finished result needs to do.

You do not need design software or technical language. A page link, exact replacement wording, original images, and a clear deadline can give your website team a strong starting point.

This guide is a way to prepare your request. Pricing, included edits, turnaround, and publishing arrangements depend on your project agreement and the change being requested.

Include these seven things.

1. The page link and section. Paste the full address and name the heading or area. “Services page, the second pricing card” is more useful than “near the middle.”
2. What should happen. Say whether to replace, add, remove, or fix something. Include the current wording when it helps identify the exact item.
3. The final replacement copy. Supply text that can be copied, including correct spelling, dates, prices, punctuation, and contact details.
4. The original assets. Attach the actual image or document, clearly named. Say which page it belongs on and confirm you have permission to use it.
5. The destination. For a button or link, include its exact target and the action a visitor should take.
6. The timing. Give the desired date, time, and time zone, plus any event or announcement the change depends on. Ask the team to confirm availability.
7. The approver. Name the person who checks the preview and authorizes publishing. Bring conflicting feedback together before sending it.

An example you can copy.

Here is a fictional request for a business changing its opening hours. Replace the example details with your own.

A marked screenshot is helpful for showing location. Put the replacement text in the message or an editable document too, so nobody has to retype it from a picture. List several changes as numbered items instead of spreading them across separate conversations.

Give images and links enough context.

Send the original photograph or approved export, rather than a screenshot from a social app. Say which subject should stay visible if the image needs cropping. A desktop banner and a narrow mobile screen can show very different parts of the same photo.

Describe what an informative image needs to communicate. That helps the team write appropriate alternative text for people who cannot see it. Decorative images may not need a spoken description. Do not put essential dates, prices, or instructions only inside an image.

For a form, booking button, or download, explain the expected result: which page opens, who receives the enquiry, or which document downloads. Flag sensitive information so the team can arrange an appropriate transfer method. Do not include passwords or payment-card details in an ordinary update request.

Check your request before sending.

Use this checklist while gathering the details. It only tracks this page while it is open; it does not send a request or save your answers.

Review the result in context.

When you receive a preview, compare it with the original request. Check the spelling, numbers, links, images, and any repeated information elsewhere on the site. Open it on a phone as well as a larger screen when you can.

Try the relevant button or download. Coordinate any form test with the team so test enquiries are recognizable. Website edits do not automatically update a Google Business Profile, social page, email signature, or third-party booking service; list those separately if they also need attention.

Send one consolidated set of corrections and make your publishing approval clear. After the update is live, check the public page again. If you see an old version, note the page address and device before assuming the change was missed.