How to Create a Website SEO Baseline Before Making Changes
Website intelligenceHow to Create a Website SEO Baseline Before Making Changes
A baseline gives your team a reference for later decisions. Without it, you may remember that a page used to look healthy but have no record of its response, metadata or report findings before a change.
Choose representative URLs
Select the homepage and important page types such as service pages, product-like pages, category pages or editorial content. The exact sample depends on your site, but include pages that use different templates and navigation paths.
Record the final URL, response status and the date of the scan. A URL that redirects to a new location should be noted so you do not compare it with a different page later.
Save the SiteBoost report context
Run a SiteBoost scan and keep the report as the starting reference. Record the score, measured checks, technical findings and performance indicators that are available for the page and plan.
Make a short baseline sheet with the issue, evidence, page or template, priority and owner. This allows a developer, SEO specialist or website owner to understand why a change was requested.
- Save the exact requested and final URL.
- Note the scan date and status.
- Record titles, descriptions, canonical and robots values.
- Keep the key findings and Lighthouse results where available.
Use the baseline after every major release
After a redesign, migration or template update, rescan the same representative URLs. Compare the same signals and check any new warnings before rolling the change out to every page.
A baseline is only useful when you keep the comparison fair. If the page content or URL changed substantially, document that difference rather than treating the two reports as identical tests.
