Publishing
SEO for published apps
How generated apps become understandable to Google: real pages, titles, and a clear site structure.
Last updated September 21, 2026
What Beeflower sets up
Every published site on a **custom domain** gets crawlable pages, a `robots.txt`, and a `sitemap.xml` that lists that app’s public pages — your real pages, in a stable order.
Sites that stay on `your-site.beeflower.dev` are live for sharing, but they are not indexed. That keeps random shops out of searches for Beeflower. Use a custom domain when you want Google to list your brand.
Owner, cart, checkout, and login URLs stay out of the sitemap so they do not compete with the sitelink row. Google still decides whether sitelinks appear. Beeflower’s job is valid pages, useful labels, and the right order.
What you should still do
Use a custom domain so search results show your brand. After Publish, open `https://your-domain/sitemap.xml` and submit it in Google Search Console.
Ask Agent to add missing pages rather than stuffing everything onto Home. Distinct URLs for Pricing, About, Contact, and similar hubs are what search engines can actually list.