Can AI crawlers read your app, or just an empty shell?
Many apps built with Lovable, Bolt, v0 and similar tools render everything in the browser. Many crawlers do not run JavaScript, so they may see only a title and an empty div.
Only scan apps you own or have permission to scan.
How to tell
Open your live homepage and use View Source (Ctrl+U or Cmd+Option+U), not Inspect. Inspect shows the page after JavaScript has run. View Source shows the raw HTML a crawler gets first.
Look for real text in that raw HTML: your headline, a few sentences about what the app does, headings, and a meta description. If all you find is a <div id="root"></div> and a script tag, a crawler that does not run JavaScript sees an empty page.
Google can run JavaScript, but it may do so later and with limits, so pages that depend on it can take longer to show up or show up with less text. Many AI crawlers fetch only the raw HTML.
What the free scan checks
- Content in the raw HTML
We count the words of server-rendered text on your homepage and look for question headings or an FAQ. A JavaScript-only shell scores 0 here, and we say so plainly.
- Title, description and headings
A real <title>, a meta description of sensible length, exactly one H1 and H2 sections, all in the HTML a crawler gets.
- Open Graph, JSON-LD and canonical
og:title, og:description and og:image tags, valid schema.org JSON-LD, and a canonical link.
- robots.txt, sitemap and llms.txt
Whether GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot and Google-Extended are allowed, whether your sitemap returns a real list of URLs, and whether /llms.txt exists.
What helps
- Render public pages on the server. Use server-side or static rendering (prerendering) for the homepage and key public pages, so the HTML already holds the text. The logged-in app can stay as it is.
- Write a real title and meta description. Say what the app does in plain words, not "Vite + React" or your project code name.
- Put an H1 and headings in the HTML. One H1 for the page and H2 sections for the main parts.
- Add Open Graph tags. og:title, og:description and og:image, so shared links and crawlers get a clear summary.
- Add JSON-LD. A small schema.org block, for example Organization, WebSite or Product, describing the app.
- Set a canonical URL. One <link rel="canonical"> per page that points at its main address.
- Publish sitemap.xml and a short llms.txt. List your public pages in a sitemap, name it in robots.txt, and add a plain-text /llms.txt that explains the app in a few lines.
FAQ
- Does this hurt Google?
- It can. Google may delay or limit indexing of pages that need JavaScript to show their content. We can't promise any ranking or AI answer outcome; making the text readable just removes one common blocker.
- Do I need to rewrite my app?
- No. Prerender the public pages (homepage, pricing, guides). The parts behind a login can stay client-rendered.
- What does the /geo score look at?
- The raw HTML a crawler gets for your homepage, plus /robots.txt, /llms.txt and your sitemap. Eleven checks, 100 points. It never changes your security score.
- Does the check touch my site?
- It is passive. It makes a few ordinary GET requests and sends no exploit payloads.
- Do I need to sign up?
- No. Paste your link, confirm it's your app (or you have permission), and run it. Adding your email is optional and shows the risk breakdown and one problem by name.
- What does it cost?
- The scan and your score are free. The full list of findings with a fix for each is a one-time $9, or $29 for a pack of 10 reports.