Website-Pflichtencheckby Jurono
ChecklistWebsite

Website launch/relaunch checklist

A compact technical pre-launch check so contact paths, indexing, tracking and security are not discovered only after publishing.

25 minv1.0.0

What is included

  • Indexing and redirects
  • Forms and booking paths
  • Tracking, cookie banner and headers

Audience and use case

Audience

Teams close to a website launch or relaunch.

Use case

Run it 24 to 72 hours before release and once again right after go-live.

Preview

Before you start

Set the scope for the website launch and note where evidence is stored.

  • Define owner and system scope
  • Collect current URLs, tools and access paths

Technical checks

  • Check the highest-risk item first
  • Record evidence, not assumptions
  • Assign one corrective action

Related resources

ChecklistWebsite

Contact-form reliability checklist

Check delivery, spam protection, error states and fallback paths before valuable inquiries get lost.

15 minOpen
ChecklistOperations

Website handover checklist

A practical checklist for clean website handovers without lost access, unclear providers, or invisible risks.

20 minOpen

Get clarity before you commit to fixes.

Start with a technical check. If the findings are minor, you can stop there, hand the report to your existing team, or book targeted fixes later.

Check first, decide laterView AI code rescue

Technical audit and implementation, not legal advice. I check visible signals, integrations, and delivery issues; legal texts and binding legal assessments remain the work of lawyers or privacy consultants.