Help center
Quick definitions and examples for logs, URL inventory, active monitors, scans, tasks, impact results, reports, and team access.
Definition
A manual log is a record of SEO work that someone intentionally adds to a project.
Why it matters
It keeps completed work from disappearing into memory, spreadsheets, or chat threads.
Example
If you update a title tag and add internal links to a service page, you can log the change and attach it to that URL.
Definition
A system log is created when SEO Logbook detects a monitored change or issue automatically.
Why it matters
It helps your team catch changes that happen through CMS edits, deployments, templates, or accidental updates.
Example
If a monitored page changes from indexable to noindex, SEO Logbook records that as a system log.
Definition
URL inventory is the list of URLs stored inside a project.
Why it matters
You can keep important URLs in the project without monitoring every single one.
Example
An agency can store 200 client URLs, then monitor the 25 pages that need scheduled checks.
Definition
An active monitor is a stored URL with automatic monitoring turned on.
Why it matters
Active monitors are the pages SEO Logbook checks on a schedule.
Example
A homepage, pricing page, and top service page might be active monitors. Older blog posts can stay in inventory without scheduled checks.
Definition
One scheduled scan credit equals one automatic check of one active monitored URL.
Why it matters
Scheduled scan credits explain how automatic monitoring usage is counted.
Example
Ten active URLs checked weekly use ten scheduled scan credits each time the weekly scan runs.
Definition
An instant scan is a manual live check started by a user.
Why it matters
It lets you re-check a page while investigating a change or verifying follow-up work.
Example
After fixing a noindex issue, you can run an instant scan and document the result.
Definition
A task is follow-up work attached to a project, URL, log, or detected issue.
Why it matters
It keeps action items close to the SEO context that created them.
Example
If a system log shows an unexpected H1 change, you can create a task for review from that log.
Definition
An impact result is a note added after reviewing what happened after a change.
Why it matters
SEO impact is not always immediate. Impact results let you connect later outcomes back to the original work.
Example
After a title update, you might add: CTR improved after the snippet was rewritten.
Definition
A monitor run is one scheduled or manual check of monitored URLs.
Why it matters
It shows when checks happened and whether any tracked page elements changed.
Example
A weekly run checks active monitors and records any title, canonical, status, or robots changes it finds.
Definition
A health issue is a detected problem that may need attention after a monitor run.
Why it matters
It separates issues from ordinary history, so people can decide what needs follow-up.
Example
A page returning a failed fetch or unexpected status code can appear as a health issue.
Definition
Retention is how long workspace history remains available for logs, monitoring, issues, and reports.
Why it matters
It sets the window of past activity that reports and reviews can use.
Example
A report can include only project activity that still falls inside the workspace retention window.
Definition
A workspace member is a working user with access controlled by their workspace role.
Why it matters
It lets teams manage owners, admins, members, and viewers from one place.
Example
An agency strategist can work across several client projects as a workspace member.
Definition
A project-specific user can access only the projects they are invited to.
Why it matters
It keeps client visibility and limited project work separate from the full workspace.
Example
A client stakeholder can view one project without seeing another client project.
Definition
A client viewer is a limited-visibility user who can review project information without full workspace access.
Why it matters
It helps agencies and consultants share project context without mixing client work.
Example
A client can review recorded logs and reports for their own project when invited.
Definition
A monthly report summarizes selected project activity from recorded history.
Why it matters
It turns logs, tasks, monitor runs, health issues, and impact results into a clearer update.
Example
A report can show what changed, which tasks were completed, and which detected issues needed attention.
Definition
Assets are project links and references such as briefs, docs, sheets, calendars, or supporting resources.
Why it matters
They keep supporting material close to the project history.
Example
A content brief or keyword sheet can be stored with the project instead of being lost in a message thread.
Inventory stores URLs. Active monitors use scheduled scan credits when they are checked. Instant scans are user-started checks.
Workspace members are working users. Project-specific users and client viewers can be limited to the projects they should see.
Reports use recorded project history. Impact results stay manual, so the report does not claim results the product did not measure.
No. Monitoring is one part. The product also records manual work, tasks, URL history, impact results, and reports.
No. URLs can stay in inventory without scheduled monitoring. Active monitors are the stored URLs that get checked on a schedule.
No. System logs stay in history. Create a task only when the change needs follow-up.
No. Impact results are manual notes added after a person reviews what happened.
Send the question and we can point you to the right page or improve the guide.
