go-live-checklist

Verify DNS, HTTPS, robots.txt, SEO metadata, performance, analytics, and redirects for Adobe Edge Delivery Services sites.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill go-live-checklist-focus-gts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-live-checklist
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/go-live-checklist
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill go-live-checklist-focus-gts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents expensive launch failures by checking an Adobe Edge Delivery Services (EDS) site’s production readiness across DNS/HTTPS, crawl controls, metadata, performance, analytics, social previews, and migration redirects.

Core Features & Use Cases

  • Pre-launch readiness gate: Produces a categorized report (blocking, warning, info) to decide whether you are truly ready for the production domain cutover.
  • DNS, robots.txt, and metadata verification: Confirms HTTPS validity, canonical URLs, robots/sitemap correctness, and required SEO/social tags on key pages.
  • EDS-specific performance and analytics checks: Flags common EDS regressions like eager-loading third-party analytics instead of using delayed.js, plus basic Core Web Vitals risk patterns.
  • Migration redirect validation: Spot-checks old-domain redirects for 301 behavior and coverage via an EDS redirects spreadsheet.

Quick Start

Run the go-live-checklist against your production domain and key pages before switching traffic.

Frequently Asked Questions about go-live-checklist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my Adobe Edge Delivery Services site is ready for production go-live?

Verify production go-live readiness by checking DNS configuration, HTTPS validity, robots.txt rules, SEO metadata, analytics loading patterns, social sharing tags, and migration redirects to generate categorized blockers and warnings for safe Adobe Edge Delivery Services launches.

What EDS-specific performance checks should I run before a domain cutover?

Run EDS-specific checks to flag eager-loading third-party analytics instead of using delayed.js, and identify basic Core Web Vitals risk patterns before switching traffic to prevent performance regressions during domain cutover.

How do I validate 301 redirects when migrating to an EDS site?

Validate 301 redirects by spot-checking old-domain redirect behavior and coverage via an EDS redirects spreadsheet to ensure old URLs properly route to new destinations without breaking search rankings or user access during migration.

Does the go-live checklist confirm robots.txt and sitemap correctness for EDS sites?

Yes, the go-live checklist confirms robots.txt and sitemap correctness for EDS sites by verifying crawl controls alongside canonical URLs, HTTPS validity, and required SEO and social sharing tags on key pages to ensure proper search engine indexing.

Can I use this checklist as a periodic production health check after launch?

Yes, you can use this checklist as a periodic production health check after launch to continuously verify DNS, metadata, analytics loading, and redirect integrity on live Adobe Edge Delivery Services sites beyond the initial pre-launch readiness gate.

What types of issues are flagged when checking EDS production readiness?

When checking EDS production readiness, issues are categorized as blocking, warning, or info to help decide readiness for domain cutover across DNS, HTTPS, SEO metadata, analytics loading, social sharing tags, and migration redirects.