Website release workflow
Do not finish at “we fixed it.”
Declare what the website is meant to do, find what contradicts that release, repair the cause and run the same evidence again after deployment.
No indexation promise
A technical preflight proves observed public signals. Search engines still decide crawling, canonicalization, indexing, presentation and ranking.
Choose by situation
Open the mode that matches the job.
A new website is about to go live
Release preflight
Crawl the public scope, block demonstrated launch failures and export the fix list.
One page is missing or excluded
Indexability diagnosis
Trace access, robots, noindex, canonical and initial HTML without claiming to see a private search index.
A domain, CMS or URL structure changed
Migration check
Follow old URLs, expose chains and confirm that final destinations are available.
A language or region is being added
International audit
Inspect language alternatives together with status, canonical and indexability signals.
A correction has just been deployed
Verify fixes
Load the previous local project and separate resolved, new and persistent issues.
Closed-loop release
Five steps from intent to proof.
- 1
Declare release intent
Choose what should be public, which hosts belong to the release and whether old URLs should redirect. The same response can be correct for a retired page and a blocker for a new public page.
- 2
Run the smallest useful scope
Start with one URL when diagnosing one page. Use the sitemap or crawl limit only when a template, migration or site-wide conflict is possible.
- 3
Repair causes, not rows
Use affected URL groups and detected path patterns to find one template or server rule behind repeated symptoms. Review every generated change before it reaches production.
- 4
Save the evidence
Download the URL inventory, issue CSV and SolveKit release project. The project contains normalized signals for comparison, never full HTML or credentials.
- 5
Verify after deployment
Load the project and run the same public scope again. A finding is resolved only when its originating signal disappears without creating another release blocker.
Start with the public URL.
No installation and no account. Keep the page open while the respectful crawl batches run.