“It’s live” does not tell you whether the intended SEO change reached the public page, whether a crawler can access it, or whether search performance changed afterward. A reliable post-release checklist checks each of those stages separately.
Define what success means before the release
Write down the URL, planned change, release owner, and acceptance criteria. For a title update, the check might be that the new title appears in the rendered HTML and accurately describes the page. For a redirect, record the old and new URL, expected status, and final destination. Clear criteria prevent a vague “SEO improved” judgment.
Check the public page after release
Open the URL in a browser and fetch it as a public visitor would. Confirm the expected content appears, the page returns a successful response, the canonical points where intended, and robots directives do not block crawling or indexing. Check internal links and templates if the change affects multiple pages.
For JavaScript-rendered pages, inspect the rendered output as well as the source response. Google documents JavaScript SEO guidance for sites that rely on client-side rendering; verify that important content and links are available to search systems as intended.
Inspect Google’s view when needed
Use Search Console’s URL Inspection tool to review the indexed URL or test the live URL. Check the inspection date and the reported canonical, crawl, and indexing details. A live test is useful for diagnosis, but it is not the same as an indexed result. A request to recrawl is also not a guarantee of when Google will revisit or index the page.
Use a sitemap to list canonical URLs you want discovered and keep its last-modified information accurate when pages materially change. Sitemaps are hints for discovery, not promises that every listed URL will be crawled immediately.
Measure search performance on an appropriate timeline
After implementation and recrawl have had time to occur, compare relevant Search Console metrics for the affected pages and queries. Use comparable time windows and account for seasonality, demand, other site releases, and search changes. If you are tracking leads or sales, use your analytics or business system as a separate source.
Report the evidence precisely: “the new title is live,” “Google last crawled the URL on this date,” or “clicks rose in this comparison period.” Avoid saying “the title caused more leads” unless you have an appropriate way to support that causal claim.
Keep a simple release record
- URL and intended change.
- Release date and person or team responsible.
- Evidence that the public page matches the acceptance criteria.
- Search Console inspection and recrawl observations, where relevant.
- Performance comparison dates and source.
- Follow-up decision: complete, investigate, or revise.
SEO change verification checklist
- Confirm the intended update is present on the live page.
- Check response, canonical, robots directives, rendered content, and links.
- Use URL Inspection to diagnose Google’s indexed or live view.
- Keep release, crawl, indexing, and performance states distinct.
- Compare performance over suitable periods and state limitations.
Verification makes SEO work accountable: the team can see what it changed and what happened next. It cannot guarantee a ranking, citation, or conversion, but it prevents assumptions about whether the work shipped and how the evidence reads.
Primary sources: Google Search Central debugging tools · Google: Ask Google to recrawl your URLs · Google: Build and submit a sitemap.