AI assistants can help refresh an old website, but only if they know what kind of website you have. Without that context, they often recommend tools built for a web applications, not for a personal or small business site.
This article explains why that happens, how to spot it, and gives you a short paragraph to paste into your AI chat so its advice fits your site and your hosting.
This article was written by Claude, a frontier AI model made by Anthropic, at the request of the 2mhost team. In other words, it's an AI explaining how to get better advice from AI.
Paste this into your AI chat first
Start your AI conversation with one of these paragraphs. Replace the parts in square brackets with your own details.
If your site is plain HTML (or you want it to be):
My website is hosted on shared cPanel hosting that supports PHP, MySQL and static files. It is a small [type of business] website with about [number] pages: [list the pages]. Its main goal is [for example: getting enquiries, showing my work, taking bookings]. I want a simple, fast, mobile-friendly and SEO-friendly site that I can upload myself through cPanel File Manager or FTP. Please avoid frameworks, build tools, Node.js or Python servers unless they are truly necessary, and explain why if you think they are. Recommend the simplest solution that works on this hosting.
If your site runs on WordPress:
My website runs on WordPress, hosted on shared cPanel hosting with PHP and MySQL. It is a small [type of business] website with about [number] pages, and its main goal is [your goal]. I want to refresh the design and improve speed and SEO without rebuilding it on a different platform. Please suggest the simplest changes, such as a modern lightweight theme, essential plugins only, and content improvements. Do not suggest moving to another technology unless my needs clearly require it, and explain why if you do.
Why this works: it replaces the AI's guesses with facts. Naming your hosting tells it what can actually run on your account. Describing the site's size and goal sets the scale. Asking for the simplest solution, and for reasons behind anything complex, means the AI has to justify complexity instead of assuming it.
Why AI advice is often too big, and how to spot it
A question like "how do I modernize my website?" says nothing about your site's size, hosting or budget. So the AI fills the gaps with a generic modern web project, built on tools like React, Next.js and Node.js that dominate developer tutorials. Suggestions then read like requirements, and security questions get full enterprise checklists with no sense of what matters for a small site.
For a site of a handful of pages, be cautious when the AI suggests:
- Rebuilding in React, Vue, Angular or Next.js
- A Node.js or Python server when your site has no custom application logic
- Build tools, npm or deployment pipelines just to publish a few pages
- Long lists of advanced security features with no explanation of why you need them
A real example: A real example: a business owner asked an AI to build a landing page for his software. The AI produced a React single-page app. It looked fine, but search engines struggled to read it. Fixing that meant adding server-side rendering, which became a project of its own. In the end, the right answer was a simple HTML page that could have been uploaded in minutes.
Start with your goal, not the technology
The goal decides the shape of your site, and the shape decides the tools. Before asking about frameworks or features, answer these:
- What should a visitor do? Call, book, buy, read, or look at your work.
- What content will you add over time? Fixed pages, a blog, a growing gallery, products.
A brochure or portfolio site fits plain HTML, siteSPARK builder or WordPress, and a fast, mobile-friendly, HTTPS site like that runs fine on standard hosting. Regular publishing fits WordPress. Selling online fits an e-commerce platform. Client portals, custom booking systems or software with user accounts need a real web application, and that's the one case where the bigger tools are justified. If that's you, tell the AI so its advice is sized correctly.
Content comes first
Visitors come for information, not for effects or the software behind the page. Design exists to deliver your content clearly; the technology stack is invisible to them.
- Write the content first, then design around it. A design built on placeholder text rarely fits the real thing.
- Lead with what visitors need. What you do, who it's for, and how to reach you.
- Be specific and use real photos. Real services, examples and images build more trust than generic text and stock photos.
- Keep it current. Outdated hours, prices or news damage trust more than an old design does.
This is often where AI helps most: improving your wording and organizing your pages. Just check AI-written text for accuracy, as it can invent claims.
Before you change anything
- Back up your site. Download a full backup from cPanel, including files and databases.
- Test first if you can. Try new pages in a subfolder or subdomain before replacing your live site.
- Don't paste server settings blindly. If the AI gives you .htaccess rules, PHP settings or security headers, have someone who manages your hosting check them first. One wrong line can take a site offline.
- Never share passwords with an AI chat. Keep cPanel, FTP and database credentials out of your conversations.
- Question new technology before adding it. If an AI says you need Node.js, Python or a special security feature, ask it why, given your site's goal. Then confirm with your hosting provider or developer.
A final word
AI only knows what you tell it. Give it honest context, put your content first, and ask it to justify anything complex.