
Migrating a Pages app to App Router without drama
I migrate Pages to App Router one URL at a time. Copy the data rules, keep a rollback, and leave the next route until this one is boring.
What I learn shipping client projects, written up so you can use it. Read how to set up Cursor so AI-written code passes review, when a WordPress site should move to Next.js, what a Next.js developer costs, and how to keep your SEO through a migration.
Hire me to build it, or bring me in to coach your team on Cursor. I reply within 24 hours and tell you plainly whether I'm the right fit.

I migrate Pages to App Router one URL at a time. Copy the data rules, keep a rollback, and leave the next route until this one is boring.

Next.js App Router API pick: route.ts for outside callers, Server Action for our forms. Example route.ts plus the mistakes I still inherit.

I start new work in App Router. I still open pages/ on old repos. Here is when, and what I refuse to rewrite in a weekend.

I use App Router as a route tree I can explain, not a React SPA with a Next wrapper. Here is the set I keep.

When someone asks me to hire a Next.js developer, I ask for a shipped App Router repo, not a year count. Here is what I open first.

Same family name, two products. The open-source toolkit lives in your repo. The private SaaS stores SERP history for you. Here is the honest split, the Competitors tab matrix, and how open beta next week fits.

I built a hosted RankMySEO next to the open-source toolkit so you can own daily SERP history without running the tracking stack yourself. Here is the clickable MVP, what Overview and Keywords already do, and how open beta next week works.

People mix up “SEO for AI,” “SEO for LLMs,” and GEO like they are one thing. They are not. Classic SEO still ranks blue links. SEO for AI is clarity and structure for machines. GEO is about getting cited in generative answers. Here is the plain split, and what I am building with RankMySEO.

Buying Cursor seats for the whole team on Monday is not a rollout. Here is the 30-day plan I actually use with client teams: a small group, shared rules, one repo, and a review habit before you scale.

Cursor Composer writes a confident summary. The diff still sneaks in extra files, a duplicate helper, and skipped tests. Here is the PR review checklist I actually run on AI-generated code.

“Build me an app” is how Cursor invents a stack, extra packages, and no tests. Here is the small-app loop I actually use: one slice, your stack, a fence, then Chat, Composer, review.

Orang googling cara menggunakan Cursor AI, skip pagar, lalu Accept. Seminggu kemudian repo klien penuh package baru, utils2, dan diff yang nggak ada yang berani review. Ini loop yang saya pakai.