Next.js: automate Indexing API submissions from your CI pipeline

If your Next.js site rebuilds on every push, you already have a CI signal that says "these URLs changed." The missing piece is wiring that signal into the Indexing API so Google hears about it within seconds of deploy. IndexerNow handles the OAuth and quota tracking so your CI script just has to know which URLs to send.

The two-step approach

1. In your build script, generate a list of URLs that actually changed (diff your sitemap, parse your MDX frontmatter, or read the routes that touch updated source files).
2. Sign into IndexerNow once with the Google account that owns Search Console. Paste the URL list. Submit.

When the manual flow is enough

For most teams, the deploy frequency doesn't justify full automation. A weekly release with 5-20 changed URLs is faster to push by hand through IndexerNow than to build, debug, and maintain a CI integration that uses OAuth refresh tokens. Use the manual flow until volume forces your hand.

When volume forces full automation

• Documentation sites that deploy on every merge.
• Content platforms publishing 50+ pieces a day.
• Programmatic SEO sites generating thousands of pages a week.
• Multi-tenant SaaS where customer signups create new public URLs.

Vercel-specific tip

If you deploy to Vercel and use ISR or on-demand revalidation, you already have a hook for "a URL changed." Tag that hook with a call to push the URL to IndexerNow's API or use the dashboard at the end of your release. Either way, decouple it from your build so a failure here doesn't fail the deploy.