Check your website.
Type your address and I’ll check the basics Google and your customers notice. Free, no email asked for.
What I check
24 checks in 6 groupsEach one is something a visitor or a search engine runs into on a real page. Every result says what I found, why it matters and, where something needs doing, what the fix is.
Can Google find you?
The settings that decide whether Google can list your homepage, and what it shows when it does.
Google is allowed to list the page
One "noindex" instruction tells Google to leave the page out of its results altogether. It's often left switched on by mistake after a site is built.
Page title
The title is usually the blue link people click in Google. One that says what you do and where earns more clicks than "Home".
Your robots.txt file
This small file tells search engines where they may go. One wrong line can ask Google not to look at anything.
Page description
It's often the two lines under your link in Google, so it works like a free advert for the page.
Canonical tag
It tells Google which address is the real one for this page. A wrong one, often left over from a test site, can quietly push the page out of search.
Business details for Google
Structured data spells out your name, address and phone number in a form Google can read, which can help it show your details in local results. Google doesn't promise to use it.
XML sitemap
A sitemap lists your pages so Google can find them all. Google says small, well-linked sites may not need one, so this is a nice-to-have.
Can customers get in touch?
Whether someone who likes what they see can call or message you straight away.
Tap-to-call phone number
Most local searches happen on phones. If your number can't be tapped, people have to copy it by hand, and some won't bother.
A clear way to get in touch
A site's job is to turn visitors into enquiries. If there's no obvious way to get in touch from the homepage, some people will simply leave.
Does it work well on a phone?
Most people looking for a local business are on a phone, so the page has to fit and hold still.
Set up for phone screens
Without a viewport tag, phones show a shrunken desktop page that's hard to read. Blocking zoom makes life harder for anyone who needs bigger text.
Images with a set size
When images have no size set, the text jumps about as they load and people tap the wrong thing. It's one of the most common causes of a jumpy page.
Is it quick to load?
How long the page takes to arrive, and what makes the browser wait before it shows anything.
Server response time
A slow server holds up everything else on the page. On a phone, that wait is often when people give up and go back to Google.
Size of the page's code
A heavy page takes longer to arrive on mobile data. Google also stops reading a page's code after the first 2 MB.
Files that hold up the first view
Each script or stylesheet loaded this way makes the browser wait before it shows anything, so the screen stays blank for longer on a phone.
Trust and the law
Things visitors notice without thinking, and a few basics for UK businesses. None of this is legal advice.
Secure connection (HTTPS)
Browsers warn visitors when a page isn't secure, which puts people off before they read anything. Google also prefers the secure address when it chooses which one to show.
Tracking and cookie consent
Advertising pixels need visitors' consent under the UK's PECR rules, and the ICO says advertising is never covered by the exceptions. For analytics, what's needed depends on how it's set up. Tracking scripts also slow a page down.
One address, with or without www
If the www and plain versions both load on their own, Google sees two copies of the site and has to pick one. Each extra redirect also adds a little wait on a phone.
Company details for a limited company
UK limited companies must show their registered number, where they're registered and their registered office address on their website. It's also a quiet sign that a real business is behind the site.
Copyright year
A footer with an old year can make visitors wonder whether the business is still trading. There's no official rule on this.
Site icon
The small icon in browser tabs and next to your result in Google. Without one, the site can look unfinished.
Preview when the link is shared
When someone shares your link on WhatsApp, Facebook or LinkedIn, these tags set the picture and title in the preview. Without them you can get a blank or random card.
Accessibility basics
A few basics that help people using screen readers and other assistive technology. This isn't a full accessibility audit.
Image descriptions (alt text)
Blind and partially sighted visitors hear nothing useful about an image without a description. Google also uses alt text to understand images.
Page language
Screen readers use it to pronounce your words properly. It's one of the most basic accessibility requirements.
Main heading
A clear main heading tells visitors and screen readers what the page is about. Google says the number of headings doesn't affect ranking, so this is about clarity.
What it cannot tell you
A quick check is useful because it is quick. Here is what it leaves out.
One page, usually your homepage
It reads the page you give it, plus the robots.txt and sitemap files that tell search engines what to read. The rest of your site isn’t opened.
Only the code your server sends
It sees the page the way Google first does. Anything added to the page after it loads isn’t seen.
No scripts are run
Nothing on your page is run or clicked, so forms, pop-ups and anything that loads later go untested.
Response time is measured from London
Once, from my server in London. Your visitors are elsewhere, on other connections, so treat it as a rough guide.
Not an accessibility audit
It checks a few basics a machine can spot. A real audit needs a person working through the site with a keyboard and a screen reader.
Not legal advice
Where it mentions trackers, cookies or company details, it is pointing at something worth checking, not giving a ruling.
StartBuilding
Tell me what you are building. You get a straight answer: whether I am the right person for it, what it would cost, and how long it would take. If I am not, I will say so and point you somewhere better.
What Mia, Omur, Jason and Linda said
- You send the details
What you are building, roughly when you need it, and the budget range. A paragraph is plenty.
- I reply within a day
A straight yes or no, a realistic timeline, and anything I would change about the plan before we start.
- Fixed price up front
Agreed before any work begins. No hourly billing, no scope creep, and the source is yours at the end.