gsc-site-profilelisted

# Site profile A site profile is a short Markdown file describing one site: its brand terms, what it sells, who it competes with, and which pages matter. The analysis skills read it so that a report says "the /pricing page is losing ground on a competitor-comparison query" instead of "some pages changed position". Everything works without a profile. A profile is what raises the output from correct to useful. ## Where it lives The profile belongs **with the user's own files, not in this plugin**. Plugin directories are replaced wholesale on update, so anything stored inside one is lost at the next version bump. Recommend, in order: 1. The repo or working folder for the site itself — `docs/seo-profile.md`. Best option: it is versioned alongside the thing it describes. 2. The user's Claude project or workspace folder. 3. Anywhere stable the user will remember, as long as they can point Claude at it. Ask the user where to put it rather than choosing for them. Then tell them to mention the path when they ask for analysis, or keep it in a folder Claude already has access to. A profile is **business-sensitive**. Competitor targeting and page priorities are strategy. Do not commit one to a public repository, and do not paste one into a shared document without asking. ## Building one Do not interview the user through all of this. Fill in what can be derived and confirm the rest. **Derive first:** - `list_properties` → the exact `site_url`. - `get_search_analytics` with `d