See where your site loses visitors before checkout
Paste your link. A real phone browser maps every flow it can reach from your home page and records each one. Free: your score in 5 areas, every serious issue by title, the smaller ones counted by theme, and one fix ready to paste. $20, once: every fix ready to paste and the recording of every flow.
Advanced: where your visitor comes from · Automatic
By default we infer your most likely visitor from the landing page. Tell us where the visitor really comes from and the check enters through that page and tests whether it delivers what was promised. Up to 3 origins per check.
No card to start. The test takes 4 to 14 minutes; you can watch it work or leave, and we email you the link.
People visit. Few reach the pay button. Analytics won't tell you why.
Site Check walks the path from your landing page to your checkout, on a phone, and shows the step where it breaks: the screenshot, the words that caused it, and the fix ready to paste.
A phone-sized browser maps every flow it can reach
Real Chromium at 390×844. From your home page it follows the menu, the buttons, the footer and your sitemap, and records each flow: up to 12 flows, 4 taps deep, 40 screens. Pages that share a template are walked once. It never submits a form, signs in or pays.
Fixed checks run on every page
Security headers, layout at 360, 768, 1366 px, technical SEO and AI-crawler access.
Free: the work, and one fix
Scores, every serious issue by title and the smaller ones counted by theme, the screenshots of the path, and one fix ready to paste.
$20: every fix, ready to paste
Headers, tags, CSS and rewritten text to copy, all in one file, plus the recording. Refund in one click.
Five areas. Open one to see what is checked, how, and what is not.
Flow & UXCan your visitor get from the landing page to checkout?
- What we check
- Whether a first-time visitor on a phone can tell what you sell and what to do next from the first screen
- Every flow a visitor can walk by tapping from your home page: each call-to-action button, each item of the main menu and the links that matter, to the end of the line (a form, the payment step, a sign-in or a dead end). A flow is named after what is at its end: purchase, sign-up, contact or content
- Paths to buy and sign up come first and get the videos; documentation, blog and support are walked as sampled content branches and judged as what they are, not as sales pages
- Pages that are in your sitemap but that no link on a walked screen leads to: they are listed as not linked from your navigation, not as flows
- The limits of one check: up to 12 flows on video, 4 taps deep, 40 screens; pages that share a template (blog posts, product pages) are walked once, and the report says how many flows exist and which ones have no video
- How long each page took to load, which prices and form fields show up, and where the path stops
- How we check it
- A real Chromium browser, sized like an iPhone (390×844), opens your home page, reads every link on it and builds the map of your flows. Then it walks each flow the way a visitor would, tapping the links, with one recording per flow and a screenshot of each screen.
- An AI model works out your most likely visitor from the words on your site, then reviews each flow as that person, judging each page by its type (sale, pricing, sign-up, checkout, docs, legal, support, content). Every AI finding has to quote text that is really on your page; findings without a matching quote are thrown away, and “high” is kept only for what blocks or diverts a path to buy or sign up.
- Every ready-to-paste text the AI writes is checked by code before it reaches you: language of that page, no number or promise your site does not state, no leftover brackets, more than a one-word change. A missing fact is left as a marked [FILL IN] gap; a text that fails is dropped.
- Load times, missing prices, long forms and buttons that lead nowhere are measured by code, not by AI.
- Every action on every page is logged with its time. The report shows that log page by page.
- What we don't check
- Anything behind a login or after the pay button: we never submit forms, create accounts or enter payment details
- Your real conversion rates: we see your pages, not your analytics
- Visual polish: the AI reads the text, buttons and form fields of each screen, not your colors or images
- Load time on a real phone network: ours is measured from a data center
Security (passive)What any browser can see about how your site protects visitors.
- What we check
- HTTPS on your home page, and whether the http:// address redirects to it
- Security headers: HSTS, Content-Security-Policy, X-Content-Type-Options, clickjacking protection, Referrer-Policy
- Flags on the cookies your home page sets (Secure, HttpOnly, SameSite)
- Mixed content, forms that post over plain http, and server version banners
- On the other pages of the path (pricing, sign-up): HTTPS, forms, mixed content and framing protection
- How we check it
- One ordinary request to your home page over https and one over http, the same thing any browser sends. We read the response headers, the cookies and the HTML. Nothing is typed into or sent through your forms.
- On the other pages of the path we read what the test browser received when it loaded each one. No extra requests are made.
- What we don't check
- This is not a penetration test: we don't probe for vulnerabilities, guess passwords, scan ports or look for hidden files
- Cookies and the http redirect on pages other than the home page, pages outside the path we walked, and anything behind a login
- Your server, your code and your dependencies
ResponsivenessDoes the layout hold at phone, tablet and laptop widths?
- What we check
- Sideways scrolling on your home page at 360, 768, 1366 px wide
- The viewport meta tag
- Links and buttons smaller than 40 px in the first two screens, at the touch widths (phone and tablet). At laptop width they are measured and shown, but not counted: a mouse pointer does not need a 40 px target
- Text smaller than 12 px, and images or tables wider than the screen
- Sideways scrolling and small tap targets (3 or more under 40 px) at phone width on every page of the path
- How we check it
- Chromium opens your home page at 3 widths (360, 768, 1366 px). At each one the page measures its own width, tap targets and font sizes, and we keep a screenshot.
- What we don't check
- Tablet and laptop widths on pages other than the home page (those are measured at phone width only)
- Real devices, landscape orientation and browsers other than Chromium
- Menus, modals and other states that only appear after a tap
SEO (technical)Can search engines find, read and index your pages?
- What we check
- robots.txt, sitemap and whether your pages can be indexed
- Titles, descriptions, headings and canonical tags on a sample of your pages
- Structured data (schema.org) and server response time
- How we check it
- Our server reads your robots.txt, your sitemap and a sample of your pages over plain HTTP (no browser, no AI) and runs a fixed list of checks. Structured data is validated with the public schema.org validator.
- What we don't check
- Your rankings, backlinks and keywords
- What Google has already indexed (that needs your Search Console)
- Core Web Vitals
GEO (AI visibility)Can AI assistants reach and understand your site?
- What we check
- Whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) are allowed by your robots.txt and get an answer from your server
- llms.txt and the structured data assistants rely on
- How much of your text is in the raw HTML, where crawlers that don't run JavaScript can read it
- How we check it
- Our server requests your home page with each AI crawler's user-agent and reads robots.txt, llms.txt and the raw HTML of a sample of pages. No AI model is involved in these checks.
- What we don't check
- Whether assistants actually mention or cite you: this check does not ask ChatGPT, Claude or Perplexity anything
- Text that only appears after JavaScript runs in a real browser
$20, once. After you've seen the results.
- The test runs in full before you pay anything. The scores, the list of issues, the path and one ready-to-paste fix are yours either way.
- One payment by card unlocks the full report and the recording for that check. No subscription.
- The charge shows as GVO on your statement.
Refund in one click
- Every paid report has a Get a refund button, for 30 days. You don't talk to anyone; telling us why is optional.
- The money goes back to your card through Stripe, and the report and recording for that check close.
- Rather have it fixed? Ask for adjustments sends your request to the team, and a person reviews the report.
Why not just ask Claude or another AI assistant?
You can, and for a quick opinion on a page it works well. If you already have an assistant that can drive a browser, you can build most of this yourself.
What you get here is the test already set up: a real browser at phone size that taps through to your checkout, a recording and a screenshot of every step, the same fixed checks for security headers, layout at 3 widths, SEO and AI-crawler access every time, and one report that says how each thing was checked and what was not.
It is a product built for this one job, and we improve the checks with every run. It does not replace a designer, a security audit or your analytics, and it does not promise more sales.
Who is behind this
The FarejaLeads team. We build tools to find and understand customers, and Site Check uses the same browser and checks we run on our own sites. The check itself is automated: a browser and an AI model, no person in the loop. When you ask for adjustments on a paid report, a person on the team reads your request and reviews the report.