Updates
Changelog
What recently shipped in the NextBento product app and on this marketing site. For deeper kit notes, see the docs changelog.
- Website
Titles that say the point
Search titles on the roundup, compare hub, ShipFast pages, and three glossary entries now say the point. Prices stay in the body.
- Roundup: Best Next.js SaaS boilerplates that stayed on Next.js
- Compare hub: Next.js SaaS boilerplates compared by what you still wire
- ShipFast blog and shortlist titles no longer read as a generic 2026 list
- Removed the duplicate Quick answer box on the compare hub
- Website
Clearer TanStack and Crawler Hints blurbs
The TanStack glossary now says what the name means. The Cloudflare doc says what Crawler Hints do before the setup steps. The ShipFast alternatives link goes to the short list.
- Glossary title: What is TanStack? Meaning of the name
- Crawler Hints description starts with the definition, then how to turn it on
- “ShipFast alternatives” links to the shortlist. The blog link is the longer post
- Website
Search snippets for compare and Gmail OAuth
Search Console showed the compare hub and the Gmail OAuth doc on page 1 with no clicks, and the ShipFast vs URL with no impressions.
- Compare hub title shortened to Next.js SaaS Boilerplates Compared (2026), with prices in the description
- NextBento vs ShipFast no longer leads with the alternatives query
- Gmail OAuth doc title names the consent-screen outcome
- /pricing.md stays available for agents, is out of the sitemap, and markdown responses send a canonical to the HTML URL
- Website
robots.txt limited to rules Googlebot honors
Search Console was flagging Agentmap as a syntax error and Content-Signal as a rule Googlebot ignores.
- robots.txt now uses User-agent, Allow, Disallow, and Sitemap only
- Content preferences stay in comments and the Markdown content-signal header
- ARD catalog stays at /.well-known/ai-catalog.json, with rel="ai-catalog" and rel="ard"
- Product
TanStack Query on API keys and onboarding
The kit now uses TanStack Query for client server-state. TanStack Table was already the grid library. Next.js stays the framework.
- API keys and onboarding use Query. The full API key stays out of the cache.
- Homepage stack line includes TanStack Query and TanStack Table.
- Posts: /blog/tanstack-query-nextjs-saas-boilerplate and /blog/which-tanstack-libraries-fit-nextjs
- Website
Five newest posts: first-person, sourced stats
Rewrote the five newest blog posts so they read like a builder’s notes: hooks, first-hand work on this origin, and citations to Google, Stripe, Cursor, Next.js, and the GEO paper. Titles and H2s stayed put.
- SEO tags vs comparison pages; prompting SEO pages from a blank repo
- AI bootstrap vs boilerplate; 2026 roundup; Cursor / Claude skills
- Stats are sourced (no invented token totals or unbacked “best”)
- Website
Blog: SEO tags vs a comparison factory, and prompting vs pages
Two posts on the SEO side of the blank-repo argument: metadata is not ranking for X vs Y, and prompting twenty vs pages still burns a weekend. Factory how-to and glossary definitions stay on their own URLs.
- Post: /blog/seo-tags-vs-comparison-pages
- Post: /blog/prompting-seo-pages-from-a-blank-repo
- Keyword-ownership notes so they do not collide with the factory article, glossary, or /compare
- Website
Compare, alternatives, and blogs now argue for NextBento
Rewrote comparison Quick Answers, alternatives shortlists, and buyer posts so NextBento is the recommended kit. Competitor extras stay sourced. One anti-persona line instead of sending readers to another buy.
- Compare and alternatives hubs: NextBento-first Quick Answer; table column is extras, not “pick when”
- Alternatives spokes: “When NextBento is the wrong kit” / “Why NextBento is the alternative”
- Blog roundup and ShipFast long-form recommend NextBento for a solo Next.js + Supabase launch
- Website
Blog: AI bootstrap vs a Next.js boilerplate
New post comparing from-zero Cursor/Claude token spend on plumbing with cloning a wired $59 kit. No invented token totals; links the existing blank-repo and skills posts instead of duplicating them.
- Post: /blog/ai-bootstrap-vs-saas-boilerplate
- Internal links from the blank-repo and skills posts; keyword-ownership note so the three URLs stay distinct
- Website
Homepage retargeted to Next.js SaaS boilerplate / starter kit
Title, H1, and schema now lead with the phrases that rank on Google for this category (boilerplate, starter kit, template), with Cursor as the differentiator — not the only head term.
- Homepage title: Next.js SaaS Boilerplate & Starter Kit — Cursor-ready
- Compare hub titled as boilerplates, starter kits & templates (2026)
- FAQ covers “best Next.js boilerplate for SaaS” and boilerplate vs starter vs template
- Website
Alternatives hub, buyer posts, and keyword retarget
ShipFast / MakerKit / Supastarter / Indie Kit alternative pages, competitor-first compare titles, five searchable posts, and a 2026 pricing glossary. Competitor stickers re-checked the same day.
- Hub at /alternatives plus spokes for shipfast, makerkit, supastarter, indie-kit
- Compare titles lead with “[Competitor] alternative”; prices verified 2026-09-14
- Blog: 2026 boilerplate roundup, ShipFast alternatives, Next.js 16, Supabase+Stripe leftover work, Cursor/Claude skills
- Glossary: SaaS boilerplate pricing 2026; /pricing.md structured for agents
- EventDash goals: compare_view, alternatives_cta, docs_to_checkout (checkout_click unchanged)
- Website
Two more marketing blog posts
Why nextbento.dev is not the kit you clone, and why Stripe sits on the owner instead of a seats column.
- Blog: marketing site vs product repo
- Blog: owner / admin / member with billing on one person
- Website
Human-readable GET for /mcp
Opening /mcp in a browser no longer returns 405. POST is still the Streamable HTTP JSON-RPC endpoint.
- GET and HEAD /mcp return an HTML (or Markdown) explanation with links to the server card and API docs
- GET with Accept: text/event-stream still returns 405 — this origin does not offer an SSE session
- Docs table no longer sends humans to a protocol-only error
- Website
Marketing blog and SEO review snapshot
Three editorial posts that do not copy the compare hub, plus a documented GSC and EventDash snapshot.
- Blog at /blog with RSS, schema, sitemap entries, and nav/footer links
- Audience hub (/for) added to the main nav
- EventDash checkout_click goals on Get NextBento buttons
- Keyword map now separates /blog, /compare, and vendor-howto docs
- Website
CodeHype badge in the footer
Find NextBento on CodeHype from the site footer, next to Google Preferred Sources.
- Featured-on CodeHype badge linking to the product listing
- Remote badge asset allowed via next.config images.remotePatterns
- Website
Stop Cloudflare email links from 404ing crawlers
Ahrefs reported broken links to /cdn-cgi/l/email-protection. Those were Cloudflare Email Obfuscation rewrites, not missing pages.
- Pages wrap emails so Cloudflare does not rewrite mailto: to /cdn-cgi/ 404s
- robots.txt disallows /cdn-cgi/
- Contact links use the canonical mailto from legal facts
- Website
More pSEO pages and fresher comparisons
Stale comparison and integration pages re-verified; new vs Indie Kit, vs next-forge, audience, and llms.txt glossary pages.
- ShipFast, Supastarter, and official starter pages updated with live prices and stacks
- New comparisons: NextBento vs Indie Kit and vs next-forge
- Persona hub at /for (indie hackers, AI-assisted founders)
- Glossary: what is llms.txt
- pnpm validate:pseo checks required blocks and last-verified dates
- Website
ARD capability catalog
Agents can discover MCP, OpenAPI, and skills from /.well-known/ai-catalog.json.
- specVersion 1.0 catalog with host and urn:air:www.nextbento.dev entries
- Same document at /.well-known/ard.json; CORS Access-Control-Allow-Origin: *
- No A2A agent — this origin does not host one
- Website
WebMCP browser tools
In-page AI agents can call public site tools through navigator.modelContext.
- registerTool / provideContext on page load for navigate, search_docs, get_product_facts, start_checkout
- AbortController unregisters tools on pagehide
- No login or account creation — checkout still requires a human in Stripe
- Website
Agent Skills discovery index
Agents can list published skills from /.well-known/agent-skills/index.json.
- RFC v0.2.0 index with $schema and skill-md entries
- Each skill has name, type, description, url, and sha256 digest
- SKILL.md files served under /.well-known/agent-skills/{name}/SKILL.md
- Website
Content Signals in robots.txt
robots.txt declares ai-train, search, and ai-input preferences.
- Content-Signal: ai-train=yes, search=yes, ai-input=yes under User-agent groups
- Matches the existing HTTP content-signal header on Markdown responses
- Website
MCP Server Card
Agents can discover a public MCP server from /.well-known/mcp/server-card.json.
- SEP-1649 server card with serverInfo, Streamable HTTP /mcp, and capabilities
- Public tools: get_product_facts, list_docs, get_doc
- No agent signup or login — marketing facts and docs only
- Website
RFC 9727 API catalog
Agents can discover public HTTP APIs from /.well-known/api-catalog.
- application/linkset+json catalog with checkout, health, and IndexNow
- /openapi.json OpenAPI 3.1 description
- GET /api/health liveness probe
- Homepage Link headers: api-catalog, service-desc, service-doc, describedby
- Website
Markdown for agents
Agents can request chrome-free markdown from the same URLs browsers use for HTML.
- Accept: text/markdown content negotiation on public pages
- Optional .md URL suffix (including /index.md) as a fallback
- x-markdown-tokens and Vary: Accept on markdown responses
- Website
IndexNow submit script
Notify Bing and IndexNow partners when pages change.
- pnpm submit:indexnow or submit:sitemap — all sitemap URLs
- Optional paths: pnpm submit:indexnow /pricing /changelog
- Auto-detects public/{key}.txt for key verification
- Website
AI search discoverability
llms.txt and crawler rules so ChatGPT, Claude, and Perplexity can find and summarize NextBento accurately.
- /llms.txt and /llms-full.txt with claim-safe product facts
- Explicit Allow rules for OAI-SearchBot, Claude-SearchBot, PerplexityBot, and related agents
- Footer link to llms.txt
- Product
Phase 2 product upgrades
Stronger teams, fuller auth, onboarding, and production-minded rate limiting in the NextBento app.
- Owner / admin / member team roles with invite role picker
- Email/password alongside OAuth and magic link
- Post-signup onboarding gated by profiles.onboarding_completed
- AGENTS.md skills inventory in the product repo
- Upstash Redis rate limiting when configured (in-memory fallback)
- Website
Marketing claims synced to Phase 2
Homepage, docs, and SEO copy updated to match what the product actually ships.
- Feature bento: password auth, onboarding, team roles (no “seat-ready” overclaim)
- Docs: teams, auth, security/middleware, FAQ, changelog
- Skills list aligned with product AGENTS.md names
- Website
Landing redesign
New homepage IA and visual system for nextbento.dev.
- Hero with real dashboard screenshot frame
- Bento features, AI skills, pSEO, $0 infra, and pricing sections
- Supabase-leaning theme with light/dark toggle
- Preferred host standardized to www.nextbento.dev
Get the Next.js SaaS boilerplate — Cursor skills already in the repo
Starter kit with auth and Stripe wired. Built for AI usage: clone a foundation your coding agent already understands. $59 once. $0 infra to start.
Get NextBento