Skip to content

docs(faq): rename docs/faq/index.md → docs/faq/faq.md for cleaner site URL (re-filed) #51

Description

TL;DR

Rename docs/faq/index.mddocs/faq/faq.md on main. One-file rename, no content changes. Unblocks a cleaner public URL on littlebearapps.com.

Why now

Today's FAQ SEO audit (2026-05-26) confirmed the FAQ at https://littlebearapps.com/help/pitchdocs/index/ is working — TechArticle + FAQPage + BreadcrumbList JSON-LD all valid, 10 questions extracted. But the URL slug is /index/, which:

  • Looks like a category landing page, not an FAQ
  • Hurts SERP click-through ("/faq/" is self-explanatory)
  • Is inconsistent with contextdocs (already shipped on /faq/)
  • Provides a marginal SEO uplift via URL-keyword match

This was tracked in #49 but is being re-filed today with sharper framing and current audit data to surface the work. The old issue can be closed as superseded once this one is actioned.

EXACT instructions

  1. On main:
    git mv docs/faq/index.md docs/faq/faq.md
  2. Update any references to the old path:
    git grep "docs/faq/index" | grep -v node_modules
    # Update each match to docs/faq/faq.md (or remove if stale)
  3. Do not modify the file's content — same frontmatter (title, description, tool, category: faq), same Q&A prose, same headings. Pure rename.
  4. Commit + PR. Suggested title: docs(faq): rename docs/faq/index.md → docs/faq/faq.md.

Acceptance criteria

What happens after merge (site-side)

  1. Next build of littlebearapps.com (auto-runs on push to main of this repo + daily 6am UTC cron) picks up the new filename
  2. Public URL flips to https://littlebearapps.com/help/pitchdocs/faq/
  3. Old URL /help/pitchdocs/index/ will 404 until a 301 SSR redirect lands on the marketing site — tracked separately, not your concern here

Out of scope

  • Editing FAQ content (purely a rename)
  • Renaming the docs/faq/ directory itself — keep that
  • Marketing-site changes (301 redirect, sync config)

References


🤖 Filed by Claude Code (via Untether) on behalf of Nathan Schram on 2026-05-26.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions