website-positioning-checklisted

# Website positioning check Answer one question: **can the right visitor quickly tell this is for them, what they get, and why to believe it?** This is a diagnostic, not a workshop. Keep the answer to about 300 words — one screen; the bold labels do not count. The cap exists so the owner reads the whole thing: when a finding needs its evidence sentence, keep the sentence and cut elsewhere. Do not edit files unless the user explicitly asks for implementation. ## Inspect Read like an unfamiliar visitor before adopting the site's internal vocabulary. Inspect, in this order: 1. **The rendered homepage.** A live URL if the user gives one. Otherwise build the site and read the built homepage (`dist/index.html` on a kit-built site; there `npm run build` writes only gitignored output). Confirm with `git status` that the tree is still clean afterwards; if it is not, say so. If you cannot build, read the homepage source (`src/pages/` on a kit site). Do not trust a build you did not just make — it may be stale. 2. **The primary offer page** — the services, product, or offer page the homepage's main CTA leads to. Follow it even when it leaves the site (a repo, an app store, a booking tool): the offer is wherever the CTA goes. If the target is missing or unreachable, the visitor has no next step — make that the Primary blur and carry on with the pages you have. 3. **`POSITIONING.md` and `CONTENT_GUIDE.md`**, when present — last, so the site is judged by