SiteGround Support FAQ & Answers

Frequently asked questions

These are the questions that come up most often in real SiteGround support conversations, answered plainly and organized by what you're actually trying to do.

Hosting and troubleshooting

Errors, lockouts, and downtime, sorted

Website speed & performance

Caching, CDN, and load-time fixes

Security and malware

Scans, suspensions, and phishing

Hosting for WordPress

Staging, migrations, and plugin errors

AI solutions for small business

AI Studio, Coderick AI, and WordPress agents

Website building

Builders, plans, domains, and collaborators

Vibe coding

Building with AI-generated code

Billing, plans, & cancellations

Renewals, refunds, and Expert Care

Hosting and troubleshooting

The most common errors and lockouts and what's actually happening behind each one.

  • Why am I seeing "This site can't be reached" or a DNS error?

    Nine times out of 10, your domain either isn't pointing to SiteGround yet, or a DNS change hasn't finished spreading across the internet. If you just moved your domain here or edited a record, give it up to 24 to 48 hours before worrying. Longer than that, and it's worth double-checking that your nameservers actually list SiteGround, since a single typo in one record is enough to break everything.

    Before you assume it's still propagating, try loading the site from your phone's mobile data. Your computer's local DNS cache is the most common false alarm here: it remembers the old, broken address long after the server has already been fixed. Walk through the full checklist in fixing DNS_PROBE_FINISHED_NXDOMAIN.

  • What does a 500 Internal Server Error mean, and how do I fix it?

    A 500 error just means something in your site's code failed to run, and the server doesn't tell you what, on purpose. Usually it's a plugin or theme conflict, a corrupted .htaccess file, or a script that hit a memory limit. Guessing rarely works here; the PHP error log almost always names the actual culprit.

    If wp-admin still loads, deactivate plugins one at a time until the error disappears. Locked out entirely? Use the file manager in Site Tools to rename your plugins folder, which switches everything off at once. Both paths are covered in our 500 error guide.

  • Why is my site showing a 403 Forbidden error?

    A 403 means the server saw your request and refused it anyway, usually because a firewall or security rule flagged something as suspicious: an odd user agent, a request pattern that looks bot-like, or file permissions set too loose or too tight. It's your security doing its job, even when the thing it caught happens to be your own SEO tool.

    Check file and folder permissions first (644 for files, 755 for folders). Still stuck? The block is likely at the firewall layer, and a specific IP or user agent needs to be added to an allowlist. Full details in our 403 Forbidden error guide.

  • Why did SiteGround block my IP address, and how do I get it unblocked?

    Almost always, it's not an attack: it's a saved email account somewhere with an old password, quietly trying and failing to log in over and over. After enough failed attempts, the firewall reads that as a brute-force attempt and blocks the IP, which then locks you out of Site Tools too, since it's the same address.

    Support can lift the block in seconds, but it'll come right back unless the stale credential gets found and fixed. Check every phone, laptop, and mail app tied to that address, not just the one in front of you. Our website security tips guide has more on keeping login attempts from tripping your own firewall.

  • I can't log into my SiteGround account. What do I check first?

    Start with the basics in order: confirm you're at login.siteground.com rather than a bookmarked page from years ago, try a password reset, and check whether your two-factor device is the problem (a new phone without your authenticator app is a classic). If you signed up with Google, use the login with Google option rather than guessing at a password that may never have existed.

    Still locked out, or lost access to your email and 2FA together? There's a proper recovery process for proving account ownership: see recovering access to your account.

  • My site loaded fine yesterday. Why is it down or showing an old version today?

    Clear your browser cache before anything else. It's the single biggest false alarm in hosting support: your browser is quietly showing you a saved copy of the page from before whatever changed. If the page still won't load after that, then it's time to check DNS or server status.

    On caching-enabled plans, a code or content update sometimes needs a manual cache purge from Site Tools before visitors see it. Here's how, step by step: how to clear cache and cookies.

  • What's a data center, and can I move my site to a different one?

    Your data center is simply the physical location of the server your site lives on, and it matters most for speed: a visitor in Sydney gets a faster response from a server in Sydney than from one in Chicago. You picked it (or we picked it based on your audience) when the account was first created.

    Moving later is possible, but it's a backend change our team handles for you, not a setting you flip yourself, and it does involve a short window of downtime while files and databases relocate. Read more in what is a data center.

