What
The playbook chapter is a single long page with 12 sections. Each section targets a distinct search query (e.g. "how to undo git commit", "git rebase onto branch"). Splitting them into individual pages would let each recipe rank independently in search results.
Why
- Google ranks pages, not sections — a dedicated
/playbook/undo-commit/ page ranks better than an anchor link to a section
- Each recipe becomes a potential landing page for high-intent long-tail queries
- Individual pages get their own meta description, OG tags, and canonical URL
- Easier to share and link to specific recipes
Current recipes (12 sections)
- Undoing changes
- Branching
- Merging
- Rebasing
- Remote operations
- Cherry-picking
- Stashing
- Tagging
- Submodules
- Debugging
- Configuration
- (index page listing all recipes)
Implementation approach
- Create a
playbook/ content collection or nested route
- Each recipe becomes its own Markdown file with frontmatter (title, description)
- The playbook index page lists all recipes with links
- Add JSON-LD HowTo schema to each recipe page
- Optimize recipe titles for search queries (e.g. "How to Undo a Git Commit")
What
The playbook chapter is a single long page with 12 sections. Each section targets a distinct search query (e.g. "how to undo git commit", "git rebase onto branch"). Splitting them into individual pages would let each recipe rank independently in search results.
Why
/playbook/undo-commit/page ranks better than an anchor link to a sectionCurrent recipes (12 sections)
Implementation approach
playbook/content collection or nested route