Ship Fast Without Breaking Things: Our Quality System
How we maintain 98% on-time delivery without cutting corners on code quality, tests, or documentation.
From the Metadata API to Core Web Vitals — everything you need to ensure your Next.js 16 app ranks and loads fast.
Most SEO guides for Next.js are outdated the moment they're published. The App Router changed everything — the way metadata works, how pages are statically generated, and how the runtime handles streaming. Here's the checklist we run on every project before going live.
The old <Head> component is gone. In Next.js 16 every route exports a metadata object or a generateMetadata function. Forgetting this means your pages get no title, no description, and no OG data.
For dynamic routes — blog posts, product pages, user profiles — always use generateMetadata with await. It runs at build time for static routes and at request time for dynamic ones.
export async function generateMetadata({ params }): Promise<Metadata> {
const post = await getPost(params.slug);
return {
title: post.title,
description: post.excerpt,
openGraph: {
title: post.title,
images: [{ url: post.ogImage }],
},
};
}
If you have both /blog/seo-guide and /blog/seo-guide/ resolving to the same content, you have a duplicate-content problem. Set a canonical explicitly:
alternates: {
canonical: `https://www.cielont.com/blog/${params.slug}`,
}
Also set this for paginated routes (/blog?page=2) and filtered collections (/products?category=mobile).
Schema.org markup doesn't directly improve rankings, but it unlocks rich results — article bylines, star ratings, FAQ dropdowns, sitelinks. For a software company blog, Article and Organization schemas are the minimum.
Inject JSON-LD via a server component so it's included in the initial HTML, not hydrated later:
export default function ArticlePage({ post }) {
const schema = {
"@context": "https://schema.org",
"@type": "TechArticle",
headline: post.title,
datePublished: post.isoDate,
author: { "@type": "Organization", name: "Cielont" },
};
return (
<>
<script type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
/>
...
</>
);
}
Next.js 16 has first-class support for both. Create app/sitemap.ts and app/robots.ts — they run at build time and serve the correct content-type headers automatically.
// app/sitemap.ts
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
const posts = await getAllPosts();
return posts.map((p) => ({
url: `https://www.cielont.com/blog/${p.slug}`,
lastModified: p.updatedAt,
changeFrequency: "monthly",
priority: 0.7,
}));
}
LCP (Largest Contentful Paint) — almost always a hero image. Use <Image priority /> for above-the-fold images and ensure your server response is fast. If LCP is above 2.5s, look at your TTFB first.
CLS (Cumulative Layout Shift) — reserve explicit dimensions for every image, font, and embed. Next.js next/image handles this automatically with width and height props. Fonts using next/font set font-display: optional by default, eliminating FOUT.
INP (Interaction to Next Paint) — replaced FID in March 2024. Audit your JavaScript bundles. Server Components reduce client JS significantly; anything you can move server-side, move it.
Any dynamic route that doesn't export generateStaticParams is rendered on-demand, adding latency and bypassing the CDN edge cache. For a blog this is inexcusable — every post slug is known at build time.
export async function generateStaticParams() {
const posts = await getAllPosts();
return posts.map((p) => ({ slug: p.slug }));
}
Use next/font for all Google Fonts. It downloads fonts at build time, self-hosts them, and adds the <link rel="preload"> tag automatically. Zero layout shift, zero round trip to fonts.googleapis.com at runtime.
Pair it with display: 'swap' for body fonts and display: 'optional' for display fonts to minimise CLS.
viewport metadata export to layout.tsx<img> tags with <Image> from next/imagenext build output for routes that are not statically generated/sitemap.xml and /robots.txt resolve correctly in productionSEO isn't a launch checklist item — it's a system. The sites that rank in 2026 are the ones that treated performance and structure as engineering requirements from the start, not an afterthought.
How we maintain 98% on-time delivery without cutting corners on code quality, tests, or documentation.
Real-world lessons from building and shipping retrieval-augmented generation systems for enterprise clients — what nobody tells you before you start.
The optimisations that doubled frame rates in our mobile commerce app — Hermes, list virtualisation, and the profiling workflow we use on every project.
Work with us
From custom software to AI systems — we ship production-grade products on time.