Google Search Console for Small Business: Setup, the Reports That Matter and a 15-Minute Weekly Routine

What is Google Search Console and why should a small business use it?

Google Search Console is a free tool from Google that helps anyone with a website see how the site performs in Google Search. Google's own description says it shows how Google crawls, indexes and serves your pages, so that you can monitor your results and find ways to improve them. It has no cost and no paid version.

For a small business, the value is simple. You find out which searches show your website, which pages get clicks, which pages Google has not added to its index and whether Google has found a problem that needs your attention. Nothing else gives you that information straight from the source. Other tools estimate it. Search Console reports what Google itself recorded for your site.

You do not need Search Console for your pages to appear in Google. Google's guide says that pages can be discovered without it. What you need it for is visibility into what is happening. A site without Search Console is like a shop with no way of counting people who looked in the window.

This guide is for owners and marketers who run a service business, a local company or a small online store and who want a setup they can finish this week and a routine they can keep. It follows the order we would use on a client site: choose the property type, verify ownership, add the right people, submit the sitemap, learn the four or five reports that matter and then settle into a short weekly check.

One honest note before we start. Google changes menu names and report layouts from time to time. We checked the descriptions in this guide against Google's current help pages, but the screen in front of you may use slightly different labels. When a name in this guide does not match, look for the same idea under a similar name, and check the linked help page.

Search Console or Google Analytics: what is the difference?

Owners often ask which one to use. The answer is both, because they answer different questions.

Search Console covers the part of the journey that happens on Google. It tells you how often your site appeared in search results (impressions), how often someone clicked (clicks) and for which searches and pages. It also tells you whether Google can crawl and index your pages and whether it has found problems.

Google Analytics 4 covers what happens after the visitor arrives. It tells you how people behaved on your site, which actions they took and which channels produced calls, forms and sales. It cannot tell you how often you appeared in Google without a click, because no visit took place.

Put together, they close the loop. Search Console says that a page is shown for a search and gets clicks. Analytics says whether those visitors then called you, filled in the form or left. If you have not set up Analytics properly yet, read our GA4 setup guide for small businesses next, and link the two products when you are done.

Your Google Business Profile has its own performance information for Maps and local listings. Search Console focuses on Google Search results for your website. For local businesses that depend on the map pack, our local SEO checklist explains how those pieces fit together.

Domain property or URL-prefix property: which should you add?

When you add a site, Search Console asks you to choose a property type. This choice matters because it decides what data you see.

A Domain property covers a whole domain, for example your-business.com. According to Google, it includes all subdomains, such as www or m, and multiple protocols, such as http and https. You enter only the domain, without www and without https://.

A URL-prefix property covers only the exact address you enter, including the protocol. Google's example is that only URLs starting with that exact prefix are counted, so the http and https versions of a site need separate properties. A URL-prefix property is useful when you want to look at one section of a site, for example a blog folder, or when you cannot change your domain's DNS settings.

For most small businesses, add the Domain property first. It gives you one complete view, including traffic that arrives on a subdomain or on an old http address. Many people also add a URL-prefix property for the main site afterwards, so that they have a second view and a second way to verify. That is optional.

The trade-off is verification. Google says a Domain property needs DNS record verification, unless the site is hosted on a Google product such as Blogger or Google Sites. A URL-prefix property offers many methods. If you do not control the DNS settings and cannot ask whoever does, start with a URL-prefix property and switch later.

• Domain property: all protocols and subdomains in one place, verified by a DNS record.
• URL-prefix property: one exact address and protocol, with several verification methods.
• Start with the Domain property unless you cannot reach your DNS settings.

How do you verify ownership, and who should own the property?

Verification proves to Google that you control the site, and it unlocks the data. For a Domain property you add a TXT record that Search Console gives you to your domain's DNS settings, usually at your domain registrar or DNS host. Paste the value exactly, save the record and return to Search Console to press Verify. DNS changes can take time to spread, so if verification fails the first time, wait and try again later instead of changing the record.

For a URL-prefix property, Google lists several options, such as uploading a file to the site, adding a tag to the home page or using an existing Analytics or Tag Manager connection. If you use one of these, leave the file or tag in place after verification. Google checks again from time to time, and removing it can remove your access.

Now think about who owns the property. Google describes four permission levels. An Owner has full control, including adding and removing users and changing settings. A Full user can view all data and take some actions but cannot add users. A Restricted user has simple view rights on most data. An Associate can take certain actions for the site but cannot open the account or its data.

