Cases
Evidence, not vibes
Industry, starting point, and numbers — not a generic portfolio grid.
Library
Public material instead of gated decks: case studies with the problem and metrics, a blog to align IA and technical SEO, and patterns for the App Router (metadata, schema, indexing, CWV). The pattern catalog is below; a dedicated “Patterns” page is handy for bookmarks and breadcrumbs. Cases and blog are linked from the section cards. The English library is written for SMB teams in the United States and comparable markets; we adapt examples by locale and name contentious topics (rich results, duplicate URLs) plainly.
Library sections
Projects, long reads, or copy-paste snippets for your repo — depending on what you need.
Case studies
Problem, stack, and post-launch metrics you can map to your own brief.
Summary in the list, full write-up inside
Blog
Notes on IA, technical SEO, acceptance, and forms for stakeholder alignment.
How pages, briefs, and Next.js fit together
Patterns
App Router snippets for metadata, schema, and indexing without reinventing basics.
Topic, difficulty, time estimate
Code and markup patterns
Ready-to-use snippets for Next.js App Router: JSON-LD, sitemap, robots, canonicals, redirects, CWV. The same catalog with an audience intro lives on the Patterns page.
Level reflects depth in Next.js, TypeScript, and SEO/markup: basic (follow the snippet), intermediate (integrate in App Router), advanced (policies and edge cases in search).
Time estimate is a guide for reading and a first implementation in a typical project; your process may differ.
Filter by topic
Patterns by topic
All topics in one list. Use the filter above to narrow it down.
- IndexingDeveloperTypeScript
Dynamic sitemap.xml in Next.js (app/sitemap.ts)
One sitemap with static and content URLs; aligned with collectIndexableUrls and canonical URLs.
- Level:
- intermediate
- Time estimate:
- ~40 min
- IndexingSEOTypeScript
robots.txt and robots metadata in Next.js App Router
Static robots via app/robots.ts and per-route noindex via generateMetadata.
- Level:
- beginner
- Time estimate:
- ~25 min
- JSON-LDDeveloperTypeScript
BreadcrumbList JSON-LD for internal pages
One helper feeds both visible breadcrumbs and markup — names and URLs stay in sync.
- Level:
- beginner
- Time estimate:
- ~15 min
- JSON-LDDeveloperTypeScript
Extending JSON-LD Organization and WebSite in the root layout
Linked @id values in @graph: organization, person, site — the base for other entities.
- Level:
- intermediate
- Time estimate:
- ~45 min
- Markup and policiesSEOTypeScript
FAQ and HowTo JSON-LD: when markup is appropriate
Avoid markup “for stars only”: visible content, one primary intent per page, Google guidelines.
- Level:
- advanced
- Time estimate:
- ~30 min for policy
- Next.jsSEOTypeScript
Canonical URL and page metadata in Next.js App Router
A generateMetadata pattern with canonical and Open Graph — baseline SEO hygiene.
- Level:
- beginner
- Time estimate:
- ~20 min
- Next.jsDeveloperTypeScript
Permanent redirects in Next.js (config and middleware)
301/308 for slug changes and duplicate consolidation; watch for loops and canonical drift.
- Level:
- intermediate
- Time estimate:
- ~35 min
- PerformanceDeveloperTypeScript
Core Web Vitals in a production Next.js app: LCP, INP, CLS
Practical levers: LCP image priority, stable layout, splitting heavy JS.
- Level:
- intermediate
- Time estimate:
- ~1 h for an audit
Why use all three sections
Cases before the call, articles before sign-off, patterns before you edit code. Together they cut bad specs and late prod fixes.
Blog
Shared language
IA, SEO, and “done” criteria before the budget is gone.
Patterns
One standard in the repo
Metadata, schema, and indexing stay consistent across templates.