flyenv-docs-seo

name	flyenv-docs-seo
description	Use when creating or revising FlyEnv documentation guides that should rank for real developer problem-solution queries while staying factual, people-first, and aligned with current Google Search guidance.

FlyEnv Docs SEO

Write FlyEnv guides as problem-solving tutorials, not feature inventories.

Core Pattern

1. Lead with the real developer problem or search intent.
2. Keep every claim grounded in real FlyEnv behavior.
3. Make the page easy to scan with steps, tables, code, and concrete outcomes.
4. End with the next useful FlyEnv action: download, related setup, or the next guide.

Page Checklist

• Title + H1: Promise one clear outcome. Put the main query near the front, and keep the visible heading aligned with the page body.
• Meta description: Write a concise summary of what the page helps the reader do. Do not chase a fixed character count.
• Intro hook: Start with the pain point, friction, or failure mode the reader already has.
• Main body: Prefer H2/H3 sections, numbered steps, comparison tables, and real config/code blocks over marketing copy.
• Keyword use: Use search terms naturally in the title, intro, headings, alt text, and link text. Do not stuff variations into every section.
• FAQ: Add only real questions a developer is likely to ask after reading the page. Treat FAQ as reader support, not a rich-result trick.
• Internal links + CTA: Link to the next relevant FlyEnv guide or conversion page with descriptive anchor text.
• Freshness: Remove stale versions, screenshots, claims, or workflows that no longer match the product.

FlyEnv-Specific Heuristics

• Favor queries FlyEnv can answer honestly, such as local AI coding workspace, MCP server, offline local AI, without Docker, alternative, and how to fix.
• Keep product advantages concrete: native binaries, project-level runtime switching, local services, AI coding CLI management, MCP tool controls, and audit logs.
• If a paragraph could describe any tool, tighten it with FlyEnv-specific workflow detail or delete it.

Avoid

• Keyword stuffing or boilerplate H2s written only for search engines
• Empty FAQ sections created only to chase snippets
• Mechanical rules such as strict title or description character counts
• Structured data claims unless the site actually implements eligible markup that matches the visible page
• Generic AI-written filler with no firsthand product detail

Reference

Read references/google-search-central-2026.md when you need the source-backed rationale or want to see which parts of Guide-Task1.md were kept, updated, or dropped.