SEO fieldnotes

Editorial planning

25 checkable notes for editorial planning.

1. Prioritize a content backlogA backlog rewards loud requests over reader needs.
2. Plan around evidence readinessA calendar assumes every claim can be verified on demand.
3. Build a review capacity planWriters produce more than reviewers can accept.
4. Separate evergreen and timely workA news deadline crowds out reusable guidance.
5. Plan a content refreshOld pages need more than a new date.
6. Map content dependenciesSeveral pieces rely on the same unfinished explanation.
7. Choose a campaign sequencePosts are ordered by asset completion rather than understanding.
8. Build a seasonal planning bufferA fixed event date leaves no recovery time.
9. Reduce a crowded calendarMore scheduled items dilute review quality.
10. Plan a research sprintThe team starts collecting sources without a decision target.
11. Create a content dependency ownerA draft waits indefinitely for a missing input.
12. Plan a launch delay responsePrepared content assumes a release date that may move.
13. Design a recurring editorial meetingThe meeting repeats status without making decisions.
14. Plan content retirementA page no longer serves its original purpose.
15. Build a small-team cadenceA plan assumes more people than are available.
16. Plan a multi-owner campaignDifferent teams own pieces of one story.
17. Use a content opportunity noteAn idea is too early for the calendar.
18. Plan for correctionsThe schedule has no capacity for fixing released material.
19. Build a channel-fit planThe same material is sent everywhere unchanged.
20. Plan an editorial experimentA test changes too many variables to interpret.
21. Balance acquisition and support contentThe calendar attracts readers but leaves users stuck.
22. Schedule a source recheckVolatile claims can change between approval and release.
23. Create a handoff calendarA publication date hides earlier deadlines.
24. Plan a topic consolidationSeveral pages compete to answer the same question.
25. Review the calendar retrospectivelyOutput count hides whether the plan helped anyone.