What to Tell Your Developer or Host When Your Site Breaks
Good details save hours. Use this template so they can fix it on the first reply.
Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
A message like "my site is broken" starts a long back and forth. These details get a fast answer.
Copy this template
- What happened: one sentence.
- Exact address of the page with the problem.
- When it started, with time zone, and what changed just before (update, new plugin, DNS change).
- The exact error text or a screenshot.
- What you already tried.
- Versions: WordPress, PHP, theme, and the plugins involved.
- Who is affected: only you, everyone, one device, one country.
- Backup: the date of the last good backup.
Get the facts cheaply
- PHP and WordPress version: Tools, Site Health, Info.
- Error text: debug log guide or console guide.
- Is it only you? Test on mobile data.
Do not
- Do not send passwords in a chat or email. Use the host's secure access or a temporary account you delete afterwards.
- Do not make five changes at once while waiting. Note each change you do make.
More: site down checklist.
Related guides
- YouTube Video Embed Not Working or Showing an Error on Your Website
- WordPress XML Sitemap Gives 404 or Is Not Generating
- Changed the WordPress Address (URL) and Now the Site or Login Is Broken
- wp-config.php Explained: The Settings That Matter and How to Edit Them Safely
Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.