Start with the right access
Use the editor link already supplied for your site. Use the current editor login linked from Client help. If your site uses a legacy editor, ask the team which route applies before signing in. If access is missing, contact support. Don’t create a second account or share a password to solve it. Platform-specific screenshots and the quick-edit PDF need a current check, so this guide does not pretend every editor works identically.
Write the change before making it
Keep the page address, old wording and replacement wording together. Confirm prices, GST and any conditions with the person responsible. Keep a copy of the current content or use your verified version history before editing. Change text and approved photos first; ask for help before altering navigation, forms, tracking or a shared template.
Photos need context
Use an image you have permission to publish. Keep the subject visible in a phone crop and use a sensible file size. Add alternative text describing meaningful information. A decorative image does not need a sales pitch hidden in its description.
Preview before publishing
Read the text aloud. Ask a second person to check names, numbers and links. Preview phone and desktop layouts. Check button destinations, readable contrast and keyboard focus. If the platform offers a preview or draft, use it before its publish action. Arrange an authorised test of a real production form; this review site cannot send enquiries.
Check the published page
Open the page outside the editor and verify the change is visible and accurate. Keep a note of what changed and when. If the layout breaks or you are unsure what a control affects, stop and send support the page address and a description. Build revisions, mistake corrections and later maintenance have different scopes; agree the relevant work rather than guessing.