---
title: "A website check you can do yourself in an afternoon"
description: "Run a website audit yourself in one afternoon with free Google tools. Check indexing, your Business Profile, phone and forms first, then speed."
url: "https://webleveling.com/blog/website-check-you-can-do-in-an-afternoon/"
lang: "en"
published: "2026-10-07"
modified: "2026-10-07"
author: "Cal Hewitt"
tags: ["seo","website-maintenance","small-business"]
image: "https://webleveling.com/og/blog-website-check-you-can-do-in-an-afternoon.jpg"
alternates:
  es: "https://webleveling.com/es/blog/revision-del-sitio-web-en-una-tarde.md"
---

# A website check you can do yourself in an afternoon

Run a website audit yourself in one afternoon with free Google tools. Check indexing, your Business Profile, phone and forms first, then speed.

![A closed notebook, a pencil and a small stopwatch laid out on a wooden desk.](https://webleveling.com/blog/website-check-you-can-do-in-an-afternoon/website-check-afternoon-featured.jpg)

You have a feeling the website is costing you calls. Maybe a customer said the form never answered, maybe a competitor sits above you on Google, or maybe the phone has been quiet and nobody can say why. A paid audit is not in the budget right now, and you do not want to learn a pile of tools just to find out what is wrong. This website audit checklist for small business owners fits into one afternoon, uses only free tools from the companies that make them, and puts the problems that cost you customers first. Each step tells you where to look and what the result means. By the end you will have a short repair list in the right order, and you will know which items are yours to fix and which belong to a developer.

**Key Takeaways**

**Start with the customer path**

Tap your phone number, send a test message through your contact form, and open your menu on a phone before you look at any score.

**Read "not indexed" before you worry**

Google says a page labeled not indexed is not necessarily a problem, because duplicates and pages left out on purpose can be legitimate.

**Match your Business Profile to your site**

Name, phone, hours and the website link should say the same thing in both places, and the website link must start with http:// or https://.

**Speed has two kinds of data**

PageSpeed Insights shows lab results from a test run and field data from real visitors over the previous 28 days, and they answer different questions.

**Fix in order of lost customers**

Anything that blocks a call or form comes first, wrong business details second, blocked pages third, and cosmetic changes last.

## Which checks come first, and what do they cost you?

All of the checks below cost nothing, and they run in a fixed order so the worst problems surface early. Work through them in one sitting with a notepad, a phone, and the login for your website, your Google Business Profile, and Search Console if you have one. Write every problem down as you find it. Do not fix anything yet, because you will sort the list at the end and some fixes belong to a developer.

![A closed notebook and a pencil lying beside a phone placed face down on a wooden desk.](https://webleveling.com/blog/website-check-you-can-do-in-an-afternoon/notebook-and-face-down-phone.jpg)

Keep a notepad open for the whole check and write problems down without fixing them yet.

The order follows one idea: a customer has to find you, reach you, and then be able to use the page. A site that Google cannot show, or a phone number that does not connect, loses the sale before design or speed matters. So, the afternoon runs in this sequence: reach, listing, index, speed, then extras.

1.  **Reach**: Test the phone number, the contact form and the menu on a real phone.
2.  **Listing**: Compare your Google Business Profile with your website.
3.  **Index**: Ask Search Console whether Google can find your key pages.
4.  **Speed**: Run your home page and main service page through PageSpeed Insights.
5.  **Extras**: Test structured data only if a search feature applies to you.
6.  **Sort**: Write the repair list in the order given near the end of this post.

## Can a customer actually reach you from a phone?

Begin on your phone, not your computer, because a phone is where a customer will test your site. Google says it uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking, so [the mobile version of your site](https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing) is the version that counts. Search your business name, open your website from the result, and then test the things that earn you money.

- **Tap the phone number**: It should open the dialer and reach your business. If the number is only text, or it dials the wrong line, write it down first.
- **Submit every important form**: Send a real test message through your contact or booking form. Then confirm the success message appeared, the email arrived in your inbox, and check the spam folder too. A thank-you message does not prove the message reached you.
- **Check the details on the page**: Read the business name, address, hours and service area as a stranger would.
- **Open every path a customer might use**: Try the main menu, service pages, booking links, map links and social links.
- **Rotate the phone and zoom in**: Turn the phone sideways, then zoom to 200 percent. Buttons and form fields should stay usable.
- **Look at your form fields**: Each field needs a visible label or instruction. The W3C recommends [labels for form controls](https://www.w3.org/WAI/tutorials/forms/labels/) and notes that placing labels above fields can reduce sideways scrolling on a phone.

If the form did not deliver, you have likely found your most expensive problem already. Our post on [a contact form that is not sending emails](https://webleveling.com/blog/contact-form-not-sending-emails/) walks through the usual causes. If you want to see whether form submissions are counted at all, Google Analytics has a [DebugView](https://support.google.com/analytics/answer/7201382) that shows events as they happen when debug mode is turned on.

## Is your Google Business Profile telling the same story as your website?

A customer often meets your business on Google before they ever see your site. So, the next check is your public Business Profile set side by side with your website and with the real business. Search for your business name on your phone, or open your profile from the Google account that manages it, and compare each item below.

- **Business name**: It should match the name on your signs, paperwork and website.
- **Address and map pin**: Both should be complete and accurate if customers visit you. If you serve customers at their homes and do not meet them at a shop, Google's guidance for service-area businesses is to hide the address.
- **Phone number**: It should connect to the right part of your business.
- **Hours**: They should match your website, including special hours for holidays.
- **Website link**: Tap it. The page should load. Google says the website address must include \`http://\` or \`https://\`, and that Googlebot must not be blocked from reaching it.
- **Category, services and service area**: They should describe what you actually do.

Google's own help pages on [adding or editing your business information](https://support.google.com/business/answer/3039617) say changes are made through "Edit profile" and may be reviewed before they appear, so a correction can take a while to show. Google also asks for accurate [hours, website, phone number and location](https://support.google.com/business/answer/7039811). Wrong hours and a dead website link are small jobs to fix, and they are the kind of problem that quietly sends customers elsewhere. If your listing is missing from the map altogether, see our post on [a business not showing on Google Maps](https://webleveling.com/blog/business-not-showing-on-google-maps/).

![A small brass key and a blank paper tag resting on a worn counter next to a closed appointment book.](https://webleveling.com/blog/website-check-you-can-do-in-an-afternoon/key-and-blank-tag-on-counter.jpg)

Your listing and your website should hand a customer the same answers.

## Does Google know your important pages exist?

Now ask Google directly. Search Console is the free tool Google provides for this, and it answers two separate questions. The URL Inspection tool looks at one page at a time. The Page Indexing report looks at all the pages Google knows about. If you have never set it up, our post on [setting up Search Console for a small business](https://webleveling.com/blog/google-search-console-setup-for-small-business/) covers the first steps.

Run URL Inspection on your home page and on your most important service page. According to Google's [URL Inspection help](https://support.google.com/webmasters/answer/12482179), it shows whether a specific page is indexed, which address Google selected as the canonical version, whether Google can crawl the page, and any indexing problems. Then open the Page Indexing report, which groups the pages Google knows about as indexed or not indexed.

Do not panic at the not-indexed group. Google's [indexing report help](https://support.google.com/webmasters/answer/7440203) says "Not indexed is not necessarily bad," because duplicate pages and pages left out on purpose can be legitimate. What matters is the reason Google gives for each page. A thank-you page, a login page or a duplicate of another page can sit there without hurting you. A main service page that is excluded is a different matter, and our post on [pages that are not indexed in Search Console](https://webleveling.com/blog/page-not-indexed-search-console/) explains the common reasons.

Two points help you read the results correctly:

- **Indexed is not the same as ranking**: Being in Google's index means a page is eligible to appear. It says nothing about whether the page will show up high or bring traffic.
- **A sitemap is not a command**: Submitting one does not force Google to crawl or index every address. Our post on [whether your website needs a sitemap and robots.txt](https://webleveling.com/blog/does-your-website-need-a-sitemap-and-robots-txt/) covers what each file does.

If an important page is blocked from crawling or carries a \`noindex\` instruction, write the page address on your list. That is often a setting inside your website platform, and sometimes it needs a developer.

## How do you read a PageSpeed result without chasing a perfect score?

PageSpeed Insights is Google's free speed tool. Enter your home page address, then your main service page, and read the mobile results first. The tool combines two kinds of data, and Google's [PageSpeed Insights documentation](https://developers.google.com/speed/docs/insights/v5/about) is the place to confirm what each one means.

The two kinds of PageSpeed data

| Kind of data | Where it comes from | What it tells you |
| --- | --- | --- |
| Lab data | A Lighthouse test run on the page when you press the button | A repeatable check you can compare before and after a change, with diagnostics that point to causes |
| Field data | Chrome UX Report data from real visitors over the previous 28 days | How the page has felt to actual visitors, shown for LCP, CLS and INP |

The three field measures are LCP, CLS and INP. Each one is explained on the tool's own page, and PageSpeed Insights shows its own ratings next to them, so use those ratings rather than a number from an article. Lab and field results can disagree because they answer different questions, so a good lab number does not prove your visitors had a good experience, and a weak one does not mean your site is unusable. A score by itself also does not tell you whether the site brings in calls.

Look at the diagnostics under the score. They name the likely causes, such as oversized images, code that blocks the page from displaying, or slow hosting. Image problems are often within an owner's reach. Hosting and code problems usually are not. Add what you find to the list and move on, because a perfect score is not the goal of this afternoon.

![A stopwatch lying beside a small stack of blank index cards on a gray tabletop.](https://webleveling.com/blog/website-check-you-can-do-in-an-afternoon/stopwatch-and-index-cards.jpg)

Speed numbers are clues about causes, and the cause is what you write down.

## Do you need to test structured data at all?

Structured data is extra code that tells search engines what a page is about, such as a business, a product or a set of questions and answers. Check it last, and only if a search feature applies to you. Google's [introduction to structured data](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) explains the supported features, and the free Rich Results Test checks whether your markup is valid and whether the page may be eligible for supported rich results.

Read a passing result carefully. Google says it does not guarantee that your structured data will show up in search results, and its [structured data policies](https://developers.google.com/search/docs/appearance/structured-data/sd-policies) say the same about valid markup. So, an error matters only when it affects a feature you intended to qualify for. If you see errors on a page and your site platform handles the markup for you, note it down for a developer rather than editing code yourself.

## What should you fix first, and who can fix it?

You now have a notepad full of problems, and not all of them deserve equal attention. Sort them with this order, which puts lost customers ahead of everything else.

Repair order for your afternoon list

| Order | Problem | Can an owner usually fix it? |
| --- | --- | --- |
| 1 | Anything that blocks a call, booking, purchase or form | Often, if it is a wrong number or link; a developer if the form code is at fault |
| 2 | Wrong business name, phone, address, hours or website link | Yes, in the Business Profile and the website text |
| 3 | Important pages blocked from crawling or marked noindex | Sometimes a platform setting; a developer for robots directives |
| 4 | Broken pages, broken forms, bad redirects, HTTPS failures, server errors | Rarely; these usually need a developer |
| 5 | Mobile layout that hides content or makes actions hard | Sometimes, through platform settings; otherwise a developer |
| 6 | Major speed causes such as oversized images or slow hosting | Images, yes; hosting and code, a developer |
| 7 | Structured data errors tied to a feature you want | A developer |
| 8 | Copy, menu and conversion improvements | Yes |

An owner can usually correct obvious text, hours, links and some content inside a website platform. Do those first, since many fixes are only words, hours, links or settings. Doing the free checks before you pay anyone means that if you do hire help, you can hand over a specific list instead of a vague worry.

## When is a problem too big to fix yourself?

Some items on your list need access or skills that sit beyond a settings page, and that is a reasonable place to stop. A developer is normally needed for server errors, DNS, HTTPS, redirects, robots directives, site templates, JavaScript failures, form-processing code, structured data setup and hosting configuration. Google's help on [troubleshooting crawling errors](https://developers.google.com/search/docs/crawling-indexing/troubleshoot-crawling-errors) shows how technical these can get.

When you bring in help, give that person your list, in order, with the page address and what you saw. Then ask which tools they used to confirm the fix. A good answer names the same free tools you just used: the page showing as indexed in URL Inspection, a clean PageSpeed or Rich Results result, a form test that reached an inbox. A fix you cannot check yourself is hard to trust.

A paid audit adds diagnosis across systems you cannot see into, such as server logs, analytics setup and email delivery, plus someone to carry out the repairs and keep watching afterward. It is worth paying for when your list points at server, redirect or template problems, or when many pages need testing together. It is not required for the first pass, because the afternoon check already finds the problems that cost the most. If your own list reads like the symptoms in our post on [signs your website is costing you customers](https://webleveling.com/blog/signs-your-website-is-costing-you-customers/), you are in the right place. If the site was built with an AI tool, see how to [check a website built with AI](https://webleveling.com/blog/check-a-website-built-with-ai/) for extra things to look at.

![A closed metal toolbox beside a blank work order pad on a clean workbench.](https://webleveling.com/blog/website-check-you-can-do-in-an-afternoon/toolbox-and-blank-work-order.jpg)

Hand a developer a specific list, and ask how they will confirm each fix.

**Quiz: Can you run your own website check?**

1. Google's help says a page listed as not indexed in Search Console is:
   - Always a serious error
   - Not necessarily a problem, since duplicates and pages left out on purpose can be legitimate **(correct answer)**
   - A sign your site was penalized
   - Proof the page will never rank
2. What does PageSpeed Insights field data show?
   - A lab test run on the page when you press the button
   - Real visitor data from the previous 28 days **(correct answer)**
   - Your Google ranking
   - Your conversion rate
3. Which problem belongs at the top of your repair list?
   - A slightly low speed score
   - A missing structured data tag
   - A phone number or contact form that does not work **(correct answer)**
   - A redesign idea for the footer

## Frequently Asked Questions About website audit checklist for small business

**How do I check my website for free?**

Use the free tools Google provides. Test your phone number and contact form on a phone, compare your Google Business Profile with your site, inspect key pages in Search Console, run PageSpeed Insights, and test structured data with the Rich Results Test only if it applies to you.

**How do I know if Google has indexed my website?**

Open the URL Inspection tool in Search Console and enter a page address. It shows whether that page is indexed, which canonical Google selected, and whether there are indexing problems. The Page Indexing report shows the same for all the pages Google knows about.

**Is a "not indexed" status always a problem?**

No. Google says a not-indexed status is not necessarily bad, because duplicates and pages excluded on purpose can be legitimate. Check the reason listed for each page, and look closely only at the pages you want customers to find.

**What does PageSpeed Insights measure?**

It combines Lighthouse lab testing with Chrome UX Report field data from real visitors over the previous 28 days. It reports LCP, CLS and INP plus diagnostics. Lab and field results answer different questions, so read both.

**What should I fix first on my website?**

Fix whatever stops a call, booking or form first, then wrong business details, then pages blocked from search, then broken pages and server errors, then mobile layout, speed, structured data and finally copy changes.

**When do I need a developer?**

Bring in a developer for server errors, DNS, HTTPS, redirects, robots directives, templates, JavaScript failures, form-processing code, structured data setup and hosting configuration. Ask which tools they used to confirm each fix.

## Wrapping Up

The afternoon check runs in a fixed order. You test the phone number, the form and the menu on a phone, compare your Business Profile with your website, ask Search Console what Google can find, read PageSpeed Insights as lab data plus field data, and test structured data only where it applies. Then you sort what you found so that anything blocking a call or form sits at the top.

A short list in the right order is worth more than a long report of warnings. Many fixes turn out to be a corrected phone link, updated hours or a changed setting, and you can make those without spending anything. What remains after that is a precise brief for a developer, which saves time and money when you do need one.

If your list points at problems you would rather not touch, [Web Leveling](https://webleveling.com/) can take them from there. Our [web design](https://webleveling.com/services/web-design/) work covers the site itself, and you can [contact us with your repair list](https://webleveling.com/contact/) and ask about it. We work with small and medium businesses across the country and overseas.

## Terms

Website check words in this post

Tap a term to see what it means.

**Indexed.** A page that Google has added to its search index, which makes it eligible to appear in results but does not mean it will rank.

**URL Inspection.** A Search Console tool that shows whether a specific page is indexed, its canonical, whether Google can crawl it, and indexing problems.

**Canonical.** The address Google treats as the main version of a page when similar versions exist.

**Lab data.** Results from a Lighthouse test run on a page at the moment you test it.

**Field data.** Chrome UX Report data from real visitors to a page over the previous 28 days.

**Structured data.** Extra code that describes a page to search engines, which may make it eligible for supported rich results.

- [Does My Website Need a Sitemap? What to Check First](https://webleveling.com/blog/does-your-website-need-a-sitemap-and-robots-txt/): Google says a sitemap helps most on large, new, or media-rich sites. Check yours and robots.txt, then submit a sitemap in Search Console if you have one.
- [Duplicate Content SEO: Check Search Console, Then Fix It](https://webleveling.com/blog/duplicate-content-on-a-small-business-website/): Duplicate content SEO for a small business site: find the pages Google grouped, see which one it chose, and fix town pages, supplier text and URL versions.
- [How to get a new page found by Google faster](https://webleveling.com/blog/get-a-new-page-found-by-google/): How to get google to index a new page: a ten-minute check in Search Console, what the reported 20-hour discovery figure means, and when to fix a blocker.