The difference between a hire that fixes the site in hours and one that bills you for a week of 'investigation' is rarely skill — it's what you hand over on day one. An engineer can't inspect what you can't open, so every missing access costs paid hours and hands the freelancer the excuse of 'urgency'. Fifteen minutes of reading this list and gathering the items below turns you from a nervous buyer with a panic attack into a client who arrives with the keys already in the lock.
Check these first, yourself
Write the exact problem in one plain sentence: 'checkout shows error after card, since Tuesday, browser Chrome on phone'. Include when it started, what changed right before, and the exact URL. This one sentence silently filters 80% of bad quotes.
Gather your hosting — The service that runs your site on a server; the plan you pick decides your speed ceiling and your crash risk. panel login (the dashboard with cPanel/hPanel, not the WordPress admin). Most fixes live in the panel — backups, logs, caching, PHP — The language most WordPress sites run on; an outdated version is one of the most common ways in. settings — and no panel means the first day is spent rescuing it from whoever owns it.
Collect FTP — File Transfer Protocol — the old way of moving files to a server; left open and unencrypted, attackers love it./SFTP access or a file manager route, plus any staging/development URL. Engineers work on a copy first when they can; a stage saves them from touching live, which saves you a second incident.
Copy the exact error text and take a screenshot of the broken page (full page, not just the top). 'It's broken' is useless; a full-page screenshot with visible URL often answers the question without a single access.
Should you fix it yourself or call a rescue?
Still have questions?
Is it really worth spending time on this before hiring?
It's the highest-ROI hour you'll spend. Every item you collect removes one thing an engineer will otherwise bill you for locating — and a client who arrives prepared also gets honest quotes faster, because the scope is 'fix this' instead of 'find what I need first'.
What if I don't have the hosting credentials anymore?
That's the most common recovery case — usually the person who built the site took them along. Hosts can reset panel access if you can prove ownership by email, and the same documents that prove it (invoice, domain registrar — The company where your domain name is registered — whoever controls that account controls the domain.) unlock most recovery paths.
Should I give a contractor all my passwords?
Only what the job needs, and never more. Hosting panel with a temporary password is usually enough — you can rotate it after they finish. Handing over your main email or admin accounts 'just in case' is how surprise bills happen.