There are also two kinds of owners. A verified owner proves ownership with a token such as a DNS record or a file. A delegated owner is added by an existing owner and needs no token of their own. To add someone, open the property, go to Settings, then Users and permissions, choose Add user and enter their Google Account email. Google notes that email groups cannot be added, so each person needs an individual account.

Our advice is practical. The business should always be a verified owner, using a role account or the account of a director that is not tied to one employee. If an agency or freelancer helps you, add them as a Full user, or as an owner only for the duration of a project that really needs it, and remove them when the work ends. Never leave the only owner as a person who may leave.

How do you submit a sitemap, and what does it really do?

A sitemap is a file that lists the pages you want search engines to know about. Google can discover pages without one, so a sitemap is not a requirement, but it helps, and it gives you a report that shows what Google read.

Before you submit, open the sitemap address in your browser and check that it loads. Google also recommends running a live URL inspection on the sitemap and checking that the page fetch shows Successful. Then open the Sitemaps report, paste the sitemap address into the Add a new sitemap box and press Submit. You need owner permission on the property to do this. Without it, Google says you can list the sitemap in your robots.txt file instead.

Afterwards the report shows a status. Success means Google fetched and processed the file without errors. Has errors means it fetched the file but some entries failed, while the entries that parsed correctly are still queued for crawling. Couldn't fetch means Google could not retrieve the file, so check the address, that the file returns a normal page and that nothing blocks it.

Be realistic about what a sitemap does. Google's documentation says that there is no guarantee that a URL discovered in a sitemap has been or will be crawled or indexed. A sitemap is a hint, not an instruction. If a page is thin, duplicated or blocked, listing it in a sitemap will not fix it. Also keep the sitemap honest: list only pages you want in search, with their canonical addresses, and leave out redirects and pages marked noindex.

Each sitemap file can hold up to 50 MB uncompressed and 50,000 URLs. A larger site splits its URLs into several files and lists them in a sitemap index, which Google describes as a sitemap of sitemaps. An index can list regular sitemap files but not other index files.

Here is what we do on this website, as a checkable example. Our sitemap index at /sitemap.xml lists eight child sitemaps: core pages, services, city pages, service-in-city pages, blog posts, portfolio, USA pages and industry pages. Each one is also listed in our robots.txt file. The date in each entry is the date we last reviewed that page's content, not the date we last built the site, so the dates mean something when Google reads them. You can open our sitemap and see all of this yourself. We make no claim about rankings from it. It is simply a setup we can explain and keep tidy.

How do you read the Performance report?

The Performance report for Google Search results is the one most owners open first, and it is the one most often misread. It has four measures.

Clicks are the number of times a user clicked through to your site from Google Search results. Impressions are how many times your site appeared in Search results. CTR, or click-through rate, is clicks divided by impressions. Average position is, in Google's words, the average position of the topmost result from your site. In the chart this covers your whole site. In the table it is calculated for the page, query or other grouping in each row.

By default the report shows the last three months, and you can change the date range. The newest data can be preliminary and may change within hours, and Google says collected data is usually available within two to three days. Daily data follows California time, so it may not match other tools that use a different time zone.

Below the chart you will find tables you can switch between: queries, pages, countries, devices and dates, and search appearance where it applies. Queries show what people typed. Pages show which of your URLs were shown or clicked. Click a row, or add a filter, to see the same measures for that page or query only. That filtering is where the report becomes useful, because a site-wide average hides everything interesting.

Three habits make the report reliable. First, compare like with like: the last 28 days against the previous 28 days, or the same period last year if your business is seasonal, rather than this week against a holiday week. Second, read the measures together. Impressions rising with clicks flat suggests you are being shown for more searches but not being chosen. Clicks falling with impressions steady suggests a worse title or a lower position. Third, ignore single-day spikes and read trends.

Know the limits too. Google says it might not track some queries that are made a very small number of times, to protect privacy, so the query table may not add up to your total. Tables show a maximum of 1,000 rows, and Google points to the Search Console API for larger sets. Search Console also does not keep your history forever, so export the pages and queries that matter every quarter and keep the file.

For a service business, three views repay the effort. Filter the pages table to your service pages and look at which ones get impressions but few clicks, then improve their titles and descriptions. Filter queries to see whether your own business name appears, which shows whether people look for you directly. And check the countries and devices tables so that you know where visitors come from and whether most of them use a phone.

• Clicks, impressions, CTR and average position only make sense together.
• Compare equal date ranges, and expect the newest days to be incomplete.
• Use filters by page and by query, not only the site-wide totals.
• Export key data every quarter, because history is limited.

