Website Maintenance & Hosting

Report a Website Problem With Details a Developer Can Use

Send the affected URL, steps and safe evidence when requesting website support. Keep passwords and private customer information out of public messages.

Smiling businessman on a phone
Illustrative photograph, not a client or team claim. Photo: rawpixel.com rawpixel via Wikimedia Commons · CC0. Resized and cropped.
In this guide
  1. Describe the action and result
  2. Share evidence safely
  3. Make the report reproducible
  4. Ask for a clear next step

“The website is broken” is a valid concern, but it does not tell the maintainer where to start. A few specific details can make the first investigation much more useful.

Describe the action and result

Provide the page URL, what you tried to do and what happened instead. Include the approximate time and whether the issue affects mobile, desktop, a logged-in account or a particular product. Distinguish what you observed from what you suspect caused it.

Share evidence safely

A screenshot or error reference can help. Remove passwords, payment details and unnecessary personal information before sending it. Use an agreed secure route later if the investigation requires access; do not paste administrator credentials into a public contact form.

  • Note whether the issue repeats consistently.
  • Describe recent changes you know about.
  • Mention the business function affected.
  • Identify a working comparison where available.
  • Keep a contact person available for clarification.

Make the report reproducible

For example, explain that selecting a particular service and submitting an incomplete email produces a blank confirmation area on a phone. That is more actionable than saying the contact page looks strange. Do not repeatedly submit real customer orders merely to produce more examples.

Ask for a clear next step

The response should distinguish initial review, access requirements and any agreed investigation scope. A detailed report does not guarantee immediate repair, but it helps the right person assess the problem without avoidable guessing.

Need help putting this into practice?

Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.

Discuss website maintenance

Further reading from the official documentation