Skip to content

Enhance blog posts' discoverability for both search engines and LLMs #2

@stefaniuk

Description

@stefaniuk

Improve the findability and accessibility of blog content for both human readers and AI systems through enhanced metadata and structured content.

Tasks

1. Jekyll Template Updates

  • Add OpenGraph meta tags (og:title, og:description, og:image)
  • Add Twitter Card meta tags
  • Implement schema.org BlogPosting markup
  • Add canonical URLs
  • Ensure proper heading hierarchy (h1, h2, h3)

2. Content Structure

  • Add clear TL;DR or executive summary at the start of each post
  • Include table of contents for longer posts
  • Structure content with clear sections and subsections
  • Tag posts with relevant categories and keywords
  • Add "Key Takeaways" section at the end of posts

3. Metadata Enhancement

  • Create consistent meta descriptions for all posts
  • Add alt text to all images
  • Implement proper title tag format: {Post Title} | Dan's Engineering Journal
  • Add reading time estimates
  • Include last updated dates

4. Technical SEO

  • Complete the robots.txt configuration
  • Generate and verify sitemap.xml
  • Implement JSON-LD structured data
  • Verify RSS feed functionality
  • Set up proper redirects for any URL changes

5. Content Optimization

  • Add descriptive section headers
  • Include relevant internal links between posts
  • Create topic clusters for related content
  • Add descriptive code block comments
  • Include reference links to official documentation

6. AI/LLM Optimization

  • Add clear context markers for code examples
  • Include version information for all technical references
  • Structure code snippets with clear input/output examples
  • Add semantic HTML markup for better content parsing
  • Include machine-readable metadata for technical concepts

Acceptance Criteria

  • All posts pass SEO audit tools
  • Structured data validates in Google's testing tool
  • Content is properly indexed by search engines
  • Posts are easily discoverable through related content
  • Technical content is machine-readable and well-structured
  • Clear separation between explanatory text and technical examples

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions