Lovable
Agents write the pages that get your Lovable app found, straight into the Supabase database it already runs on. You decide what goes live.
SEO AI Agents for Next.js
Agents find what your buyers search for and write the pages to catch it, straight into the database your app already reads. Paste one connection string, pick a table, map your columns.
- Writes into the database your app already reads, not a new one
- Nothing is published until you approve it
- Updates its own rows instead of piling up duplicates
Next.js
About Integration
SEOmatic publishes into the Postgres database behind your Next.js site. You pick the table and map your columns, and SEOmatic writes the rows your existing routes render.
Supported Content
- Pages
- Blog Posts
Pricing
All integrations are included in every plan. Plans start at $99/month. See pricing.
Requirements
A Postgres database reachable from the public internet, with a table that has an id column, plus INSERT and UPDATE permissions. Works with Supabase, Neon, Railway, Render, RDS and Lightsail. SSL is used automatically.
Resources
Visit our blog to learn more about programmatic SEO and how it can help your business generate more traffic, leads, and sales.
Next.js Integration with SEOmatic
How to Connect Next.js with SEOmatic
SEOmatic writes directly into the Postgres database your Next.js site already reads from. Works with both App Router and Pages Router, because SEOmatic never touches your routing.
Step 1: In SEOmatic, go to Connections and select Next.js.
Step 2: Paste your Postgres connection string. SEOmatic validates it and confirms the database name.
Step 3: Pick the table to publish into, then map its columns to title, content, slug, excerpt, image and meta fields.
Step 4: Build your content template using variables, AI, or both, and publish. SEOmatic inserts new rows and updates ones it published before, so republishing never creates duplicates.
Because your pages are rendered by your own code, revalidate the route after publishing (revalidatePath) or render it dynamically, so new content is visible to search engines right away.
What Agents Can Do on Next.js
Writes The Pages
Full articles and programmatic pages from research to finished draft, published as rows your routes already render.
Nothing Applies Without You
The agent arrives switched off and starts in approval mode. It earns more rope only when you give it.
Update, Never Duplicate
Agents remember the row they wrote and update it, so republishing does not leave you cleaning up copies.
Column Field Mapping
Map your table's columns once to title, content, slug, excerpt, image and meta. Common names are matched for you.
Publish Verification
After publishing, SEOmatic fetches the live URL and tells you if your route is still serving the old version.
Draft And Published States
Rows carry their status, so your app can hold work back until you are ready for it to appear.
Either Router
App Router or Pages Router makes no difference, because agents never touch your routing layer.
Your Postgres, Your Rules
Supabase, Neon, Railway, Render, RDS or Lightsail. SSL is used automatically and nothing is added to your schema.
Bulk Campaigns
Whole page sets generated from your data and real search demand, with sample pages shown before any of it lands.
Your app owns the rendering, so agents stay on their side of the line: they research, write and publish rows, and your code decides what happens to them.
Use Case 1: SaaS Product Pages for Next.js
Every capability, module and add-on you ship is something people search for by name. Agents check which ones have real demand behind them and write a page for each, straight into the table your app renders from.
Use Case 2: Ecommerce Product Pages for Next.js
A large catalogue usually means hundreds of products sharing a supplier description. Agents write a real one for each from your own data, and you review sample pages before any of it goes into your database.
Use Case 3: Comparison Pages for Next.js
Comparison and alternative pages catch people close to deciding. Agents build them from your own data and real search demand, then revisit them as the competitive picture shifts.
Frequently Asked Questions
Can agents fix pages I already have?
Not on this connector, and the distinction matters. A Postgres connection is a place to publish into, not a website we can read, so agents write new rows and update the ones they wrote before. They do not go through your existing content and rewrite it the way they do on WordPress or Shopify, because a database gives them no way to know which row is which page. If in-place fixes to your current pages are what you want, connect the CMS your content actually lives in.
Does it work with both App Router and Pages Router?
Yes. Agents write to your database, not your routing layer, so it makes no difference whether your pages come from generateStaticParams in the App Router or getStaticProps in the Pages Router. Your existing route reads the new rows the same way it reads the rest.
Does it work with Incremental Static Regeneration?
Yes, with one thing on your side. SEOmatic writes the row, but a statically generated or ISR-cached route keeps serving its previously built HTML until it revalidates. Call revalidatePath after publishing, set a revalidate interval, or render the route dynamically. SEOmatic checks the live URL after each publish and warns you if the page is still serving an older version.
Which Postgres providers are supported?
Any Postgres reachable from the public internet, including Supabase, Neon, Railway, Render, AWS RDS and Lightsail. SSL is used automatically, so you do not need to add an sslmode parameter. Databases on localhost or a private network cannot be reached, so public access needs to be enabled.
Will it change my database schema?
No. Agents write into the table and columns you map and nothing else. No tables are created, no columns are added, and no migrations are run. If a column in your mapping no longer exists, that field is skipped rather than the write being forced through.
Will republishing create duplicate rows?
No. SEOmatic records the row id it wrote and updates that row on subsequent publishes. It only inserts when there is no existing row to update, so you can regenerate and republish content without cleaning up duplicates afterwards.
What happens to the work if I cancel?
It stays yours, more literally here than anywhere else. The pages are rows in your own database, rendered by your own code. Nothing reverts, nothing is deleted, and nothing stops working if you stop paying.
Explore Other Integrations
See what agents can do on the other platforms SEOmatic connects to.
WordPress
Agents fix titles, meta, content and schema on your live WordPress site. You stay in control, and every change can be undone.
Webflow
Agents work through your CMS collections item by item, fixing the SEO nobody has time to maintain. You stay in control.
Shopify
Agents write your blog, build the collection and landing pages you are missing, and repair the pages that are slipping. You decide what goes live.
Ghost
Agents write and refresh your posts, and set the canonical tags and schema most platforms will not let them touch. You decide what goes live.
Wix
Agents write and refresh your Wix blog, and fix the meta on posts already published. You stay in control of what ships.