What a website emergency assessment includes

When a business site stops working, the first question is almost always “how much will this cost?” The honest answer before anyone has looked is: it depends. That is not evasion — it is the difference between guessing and investigating.

A website emergency assessment — what Rescue 404 calls the paid rescue diagnostic — is the structured first step that turns “it depends” into a written scope. You pay for real investigation, not a sales call dressed up as support. Current pricing and credit rules are on Pricing; the diagnostic fee is credited toward the repair when you proceed with us.

This post explains what that assessment includes, what it does not include, and why it exists as a separate step from the repair itself.

Why assessment comes before repair

Outages rarely have one obvious cause. A white screen might be a plugin conflict, a PHP version mismatch, corrupted core files, exhausted server memory, a bad .htaccess rule, DNS pointing at the wrong host, or a combination — especially on sites that have not been maintained in years.

Quoting a fixed repair price from a one-line email (“site is down”) forces someone to either pad the quote heavily or under-scope and surprise you later. Neither is fair.

Assessment exists so:

• You know what was actually checked
• Likely causes are ranked with evidence, not guesses
• Repair scope and pricing reflect reality
• You can approve or decline major work with eyes open

If you are deciding whether you need repair or a full redesign, read Website repair versus website redesign first — assessment answers “what is broken,” not “should we rebuild the brand.”

What the assessment covers

Every stack is different, but a proper emergency diagnostic should touch these layers in proportion to the symptoms:

Symptom and timeline intake

What broke, when it started, and what changed recently — updates, DNS moves, new plugins, hosting migrations, password changes, marketing campaigns adding scripts. This sounds basic; it prevents chasing the wrong layer for hours.

Public-facing checks

How the site fails for a visitor: HTTP status codes, SSL errors, redirect loops, Cloudflare or CDN challenges, geographic differences, mobile versus desktop. Screenshots and exact error text matter.

WordPress and application layer (when applicable)

For WordPress sites: admin accessibility, fatal error logs, debug output when safely enabled, plugin and theme inventory, recent update history, database connectivity, cron health, and obvious malware indicators. We look for the smallest reversible change that explains the failure — not a full rebuild.

Hosting and server environment

PHP version compatibility, resource limits, disk space, error logs on the server, file permissions, suspension notices, and whether the host panel is reachable. Many “WordPress problems” are server problems wearing a WordPress skin.

DNS and domain resolution

Whether the domain resolves to the expected IP, nameserver consistency, propagation issues, expired registration, and mixed WWW/non-WWW behavior. A perfectly healthy site files fail when DNS points elsewhere.

Access and ownership reality

What logins exist, what is missing, and whether recovery requires registrar, hosting, or former-vendor cooperation. If you cannot reach admin or hosting, assessment maps which recovery path is realistic — see How much access recovery can cost and why.

Backup posture

Whether usable backups exist, where they live, and whether restore has ever been tested. Assessment is not a backup product — but quoting repair without knowing restore options would be reckless.

What you should receive afterward

A completed assessment should produce written findings, not a verbal “we think it is the cache.” At Rescue 404, that means:

• Plain-language summary of what is failing and where
• Likely root cause or ranked hypotheses with evidence
• What was ruled out
• Recommended repair path with fixed-scope pricing when the work is clear enough to quote
• Honest “no” when the platform, ownership, or stack blocks a safe fix
• Clear note on what is urgent versus what can wait

You should be able to forward the findings to another vendor or internal IT and have them understand the situation without a follow-up call.

What assessment does not include

Naming boundaries prevents disappointment:

• It is not unlimited repair time. Assessment investigates and quotes; the repair is approved separately.
• It is not a redesign discovery. Visual brand work and information architecture belong in a design project.
• It is not free. Free “diagnostics” are often sales screens with no log review. Paid assessment aligns incentives toward investigation.
• It is not a guarantee the fix is cheap. Sometimes assessment reveals malware, corrupted databases, or abandoned themes that require substantial work — but you learn that before authorizing it.
• It is not ongoing care. After repair, supervision belongs in a care plan — see Managed care versus hourly support.

Assessment also does not bypass legal ownership checks. We help account holders recover access they can prove — not bypass someone else’s registrar account.

How long assessment takes

Most rescue diagnostics land in a focused block — often 40–90 minutes of skilled work across the layers above, plus documentation. Complex multi-system failures take longer and may surface follow-on scopes.

Why the diagnostic is paid upfront

Three reasons, stated plainly:

1. It reserves real calendar time for investigation, not a five-minute glance between other tickets.
2. It filters unserious requests so emergency capacity stays available for owners whose businesses are offline.
3. It credits toward repair when you proceed — you are not buying a separate product and then paying full price again for the same findings.

Full payment and credit rules are documented on Pricing and Refunds & Payment.

When to skip DIY and start with assessment

You can try safe DIY steps when admin or hosting access still works and the business is not bleeding revenue — many are documented in our Website Repair knowledge base.

Move to paid assessment sooner when:

• The site is down during business hours and leads or checkout are affected
• Admin and hosting are both unreachable
• You already tried disabling plugins or clearing cache and nothing changed
• The host suspended the account or reports malware
• Multiple systems changed at once (migrate + DNS + SSL + update)
• A former developer or vendor still controls critical access

Waiting three days while staff tries random fixes often costs more than starting with evidence.

What happens after you approve repair

Assessment ends with a decision point. If you approve the quoted repair:

• Work proceeds within the agreed scope
• Diagnostic credit applies per current pricing rules
• You receive confirmation when the agreed outcome is met — or an early call if discovery during repair requires re-scoping

If you decline repair, you still keep the findings. You paid for investigation and documentation — not a hostage situation.

The point of the step

Emergency assessment exists because guessing on broken revenue-critical sites is expensive. It separates investigation from execution, gives you a paper trail, and lets you compare repair versus redesign versus care from a stable factual baseline instead of panic.

If your site or admin is broken now, that baseline is the right place to start — not an open-ended hourly meter and not a redesign mockup. Current diagnostic pricing and what happens next are on Pricing.