Context
We shipped the FAQ scaffold from #45 — docs/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
- Marketing site's nightly docs sync (or next CF Pages build off
main) picks up the new filename.
- New URL goes live at
https://littlebearapps.com/help/pitchdocs/faq/.
- 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
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.
Context
We shipped the FAQ scaffold from #45 —
docs/faq/index.mdis now syncing to the marketing site's help centre with FAQPage JSON-LD firing correctly. ✅The page is live at:
But that URL is awkward. The marketing-site sync derives the URL slug from the filename, so
index.mdbecomes/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: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
/help/pitchdocs/faq/reads as a FAQ;/index/doesn't./faq/is self-explanatory./getting-started/,/install/, etc.). FAQ should match.What happens after merge
main) picks up the new filename.https://littlebearapps.com/help/pitchdocs/faq/./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.mdrenamed todocs/faq/faq.mdonmain.docs/faq/index.mdupdated (rungit grep "docs/faq/index").Out of scope
docs/faq/itself — keep that. Only the file moves.References
/index/URL: littlebearapps/littlebearapps.com#170 (outlook-assistant) and littlebearapps/littlebearapps.com#172 (pitchdocs / contextdocs / cf-monitor).🤖 Filed by Claude Code (via Untether) on behalf of Nathan Schram.