Claude suggests placing static HTML pages inside wp-content directory

Bug Description

When asked where to upload static HTML pages to a cPanel server, Claude suggested placing them inside the wp-content/ directory and even proposed a URL like ingilizcepedia.com/wp-content/my-pages/.

This is a fundamental web knowledge error. wp-content/ is WordPress's internal system directory for themes, plugins, uploads, and cache. No one — not even a beginner — would serve user-facing static pages from wp-content/.

Expected Behavior

Claude should know that:

• wp-content/, wp-admin/, wp-includes/ are WordPress system directories and should never be suggested for serving custom static pages
• Static HTML pages should be placed under public_html/ with an appropriate folder name
• Claude should ask the user what URL path they want (e.g., public_html/notes-to-speak/ → example.com/notes-to-speak/)

Impact

This demonstrates a serious gap in basic web/server knowledge. A user who trusts this suggestion would end up with unprofessional URLs and potential security concerns.

Environment

• Claude Code (CLI)
• Task: Preparing static HTML pages for cPanel upload