Skip to content

docs(faq): rename docs/faq/index.md → docs/faq/faq.md for cleaner site URL #49

Description

Context

We shipped the FAQ scaffold from #45docs/faq/index.md is now syncing to the marketing site's help centre with FAQPage JSON-LD firing correctly. ✅

The page is live at:

https://littlebearapps.com/help/pitchdocs/index/

But that URL is awkward. The marketing-site sync derives the URL slug from the filename, so index.md becomes /index/. The natural URL would be /help/pitchdocs/faq/.

This issue tracks renaming the file to clean up the URL.

What needs to change

A single file rename, on main:

docs/faq/index.md  →  docs/faq/faq.md

Plus update any links pointing at docs/faq/index.md (probably a README link or two — git grep "docs/faq/index" will find them).

Why this matters

  • URL polish: /help/pitchdocs/faq/ reads as a FAQ; /index/ doesn't.
  • Marginal SEO uplift: URL keyword matching is a small ranking signal in 2026; FAQ-shaped queries get a slight boost. Not material on its own; nice as a compounding signal.
  • Better SERP click-through: when this URL appears in search results or gets shared on Slack / social / blog backlinks, /faq/ is self-explanatory.
  • Zero impact on AI citations: the FAQPage JSON-LD inside the page is what ChatGPT, Perplexity, Google AI Overview, and Google's structured-data parser actually read. URL doesn't matter to them. Same Q&A pairs surface either way.
  • Internal consistency: every other help article on the site uses a descriptive slug (/getting-started/, /install/, etc.). FAQ should match.

What happens after merge

  1. Marketing site's nightly docs sync (or next CF Pages build off main) picks up the new filename.
  2. New URL goes live at https://littlebearapps.com/help/pitchdocs/faq/.
  3. Old URL /help/pitchdocs/index/ will 404 until a 301 redirect lands on the marketing site (separate small PR there). Will be handled once this rename merges — the FAQ has only been live for ~1 day so inbound-link exposure is minimal, but the 301 is good hygiene.

Acceptance criteria

  • docs/faq/index.md renamed to docs/faq/faq.md on main.
  • No content changes — same Q&A, same frontmatter title/description, same prose.
  • Any internal references to docs/faq/index.md updated (run git grep "docs/faq/index").
  • PR description references this issue + the predecessor docs: add docs/faq/index.md for help-centre FAQPage schema #45.

Out of scope

  • Adding/editing FAQ content. This is a pure file rename.
  • Marketing-site changes (301 redirect, sync-pipeline tweaks). Site-side handled separately.
  • Renaming the directory docs/faq/ itself — keep that. Only the file moves.

References


🤖 Filed by Claude Code (via Untether) on behalf of Nathan Schram.

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