How to ask for hosting recommendations and actually get useful answers

[Aior]

"Recommend me a hosting" doesn't work​

The most common hosting question on any forum is "best hosting?" or "I need hosting, what should I use". The most common answer is "depends" — because the question doesn't include what it depends on.

If you want useful recommendations, give the people answering the information they need. Below is the structure that produces good responses.

The information that matters​

Before posting a hosting request, write down:

• What you're hosting — WordPress, custom Node app, e-commerce, large media files, just email, etc.
• Expected traffic — a number, not "a lot". Pageviews / month or peak concurrent users.
• Where your audience is — affects latency requirements
• What you've used before — and why you're moving
• Budget — a real number. "Cheap" is meaningless.
• Technical comfort — can you SSH in and configure nginx, or do you need cPanel + click?
• Compliance / sovereignty needs — GDPR, KVKK, PCI-DSS, etc.
• Special requirements — Redis, Node.js, custom PHP extensions, large file uploads, email volume, etc.

The post that includes all of this gets specific recommendations. The post that says "best hosting?" gets the responder's favourite host.

A good template[/HEADING>

Site type: WordPress, ~5 000 pageviews/day
Audience: mostly Turkey, some EU
Currently on: GoDaddy shared, slow + bad support
Budget: up to 50 USD/month (or equivalent TL)
Technical comfort: I can use cPanel, can ssh if needed but prefer not to
Need: managed backups, free SSL, decent support
Special: WooCommerce with ~200 products, ~30 orders/day

Specific. Easy to recommend against.

Useless requests​

• "Best hosting in 2026?"
• "Cheapest reliable hosting?"
• "Recommend hosting" with no other detail
• "My site is slow, what host should I switch to?" — without diagnosing whether the host is the problem

These get the same noise responses every time. If your post fits this pattern, expect noise.

The response to expect​

A good response identifies:

• A specific host or 2-3 alternatives
• Why those, given your stated criteria
• Caveats — "but only if you can do X" or "but be aware of Y"
• Sometimes: "your real problem isn't hosting" with diagnosis

Diagnosing before switching​

Often the cause isn't the host. Before posting "what host should I move to":

• Run the site through GTmetrix or PageSpeed Insights — what does the diagnosis say?
• Open the terminal and curl the homepage — is the time-to-first-byte 300 ms or 3 seconds?
• Check the database query log — are you running 200 queries to render a page?
• Check the host's resource usage panel — are you actually using less than your limit?

Sometimes the answer is "fix the cache plugin", not "switch hosts".

Asking about transfer / migration​

If you're asking about moving:

• Specify what you have now (host, control panel, app type)
• Specify whether you have backups, and whether the current host will give you a migration package
• Specify whether downtime is acceptable, and how much
• Specify whether you can edit DNS yourself

One pattern we'd warn about​

Trusting a single response. Cross-check at least two answers before committing to a host. Hosting forums have a constant stream of affiliate-pushers and people with single bad experiences. Patterns across responses are reliable; single responses less so.

One pattern that always pays off​

Posting a follow-up after you've decided. "I went with X, here's how it's been." This thread becomes useful for the next person searching. Most requests get the recommendation phase but not the follow-up phase, and the community loses the calibration.

What's the most useful hosting recommendation you've gotten on a forum?​