Sample mini audit

What the 3-point Framer AEO audit looks like.

This is the short format I send after checking a public multilingual Framer site. It focuses on launch risks that can be verified without private project access.

Request this for your site See Pro workflow

Example findings.

The real audit uses the submitted URL and visible locale structure. This anonymized sample shows the level of specificity.

Finding 1

Root llms.txt is not reachable

Why it matters: AI crawlers may understand the default page but miss the localized context your team already shipped.
First fix: Publish a root llms.txt with canonical pages, locale variants, and the highest-value public docs.

Finding 2

Homepage JSON-LD is missing

Why it matters: Search and answer engines have less structured context for the brand, service area, and language coverage.
First fix: Add Organization and WebSite schema, then verify it from the published domain rather than the editor preview.

Finding 3

Localized metadata still matches default copy

Why it matters: Language-specific pages can look duplicated, which weakens both search snippets and AI answer summaries.
First fix: Review locale titles, descriptions, CMS summaries, and schema inLanguage values before the next handoff.

Want this for a live site?

Send the public URL and visible locales. If the site is relevant, I will reply with a short audit or one practical next step.

Request mini audit