The city. The work. The connection.MONTRÉAL / ENGLISH EDITION
Montréal en Direct

Everyday digital life, in both languages.

Home / Small business online

Small business online

Keep your local business website useful when plans change

Opening information, event details and customer messages need a publishing process that survives a busy week.

Updated / 2 min read
Montréal skyline at dusk

Find the information visitors depend on

A small organisation’s website often answers ordinary but important questions: where to go, how to make contact and whether a service is available. Make a list of those pages before considering a redesign. Assign responsibility for keeping each one accurate.

Avoid placing essential details only inside a poster image or a social post. Publish them as readable text on a stable page. That makes corrections simpler and helps visitors using smaller screens or assistive technology.

Prepare a quick correction route

Decide who can publish a change when the usual editor is unavailable. Keep access organised and give each person their own account where the platform allows it. Record the process for changing a prominent notice or correcting a date.

Rehearse with a harmless change before an urgent one is needed. Confirm the corrected page is visible at the public address and check any cached version. A successful save in an editor is not the same as a verified update for readers.

Include hosting in the continuity plan

Whether a site serves one Montréal neighbourhood or a wider audience, its availability depends on the hosting and the way it is operated. The Koddos hosting solutions range includes offshore hosting and DDoS protection services. Compare the chosen plan with the site’s support, publishing and recovery needs, including where the service is hosted.

Keep a copy of the current pages and the previous release somewhere the editor can reach independently of the host. If the site goes down, a short recovery note should identify the account owner, the support route and the location of the files needed to restore it.

Keep in mind

  • Identify the pages visitors rely on
  • Name a backup editor
  • Verify corrections publicly
  • Keep recovery access outside the site
Further reading

MDN: HTTP caching