Skip to main content
All pages are optimized for SEO by default. The codebase ships with automatic metadata tags, a generated sitemap, and dynamic OG banners. You mostly just need to update the content.

​
The Three SEO Pillars

The root app/layout.tsx exports default metadata using values from config.ts. Each app can override the defaults through its own toolConfig.ts file.
app/layout.tsx
export const metadata = {
  title: `${defaultTitle}`,
  description: defaultDescription,
  keywords: defaultKeywords,
  icons: [{ rel: "icon", url: `${companyConfig.company.homeUrl}${favicon}` }],
  openGraph: {
    url: companyConfig.company.homeUrl,
    title: `${defaultTitle} | ${companyConfig.company.name}`,
    description: defaultDescription,
    images: [
      {
        url: `${companyConfig.company.homeUrl}${defaultOgImage}`,
        width: 800,
        height: 600,
        alt: `${companyConfig.company.name} logo`,
      },
    ],
  },
};
You can override the default meta tags by exporting a metadata object in any page.tsx file. The defaults in config.ts are your safety net.
The sitemap at app/sitemap.ts combines your static public routes with blog posts from Content Collections. As you customize the starter, keep that file aligned with the routes you actually expose, such as /blog, /apps, /chat, /image-studio, /video-studio, /audio, /vision, /marketing-plan, /launch-simulator, and /voice.
Every blog post you write automatically appears in the sitemap. Just add the .mdx file and it’s indexed.
The route at app/api/og/route.tsx generates dynamic Open Graph images for your pages using next/og. These are the preview cards that show up when someone shares your link on social media.Check out the Vercel OG examples for inspiration on customizing yours.

​
Where to Edit

WhatWhere
Default SEO valuesconfig.ts at the project root
Page-specific overridesExport a metadata object in any page.tsx
Sitemap entriesapp/sitemap.ts
OG image generationapp/api/og/route.tsx
Before launching, search for any leftover “AnotherWrapper” references in your metadata. You want your brand name, not the boilerplate’s.