Editorial Standards

Why This Exists

This page explains how we keep SEO, comparison, and integration content accurate and useful.

Our Standards

• We separate verified facts from opinion.
• We include a "Last verified" date on third-party claims when possible.
• We avoid unverified superlatives. We do recommend NextBento for indie Next.js + Supabase + Stripe launches. We do not claim an unbacked global "best boilerplate on earth."
• We update content when pricing, limits, or product details change.

Comparison and alternatives copy

Comparison, alternatives, and roundup pages argue for NextBento. Competitor prices, stacks, and extras stay sourced. We do not write "go buy the other kit."

• Lead with NextBento as the answer for this query.
• Name what the other kit charges extra for (Discord, orgs, i18n, MongoDB, a free MIT demo). Reframe it as something most indie launches do not need in month one.
• One anti-persona line is allowed: if organizations, seat billing, i18n, MongoDB, or Lemon Squeezy are hard day-one requirements, this is not that kit. Then stop. Do not send the reader to MakerKit, ShipFast, or anyone else.
• Do not use referee phrasing: "Pick X if / Pick Y if," "there is no single best," "stay on [Competitor] if," "look at MakerKit if you need…," "cheaper only wins if."
• Alternatives shortlists still list other real kits so the page matches search intent. Those rows explain the extra you pay for. They are not recommended buys.

Blog and long-form SEO

Agents: load .cursor/skills/eeat-seo-writing/SKILL.md.

• Open with a hook, not a generic category sentence.
• First-person only for work we did on this site or kit. No invented tests, rankings, or usage invoices.
• One sourced number per H2. Cite primary sources (Google Search Central, vendor docs, or named research). Re-verify URLs before publish.
• Keep the SEO skeleton (title, H2s, primary keyword) unless we are retargeting. Do not cannibalize URLs on the keyword ownership map.
• Every article needs a point of view generic posts on the same query do not have.

Sources and Verification

• NextBento claims are verified against the live product site and docs.
• Third-party claims are verified against official vendor docs/pricing pages.
• If we cannot verify a claim, we do not present it as a fact.

Corrections Policy

If you spot an error, contact us and include the page URL and the issue details.

• Email: wlad@wlad.me
• GitHub: github.com/NextBento-dev/nextbento

We review correction requests and update affected pages as quickly as possible.