> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypergsc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Measure what happened after an SEO change

> Record an applied title, content, linking, or technical change in HyperGSC and compare complete before-and-after Search Console periods.

Use HyperGSC to keep a factual record of an SEO change and compare search observations before and after it. The record helps you remember what changed; it does not apply the edit to your site.

Creating records and running evaluations requires Starter or higher. Writes also require OAuth `projects:write` consent.

## Record an edit after applying it

```text theme={null}
Use HyperGSC to record the SEO change I already applied.
The change date was [actual Pacific calendar date].
Affected URLs: [exact page URLs].
Change type: [title, content, linking, or the applicable supported type].
Notes: [a factual description of the applied change].

Confirm the tool's accepted fields before saving.
```

The assistant uses `record_seo_change`. If it retries the same event, it should reuse the same idempotency key. A retry with different content can conflict.

## Wait for a complete comparison

`evaluate_seo_change` uses equal before/after windows, excludes the change day, and waits until the after-period is complete plus three days of reporting lag.

If the evaluation is not ready, ask for the ready date. HyperGSC does not turn an incomplete window into a final result.

## Ask for the evaluation

```text theme={null}
Use HyperGSC to find my saved SEO change for [page or description].
Evaluate it when the complete after-period is available.
Show affected URLs, exact periods, clicks, impressions, CTR,
average position, missing observations, and source failures.
Explain what changed without claiming the edit caused the result.
```

Each affected URL needs two filtered Search Console requests, with at most twenty such requests per evaluation. Keep the URL set focused on the change you actually made.

## Interpret the result

A click increase is an observed association. Demand, seasonality, competitors, and other edits may also explain it.

Missing observations remain unknown. Growth from a zero baseline should not be expressed as a normal percentage increase.

Use the result to decide whether to keep investigating, run a follow-up experiment, or gather more complete data. Saved records can be listed later; delete one only when you intend to remove that record.

Evaluations are on demand. Recording a change does not create background monitoring or email updates.

See [data and metrics](https://docs.hypergsc.com/reference/data-and-metrics.md) for comparison pitfalls and [authentication](https://docs.hypergsc.com/mcp/authentication.md) for write permissions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.