Website speed & performance

What actually moves the needle on load times, and the tools already included in your hosting.

  • How can I make my WordPress site load faster?

    Start with what's already included before buying anything new. SuperCacher and Speed Optimizer ship with every SiteGround plan and handle server-level caching, image compression, and front-end optimization for you. Slow sites are usually the result of unoptimized images and too many active plugins, so that's where to look first.

    Our WordPress performance guide lays out the order that works best: dynamic caching, then front-end optimization, then a fresh speed test before you consider adding a third-party plugin.

  • What is SuperCacher and Speed Optimizer, and do I need to configure them?

    SuperCacher is the server-side caching engine, and Speed Optimizer is the WordPress plugin that puts a dashboard on top of it, along with front-end features like lazy loading and minification. Dynamic caching turns itself on for most plans automatically, so you're already benefiting from it whether or not you've opened the plugin.

    Where hands-on configuration helps is WooCommerce stores and membership sites, where cart and checkout pages sometimes need to be excluded so every visitor doesn't end up seeing the same cached page. See SuperCacher for how to set exclusions.

  • What are inodes, and why do I keep getting an inode limit warning?

    An inode is a unit that counts every single file on your account: every image, every email, every cache file, every log entry. Shared hosting plans cap the total number, and the usual culprit isn't your website content at all, it's an accumulation of old backups, cache files, or a mailbox with years of unread messages.

    Deleting unused plugins, clearing the media library of duplicate uploads, and emptying old email folders usually solves it. Our guide on reducing inode usage ranks the biggest offenders.

  • What's a CDN, and should I turn it on?

    A content delivery network keeps copies of your images, CSS, and JavaScript on servers around the world, so someone browsing from another country pulls those files from a nearby location instead of your one origin server. You'll notice the difference most if your visitors are spread across several countries.

    Turning on the SiteGround CDN takes a couple of clicks in Site Tools and doesn't touch your DNS or code. See managing your CDN to turn it on.

  • Does caching or the CDN ever break my WooCommerce cart or checkout?

    Occasionally, yes, and it's worth knowing about. If dynamic caching serves up a static version of a cart or checkout page, one customer can briefly see another customer's cart, which is about as bad a bug as a store can have. WooCommerce plugins typically flag these pages so caching skips them automatically, but a theme conflict or an overly aggressive third-party cache plugin can quietly undo that protection.

    If a customer reports a cart behaving oddly, check the caching exclusion list for cart, checkout, and my-account pages before you start digging into the payment gateway. Our guide to dynamic caching shows where those exclusions live.

Security and malware

What to do the moment you see a warning, a suspension notice, or a suspicious email.

  • My site got flagged for malware. What do I do now?

    Run a scan from the SiteGround Site Scanner in Site Tools first: it's free on every plan and will list the exact infected files by path, rather than making you guess. Most infections trace back to an outdated plugin, a nulled theme, or a compromised admin password, not to SiteGround's infrastructure.

    Delete the flagged files, update everything (core, theme, and every plugin), and change your admin password before you consider it resolved. If Site Scanner can't clean it on its own, Expert Care's security team can remove the infection manually. See Site Scanner for how the free and paid tiers differ.

  • Why is my site suspended, and how do I get it reactivated?

    A suspension almost always follows a confirmed malware detection. It's a protective step, so an infected site can't be used to attack visitors or other accounts on the same server while it's still dirty. Nothing about it is permanent, and it's not a billing issue.

    Clean the infected files yourself, or have Expert Care do it, then run a fresh scan from Site Tools. A clean result usually lifts the suspension on its own; if it doesn't, support can confirm and reactivate manually. Start with the Site Scanner.

  • I received an email that looks like it's from SiteGround asking about billing or my domain. Is it real?

    Treat anything that pushes urgency around payment, domain expiry, or account suspension with suspicion, especially if the sender address looks even slightly wrong or the link doesn't lead to siteground.com. Phishing attempts that copy hosting providers work precisely because people panic first and check second.

    Don't click the link. Type the address in yourself and log in directly to check your real billing or domain status. If what you see there doesn't match the email, the email was fake. If you've already clicked something you shouldn't have, our guide on recovering a lost or compromised account covers what to do next.

  • Should I turn on two-factor authentication for my SiteGround account?

    Yes, and it's worth the extra 30 seconds at login. A password is one factor; a code from your phone is a second, and together they stop most account takeover attempts even after a password has leaked somewhere else entirely.

    See setting up two-step verification to turn it on for your account login.

  • Why are AI crawlers or bots getting blocked on my site?

    SiteGround's firewall treats unfamiliar or high-frequency automated traffic the same way it treats a potential attack: it challenges or blocks it first and asks questions later. That catches some legitimate AI crawlers indexing your content, along with SEO tools and uptime monitors, in the same net as actual threats.

    If you want a specific crawler let through, it needs to go on an allowlist rather than fight the firewall on every visit. See allowed AI crawlers for what's permitted by default and how to request others.

