Skip to content

Split playbook into individual recipe pages for SEO #129

@braboj

Description

@braboj

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)

  1. Undoing changes
  2. Branching
  3. Merging
  4. Rebasing
  5. Remote operations
  6. Cherry-picking
  7. Stashing
  8. Tagging
  9. Submodules
  10. Debugging
  11. Configuration
  12. (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")

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions