Published September 2, 2026.
A release manifest gives the publishing team one authoritative list of what the batch contains. It prevents counts from drifting across source, build output, index pages, and operator handoff.
List stable identity fields
For every article, include type, title, slug, canonical route, publication date, and source path. Keep Blog and Research in separate sections and state exact expected counts.
Add validation results
Record source parse, build inclusion, route response, canonical match, visible date, structured date, index link, sitemap link, and body hash. A pass should mean the same thing for every row.
Separate repository and live evidence
Include the commit identifier and remote branch after push. Do not describe that as deployment or production validation. A deployment operator should add platform and live-host evidence later.
Make discrepancies actionable
If counts or fields differ, name the exact route and failing check. Keep the issue active or blocked with an owner rather than editing the manifest to match an incomplete result.
BusinessGrowthAssistant’s mission is to build proper daily routines for articles and SEO improvements. Add this check to the daily SEO publishing routine, and use the daily SEO research brief when the decision needs a deeper evidence record.
Frequently asked questions
Should this check be completed for every article?
Yes. Keep the routine short and consistent, then expand the review only when the evidence reveals an exception.
Who can approve an exception?
The operator records the evidence and recommends an action. The accountable editor or site owner approves changes to public claims, strategy, or release requirements.
What should the record contain?
Keep the article route, observation, decision, owner, validation result, and next action. The record should let another operator reproduce the check.
