Make AI get your business right.

What do AI see about your business? Paste your URL to find out.

Promoted businesses

This is the list of businesses that are already visible to AI agents after using the GeoYourself audit tool.

Sample report

Inside your audit

This is an example of the report you will receive.

Private audit report

Solara Bakery

https://solarabakery.example · Alfama, Lisbon

72 Content
35 Technical

Solara reads clearly as an artisanal bakery, but answer engines still invent or omit hours, phone, and neighborhood. Strengthening local entity facts and FAQ structure would raise answer accuracy across ChatGPT-style and Google-grounded assistants.

Your priority plan

  1. 1Publish phone, hours, and “Alfama, Lisbon” as visible HTML — not only in images or PDF.
  2. 2Add FAQ: sourdough, vegan options, weekend pickup, allergen info.
  3. 3Make “Order / reserve” a primary CTA on the homepage.
  4. 4Resolve hours mismatch between footer (closes 19:00) and menu PDF (closes 18:30).
  5. 5Add LocalBusiness JSON-LD so machines can ground name, phone, and hours.

Platform lenses

ChatGPT78

Answer-first content is thin. Add FAQs assistants can quote.

View details

Why it matters

ChatGPT favors pages with clear Q&A and quotable facts. Without FAQs and a visible phone, answers invent or skip Solara details.

Strengths

  • Strong brand story about wood-fired sourdough
  • Clear bakery category on the homepage hero

Findings

  • No FAQ block in HTML
  • Phone missing from server-rendered markup
  • Booking CTA is secondary to Instagram links

Priority fixes

  1. Add 5–7 FAQs in plain HTML
  2. Publish a tel: link in the header
  3. Make Order / reserve a primary CTA
Gemini54

NAP incomplete — locality and phone not consistent across pages.

View details

Why it matters

Gemini leans on local entity signals. Conflicting hours and missing phone weaken grounding for Alfama bakery queries.

Strengths

  • Lisbon / Alfama mentioned in marketing copy

Findings

  • No LocalBusiness schema
  • Phone absent in HTML
  • Hours conflict between footer and PDF

Priority fixes

  1. Add LocalBusiness JSON-LD
  2. One NAP line on every key page
  3. Resolve hours mismatch
Copilot70

Homepage title OK; hours only appear in a PDF menu.

View details

Why it matters

Copilot/Bing-oriented grounding prefers indexable HTML. Facts trapped in PDFs are easy to miss.

Strengths

  • Clear homepage title
  • Public crawlable URLs

Findings

  • Hours not in HTML tables or schema
  • Important menu facts only in PDF

Priority fixes

  1. Duplicate hours as HTML on Contact and Home
  2. Link Contact with a normal href
Grok68

Few short quotable facts; Instagram does more work than the site.

View details

Why it matters

Grok-style answers need terse public-web facts. If Instagram holds the phone and hours, the site underperforms.

Strengths

  • Memorable brand name
  • Distinctive sourdough positioning

Findings

  • Sparse hard facts on the homepage
  • Social channels outrank the site for practical details

Priority fixes

  1. Add a short facts block: phone, hours, pickup, price band

Expert council

Retrieval readiness

Key facts are split across Instagram, a PDF menu, and a Contact page with weak internal links. Crawlers can reach the brand, but not a single canonical answer block.

Fix: Add name, phone, hours, and Alfama address in HTML on the homepage.

More details
  • Homepage HTML has no telephone or mailto link.
  • Contact facts live mainly on Instagram and a PDF menu.
  • Internal links to Contact are sparse; crawlers may stop at the hero.

GEO / answer content

Storytelling is strong (“wood-fired sourdough”) but assistants lack Q&A pairs for dietary options, pickup windows, and weekend lines.

Fix: Add 5–7 FAQs in plain text, not only images of the chalkboard.

More details
  • No FAQ section or FAQPage schema detected.
  • Dietary and pickup answers appear only in social captions.
  • Chalkboard menu is image-only — not extractable as text.

Local entity SEO

Business category is implied, not stated. No clear “bakery in Alfama, Lisbon” phrase. Opening hours conflict between footer and PDF.

Fix: One consistent NAP + category line on every key page.

More details
  • Missing LocalBusiness JSON-LD with NAP fields.
  • Footer says closes 19:00; menu PDF says 18:30.
  • “Alfama” appears inconsistently across title and body copy.

Questions people ask AI

  • “Vegan pastry shop with good reviews open Saturday mornings near Alfama”
  • “Best sourdough bakery in Lisbon for weekend pickup”
  • “Artisan bakery in Alfama with phone number and opening hours”
  • “Where to buy wood-fired bread near Alfama Lisbon”
  • “Bakery with vegan options open early Saturday Lisbon”

Technical crawlability · 35/100 · Poor

critical
Contact details

No phone or email was found in readable HTML.

More details

Hurts: ChatGPT, Gemini, Copilot, Grok, Claude

Fix: Add a clickable tel: link in the header or footer on every page.

Phone and email are high-value answer fields. If they only appear in images or widgets, crawlers often miss them.

  1. Put a visible tel: and/or mailto: link in the header or footer HTML.
  2. Repeat the same number in LocalBusiness telephone schema.
  3. Avoid contact-only-in-PDF or contact-only-in-Instagram.
critical
Structured data missing

No JSON-LD business markup was found for machines to ground facts.

More details

Hurts: Gemini, ChatGPT

Fix: Add JSON-LD with name, address, telephone, openingHoursSpecification.

Without JSON-LD, assistants must guess entity type, address, and hours from unstructured HTML.

  1. Add a JSON-LD script on the homepage.
  2. Use LocalBusiness with name, address, telephone, and url.
  3. Validate with a schema markup tester.
warning
Opening hours

Hours are missing or not in an extractable HTML/schema form.

More details

Hurts: Gemini, ChatGPT

Fix: Duplicate hours as text on Contact and Homepage; keep one source of truth.

Opening hours are a top AI question. Unstructured or image-only hours are hard to extract reliably.

  1. Publish hours as an HTML table on Contact/Home.
  2. Mirror them in schema openingHoursSpecification.
  3. Keep one source of truth — no PDF vs footer conflicts.
warning
Facts in PDF/images

Important hours/prices/menu facts appear locked in PDFs or images.

More details

Hurts: ChatGPT, Gemini, Copilot, Grok, Claude

Fix: Duplicate hours/prices/menu as HTML text on crawlable pages.

  1. Duplicate PDF/menu facts as HTML text on Contact or Menu pages.
  2. Keep alt text descriptive, but do not rely on images as the only source of hours/prices.
  3. Link the HTML version prominently from the homepage.
warning
Canonical mismatch

Canonical host differs from the fetched URL (e.g. www vs non-www).

More details

Fix: Align canonical tags with the preferred host and redirect the other.

info
Key pages hard to discover

We crawled 18 pages, but Contact and Menu are weakly linked — easy for a shallow follow of links to miss those facts.

More details

Fix: Link Contact and Menu clearly from the homepage and main nav.

Help yourself become visible to AI

Details we couldn’t verify on the site — clients fill these in on the real report:

Paste your URL above to start.

Honest results

Clearer for AI — not a citation promise

Better structure and crawlability help assistants describe your business accurately. We can not guarantee citations, rankings, or that an assistant will mention your business.

FAQ