Jump to a section
Possible buyer
An owner with an existing website who needs occasional, approved content changes.
First deliverable
Approved edits to named pages, checked and recorded for the owner.
Skills to bring
You know the website editor, can check the published result, and can reverse a content change.
Watch for
Requests involving unfamiliar features, software updates, or emergency repairs.

Changing an opening time or replacing an old staff photograph sounds simple. An owner may still put it off because they rarely use the website editor and don’t want to break anything.

If you already know their platform, you could offer to make a small batch of approved changes. This profile focuses on content upkeep. Software maintenance, security work, and emergency repairs need a separate agreement and the skills to carry it out.

Be clear about the kind of site you know

Someone comfortable editing a straightforward WordPress site could begin there. A different theme, custom feature, or booking system may change what the work involves. Ask to see the actual setup before you give a firm quote.

Possible buyers include independent professionals and small organizations with established sites. Find out who owns the accounts, who approves changes, and whether a developer already handles support. Ask the owner to introduce you if that person needs to be involved.

A hypothetical package could update approved hours and contact details on three specified pages, replace one supplied image, check the affected links, and provide a change record. It leaves out a redesign, checkout changes, software updates, and emergency repairs.

Write the page names into the quote. If the request grows into a new booking feature, stop and agree the extra work or refer it to someone with the right experience.

Practice the whole job

Make a small site you control, with clearly fictional details. Give yourself a list of edits, carry them out, and record what changed. Label any public example as a practice project.

For each edit, check the published page rather than relying only on the editor’s preview. Look on a desktop and a phone-sized screen, follow the affected links, and confirm that the supplied text and image are correct. Practice reversing a change too.

Hypothetical practice project

Leave the owner a useful change record.

PageApproved changeCheck recorded
HomeReplace the opening hoursPublished wording matches
ContactReplace the email addressEmail link opens correctly
AboutReplace the supplied photoImage and caption checked
In your own record, add the date, person approving the work, and any outstanding items. Record the checks you actually performed.

WordPress’s content revisions can help you compare and restore earlier saved versions. Their retention can be limited or disabled, so check what the particular site keeps. Revisions are for saved content; they don’t replace a complete site backup.

You should be able to explain both your checks and your recovery plan to a buyer. If you’re still learning the editor, use your practice site until the routine feels familiar.

Agree access and recovery before editing

Use an individual account with permissions suited to the work. WordPress’s role descriptions distinguish editing posts and pages from administering software and settings. An Editor role may cover content work, but themes, plugins, and customized permissions can affect what you can do. Ask the owner or developer to confirm it.

For a full WordPress backup, the official guidance covers both files and the database. Establish who can access and restore that backup, and how current it is. A content-only job can leave full-site recovery with the owner’s existing technical support, provided everyone understands that arrangement.

You don’t need access to customer records or payment details for an ordinary page edit. Have the client confirm permission to use supplied images, and agree whether you may download files or include finished work in your portfolio.

Offer to clear a small backlog

Ask an owner or organization you can appropriately contact whether they have a few changes waiting. A useful opening question is: “Which details on the website have changed since it was last updated?” Let them identify the current information and who can approve it.

If you notice a broken public link, describe that specific problem. You aren’t doing a security audit, and you shouldn’t need intrusive tests to discuss a content job.

Include account setup, edits, checking, approval, and the change record in your time estimate. Budget for your computer, internet, any practice-site hosting or work software, payment fees, and applicable business costs. Agree who pays renewals; keep the client’s domain and hosting under their control.

Finally, state your working hours and time zone. A scheduled batch of edits may suit you well even when you’re unavailable for emergency calls. Put that limit on your service page, alongside the platform you support and the tasks you can confidently complete.