Why your AI-built site doesn’t show up in search
Single-page apps ship an empty HTML shell and fill it with JavaScript. Some crawlers wait for that, some don’t, and many sites also block themselves by accident. We load your page both ways and tell you what search engines and AI assistants actually get.
Free, no sign-up. The basic check makes only the requests an ordinary browser would.
What we check
- HighFree check
The site tells search engines to go away
A leftover noindex, or a robots.txt that blocks everything — the most common reason a new site never appears.
- MediumFree check
Missing title and description
Checked in the raw HTML and in the page rendered by a real browser, so you know which one is missing them.
- LowFree check
No sitemap, canonical or language
The basics that help search engines find every page and understand which version is the main one.
- LowFree check
AI assistants blocked or uninformed
Whether robots.txt blocks AI crawlers and whether you have an llms.txt that tells assistants what the site is.
Check it yourself
Five checks that explain most “my site isn’t on Google” cases. Each takes a minute.
Read the raw HTML
Put view-source: in front of your URL. Look for <title>, <meta name="description"> and <link rel="canonical">. If they only appear after JavaScript runs, many crawlers and every link preview miss them.
view-source:https://your-site.example
Look for a stray noindex
Search the raw HTML for noindex, and check the response headers too — some hosts add it to preview deployments.
curl -sI https://your-site.example | grep -i x-robots-tag
Open robots.txt
A single “Disallow: /” under “User-agent: *” blocks every search engine. It should also point to your sitemap.
https://your-site.example/robots.txt
See the page as Google does
Google Search Console → URL Inspection → Test live URL → View tested page. The screenshot and the rendered HTML show what Google actually got.
Submit your sitemap
In Search Console → Sitemaps, add /sitemap.xml. If you don’t have one, ask your AI builder to generate it from your routes.
Fixes your AI builder can make
Most of these are a few lines in index.html or a generated file. The report’s prompt says which.
Fix these issues on myapp.example. 1. robots.txt contains "Disallow: /". Allow crawling and add: Sitemap: https://myapp.example/sitemap.xml 2. No meta description in the server HTML. Add a description and Open Graph tags to index.html so they exist before JavaScript runs. When done, re-check: https://scanyoursite.app/en?check=myapp.example
One deploy can deindex you
A noindex copied from a staging build can remove you from search in days. With Pro we catch it on the next check.
See plansQuestions
Does Google render JavaScript?
Mostly, with a delay — but link previews, many other crawlers and some AI assistants read only the raw HTML. Putting the title and description there helps everywhere.
Is this a full SEO audit?
It is the technical basics that decide whether you can be found at all — not keyword research or content advice.
What is llms.txt?
A short text file that tells AI assistants what your site is and which pages matter. It is optional; we note when it is missing.
Paste your URL. Get the list in about a minute.
Every finding comes with what it means for you and how to fix it — or a prompt your AI coding tool can apply.
Free, no sign-up. The basic check makes only the requests an ordinary browser would.