Plain-English guide to SEO Logbook

Logs record manual SEO work and monitor-detected changes, tied to the URLs they affect.

They give the project a shared history for what changed, why it changed, and what happened later.

A title rewrite, internal link update, noindex fix, or monitor-detected change can all become part of the same timeline.

URL inventory is the list of URLs stored in a project.

It gives the project a clean list of important pages without requiring every stored URL to be monitored.

An agency stores 200 client URLs, then chooses the 25 most important pages for scheduled monitoring.

An active monitor is a stored URL with monitoring turned on.

Active monitors are the pages SEO Logbook checks automatically on a schedule.

A launch page can sit in inventory first, then become an active weekly monitor when the campaign starts.

Scheduled Scan Credits are automated monitor checks used this cycle.

Each scheduled check of one active monitored URL uses one credit. Daily monitoring uses more credits than weekly or monthly monitoring.

One URL checked weekly uses about 4 credits per month. One URL checked daily uses about 30.

An instant scan is a manual live check started by a user.

It lets a person re-check a page while investigating a finding or documenting follow-up.

After fixing a title tag, a user can run a manual check and then document the follow-up task.

Retention controls how far back history and reports can use data.

It sets the available window for older logs, monitor activity, health issues, and report ranges.

A report can summarize only the recorded activity that still falls inside the workspace retention window.

Reports summarize recorded SEO work, monitor-detected changes, tasks, health issues, and Impact Results for a selected period.

They turn project history into a client-ready summary without claiming data SEO Logbook does not store.

A monthly report can show important updates, completed tasks, monitor activity, and recorded outcomes.

Workspace members get workspace-level access to areas and projects according to their role.

This keeps owners, admins, members, and viewers managed from one workspace team list.

An admin can manage members, projects, and settings, but ownership transfer stays with the owner.

Project-specific users only access the projects they are invited to.

It lets agencies and teams give focused access without opening the whole workspace.

A project editor can work inside one invited project. A project viewer has read-only access to that project.

Email alerts go to your inbox. In-app notifications appear in the bell while using SEO Logbook.

Project defaults control which email alert types are allowed, while personal preferences control what you receive.

You can keep task assignment emails on, then turn off future important-log bell notifications if they are too noisy.

Team seats are working users. Client viewers are read-only or limited-visibility users.

It keeps internal collaboration separate from client visibility, especially across multiple projects.

An SEO manager is a workspace member. A client stakeholder can be invited as a project viewer.

Impact Results are manually recorded outcomes added after a change.

They let a team document what happened later without claiming SEO Logbook measures outside performance automatically.

After reviewing outside reporting, a user adds a short manual outcome to the original title rewrite log.

Monthly reports summarize the previous calendar month from recorded project activity.

Reports are built from the work already captured in logs, tasks, monitor runs, health issues, and manual Impact Results.

A client report can show what changed, which tasks were completed, and which monitored issues needed attention.

Sitemap import previews URLs before adding selected ones to inventory.

It helps teams add many project URLs without turning every discovered URL into an active monitor.

A user previews a sitemap, selects the pages that belong in the project, and adds them to inventory.