Can search engines understand the basics?
Page titles, meta descriptions and canonical-link presence.
What this doesn’t establish
These checks do not measure keyword positions, index coverage or traffic.
Know what’s being checked.
A practical review starts with a clear scope. Here is what our early-access audit looks for, and where further testing is needed.
A focused first look at your website
The current audit inspects the HTML and response headers of the page you submit, then up to four eligible links from that page on the same website. It does not crawl every page or render JavaScript. Pages that cannot be inspected are noted where possible.
The report applies 17 defined checks per page across seven categories. Each result records what was observed. Your free preview shows the overall score; purchasing unlocks the category breakdown and findings for that saved scan.
Are essential source signals in place?
Image alt-attribute presence and the declared document language.
What this doesn’t establish
This is not a WCAG audit. Alt-text quality, keyboard access and colour contrast need separate review.
Are pages responding as expected?
HTTP response status, HTML payload size and an observed request duration.
What this doesn’t establish
Request duration includes DNS and downloading. It is not a Core Web Vitals or Lighthouse measurement.
Are basic web protections visible?
HTTPS, Content-Security-Policy presence and the nosniff response header.
What this doesn’t establish
This is not penetration testing, malware scanning or a guarantee that the website is secure.
Does the page have a clear foundation?
H1 heading count and an approximate source-text word count.
What this doesn’t establish
Word count is a simple review signal, not a Google ranking target or a judgement of writing quality.
Is there a recognisable next step?
Contact-link patterns and common action words in page text.
What this doesn’t establish
These are source signals. We do not measure enquiries, sales, form delivery or conversion rates.
Does the source suggest a responsive setup?
Viewport metadata and stylesheet or media-query signals.
What this doesn’t establish
The scan does not render the layout. A mobile device test is still needed.
Which websites can be checked?
Public HTML pages on WordPress, Shopify, Webflow and custom-built sites can be inspected. Compatibility depends on what the website serves to an automated request. A website built mainly with browser-side JavaScript may expose little content to this scan.
A starting point for improvements
Some findings identify a clear omission; others are prompts to investigate. A missing Content Security Policy, for example, calls for a developer’s review rather than copying a policy from another website. Use the evidence to decide what is appropriate for your site.
Read the scoring methodology →START WITH A CLEARER PICTURE
Check my website What could your website do better?
Get your overall score for free. Explore the full report when you’re ready.