feat: boost long-tail SEO for parameter and model pages

[brunobuddy]

💭 Why

The site gets impressions for specific parameter and model queries, but those long-tail pages were hard for Google to reach. The homepage passed no link equity to the per-parameter pages, and its title was generic.

✨ What changed

• Homepage: new crawlable "Browse by parameter" section linking all 60 parameter pages plus the glossary.
• Homepage title and description now name real parameters (temperature, top_p, max_tokens) with live model and provider counts.
• Homepage JSON-LD gains an Organization node with sameAs to GitHub and npm.
• Model pages: data-driven FAQ built from the catalog (visible Q&A plus FAQPage JSON-LD).
• Model heading reworded to reinforce the "API parameters" phrasing.
• npm README links back to the API docs, JSON API, and llms.txt.
• Synced the packages/modelparams version in the lockfile (0.0.0 to 0.0.1).

👤 For users

Searchers looking for a specific parameter or model default land on the matching page. Each model page answers common questions inline, like the default temperature or the token limit.

📝 Notes

• No comparison ("A vs B") pages by design, to avoid thin content on a young domain.
• New pure module src/data/faq.ts backs both the visible FAQ and the FAQPage schema.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
modelparams.dev	Ready	Preview	Jul 7, 2026 8:38am