Publishing
SEO for published apps
How generated apps become understandable to Google: real pages, titles, and a clear site structure.
Last updated August 12, 2026
What Beeflower sets up
Every published site gets crawlable pages at the live URL (your domain or `your-site.beeflower.dev`), a `robots.txt`, and a `sitemap.xml` that lists the public hubs first — Shop, Search, About, and the rest of that app’s real routes, in a stable order.
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.