What does the Page indexing report tell you?

Indexing means that Google has read a page and stored it so that it can appear in results. The Page indexing report shows how many of your known URLs are indexed and, for those that are not, the reason.

The first rule is not to panic about the number of pages that are not indexed. Every site has some URLs that should not be indexed, such as redirects, internal search pages, duplicates and pages you marked noindex on purpose. The right question is whether your important pages are in the indexed list. A shop with 40 product pages and 38 indexed has a different problem from a shop that is proud that 300 URLs are indexed but cannot find its best-selling product.

A few statuses come up for almost everyone. Crawled - currently not indexed means Google crawled the page but has not indexed it. Google says it may or may not be indexed in the future and that you need not resubmit the URL. The usual causes are thin, repeated or low-value content, so improving the page is the real response. Discovered - currently not indexed means Google knows the URL but has not crawled it yet. Google says it likely rescheduled the crawl because it expected to overload the site, so it is not necessarily a fault.

Duplicate without user-selected canonical means Google treats the page as a duplicate of another and has chosen the canonical itself. Google says this is not an error and is working as intended, but if the page you care about is the one that was dropped, add a canonical tag that points to the version you prefer and make your internal links consistent. Page with redirect simply means the URL redirects elsewhere. URL marked noindex means Google found a noindex directive and did not index the page. Check that this is what you wanted.

When you fix a problem, use Validate fix once all instances are corrected. Google warns not to press it again until validation has succeeded or failed, and says validation typically takes up to about two weeks. You will get an email as it progresses. For a new site, Google recommends requesting indexing of the home page, and otherwise says it recrawls pages automatically, so ask for a recrawl only after an important change or if a change has gone unnoticed for a week or more.

Make a short list of your most important URLs, perhaps ten: the home page, your main service pages, your contact page and your best articles. Check them in the indexed list every month. This list is far more useful than a count.

How do you use URL Inspection, and when should you request indexing?

The URL Inspection tool lets you paste one address and see how Google sees it. It reports on Google's stored copy of the page, including indexing status, crawl details and the canonical URL Google chose. The top-level answer is either that the URL is on Google or that it is not. Google notes that being on Google means the page is eligible to appear in results, not that it will appear.

There are two views. The indexed version is the copy Google last stored, and Google states it is not a live test, so the page may have changed since. The live test fetches the page in real time. Its results can differ from the indexed version, for example right after you remove a noindex tag that Google has not recrawled. A live test does not confirm that a page is indexed or check every condition, such as canonical selection.

You can also ask Google to crawl an inspected URL with Request indexing. Google says that submitting a request does not guarantee the page will appear in the index, and it suggests submitting a sitemap for many pages. There is a daily limit of inspection requests for each property. Google says indexing typically takes a day or so, but can take much longer in some cases, so do not press the button repeatedly.

Use the tool in a few clear situations. Check a new page a few days after you publish it. Confirm that a fix works by running a live test before you request indexing. See which canonical Google chose when two pages look alike. And troubleshoot when a page you expect is missing from results.

What do Core Web Vitals, Manual actions, Security issues and Links tell you?

These four reports are quieter than Performance, but each one can warn you about a real problem.

Core Web Vitals uses real-world field data from the Chrome User Experience Report, grouped into mobile and desktop. It looks at three measures: largest contentful paint (how long the main content takes to appear), interaction to next paint (how quickly the page responds to clicks, taps and key presses) and cumulative layout shift (how much elements move unexpectedly). Google's report treats a result as Good at 2.5 seconds or less for LCP, 200 milliseconds or less for INP and 0.1 or less for CLS, and Poor above 4 seconds, 500 milliseconds and 0.25. A group of URLs takes the status of its weakest measure. New properties may show no data for a few days, and groups without enough data are left out. For the practical fixes, see our Core Web Vitals guide for small businesses.

Manual actions shows whether a human reviewer at Google has decided that pages on your site do not follow Google's spam policies. Most small sites never see one, and the report shows a green check mark and a message when there are none. If there is one, Google says to fix the problem on all affected pages, make sure Google can reach them and then use Request Review. Reviews usually take several days or weeks. Treat any message here as urgent.

Security issues is a separate report for hacks and harmful behavior, such as malware or phishing. Manual actions are about spam policies and are usually not dangerous to visitors, while security issues can be. A warning here means you should involve your developer or host at once.