Hosting for WordPress

What's specific to running WordPress on SiteGround, and how to fix the errors that come with it.

  • What's the difference between regular web hosting and hosting for WordPress?

    Hosting for WordPress runs on the same shared infrastructure as regular web hosting, but with WordPress pre-installed, automatic core and plugin updates handled for you, and tools like staging and one-click cloning already built into Site Tools. If your site runs on WordPress, there's really no downside to picking the WordPress-specific plan.

    See WordPress hosting vs. web hosting for the full comparison.

  • My WordPress site shows a "critical error" message. What happened?

    WordPress shows this deliberately vague message whenever a PHP fatal error stops the site from loading, most often right after a plugin or theme update introduces a conflict. It won't tell you which plugin, but your PHP error log will.

    If you have file access, use the file manager to rename your plugins folder, confirm the site loads again, then reactivate plugins one at a time until the error comes back and points you to the problem. Our file manager guide covers the exact steps.

  • How do I test changes before they go live on my real site?

    Use the staging tool built into Site Tools instead of editing your live site directly. It builds a full copy of your site on a separate URL, so you can update plugins, try a new theme, or reshuffle a page without any risk to what visitors see right now.

    Happy with the result? One deploy action pushes it live. See creating a staging copy to get started.

  • Can I clone my WordPress site to build a second version of it?

    Yes. Cloning copies your files and database onto a new domain or subdomain within the same account, which comes in handy for a client demo, a seasonal variant, or just a sandbox that's separate from your staging environment.

    See cloning WordPress for the step-by-step process.

  • How do I move my existing WordPress site to SiteGround?

    Install the SiteGround Migrator plugin on your current site, connect it to your new account, and it handles the file and database transfer for you. That covers the vast majority of standard WordPress sites without any manual file wrangling on your part.

    Got something larger or heavily customized? Our team can migrate it for you at no cost on eligible plans. Start with the WordPress Migrator or request a free migration.

  • Why did an automatic WordPress update break my site?

    Sometimes a core, theme, or plugin update changes something another plugin depended on, and the conflict only surfaces once the update actually runs. It's exactly the scenario staging exists for: testing an update there first catches most of these before they ever touch the live site.

    If it's already happened, restoring a recent backup is usually the fastest fix, followed by testing that same update on staging before you apply it again. Our guide to creating a full site backup covers restores too.

AI solutions for small business

What SiteGround's AI tools actually do, in plain language, without the hype.

  • What is SiteGround AI Studio?

    AI Studio is where SiteGround's AI agents live: tools that can draft content, check your online reputation, or take care of repetitive WordPress admin work, all built into your account instead of sold as some separate subscription elsewhere. The individual capabilities are called agents (WordPress Agent, Reputation Manager, and more get added over time).

    See the WordPress AI agent guide for how one of these agents works day to day.

  • What is Coderick AI, and who is it actually for?

    Coderick AI is SiteGround's AI website builder: describe what you want in plain language, and it generates a working site instead of handing you a blank canvas and a toolbox. It's built for people who want a real website without learning a builder interface or touching a single line of code.

    See building a website with AI for how it compares to more hands-on tools.

  • Can AI actually build my whole website for me, start to finish?

    For a small business site, a homepage, a services page, a contact form, and some basic branding, an AI builder like Coderick can get you most of the way there in a single sitting. Where it still needs a human touch is anything specific: an unusual booking flow, an integration with a tool you already use, or brand details that are hard to capture in a prompt.

    Treat what it hands you as a strong first draft, not the final word. See using an AI website builder with no code for what to check before you publish.

  • Will AI-generated content or pages hurt my SEO?

    Search engines don't penalize content for being AI-assisted. They penalize content that's thin, repetitive, or unhelpful, and that standard applies whether a human or a model wrote it. What tends to hold AI-generated pages back is generic phrasing, plus missing the specific local detail that helps a small business page rank at all.

    Our SEO checklist covers what still needs a human review pass before publishing.

  • How do the AI agents in WordPress 7.0 work?

    WordPress 7.0 added native AI connectors, so approved agents can work directly with your site's content and settings instead of needing a separate plugin for every AI task. On SiteGround, that pairs with AI Studio's agents to handle things like content drafts or site health checks right from your existing dashboard.

    See how AI works in WordPress 7.0 for what's new and how to turn it on.

  • Is Power Mode AI agent a paid add-on?

    Power Mode is a higher-capability tier for the AI agent running on your WordPress site, built for accounts that need faster or more frequent AI-driven tasks than the standard tier covers. See Power Mode AI agent for WordPress for current availability and what it unlocks compared to the standard agent.

