Skip to main content
Control how your app appears when it’s shared, bookmarked, found in search, or downloaded.

Web apps

How you set metadata depends on your project type. The quickest way to check: open Project Settings (gear icon in the left sidebar) and look for a Social Share tab. If it’s there, you’re on a V1 project. If it’s not, you’re on a V2 project and metadata is set through the agent.

V1 projects

Open Project Settings and go to Social Share. You’ll see three fields that control what people see when your link is shared on Twitter, LinkedIn, iMessage, Slack, Discord, and other platforms:
  • Title (og:title): the headline shown in the preview card
  • Description (og:description): a short summary below the title
  • Image (og:image): the image displayed in the card. PNG, JPEG, or GIF. Recommended size 1200x630px.
The panel shows live X and Google previews as you edit. Save changes, then republish to push them to your live URL.
After publishing, test your previews by pasting your URL into a social platform or using a tool like opengraph.xyz.

V2 projects

V2 projects use the Next.js metadata system. There’s no UI panel for it. You tell the agent what you want and it writes the code for you. Everything below lives under apps/web/src/app/.

Site title and description

Set the site title to "Filter Renew" and the description to
"Professional water filtration services for homes and businesses."
The agent will add or update a metadata export in apps/web/src/app/layout.tsx:
export const metadata = {
  title: "Filter Renew",
  description: "Professional water filtration services for homes and businesses.",
};

Per-page titles and descriptions

The title and description in layout.tsx are the site-wide defaults. Any individual page can override them by exporting its own metadata. This matters for content sites: every blog post, product, or article should have its own title and description so search results read well.
Give every blog post its own SEO title and description based on the post's
title and excerpt. Same for product pages.
For dynamic routes like /blog/[slug], the agent uses Next.js’ generateMetadata function so the title and description are pulled from the database at request time.

Open Graph image

The image that appears when your link is shared on social platforms. You can use a static image file or generate one from code. Static image:
Add an open graph image to apps/web/src/app/opengraph-image.png
using my logo centered on a white background.
Dynamic (generated from code):
Add a dynamic open graph image using next/og that shows my site
title on a branded background.
The dynamic option is useful when you want a per-page card, for example a blog OG that shows the post title.

Favicon

The favicon lives at apps/web/public/favicon.png and is referenced from the metadata.icons field in layout.tsx. The agent handles both pieces when you ask:
Use this image as the favicon.

Sitemap

A sitemap lists every URL in your site so Google and other search engines can find them. Google Search Console asks for one whenever you verify a site, so this is the first SEO win to grab.
Add a sitemap that lists every page in my site, plus every published
blog post from the database.
The agent creates apps/web/src/app/sitemap.ts. Next.js serves it automatically at /sitemap.xml. For dynamic content (posts, products, listings), the sitemap queries the database when it’s generated so new entries show up on their own.

robots.txt

robots.txt tells search engines which URLs they’re allowed to crawl. The two cases customers run into:
  • Block crawling of a staging or preview URL so it doesn’t show up in Google.
  • On production, explicitly allow crawling and point to the sitemap.
Add a robots.txt that allows all crawlers and points to my sitemap.
The agent creates apps/web/src/app/robots.ts. Next.js serves it at /robots.txt.
After publishing with a new sitemap and robots, submit your sitemap URL in Google Search Console so Google starts crawling sooner.

Branding badge

Free projects show a “Made with Anything” badge on the published site. Upgrade to a Pro plan to remove it.

Mobile apps

Open Project Settings and go to Branding & Icons.

App icon

The icon users see on their home screen and in the App Store or Play Store. Upload a 1024x1024px PNG with no transparency.
Keep important content centered. Both iOS and Android crop icons into rounded shapes, cutting off the edges.

Splash screen

The loading screen shown while your app launches. Upload a 1024x1024px PNG. This is the first thing users see when they open your app, so make it match your brand.
Set my app icon to a blue gradient with a white fork and knife icon

Publish

Take your app live

Domains

Custom domain setup

App Store

Submit to the App Store

Project settings

All settings options