Links shows internal and external links. It lists your top linked pages, top linking sites and top linking text. Google is clear that it shows a sample of links, tables are capped at 1,000 rows and the report does not say whether a link is nofollow. So treat it as a rough guide. It is still useful for a quick check that your home page and key service pages are linked from the rest of your own site, and that no unknown, spammy sites are producing strange anchor text.

What is a 15-minute weekly routine that you can keep?

Most owners open Search Console in a burst of enthusiasm, look at everything, understand half and never return. A short, fixed routine beats that. Google's own guide suggests checking about once a month or after content changes, because it emails you about new issues. For a business that depends on search, weekly is better, and fifteen minutes is enough.

Open a note you can reuse and run through these steps in order. The times are a guide, not a rule.

Minutes 1 to 2: messages and alerts. Check the message center and your email for anything about manual actions, security issues or new indexing problems. If there is one, stop here and deal with it first.

Minutes 3 to 6: performance. Open the Performance report for the last 28 days and compare it with the previous 28 days. Write down clicks and impressions. Then look at the top five pages and top five queries. Did a page you worked on last week appear? Did an important page lose impressions?

Minutes 7 to 9: indexing. Open the Page indexing report. Note the number of indexed pages and whether any new reason appears. Check one or two of your ten most important URLs. If you published something this week, inspect it.

Minutes 10 to 11: sitemaps. Check that the sitemap status still says Success and that the date Google last read it is recent.

Minutes 12 to 13: Core Web Vitals. Check whether any group moved from Good to Needs improvement or Poor. If so, find the page type that changed and tell whoever manages the site.

Minutes 14 to 15: write three lines. What changed, why you think so and what you will do about it. This is the step that turns a glance into a decision. A note that says that impressions on the pricing page rose, clicks stayed flat and the title will be rewritten on Thursday is worth more than any screenshot.

Here is an invented example, clearly for illustration only. A dental clinic runs the routine on a Monday. Messages are clear. Performance shows impressions up and clicks flat on a teeth-whitening page. Indexing shows the new pricing page is not yet in the index, so the owner inspects it, confirms it is in the sitemap and adds a link to it from the services page. The three-line note says: whitening page is shown more but not chosen, so rewrite its title and description; pricing page not indexed yet, recheck on Friday; no other changes. The whole thing took fifteen minutes and produced two actions.

Once a month, add ten minutes. Look at the Links report, export the main Performance tables and file them, and re-read your list of ten important pages. Once a quarter, review whether your sitemap, your property users and your DNS verification record are all still correct.

• Minutes 1-2: messages for manual actions, security and new issues.
• Minutes 3-6: Performance, 28 days against the previous 28.
• Minutes 7-9: Page indexing and one or two key URLs.
• Minutes 10-13: sitemap status and Core Web Vitals.
• Minutes 14-15: write three lines, what changed and what you will do.

What mistakes do beginners make in Search Console?

Chasing every excluded URL. A long list of excluded or not indexed URLs is normal. Fix what affects pages that matter, and leave the rest.

Pressing Request indexing all the time. It does not guarantee anything and has a daily limit. Fix the page, link to it and keep it in your sitemap. Then wait.

Comparing different periods. Looking at this week against last week during a holiday, or comparing a month with a quarter, produces false alarms.

Reading average position as a ranking. It is an average across many searches, countries and devices, and it moves when you start appearing for new, more distant queries. A rising impression count with a falling average position can be good news.

Letting only one person have access. If that person leaves, the history leaves with them. Keep the business as a verified owner.

Mixing up data sources. Search Console and Analytics count different things. Clicks in Search Console will not equal sessions in Analytics, and that is fine. Use each for its own purpose.

Ignoring it until something breaks. The point of the routine is to see small changes before they become large ones.

When should you ask for help?

You can set up Search Console and run the weekly routine yourself. Ask for help when something is outside your depth: a manual action, a security warning, a sudden and sustained loss of impressions on important pages, or a large site with hundreds of pages that are crawled but not indexed.

It also makes sense to get a specialist to look at the whole picture once. A technical review can combine what Search Console reports with a crawl of your site, your sitemap, your internal links and your page speed, and then turn it into a prioritized list. Our SEO audit service does that, and our technical SEO service fixes what the audit finds. If your main goal is to bring in more enquiries from search, start with our SEO services overview.

If you want to understand how search is changing, including answers generated by AI, our guide to AI search optimization explains what to do and what to ignore. And if you want your tracking set up properly at the same time, our GA4 setup and audit service can connect Search Console and Analytics for you.