How to add structured data to a Base44 app

Base44 adds BreadcrumbList structured data to every page on its own, and injects WebSite, Organization and FAQPage schema once you generate them with Fix with AI in the SEO & GEO scan. Anything else, such as LocalBusiness, Product, Article or Event, you add by asking the AI chat or writing it in code. Then validate it, because invalid schema does nothing.

This is one step in the Base44 SEO checklist.

What Base44 generates#

From Base44’s SEO documentation:

• BreadcrumbList “is automatically synthesized for every page.” Since May 2026 it’s generated per route, so each route gets its own trail.
• WebSite, Organization and FAQPage “are injected once generated, which you can do from the SEO & GEO scan using Fix with AI.”
• Everything else “you can ask the AI to add JSON-LD structured data into your app or add it in code.”

On the live sites in our crawler test, WebSite and Organization blocks were common, and they’re how we found each app’s custom domain: Base44 puts your public URL in them. Check what yours has:

curl -s -A 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' \
  https://yourdomain.com/ | grep -o '"@type": *"[^"]*"' | sort | uniq -c

Which types are worth adding#

Google has narrowed which FAQ results it shows over the years, so FAQPage markup rarely produces the familiar dropdowns now. It’s still useful context for search engines and AI assistants reading the page, and Base44 generates it for you.

Adding a type with the AI chat#

Base44’s docs give prompts for this. A version that works for most types:

Add valid JSON-LD "LocalBusiness" schema to the Contact page with our business name,
full address, phone number, opening hours and geo-coordinates. Use only details that
are visible on the page.

For record pages, the schema needs to come from the loaded record:

On the ProductDetail page, once the product has loaded, add JSON-LD "Product" schema
with the product's name, description, image, price and currency, and availability,
using the values shown on the page.

Two rules from Google’s guidelines that the AI won’t enforce for you: mark up only what’s visible on the page, and don’t mark up reviews you wrote yourself about your own business.

If you manage schema yourself#

If you add JSON-LD in code and Base44’s injected schema conflicts with it, turn off Platform structured data injection in the SEO & GEO page’s Advanced Settings. Keep Enable SEO for this app on, since that toggle also controls pre-rendering.

Validating on Base44#

Validate every type you add with Google’s Rich Results Test and the schema.org validator. On Base44 there’s one wrinkle: the Rich Results Test’s URL mode fetches with Google-InspectionTool, and in our tests Base44 served that user agent its generated summary block instead of the rendered page. Schema injected by the platform is usually still there. Schema your own code adds may not be.

The reliable method is to grab the HTML Googlebot’s user agent receives and paste it into the test’s Code tab:

curl -s -A 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' \
  https://yourdomain.com/contact > contact.html
grep -c 'id="seo-snapshot"' contact.html   # 0 means you have the rendered page

If the count is 1, the page has no cached render yet. Check again after your next publish.

What to do next#

1. Run the SEO & GEO scan and let Fix with AI generate WebSite, Organization and FAQPage.
2. Add LocalBusiness if you serve a location, and Product or Article on record pages.
3. Validate each with the Code-tab method above.
4. If you run a local business, continue with the local SEO checklist.