For sites built with AI
Built your site with AI? Check whether Google and AI can see it and what its security looks like from outside.
Lovable, Bolt, v0, Cursor, Replit, Framer and other AI tools help you launch a site in a few hours. But they rarely check whether Google and ChatGPT can see your text at all, whether strangers can misuse your site and whether visitor tracking starts before people say yes. Enter the address, and in a couple of minutes you will know.
- What we measure
- Whether the home page text and main heading are there as soon as a robot opens the page. Or whether the robot sees an empty page, because the text only appears after the browser runs the site's scripts.
- Why it matters
- Many AI robots and some search engines do not run a site's scripts. Then they cannot see your text and cannot show or recommend you.
- Possible statuses
- OKwarningerror
- In the report you see
- The status, the value measured on your site and one sentence on what to do.
This is what one check looks like from the inside. It shows the structure, not any specific result.
What is worth checking on a site built by AI
AI makes a site that works in your browser. But Google, ChatGPT and your visitors may see it differently. We check these things in every base audit.
Robots see an empty page
Many AI tools make a site whose text only appears after it loads in the browser. ChatGPT and other AI robots, and sometimes search engines too, do not wait for that and see an empty page. We check whether your text and heading are there straight away.In the report: Content visible without JavaScript
One name for every page
Each page has a name and a short description that people see in Google results. On every page we crawl we check that they are there, that the length is sensible and that the pages do not all share the same one. A name left over from the template gets a warning.In the report: Page title 30–60 characters Meta description 70–160 characters Titles on every checked page Meta descriptions on every checked page Unique page titles (sample)
The site is still hidden from Google
Sites are often hidden from search engines while they are being built, and then nobody remembers to open them up. Google then does not show you. We check every place such a block can be left behind.In the report: Homepage is not set to noindex robots.txt exists robots.txt does not block the site
Google does not know which pages you have
A list of your pages helps Google find all of them sooner. We check that the list exists, that its addresses open and that Google can find it.In the report: Valid XML sitemap Valid sitemap Sitemap URLs load Sitemap listed in robots.txt
Basic protection
We check whether the browser knows how to protect your site: that it cannot be embedded in someone else's page to trick visitors, that foreign code cannot be slipped into it and that the connection is always encrypted.In the report: HSTS header Content-Security-Policy X-Content-Type-Options Clickjacking protection Referrer-Policy Permissions-Policy Valid SSL certificate No mixed content (http resources on an https page)
Visible software versions
If the site shows from the outside which software and versions it runs, it is easier to find for anyone looking for old, known bugs. We check whether versions are visible and whether they have known security bugs. We show the details only to the site owner.In the report: Software version not disclosed Versions without publicly known vulnerabilities
Cookies and privacy
If the site has visitor statistics or ads, we check that there is a cookie banner, that tracking waits until the visitor has chosen and that there is a privacy policy.In the report: Cookie consent banner Tracking before consent Cookies before consent Privacy policy
Can people contact you?
Whether the site has a contact form and a visible phone number or e-mail. We never submit anything in forms.In the report: Contact or enquiry form present Phone or e-mail visible
A slow site on mobile
Google PageSpeed measures how fast the site opens on mobile and desktop. The report shows what slows it down the most.In the report: Largest Contentful Paint (LCP) Responsiveness (INP, real-user data) Layout stability (CLS) Blocking time during load (TBT, lab measurement)
Broken links
Links to your own pages that do not exist, and links to other sites that no longer open.In the report: No broken internal links (sample) Links to other sites work
Is ChatGPT allowed to read your site?
We check whether your site lets ChatGPT, Claude, Perplexity and Google robots read it, and whether a protection system stops them. If they are not allowed in, AI assistants cannot recommend you.In the report: AI search engines may read the site AI search engines can reach the site llms.txt file (for information)
Google does not know who you are
We check whether the site describes your business in a way Google and AI can understand: who you are and what you offer. And whether a link shared on Facebook or WhatsApp shows a picture and a title, and whether the browser tab shows your icon.In the report: Structured data (schema.org) Business structured data (Organization / LocalBusiness / Product) Open Graph tags for sharing Favicon present
The base audit crawls up to 5 pages of your site, not just the home page. The full list of checks is on the home page.
Problems
What goes unnoticed on a site built by AI
Your AI tool shows that the site works in your browser. It rarely shows what a visitor, Google or someone looking for weak spots sees from the outside. These are the things we look for.
We checked 1 008 sites built with AI
Real, publicly launched sites built with Lovable, Bolt, v0 and similar tools. The most common problems:
- 99% of sites
The browser gets no security instructions
If someone tries to embed your site or slip foreign code into it, the browser has no instructions to stop it.
- 64% of sites
AI robots may not see your site
They see an empty page instead of your text, because the text only appears after the page loads in a browser.
- 63% of sites
Google does not know who you are and what you offer
The site has no description that search engines and AI can read, so it is harder for them to understand who you are.
A secret key anyone can read
AI tools tend to put a secret key (for example Supabase, OpenAI or Stripe) straight into the site code that every visitor downloads. With it a stranger can spend money on your account or read the whole database. We never show or store the key, and we show what kind it is to the site owner only.In the report: Secret API keys in public JavaScript
Your data is guarded only by database settings
A Supabase or Firebase public key on the site is normal. But then your data is protected only by the database access rules. We cannot see them from the outside, so the report reminds you where to check them.In the report: Publishable keys (information)
All of your site's code is open
If development files were published together with the site, anyone can read the original code with its comments, sometimes with forgotten keys in it too.In the report: Publicly downloadable source maps
Passwords or code history can be downloaded
If an open settings file or the code history was left on the server, a stranger can download passwords, keys or all of the code. We only check this after you have confirmed the site is yours.In the report: Publicly reachable .env file Publicly reachable .git folder
“Lovable App” and Lorem ipsum
The tool's default name, description, placeholder text or an example.com e-mail. In Google and on social networks the site then looks unfinished.In the report: Builder default texts and placeholders
A shared link without a picture
If the site sets no picture for sharing, a link on Facebook, LinkedIn, WhatsApp or Slack looks empty or shows the tool's default image.In the report: Link preview (OG image, favicon)
Other sites can read your site's data
If your site's server answers any other site, that site can read the answers. Fine for public information, not for user data.In the report: API openness to other sites (CORS)
A form without spam protection
A public form without an “I am not a robot” check or another limit fills up with spam fast. We only look at what the browser sees.In the report: Form protection against spam
And what keeps you from noticing it yourself
“The AI says everything is fine”
It checks the code it wrote, in your browser. We open the public site from the outside: as a robot that does not run scripts sees it and as a real browser does.
“The speed test is green, but Google cannot find me”
A speed test rates one page. It does not look for secret keys in the site code and does not walk the subpages to see whether they all share one name.
“I do not know what to ask my AI”
Each finding comes with a sentence on what to do, written so you can paste it into Lovable, Bolt or Cursor.
“A client asks whether the site is safe”
You can forward the PDF report to a client or a developer. It is a risk check from the outside, not a penetration test, and it says so.
How it works
- Enter the address.A public address anyone can open. No access to your code, account or database is needed.
- We measure.We open the site twice: as a robot that does not run scripts sees it and as a real browser does. Google PageSpeed measures speed. You see every finished step on screen.
- Get your to-do list.For every finding: what was measured, why it matters and what to do. We e-mail you the PDF.
Fixes
A fix list you can hand to your AI
You already work with AI. So the report is written to be passed on: to a person or to your AI tool.
In the base report today
One finding is explained in full, with a sentence on what to do (for the rest, that is in a paid audit). You can paste it into the Lovable, Bolt, v0 or Cursor chat as a task. For example, for the check “Content visible without JavaScript”:
Make sure the main text and H1 are already in the server HTML (server-side rendering or a static page), not only after JavaScript loads.
After the fix, run the audit again and check whether the status changed.
Fix kit for a coding agent
A ZIP file with a README.md and one task per finding: what is wrong, what to change, how to check it and how to undo it. Open it in Claude Code, Cursor or another AI tool together with your site's code.
# task for the agent, from the kit README
Read README.md. Work through the files in the “Work order” list one at a time. Before each file, show what you will change and wait for my approval.
The fix kit is included in every paid audit (from Mini). Security findings are in it only if you have confirmed that the site is yours.
Pricing
Start with the free audit
The base audit shows what needs fixing. A paid audit tells you how to do it, step by step, with priorities and time estimates. You see the price before you pay.
For testers
Vibe coder price: Mini
Regular price €35.09 VAT incl.
Places left: 30 of 30. When they run out, the same code gives €19.90 (VAT incl.).
The code VIBECODER2026 is applied at checkout automatically when you start the free audit on this page.
One-off payment, no subscription. You order the full report from the free audit result.
Start with the free auditBase audit
free, no strings attached
- Speed on mobile and desktop (Google PageSpeed)
- Around 90 checks, up to 5 pages
- Overall score 0–100 and a to-do list ranked by impact
- Cookie check in three phases
- PDF report by e-mail
Paid audit: Mini, PRO, MAX, ULTRA
Mini €35.09 (incl. VAT; excl. VAT — from €29)
- Instructions for every finding, with priority and effort
- Rewritten titles and descriptions
- 30-day work calendar
The step-by-step instructions are written for WordPress, WooCommerce and PrestaShop. For sites made with Lovable, Bolt or another AI tool, they are general steps a developer or your AI will understand.
What exactly each plan includes →What people usually ask
Do you need access to my code or account?
No. We only read what any visitor or search engine can see. No code repository, no Lovable, Vercel or Supabase account and no password needed.
Does the audit change anything on my site?
No. We install nothing, do not log in and submit nothing in forms. In the cookie banner we only press “Accept” or “Reject”.
Do you check my code and database?
No. We cannot see your code, your database rules or anything only a signed-in user sees. This audit is not a penetration test. It shows what search engines, AI assistants and visitors see from the outside.
My site is not WordPress. Will the audit work?
Yes. The measurements and checks work for any public website, including one made with Lovable, Bolt, v0 or Webflow. In a paid audit the step-by-step instructions are written for WordPress, WooCommerce and PrestaShop. For other systems they are general steps.
Does the AI make up numbers?
No. All numbers come from measurements: Google PageSpeed and our own checks. AI only explains and suggests an order, and its text is labelled. If a metric could not be measured, you will see “not available”.
Why can I not see the security details?
We show them only to the site owner. Once you confirm the site is yours, you will see everything we found.
What do you do with my data?
We use your contact details to send the report, and for news if you agreed to that. We do not store your IP address with the audit, only a one-way checksum of it to limit excessive use. Only the security log records the address itself, temporarily, to prevent abuse, and those entries are deleted after 30 days. The rest of the data is kept for up to 12 months, and you can ask for it to be deleted at any time.
I do not want my site to be scanned. What can I do?
Add the lines User-agent: DigifyScopeBot and Disallow: / to your robots.txt. To keep the site from being scanned when someone else requests an audit (DigifyScopeAudit) as well, write to info@digifyscope.com with the domain. More on our robot page.
Enter an address. In two minutes you will know what the AI forgot.
You get an overall score from 0 to 100 with a grade from A to E, a to-do list ranked by impact and a PDF report you can forward to your developer or your AI.