Website building

Picking a starting point and getting the basics connected.

Vibe coding

Building with AI-assisted code, and when it's the right tool for the job.

  • What is "vibe coding," exactly?

    Vibe coding means describing what you want in plain language and letting an AI model write the actual code, rather than writing it yourself line by line. You're still working in a developer environment (a code editor, a repository, sometimes a command line), but the model does the syntax while you steer the direction.

    See vibe coding explained for a full walkthrough, or the vibe coding glossary if the terminology is new to you.

  • How much coding do I actually need to know to vibe code?

    Less than you'd think to start, more than zero to finish. Getting something working on screen requires almost no code knowledge: you describe, the AI writes. Where the gap shows up is when something breaks and the AI's fix doesn't work, or when you need to judge whether the generated code is safe to put in front of real users. That's when reading code, even slowly, stops being optional.

    A fair rule of thumb: if you can't roughly follow what the generated code does, keep vibe-coded projects to prototypes and personal tools. For the setup side of the equation (repositories, editors, deployment), our tutorial on using Git on SiteGround shows what that workflow looks like in practice.

  • Do I need a GitHub account and a code editor to vibe code a website?

    Generally, yes. Most vibe coding tools expect a code repository and a code editor or command-line tool connected together, before you've written a single word of website copy or picked a font. That's a developer setup checklist, not a website launch plan, which is exactly why it's not the right starting point for most small business owners.

    If that sentence made your palms sweat rather than nod along, our Git tools section is a good place to see what that setup actually involves before committing to it, or an AI website builder like Coderick will get you to a live site much faster.

  • What's the real difference between vibe coding and using an AI website builder?

    An AI website builder generates a finished, hosted website from a prompt, no code, nothing to deploy yourself. Vibe coding generates code that you still have to run, test, and deploy, which brings a lot of equipment along that you won't need if all you wanted was a website.

    Vibe coding earns its keep when you're building something custom, a bespoke app, an internal tool, an integration that doesn't exist as a plugin, rather than a standard business site. See building a website without Claude Code: the Coderick AI path for a closer look at the simpler alternative.

  • Can I turn an AI-generated design, like a Claude artifact, into a real, live website?

    Yes. An artifact or AI-generated mockup is front-end code that needs a place to actually run: hosting, a domain, and usually a bit of cleanup to make it production-ready rather than a demo. That's a deployment step, not a redesign.

    See how to turn a Claude artifact into a real website for the exact path from mockup to live site.

  • What are the risks of vibe coding a website my business actually depends on?

    AI-written code can look flawless in a demo and still miss things a careful developer would catch by habit: input validation, error handling for edge cases, and security practices around forms and payments. None of that shows up when you're just trying to get something on screen quickly, which is exactly what vibe coding is optimized for.

    Fine for a personal project or prototype. For anything touching customer data or payments, get a developer to review the security-sensitive parts before it goes live, even if AI wrote most of it. Our guide on securing a website is a good starting checklist.

Billing, plans, & cancellations

