{
  "id": 9687192,
  "title": "The Pre-Publish QA Checklist I Wish I'd Had on Day One in AEM",
  "url": "https://urgent.news/2026/09/25/the-pre-publish-qa-checklist-i-wish-id-had-on-day-one-in-aem",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-25T02:47:37.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/dale87/the-pre-publish-qa-checklist-i-wish-id-had-on-day-one-in-aem-4bb9"
  },
  "original_language": "en",
  "account": "Every item on this list exists because something broke in production. The author has spent four years running content operations on a large AEM site and has watched numerous issues arise due to overlooking the importance of a proper pre-publish QA checklist. The most common cause was someone eyeballing the page in author preview and hitting publish, leading to various problems like staging cache still warm, promotional banners with last quarter's pricing, and checkout links pointing to the author environment.\n\nThe author built this checklist after realizing the value of ensuring every detail is accounted for before publishing. By running this checklist before every publish, the production incidents dropped significantly. The checklist is practical and based on real-life experiences, ensuring that each item addresses a critical aspect of the publishing process.\n\nThis checklist is essential to prevent issues like content correctness, SEO and meta errors, broken links, image problems, responsive issues, accessibility concerns, personalization errors, publishing mechanics failures, and analytics tracking issues. By systematically going through each section, the author ensures that the content is accurate, SEO-friendly, functional, and compliant with accessibility standards. The checklist covers content correctness, SEO and meta tags, link validation, image and media checks, responsive design testing, cross-browser compatibility, accessibility compliance, personalization accuracy, and proper publishing mechanics. Each section is crucial to ensure the content is ready for publication without issues.",
  "summary": "Every item on this list exists because something broke in production. I spent four years running content operations on a large AEM site. In that time, I watched a page go live with the staging cache still warm, a promo banner with last quarter's pricing, and a checkout link pointing at the author environment. Each one had the same root cause: someone eyeballed the page in author preview and hit…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}