> ## Documentation Index > Fetch the complete documentation index at: https://apidocs.writesonic.com/llms.txt > Use this file to discover all available pages before exploring further. # Activity log > Every change to a page, and every signal that followed it, on one timeline. Correlation you can read, not attribution you have to trust. The Activity log is the per-page record of what changed and what happened next. Without it, connecting a change to a later result is guesswork. ## One timeline holds the changes and the signals The log records changes to a page, technical and editorial, whoever made them, agent or human. Alongside those it records what happened afterwards from both a search and an AI search perspective. So a single page's timeline might read: on 20 June you refreshed the content and rewrote the title. On 25 June ChatGPT started citing the page for a prompt it had ignored. On 26 June a new keyword entered the top ten. Those events sit next to each other in the order they happened. That's the whole idea. On each page's detail view, Activity sits beside Overview, SEO, AI Search and Content. ## Events are typed, and most carry the numbers Entries are grouped by date and filtered by **All**, **Changes** or **Alerts**, with a legend separating alerts, changes and impact. Each entry names what happened rather than logging a diff. A few real ones: | Event | What it recorded | | ------------------------ | ---------------------------------------------------------------------- | | Ranking improved | Average position for this page improved from 17.0 to 7.0 | | Ranking dropped | Average position for this page dropped from 2.0 to 17.0 | | SERP feature gained | Google added the People Also Ask feature on this page's target query | | SERP feature lost | Google removed the People Also Ask feature on this page's target query | | New keyword in top 10 | A query this page didn't rank for entered the top ten | | Page displaced from SERP | The page lost a result it previously held | The ones with before-and-after values state them inline. The rest carry a **View details** link. Activity log entries grouped by date, showing a lost SERP feature and a ranking improvement with its before and after positions Filter to **Changes** when you want to see only what was done to the page, and to **Alerts** when you want only what happened to it. Reading both together on one timeline is the point. ## It shows correlation, and it says so The log does not claim your change caused the result. It cannot, and nothing that reads a timeline can. What it gives you is the sequence, on the page, with dates. You decide whether the change and the signal are related. That judgement is yours, and it's a better position than the usual one, where the change and the outcome live in different tools and nobody can line them up at all. ## Turn a hunch into an experiment, then scale it The sequence becomes useful when you run it deliberately. Add FAQs to five pages. Wait, then read the five timelines. If all five moved in the same direction, you have something worth believing. Now run the same change across fifty pages, then a hundred, using a [playbook](/agents/playbooks) and a [grid](/agents/grids) so the change is identical every time. That is the difference between an opinion about what works on your site and a result you can repeat. It also means a change that did nothing gets found early, on five pages instead of five hundred. Leaving a comparable set of pages untouched makes the comparison stronger, though it isn't required to get value from the log. ## What's next See where the Activity tab lives. Run a proven change across many pages.