Quickstart
Add your first project, run a scan, and read your SiteCMD Score.
Pre-launch note. SiteCMD downloads aren’t open yet. Get on the launch list at /download and you’ll get the install link the moment we ship. The rest of this guide describes the app as it works at launch.
This is the short version. If you want detail on installing or on what a scan actually does, see Installation and Your first scan.
1. Open the app
When you open SiteCMD for the first time, it boots straight to the project setup screen. There are no projects yet, no scan history, nothing to look at. That’s expected.
2. Add a project
A project is one website. You give it a name and one or more URLs, each tagged with an environment: production, staging, development, or local. The form starts with a single production row.
If you have the source folder on your machine, link it now. SiteCMD reads your package.json, composer.json, requirements.txt, and similar files to detect your stack and pre-fill a sensible local URL. Linking the folder is optional, but it unlocks Code Scan and tailors Core’s fix guides to your framework.
3. Run a scan
Click Run Scan in the top bar. SiteCMD checks the live site, then audits the linked source folder if you’ve connected one. The scan progress overlay shows you the current stage and lets you cancel at any time.
4. Read your SiteCMD Score
When the scan finishes, the dashboard shows your SiteCMD Score out of 100. The score starts at 100 and goes down for each active issue we find, weighted by severity. Critical issues cost the most, lows barely register, and fixing, dismissing, or marking an issue not applicable gives the points back.
There are no severity cliffs: criticals cost the most, but they never lock your score to an arbitrary number. The one exception is a confirmed, actively exploitable security finding (an exposed secret, SQL injection, and the like), which pins the score at 49 until it’s fixed. An ordinary critical just costs meaningful points, proportionally, and you earn them back the moment the issue is resolved.
The dashboard shows the top issues driving the score, grouped by category. The fastest way to bring the score up is to start at the top of that list.
What’s next
- Installation if you want the install details and system requirements.
- Your first scan for what the scan actually checks, how long it takes, and where the results live.
- The SiteCMD Score for how the score math works in detail.
- AI editor setup to wire SiteCMD into Cursor, Claude Code, Windsurf, Cline, Codex, VS Code, GitHub Copilot, Zed, or JetBrains so your AI assistant can read your scan results and write fixes.