CMS Pre-Publish Checklist: Catch Problems Before Launch

Review the rendered page, not only the editor fields

A CMS pre-publish check should verify the page’s purpose, factual accuracy, links, media, metadata, accessibility, permissions, and final rendering before publication. Assign one person to own each check, record what was approved, and preview the page at the actual destination and common viewport sizes. A draft can look immaculate in the editor while the live template quietly puts the caption in another postal code.

CMS controls vary by product, version, theme, and permissions. Follow current official documentation and test changes in a safe preview or staging environment when available.

Confirm the page has one clear job

Write the intended reader and action in one sentence. Then compare the title, opening, headings, main body, and final action. They should describe the same purpose.

Check that:

• the title promises what the page delivers;
• the opening answers or frames the main need promptly;
• headings form a logical outline;
• duplicated or outdated sections are removed;
• required qualifications sit beside the claims they limit;
• the final action is available and understandable.

Do not publish placeholder copy, internal comments, prompts, or notes intended for another team member.

Fact-check every specific

Review names, dates, prices, measurements, calculations, product details, policies, and quoted material against current sources. Open the source rather than trusting a remembered tab title. Recompute arithmetic independently.

For high-stakes health, legal, financial, or safety content, obtain the review required by the organization’s policy. A publishing checklist cannot manufacture expertise.

Test links by destination and intent

Open every internal and external link in the preview context. Confirm that it resolves to the intended page, uses an appropriate secure URL where applicable, and does not point to a draft or restricted environment.

Check anchors in context. “Read more” may be ambiguous when several such links appear, while an honest descriptive phrase helps readers understand the destination. Test downloads and forms without submitting sensitive or production-changing data unless the approved test plan permits it.

Explore more publishing workflows for role and review patterns.

Inspect images and other media

Verify that each image is licensed for the intended use, relevant, correctly oriented, and not larger than the workflow permits. Add useful alternative text when the image conveys information; leave decorative treatment to the site’s accessibility implementation rather than stuffing alt text with keywords.

Check captions, credits, transcripts, poster frames, playback controls, and fallbacks. Preview what happens when media loads slowly or fails.

Review metadata without duplicating the page

Confirm the slug, page title, search description, social-preview fields, canonical setting, publication date, author treatment, category, and visibility according to current site policy. Never invent an author or credentials.

Avoid changing a live URL casually. A slug change can require redirects, link updates, analytics continuity, sitemap handling, and approval from whoever owns site operations.

Check accessibility in the actual interface

Use headings in order, label form controls, preserve keyboard access, provide visible focus, and avoid relying on color alone to communicate meaning. Automated checks are helpful but do not replace keyboard use, zoom, screen-reader testing, or human review appropriate to the page.

Confirm that tables have meaningful headers and that link text makes sense out of context. Captions and transcripts should match the final media, not an earlier cut.

Preview across states and widths

Review desktop and narrow layouts, signed-in and public views when relevant, and any scheduled or gated state. Check navigation, sticky elements, notices, cookie controls, popups, and long text for overlap or clipping.

Publish with a rollback path

Record the previous live state and know how the CMS handles revisions before replacing important content. For scheduled publishing, confirm time zone, date, dependencies, and who will check the live result.

After publication, open the public URL in a fresh session. Verify the correct version, links, media, metadata, cache behavior, and any form or action covered by the approved test plan. If a serious problem appears, follow the documented rollback or unpublish procedure—do not improvise destructive database work.

The migration inventory guide applies the same evidence-first habit to larger changes. A pre-publish checklist is successful when it makes the final click ordinary. Drama is an unreliable deployment dependency.