Next.js SEO with Snoika

A rewrite in next.config.js sends one agreed path to the Snoika origin, and the visitor still sees your domain in the address bar. Next.js fetches the page on the server and returns it under your URL, so search engines index it as part of your site. Snoika's team gives you the origin and sets the Host header to that origin in the rule. The team checks the setup once it's live.

The rule in next.config.js

// next.config.js
module.exports = {
  async rewrites() {
    return [
      { source: '/blog', destination: 'https://ORIGIN-FROM-SNOIKA/blog' },
      { source: '/blog/:path*', destination: 'https://ORIGIN-FROM-SNOIKA/blog/:path*' },
    ];
  },
};

1. Agree on the path with Snoika's team and get the origin value.
2. Add both rules and replace the placeholder with the origin.
3. Deploy to a preview and open /blog and one article URL.
4. Snoika's team checks the headers and canonical tags on the preview.
5. Promote the build to production.

Vercel, Netlify and self-hosted Node

The same rule works on all three. Rewrites are part of the Next.js config, so they run wherever your build runs. You don't need a platform-specific plugin.

The rewrite rule is the only change your Next.js app needs. Your routing and hosting stay as they were. Your deployment pipeline also stays unchanged. Snoika pages run next to your app on the same domain. Search engines and visitors see one site, and the content builds authority for your domain. Check that your middleware matcher skips the agreed path. If you use i18n routing or a basePath, test one localized URL as well.

Every page Snoika publishes carries its own schema markup, so you don't write Article JSON-LD for the proxied pages. Each page also ships with a canonical URL and Open Graph tags. It's linked internally to the related pages, too. Your own app pages still need their own structured data in a `<script type="application/ld+json">` tag in the page component. Run one Snoika article and one app page through Google's Rich Results Test to confirm both parse.

To add llms.txt to a Next.js site, put the file in /public, and Next.js serves it from the root. If the contents require frequent updates, return it from a route handler at `app/llms.txt/route.ts` instead. Jeremy Howard of Answer.AI published the format in a September 2024 proposal. It's a Markdown file with an H1 site name and a short summary. The file also contains lists of links. The format is a proposal.

Snoika gives each page a Markdown twin for AI crawlers and builds an llms.txt index for those pages. If your site already has an llms.txt, keep yours at the root and link the Snoika index from it, so you don't end up with two files competing for the same URL.

For robots.txt in Next.js, add `app/robots.ts` in the App Router. It returns your rules and sitemap URLs, and Next.js turns them into a plain text file. A static `public/robots.txt` works too, on either router. Confirm that no Disallow line covers the agreed path. And if you want ChatGPT search to cite you, don't block OpenAI's search crawler, OAI-SearchBot.

To create a sitemap for Next.js, add `app/sitemap.ts`. It returns an array of URLs with their last-modified dates. Large sites can split it with `generateSitemaps`. Each page Snoika publishes gets a sitemap entry. Confirm with Snoika's team which sitemap URL holds those entries, then list it in robots.txt next to your app's own sitemap. Submit both in Google Search Console.

You see whether the new pages under /blog get cited, and which competitors show up for the prompts you lose.

The API and MCP connection matters if your engineers want to own a piece of the work. They can pull finished content or a list of fixes into their own tools. They can even pull code with the fixes already done.

Use /blog if nothing lives there, or choose a path your app doesn't use. Then decide between the rewrite and a CDN-level connection; the integrations directory covers both, next to CMS connections such as WordPress and WooCommerce. A free AI visibility audit is the first step and requires no access to your systems (the WordPress SEO checklist shows the kind of findings it returns). You fill in a short form for an audit of buyer prompts and AI answers. The audit also checks competitors and gaps. Once work starts, Snoika asks for access to Google Analytics 4 and Search Console. It also requests Tag Manager access so AI visibility ties back to traffic you already measure. Snoika handles Next.js SEO on your domain with one rewrite. Connect Next.js to get your origin value.

Once the connection is live, pages follow the AI content creation workflow and can go out through auto-publishing when no review is needed.