Setting a baseline before SEO changes

Capture the state before changing it

Record the current URLs, metadata, indexing reports, search performance and measurement configuration relevant to the planned work. Keep dates, filters and known limitations beside the evidence. A baseline should make later comparisons interpretable, not become a large archive with no connection to the change being made.

Worked example

Illustrative scenario; not a claim of measured client results.

Before expanding an article library, capture the published inventory, sitemap count, representative page responses and current search date range. Note whether recent analytics activity is setup testing. After release, verify implementation separately from ranking outcomes. A correct deployment can be confirmed immediately, while search performance requires later observation and may be influenced by other factors.

Checks, limitations and next decisions

If a baseline is missing, state that limitation instead of reconstructing a convenient before figure. Use available historical reports carefully and preserve their actual scope. Maintain a change log for future work. The baseline is most valuable when it helps distinguish what was changed, what was verified and what remains an outcome to measure over time.

A practical starting point

Work through these checks in order. Use the results to decide what needs to change in your own workflow.

1. Record indexed pages, relevant query groups and landing-page performance.
2. Note known technical issues and current conversion definitions.
3. Save the change log alongside subsequent measurements.

A mistake to avoid

Do not compare a new measurement setup with an old incompatible one as if nothing changed.

How to check progress

Use consistent windows and annotate indexing delays and releases.