Website check
What this check does and does not see
The check fetches your page once, the way a search engine does: the HTML as your server delivers it. That is exactly where the boundary lies, and it is worth knowing before you read the results.
What we measure
- How your page appears in search results: title, description, canonical
- Whether search engines can reach it: robots.txt, sitemap, redirects, noindex
- How it looks when someone shares it on LinkedIn or WhatsApp
- Your structured data (schema.org), including the required fields
- How fast your page loads for real visitors, from the Chrome UX Report by Google
- Accessibility as far as it lives in the HTML: alt texts, labels, button names, viewport, tab order
What we deliberately do not do
- Execute JavaScript — whatever your page builds in the browser stays invisible to us
- Judge colour contrast or focus order: that needs a real browser
- Run our own load test in a simulated browser: we only read what Chrome already measured at your visitors
- Click any further than this one page
That distinction is not a hedge. For accessibility, "we found nothing" is something quite different from "this page is accessible": half of the guidelines are about things that only exist once the page is rendered. So we name what we measured, rather than what would be fine. One thing does leave our server along the way: for the speed figures we look the address up at Google. These are public pages and the figures come from there, but you should know it happens.
Want to go further? For accessibility, a test with a real screen reader is irreplaceable, and if your site has too few visitors for the speed figures, Google PageSpeed Insights runs a lab test that works without them.
Enter a web address and see at a glance whether a search engine can reach, understand and present your page properly. We check redirects, your robots.txt, your sitemap, the title and description as they appear in search results, the share preview on LinkedIn and WhatsApp, your structured data, and the accessibility points that can be read from the HTML itself. Every finding comes with what it means and what to do about it — no scores without explanation.
What people use this for
- Find out why a page does not appear in Google: noindex, robots.txt or canonical
- See how your title and description get cut off in search results
- Check whether your JSON-LD holds the fields Google needs for rich results
What others think of this tool
No reviews for this tool yet. Yours would be the first.
Do you work with Westcube?
Leave a review on Google tooFrequently asked questions
Can you tell whether my page is in Google?
No, and be sceptical of tools claiming otherwise. A page's index status is only available through Search Console or Bing Webmaster Tools, which require domain ownership. What we check is whether anything is in the way: a noindex, a robots.txt block, a canonical pointing elsewhere. We also prepare a search link you can run yourself — that is the honest answer.
Why measure the title in pixels rather than characters?
Because Google truncates by pixels. A 60-character title in capitals is considerably wider than 60 characters in lower case, so it does not fit even though a character counter says it does. Our pixel figure is an approximation based on letter widths — enough to know whether it fits.
Do you check my whole site?
No, exactly one page. A tool that walks through someone else's entire site is no longer a check but a crawler, sending anonymous traffic to third-party servers. To review several pages, enter them one at a time.
How does this differ from the AI visibility check?
This check looks at classic search engines: Google and Bing. The AI visibility check looks at whether ChatGPT, Claude and Perplexity may and can read your site — different bots, different rules, different pitfalls. They overlap partly, but the conclusions differ.
Do you store the address I enter?
No. We fetch the page, run the checks and show the result. That result stays in memory for fifteen minutes so repeated checks do not keep sending traffic to your server; after that it is gone. No database involved.