Renewals, refunds, and the questions people ask right before deciding whether to stay.

  • Why did my renewal cost more than what I originally paid?

    The rate you paid at signup was the discounted first-term price. Renewals bill at the standard rate for your plan and term, which is shown on the pricing page and at checkout, so it's the introductory discount ending rather than a price hike targeting your account specifically.

    If the jump genuinely caught you off guard, our support and retention teams can often offer a renewal discount or a longer-term rate that brings it back down, so it's worth asking before you cancel outright. Our complete guide to website hosting costs breaks down how introductory and renewal pricing works across the industry, not just at SiteGround.

  • How do SiteGround's shared hosting plans and pricing actually work?

    Shared hosting carries a lower rate for the first term, and the price returns to the standard renewal rate after that. It's how most of the hosting industry prices plans, not something unique to SiteGround, and the renewal rate is shown at checkout, so it's worth a glance before you buy.

    See current shared hosting rates for exact numbers by term length.

  • What is Expert Care, and is it worth paying for?

    Expert Care is SiteGround's premium support add-on: a dedicated team handles hands-on work like malware cleanup, performance tuning, and site management that goes beyond what standard support covers. It's worth it if you don't have the time or technical background to handle those tasks yourself, or you're running a site where downtime costs real money.

    See the Expert Care services catalog to see exactly what's included before subscribing.

  • How does SiteGround compare to Bluehost or Hostinger?

    On entry price, Hostinger and Bluehost are genuinely cheaper, and there's no point pretending otherwise. Where SiteGround earns the difference is what's bundled in: server-level caching and the Speed Optimizer tooling, daily backups, the Site Scanner, and support that consistently rates among the best in the industry. Budget hosts typically sell several of those as paid add-ons, so the honest comparison is total cost for what you actually use, not the headline rate.

    If you're moving from one of them, the switch is more painless than you'd expect: our team handles the transfer for you. See migrating from Bluehost or migrating from Hostinger for how it works.

  • How do domain transfers work, and what do they cost?

    Transferring a domain to SiteGround moves the registration here without touching your site or email, as long as you unlock the domain and get an EPP (authorization) code from your current registrar first. Most transfers include a one-year registration extension as part of the fee, so you're not paying twice for overlapping time.

    See domain transfer fees and what an EPP code is before you start the process.

  • Is SiteGround worth it at renewal prices?

    That depends on what your website is worth to you, and it's the right question to ask. If your site is a hobby project, a budget host at half the renewal price is a defensible choice. If it's a business, the math changes: an hour of downtime, a malware incident handled slowly, or a support queue measured in days tends to cost more than the annual price difference.

    What you're paying for at renewal is the bundled stack (managed updates, backups, caching, security scanning, fast support) rather than just server space. Compare what's included line by line in choosing a suitable hosting plan before deciding either way.

  • Why do people say SiteGround got expensive?

    Because compared to entry-level budget hosting, it is more expensive, and the gap widened as SiteGround moved upmarket over the years. The renewal rates fund things that don't show up on a pricing table: overprovisioned servers instead of oversold ones, humans answering support chats in under a minute, and features included in every plan that budget hosts sell as paid add-ons.

    The daily backup service is a good example of the difference: automatic daily copies of your site are kept for up to 30 days, included, where cheaper hosts often charge separately for backups or keep only one. Whether the overall trade is worth it depends on your site, and the current numbers are always at the current shared hosting rate.

  • Will I get a refund if I cancel my hosting?

    Cancel within 30 days of purchase and the hosting fee comes back in full. Past that window, refunds are usually prorated or unavailable depending on how much of the term you've already used, and domain registrations are non-refundable at any point, since that cost is paid to the registry the moment you buy.

    See refund eligibility for the specifics on your situation.

  • How do I cancel my hosting without accidentally losing my domain?

    Hosting and domain registration are billed and canceled separately, even when you bought them together. Canceling the hosting plan stops hosting; it won't touch the domain unless you cancel that too. Want to keep the domain but drop the hosting? Cancel only the hosting item.

    See canceling your hosting for the exact steps and what happens to your site's files afterward.

  • How do I actually reach SiteGround support, and is there a phone number?

    The fastest route is live chat from inside your account, available 24/7 with typical response times under a minute, and tickets work well for anything that needs a paper trail or a specialist team. Phone support exists too, with the number available from your account's help section once you're logged in; it's gated that way so the person calling can be verified as the account holder.

    For the quickest resolution regardless of channel, a few details up front (your domain, what changed recently, any error text) save a whole round of back-and-forth. See getting help from our support team for how each channel works.