How to Choose a Next.js Agency: 8 Checks from Our Own Website

How do you choose a Next.js development agency?

Choose a Next.js development agency by asking it to pass eight checks on real published URLs and on the editing flow you will use. On six live neaptide.ai pages checked on October 7, 2026, all six returned HTTP 200, one H1, a matching canonical and seven language alternates. Ask any agency for the same evidence before you sign.

• Output checks: 4 of the 8 checks test the HTML a live URL returns, namely status, canonical, H1 and language alternates.
• Own evidence: 6 of 6 neaptide.ai pages passed all four output checks on October 7, 2026, in unauthenticated HTTP requests without browser rendering.
• Work checks: the other 4 checks cover CMS editing, migration, forms and handover, and each needs a live demonstration on the project.
• Budget: Neaptide’s web development page lists starting prices of $2,900 for a landing page, $8,200 for a corporate site and $14,000 for a web app.
• Red flag: a fixed price for a multilingual CMS site that names no templates, languages or old URLs.

Which 8 checks should a Next.js agency pass before you sign?

A Next.js agency should pass eight checks before you sign: four on the HTML its live URLs return and four on work an HTTP request cannot see. The eight checks are server response, canonical, one H1, language alternates, editorial flow, migration, forms and integrations, and handover. Language alternates are the hreflang links a page declares to each language version, plus x-default.

Neaptide’s own study covers checks 1–4 only. Checks 5–8 need their own tests on the project you commission.

What should you ask a Next.js agency for first?

Ask a Next.js agency for missing evidence in this order and stop at the first match, because each gap blocks a fair comparison of proposals.

1. If the agency cannot show URL-level output checks for any live site it built, ask for them before anything else.
2. If the project includes a CMS and your intended editor has not seen a draft go through preview, publishing and restore, ask for that session next.
3. If the new site replaces an old one and the quote has no old-URL inventory, ask for the inventory and the redirect plan.
4. If forms and integrations are listed without a delivery test, ask how delivery will be tested before launch.
5. If all four are answered, compare proposals on scope, fees, exclusions and handover terms.

What did Neaptide’s check of its own website show?

On six live neaptide.ai pages checked on October 7, 2026, all six returned HTTP 200, one H1, a canonical matching the requested URL, index, follow robots metadata and seven language alternates each. Neaptide, a digital marketing studio that also builds websites on Next.js, ran this check on its own production site. The check read server HTML only, so it does not prove Google indexing, translation quality or CMS capabilities.

• Research data and method · EN
• Questions and answers

This article is Neaptide’s own-site research. It does not compare named agencies, report a client result or demonstrate a headless CMS. Our current site stores article content in the repository, so its multilingual output is evidence of that publishing system only.

How was the six-page evidence collected?

The six-page evidence comes from unauthenticated HTTP GET requests to six English neaptide.ai production URLs on October 7, 2026, with the returned HTML parsed for status, canonical, H1 count, robots metadata and language alternates. The six URLs are the SEO, GEO, web development and AI consulting service pages, the Next.js SEO audit page and the company-knowledge chatbot guide. The collection time and a hash of each HTML response are kept in the downloadable JSON.

The requests did not execute browser JavaScript. The study did not measure visual usability, performance scores, forms, CMS permissions, translation quality or search indexing, and each of those needs its own test. The six URLs were selected to cover five commercial pages and one article, not sampled at random from the whole site.

• Download the URL-level observations · JSON

Does a passed HTTP check prove that a Next.js page is indexed?

A passed HTTP check proves what the server returned at collection time; Google indexing and Google’s selected canonical have to be checked separately. On the six neaptide.ai pages the fields were consistent: one H1, one matching canonical, index, follow, and seven language alternates (six languages plus x-default).

Seven declared language alternates per page do not prove that every target works or carries a correct translation. This study did not request the targets of the 42 alternate entries (6 pages × 7). A follow-up acceptance check should request each target URL and confirm that the links are reciprocal.

Google documents a declared canonical as a signal. To investigate an indexing problem, combine the page response with Search Console evidence, crawl access, internal links and sitemaps.

• Google — canonical URL signals
• Next.js 15 — metadata reference

Which pages should a multilingual Next.js site be accepted on?

A multilingual Next.js site should be accepted on at least five page types: a representative service page, an article, a case study, a page with a missing translation and every migrated URL. The published site should expose the intended content and metadata; a private preview follows its own access and indexing rules.

If a CMS is part of the purchase, your intended editor should run the editorial flow live: create and preview a draft, publish a language version, correct it and restore a previous version. Neaptide’s HTTP study cannot show whether those actions work in a CMS, and we do not use it as evidence for that.

Five scope areas belong in the brief:

• Content models: service, article and case-study fields, shared sections and relationships.
• Language rules: translated fields, shared fields, URLs and unavailable translations.
• Publishing: editor roles, preview access, approvals and recovery.
• Migration: the actual old-URL inventory, redirects and content decisions.
• Handover: repository and account access, deployment instructions and maintenance ownership.

Do the checks differ for an agency, a freelancer or an in-house team?

The same eight checks apply to a Next.js agency, a freelancer or an in-house team, because each check tests published URLs and working flows rather than the size of the provider. Neaptide’s data does not compare these three options, so this article gives no verdict on which one is better.

Who holds access after launch is the point to settle with any of the three. Ask for repository and account access in your company’s name, with deployment and editor instructions a second person can follow.

How much does a Next.js website cost?

At Neaptide, a Next.js website starts at $2,900 for a landing page, $8,200 for a corporate site and $14,000 for a web app, according to our web development page as captured on October 7, 2026. Those figures are starting prices per format. A multilingual CMS project with migration and integrations needs a quote based on its actual templates, languages and publishing requirements.

The same page states that a project usually takes 4–8 weeks: about one week for design and architecture, 3–5 weeks for development and content, and a final week for adjustments, load testing and launch.

• Our current web development offer
• How to compare website development costs

What are the red flags when hiring a Next.js agency?

Seven red flags should stop a Next.js agency contract until the agency resolves them:

1. No URL-level output checks for any live site the agency built.
2. A representative URL that returns a status other than 200, more than one H1, or a canonical that does not match its own address.
3. Language alternates that do not list every published language plus x-default: a six-language site declares seven, as each checked neaptide.ai page did.
4. A CMS demonstration that skips preview, publishing a language version or restoring a previous version.
5. A migration quote without an inventory of the old URLs and their redirects.
6. Handover instructions that no second person has repeated before acceptance.
7. A fixed price for a multilingual CMS site that names no templates, languages, integrations or exclusions.

These red flags are acceptance checks; Neaptide has not measured how often they occur among agencies.

How do you accept a Next.js website at handover?

Accept a Next.js website at handover only after a second team member has followed the deployment and editing instructions without help from the agency. Keep the URL-level output checks next to the migration inventory and the form-delivery evidence, so verified output stays separate from untested capabilities.

The method used on the six neaptide.ai pages can run before and after a release as part of that acceptance packet, alongside editor, migration and integration checks.

• Website brief and acceptance fields · TXT
• Next.js audit and implementation scope
• Planning multilingual content