Create a Useful SEO Baseline Before Making Changes
Before making SEO changes, record search clicks, impressions, important landing pages and useful business outcomes over a defined period. That baseline helps you assess later changes fairly. This guide takes that specific topic through four practical steps, beginning with the following action: Record the last complete 28 days in Search Console: total clicks, impressions, leading queries and leading pages. Note the date range and search type. You will also see a realistic example, a verification test and a common mistake to avoid. Use the process on your own site, and check current vendor documentation whenever a platform setting has changed.

What to prepare before starting
A working list of your most important live URLs, permission to edit those pages, and a way to record the before-and-after version. Start with pages that carry business information, not an arbitrary collection of blog posts.
Keep this boundary in mind while carrying out the steps: The goal is to help a person use the site successfully; a score, a new indexed URL, and a new customer are different outcomes.
Step 1: Start with a reliable inventory
Record the last complete 28 days in Search Console: total clicks, impressions, leading queries and leading pages. Note the date range and search type.
Write down the starting state before changing anything. If an issue is not reproducible on the live site, distinguish a suspected concern from a confirmed problem. This gives you a defensible reason for prioritizing the work. Keep proof of the published outcome, especially if multiple people edit the same website. The task is complete when you have verified the intended behavior, not merely clicked Save.
Step 2: Examine the important details
From your analytics tool, record organic sessions and meaningful outcomes such as inquiries or purchases for the same period.
Keep the page's actual audience and publishing platform in view. A check that succeeds in an editor preview may fail at a public URL, and a setting that works in a custom site may not exist in a hosted website builder. For this particular task, the evidence to collect is related to create a useful seo baseline before making changes. Note any conditions that would prevent another site owner from following the same action exactly.
Step 3: Make the targeted improvement
Save a list of current indexed or eligible priority pages, with their H1, target question and last substantive update.
Focus on the smallest effective change first. Maintain a short record of the before state, the revision and the pages affected; this makes it possible to reverse a mistake instead of guessing what changed. If the page or tool returns an unexpected result, first recheck the URL, permissions and configuration rather than inventing an SEO explanation. Fix a verified issue, then run the same check again.
Step 4: Verify the live outcome
Put your baseline in a dated worksheet before editing titles, rebuilding navigation or publishing new content.
Use the public, signed-out version of the page for the final test. Search Console and analytics can provide later signals, but your immediate acceptance check is whether the intended page, content and links behave correctly. Where the recommendation affects user-facing claims, confirm them with the business owner or the relevant official source. A clear but inaccurate change can make a page less trustworthy.
Worked example: apply the process to a real website
A local repair shop records 340 search impressions, 15 clicks and 3 inquiries in one period; those figures are an illustrative worksheet example, not a performance promise.
Treat this as a planning example, not a claim about a SiteGrowth customer or a tested client outcome. Write down the starting problem, the affected URL and which of the four steps you applied. Then compare the published result with the original question. If the example does not apply to your site, adapt the sequence to its content and platform instead of copying details that are not true.
How to check whether you finished successfully
Each metric has a source and time window, allowing a fair before-and-after comparison without conflating visits and impressions.
Do the check in a signed-out browser session where possible. Follow links manually; inspect the actual mobile page and any relevant source-code or search-console evidence. If a metric matters, save the date range and definition. A page being published, discovered or indexed does not automatically establish that it gained traffic or customers.
Common failure: what to avoid and how to recover
Comparing a 28-day period against a 7-day period, or treating impressions as actual site visitors.
If you see this failure, stop expanding the change across more pages. Identify the affected URL or editor setting, restore the last known-good version when appropriate, and test one corrected example. Only then repeat the change at scale. This is especially important for URL migrations, canonical tags, robots directives and automated bulk content updates.
Final practical checklist
Before marking the task complete, confirm all five points:
1. You identified the real visitor task and the exact page or record involved.
2. You completed the initial check: Record the last complete 28 days in Search Console: total clicks, impressions, leading queries and leading pages. Note the date range and search type.
3. You completed the final step: Put your baseline in a dated worksheet before editing titles, rebuilding navigation or publishing new content.
4. You checked the outcome: Each metric has a source and time window, allowing a fair before-and-after comparison without conflating visits and impressions.
5. You recorded outstanding caveats and, when warranted, linked from a relevant existing page.
If this guidance depends on a platform feature, consult its current documentation before implementing a large change.
Key takeaways
- Record the last complete 28 days in Search Console: total clicks, impressions, leading queries and leading pages. Note the date range and search type.
- From your analytics tool, record organic sessions and meaningful outcomes such as inquiries or purchases for the same period.
- Save a list of current indexed or eligible priority pages, with their H1, target question and last substantive update.
- Put your baseline in a dated worksheet before editing titles, rebuilding navigation or publishing new content.
- Each metric has a source and time window, allowing a fair before-and-after comparison without conflating visits and impressions.
Common questions
What should I measure before starting SEO?
Start with the actual website and the reader's need. Record the last complete 28 days in Search Console: total clicks, impressions, leading queries and leading pages. Note the date range and search type. Then from your analytics tool, record organic sessions and meaningful outcomes such as inquiries or purchases for the same period. The final check is: Each metric has a source and time window, allowing a fair before-and-after comparison without conflating visits and impressions.
What is a common mistake to avoid?
Comparing a 28-day period against a 7-day period, or treating impressions as actual site visitors.
How can I confirm that the work is complete?
Each metric has a source and time window, allowing a fair before-and-after comparison without conflating visits and impressions.
Further reading
For technical search guidance, refer to the relevant official documentation. Verify changing platform details against the current source.