# aclipp GEO Playbook: Changelog

The current version is always at https://aclipp.com/geo-playbook/en/CHANGELOG.md. The skills check there themselves whether a new version exists.

German version: https://aclipp.com/geo-playbook/CHANGELOG.md

Each version describes what is new and what changes for existing project folders. The notes under "For existing projects" are written so that an AI can carry them out: usually the project check ("Start") reports new versions itself and installs them on request.

A project's version is in the project folder's `README.md` under "Playbook version".

---

## Version 1.0 · 23 October 2026

First release.

### Contents
- Playbook with background knowledge (Part A) and nine steps for setting up a GEO project (Part B), plus maintenance over the years
- Project folder template `geo-brand/` with foundations, goals, questions, measurement, actions, reviews and changelog
- Question set with fixed IDs, core set and extensions, four perspectives (Customer, Talent, Thought Leadership, Brand)
- Project folder with all guides under `skills/`: nothing to install, the AI reads them itself and installs updates itself
- Skills: `geo-project-setup`, `website-check`, `geo-first-run`, `geo-actions`, `geo-project-maintenance`, `geo-with-aclipp`
- Measuring with aclipp via the MCP connector (`https://api.aclipp.com/mcp`): transfer the project folder, fetch measurement data back
- Version check in all skills
- Measurement method (by hand or with a tool) as the first decision, with a schedule for the 7-day aclipp trial
- `AGENTS.md` in the project folder as the starting point: project check with version, progress, gaps, improvements and what is due

### For existing projects
- No changes needed. New projects start with `geo-project-setup`.

---

<!--
Template for new entries (insert at the top, newest version first):

## Version X.Y · DD Month YYYY

### New
- …

### Changed
- …

### For existing projects
Specific steps that can be carried out. Always written so that no data is lost and no IDs are reassigned. Examples:
- In `3-questions/questions.csv`, add a new column `xyz` after `perspective`, leave it empty for existing rows.
- Create a new file `1-foundations/abc.md` from the template and fill it in with the user.
- No change to the core set. (Or, if there is one: why, and that from the update date the long-term comparison only covers unchanged questions.)
- Then set the playbook version in `README.md` to X.Y and record the update in `changelog.md`.

Version numbers: X.0 for changes to the folder structure or the question format, X.Y for new insights, texts and skill improvements.
-->