Published September 2, 2026.
A published route can compile correctly and still be difficult to discover if the blog index omits it. The daily freshness check compares the source batch with the rendered listing before handoff.
Create the expected set
List every approved blog slug in the batch and count it once. Keep research routes separate. The expected set becomes the reference for source, index, sitemap, and HTTP checks.
Inspect the rendered index
Load the blog landing page from the production build and find each exact route. Confirm its visible title and date, then make sure no research-only item appears in the blog collection.
Test pagination and sorting behavior
If the index paginates or limits cards, follow the real navigation path and verify that new entries remain reachable. Same-day entries need deterministic ordering so repeated builds do not hide or reshuffle them unpredictably.
Reconcile before handoff
Compare expected and observed sets programmatically where possible. Any missing, extra, or duplicated route blocks completion until the content loader or listing behavior is corrected.
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.
