Product features
A clean history for SEO work and page changes
Record manual SEO work, catch important page changes, create follow-up tasks when needed, add impact results, and turn the project history into reports.
Know what changed, who was involved, when it happened, and what happened next.
How SEO Logbook works
SEO Logbook connects the parts of SEO work that usually live in separate places.
Part 1
Record manual work
Log title changes, internal links, content updates, technical fixes, schema changes, and other SEO work.
Part 2
Detect page changes
Monitor priority URLs for title, meta, heading, canonical, schema, robots, status code, redirect, and fetch changes.
Part 3
Create follow-up tasks
Create a task from a system log when a detected change needs action, with the URL and change context attached.
Part 4
Report the history
Use logs, tasks, monitor runs, health issues, and impact results to build a clear monthly summary.
Manual logs
Record the SEO work your team actually did
Some SEO changes are intentional and already complete. They do not need a new workflow. They need a reliable record.
Use manual logs to capture what changed, which URL was affected, who recorded it, why it mattered, whether it was important, and what impact was reviewed later.
Automatic monitoring
Catch page changes that happen outside the SEO workflow
SEO changes do not always happen inside an SEO task. A CMS edit, deployment, template change, or plugin update can change important page elements without a clean note.
SEO Logbook monitors selected URLs and records system logs when tracked elements change.
Tasks
Turn detected problems into follow-up work
Not every system-detected change needs action. But when it does, you can create a task directly from the system log.
The task keeps the affected URL and change context, so the team does not need to copy details from one tool into another.
URL history
Give every important URL its own SEO history
A single page can have manual work, detected changes, tasks, verification notes, and impact results over time.
SEO Logbook keeps that history attached to the URL, so your team can understand why a page changed before changing it again.
Impact results
Add impact when the result becomes clear
SEO changes often take time to show results. When you review the outcome later, add an impact result to the original log.
Do not fake analytics. Keep this manual and context-based.
Reports
Turn recorded work into reports people can understand
At the end of the month, SEO Logbook uses the project history to help you explain what happened.
Team access
Keep team work and client visibility separate
Workspace members can work across projects. Project-specific users can be limited to the projects they should see.
For role definitions, read the Help guide.
Start building SEO history
Record what happened, keep it attached to URLs, and use that history when tasks, reviews, and reports need context.