What is Google Search Console and why does a small business need it?
Search Console is Google's free tool showing the searches your site already appears for, how often people click, and which pages Google has and has not indexed. There is no paid tier.
Most local service sites are not connected to it, so the owner cannot tell whether the site shows up when someone nearby searches for the job they do. Everything in it is data Google already holds, and setting it up changes nothing: Google says adding a property "does not affect your website or platform property on Google Search, it only enables you to track your site's performance".
You need a Google account, your exact website address including the https, and login access either to your website platform or to your domain registrar. Which one depends on the property type.
Domain property or URL-prefix property: which should you choose?
Choose a domain property if you can log in to your domain registrar, because it is the only type that captures everything in one place. Google's documentation says it aggregates data for all subdomains, protocols and subpaths. A URL-prefix property includes only URLs starting with the exact prefix you typed, so pages served without the www would be invisible to you. Google's own example: for the property http://example.com/, the URL https://example.com/dresses/1234 does not match, because https does not match http.
| Domain property | URL-prefix property | |
|---|---|---|
| What you type | yourbusiness.co.uk (no https, no www, no path) | The full address including https and any www |
| What it covers | All subdomains, all protocols, all paths | Only URLs starting with that exact prefix |
| How you verify | DNS record only | HTML file, HTML tag, Google Analytics, Google Tag Manager, or DNS |
| Where you need access | Your domain registrar or DNS host | Your website platform |
| Best for | Almost every small business with one site | Anyone locked out of DNS, or tracking one section of a site |
A correction to the older version of this guide. This page used to say pick URL prefix every time, because DNS is more technical. That was too blunt. URL prefix is a fine fallback if you cannot get into the DNS panel, but the domain property is the better default because it cannot silently miss half your traffic. If you already have one, keep it and add a domain property alongside; Google allows 1,000 properties per account.
How do you verify a domain property with a DNS TXT record?
You add one TXT record at your registrar, leave the Host or Name field blank or set to @, paste Google's string into the Value field, save, then click Verify. Google's instruction is explicit: "For the Host/Name property, either leave this blank, or set as '@'", and for Value, "provide the Search Console TXT record string".
In Search Console: Add property, Website property, Domain, then your bare domain. If it recognises your provider it may do it for you. Otherwise add the record by hand, at the paths below.
| Registrar or DNS host | Where the record goes | What they say about timing |
|---|---|---|
| GoDaddy | Domain Portfolio → the domain → DNS tab → Add New Record → Type: TXT | "Most DNS updates take effect within an hour but could take up to 48 hours to update globally" |
| 123 Reg | Control Panel → Manage All next to Domains → the domain → DNS → Add New Record → TXT, Name: @, TTL: Default | "It will take between 24-48 hours for any changes to your DNS records to become active" |
| Namecheap | Domain List → Manage → Advanced DNS → Add new record → TXT Record, Host: @ | "It takes 30 minutes for newly created host records to take effect" |
| IONOS | Gear icon under Actions → DNS → Add Record → TXT, Host name: @ | Immediate at IONOS, "up to 1 hour for the change to take effect externally" |
| Cloudflare | DNS Records page → Add record → Type: TXT → Save | No propagation figure published; TTL sets how quickly updates reach users |
Those registrar timings are their own estimates. Google's is the one to plan around: "for manually installed records, it can take up to two or three days for your provider to start serving the record... wait a day or two and try again." A failed first attempt is normal. Do not delete the record and start over; look it up with Google's Admin Toolbox dig tool instead, because if the string is not being served yet, Verify cannot succeed. The record has no effect on your website or email, but deleting it later does break things: Google rechecks periodically, and if verification can no longer be confirmed your permissions expire after a grace period.
How do you verify a URL-prefix property on Wix, Squarespace or WordPress?
Pick the HTML tag method and paste one meta tag into your site's head, unless your platform has a built-in connection, in which case use that. The tag must sit in the head of a homepage that does not require a login, less than 2MB into the file.
- Wix. Wix has moved this. Its current instructions put it in the SEO & GEO dashboard: Tools and settings, Site Verification, expand Google Search Console, paste the tag, save. You need an upgraded site with a connected domain. If older notes say Settings then Custom Code, that path still exists for other scripts but is no longer what Wix documents here.
- Squarespace. Squarespace no longer asks you to paste a code at all. Its current route connects the accounts directly: Analytics panel, Search keywords, Connect, sign in, Allow. Squarespace then says "wait 72 hours for the data to populate" — its figure about its own panel, not a Google one.
- WordPress. Any SEO plugin has a field for the code. Google names Site Kit, adding that it "is the only plugin that is officially sponsored by Google, so do a little research on any plugin before you install it". Editing header.php by hand works, but a theme update can wipe it.
- Shopify and the rest. Search your platform's help for "Search Console verification" before hunting for a code editor. Most have a dedicated field.
The alternatives: HTML file upload puts a file at your site root, and Google will not follow redirects to another domain when looking for it. Google Analytics and Google Tag Manager work if that snippet is already in your head and you use the same Google account for both. All three are URL-prefix only; none verifies a domain property.
Why did my Search Console verification fail?
Nine times out of ten it is one of four things, and Google's error messages map onto them.
- Record or tag not found. For DNS, wait. For a tag, load your live homepage, view source and search for "google-site-verification". If it is not there, your platform has not published the change.
- Tag in the wrong location. Google looks for it "in the rendered source of your site's home page", in the head. A tag in a footer widget or page body never verifies.
- Record did not match. The string has been altered, or someone else's token is there. Paste exactly what the wizard gave you.
- Wrong property. Verifying https://yourbusiness.co.uk while the site serves https://www.yourbusiness.co.uk fails every time.
How do you submit a sitemap to Google Search Console?
Open Sitemaps in the left menu, paste your sitemap URL into the "Add a new sitemap" box and click Submit. Google's phrasing is worth reading twice: "'Submitting' a sitemap means telling Google where to find the file on your site. You cannot actually upload a sitemap to Google." Check the file is reachable first, as Google now asks: run a live URL inspection on the sitemap address and check Page fetch says "Successful". One extra minute, and the difference between a Success and a "Couldn't fetch".
On most platforms the file is at /sitemap.xml. Google is blunter about this than the older version of this guide was: hosted platforms "probably manage your sitemap for you, in which case you don't need to make your own sitemap or use this report", and a site of "about 500 pages or fewer" whose pages are all reachable from the homepage "probably" does not need one either. Submit it anyway, because it is free and it helps, but Google also notes "there is no guarantee that a page URL discovered in a sitemap has been or will be crawled or indexed".
What do the "not indexed" reasons in the Pages report actually mean?
Most of them are not errors. The report sits under Indexing then Pages and gives a reason for every URL it has not indexed. What the ones a small site actually sees mean, in Google's own terms:
| Reason shown | What it means | Does it need fixing? |
|---|---|---|
| Crawled – currently not indexed | "Crawled by Google but not indexed. It may or may not be indexed in the future" | Usually a content quality signal. Google says "no need to resubmit this URL" |
| Discovered – currently not indexed | Found but not crawled. "Google wanted to crawl the URL but this was expected to overload the site" | Usually wait, and check hosting is not slow |
| Duplicate without user-selected canonical | Google picked another page as canonical. "This is not an error, but is working as intended" | Only if the pages really are different, in which case make them so |
| Page with redirect | The URL redirects elsewhere, so it is not indexed itself | No. That is how redirects are meant to work |
| Not found (404) | "404 responses are not necessarily a problem, if the page has been removed without any replacement" | Only if it was a real page. If it moved, use a 301 redirect |
| Excluded by noindex tag | Something on the page tells Google not to index it | Yes, if you want that page found |
| Indexed, though blocked by robots.txt | Indexed from links elsewhere but unreadable, so the snippet "will probably be very limited" | Yes. robots.txt is not the way to keep a page out of the index |
The pattern that should worry you is service pages sitting in "Crawled – currently not indexed". That is Google saying it read the page and chose not to keep it: a thin-content problem, not a technical one. The fix is in how to write a service page that gets found.
How do you use URL Inspection and ask Google to reindex a page?
Paste any URL from your property into the box at the top of Search Console and it tells you whether that page is on Google, when it was last crawled, and which URL Google chose as canonical. If you have just published or fixed something, click Request Indexing.
Three things people misread. The default view is not a live test: results come "from most recently indexed version of a page, not the live version on the web", so click Live Test for what is true now. Second, "URL is on Google" "doesn't actually guarantee that your page will appear in Search results". Third, requesting indexing is not a fast lane. Google's crawling documentation, last updated 10 December 2025, says "crawling can take anywhere from a few days to a few weeks", that there is a submission quota, and that "requesting a recrawl multiple times for the same URL won't get it crawled any faster". If speed matters, Bing accepts an instant submission protocol Google does not take part in: how to enable IndexNow for Bing.
How do you read the Performance report without misreading it?
Four numbers, and only two mean what people assume. Google defines clicks as the times someone clicked your site from Google results; impressions as how many times your site appeared; CTR as clicks divided by impressions; and average position as "the average position of the topmost result from your site". In plain words: an impression means you were on the page someone was looking at, whether or not they noticed you. A click means they came. CTR is the share of people who saw you who bothered.
The trap is average position. It averages your topmost result across every search where you appeared, including ones you barely register for. A site at position 12 is not "on page two": it might be 3 for its own business name and 40 for everything else. Treat it as a direction of travel, never a ranking.
The second trap is aggregation. Google's worked example: three of your pages appear for one query and someone clicks all three. Aggregated by property that is 1 impression, 3 clicks, 100% CTR and position 1; aggregated by page it is 1 impression each, 33% CTR and position 2.
- Dates are shown in Pacific Time, not UK time, in every view except the 24-hour one.
- The newest data is preliminary, shown as a dotted line, and "may change in the next few hours".
- The default view is the last three months. The date filter's longest option is 16 months, though Google's current help pages state no retention figure, so treat that as what the interface offers rather than a guarantee.
- Weekly and monthly granularity, added in December 2025, sit in a dropdown above the chart and suit a small site far better than the daily view.
Why is there no data in Search Console, and what can it not tell you?
If the property is new, give it a few days: Google says "data should begin to appear in your property in a few days", and that collection starts as soon as anyone adds the property, even before verification. If several days pass with nothing, Google's diagnosis is "the site hasn't been seen in Google Search, or that you have specified the wrong URL (for example, you specified http instead of https for your URL-prefix property)". Assuming it is working, here is what it still will not tell you:
- Every search term. Google omits some queries to protect privacy. It calls these anonymised queries, still counted in chart totals unless you apply a query filter, so the Queries table never adds up to your total clicks.
- Every row. Beyond that, Google says it "stores and shows only the most important data rows".
- What people did after arriving. Search Console stops at the click.
- Why a competitor outranks you. There is no competitor data in it at all.
- Bing, Copilot or ChatGPT. This is Google only: see how to set up Bing Webmaster Tools.
- Your Google Business Profile. Map pack and profile performance are reported inside the profile itself.
What is the difference between Google Search Console and Google Analytics?
Search Console reports what happens before someone reaches your site; Analytics reports what happens after. Two free tools from the same company, measuring different halves of one journey, and they will never agree on a number. Search Console knows the search someone typed, that your page was shown, and that they clicked. Analytics knows a visit happened, which pages were viewed and whether they filled in your form, but has no idea what was typed into Google. You want both. Set Analytics up second, following how to set up Google Analytics, bearing in mind it needs a cookie banner in the UK while Search Console does not, because it puts nothing on your site.
If the two disagree, they are both right. Search Console counts clicks from Google results; Analytics counts sessions that loaded your tag. Ad blockers, people who leave before the page loads, and consent banners sit between the two. A sizeable gap is normal, not a fault.
What should you do in the first week after verifying?
- Day one. Submit your sitemap, having live-tested the URL first. Then inspect your homepage and each main service page and check each says "URL is on Google".
- Day two. Read the "not indexed" reasons under Indexing then Pages against the table above. Write down only the ones involving a page you want found.
- Day three. Add a second verification method, so a theme update or a DNS clear-out cannot lock you out.
- End of week one. Open Performance, widen the date range and read the Queries tab. If every query is your business name, people who already know you can find you and nobody else can. That is the commonest finding on a small business site, and the answer is service and location pages: start with why isn't my website showing on Google.
- Then leave it alone for a month. Weekly granularity, not daily. Small sites produce noisy daily numbers, and reading them daily leads to bad decisions.
Then look for searches with many impressions and almost no clicks: usually a title and description problem, and the cheapest fix in search. See how to write a good page title and meta description.
Common questions
- Is Google Search Console free?
- Yes, completely. There is no paid tier, no trial and no upsell. Google provides it to every site owner, and the only cost is the time it takes to verify. You can hold up to 1,000 properties in one account, so someone running two businesses can keep both in one login for nothing.
- How long does Google Search Console take to show data?
- Google says data should begin to appear in a few days, and that collection starts as soon as anyone adds the property, even before verification completes. If nothing appears after several days, Google's own explanation is that either the site has not been seen in Google Search yet, or the property URL is wrong, most often http typed where the site serves https.
- What is the difference between a domain property and a URL-prefix property?
- A domain property covers every subdomain, protocol and path of your site in one place, and can only be verified with a DNS record. A URL-prefix property covers only URLs starting with the exact address you typed, so https and http, or www and non-www, are separate properties. Choose the domain property if you can get into your registrar account.
- How long does DNS verification take to work?
- Google says that for manually added records it can take up to two or three days for your provider to start serving the record, and advises waiting a day or two before trying again. Registrars quote shorter times, from 30 minutes at Namecheap to 48 hours at GoDaddy and 123 Reg. Plan around Google's figure, and do not delete and re-add the record while you wait.
- What does crawled - currently not indexed mean?
- It means Google fetched your page, read it, and decided not to put it in the index. Google says it may or may not be indexed in future and that there is no need to resubmit the URL. On a small business site this is nearly always a content problem, not a technical one: the page is thin, close to a duplicate, or answers nothing anyone searches for.
- How do I submit a sitemap to Google Search Console?
- Open the Sitemaps report, paste the sitemap URL, usually yoursite.co.uk/sitemap.xml, into the Add a new sitemap box and click Submit. Google recommends first running a live URL inspection on that address and checking Page fetch says Successful. Submitting only tells Google where the file is, and a listed URL is never guaranteed to be indexed.
- Do I need Google Search Console if I already have Google Analytics?
- Yes, they measure different halves of the journey. Search Console reports what happened in Google's results before the click: the query, the impression, the position. Analytics reports what happened after: the pages viewed, the enquiry. Neither sees the other half, and the two never match exactly because ad blockers and cookie consent sit between them.
- Will Search Console slow down my website or affect my rankings?
- No. Verifying adds one meta tag, one small file or one DNS record, none of which a visitor sees or feels. Google states that adding a property does not affect your site on Google Search, it only lets you track performance. The caution runs the other way: remove the verification token later and your access expires after a grace period.
Related guides
Sources, all checked 15 September 2026. Google Search Console Help: "Add a website or platform property" (property types and coverage, the 1,000-property limit, platform properties, data appearing in a few days); "Verify your site ownership" (the method table, DNS-only verification for domain properties, the Host/Name and Value fields, "up to two or three days", the 2MB head-tag limit, Site Kit, loss of access if a token is removed); "Sitemaps report" (the live-inspection test, the 500-page guidance); "Page indexing report" (each not-indexed reason); "URL Inspection tool"; "Performance report" overview, "About the data" and "Dimensions and data groupings" (anonymised queries, data truncation, Pacific Time). Google Search Central: "Ask Google to recrawl your URLs", page last updated 10 December 2025; Search Central Blog, "Introducing weekly and monthly views in Search Console", December 2025. Registrar and platform steps from each publisher's own current help pages: Wix, Squarespace, GoDaddy, 123 Reg, Namecheap, IONOS and Cloudflare. One figure could not be established from a primary source: Google's current Performance report help pages state no data retention period, so the commonly quoted 16 months is described here as the longest range the date filter offers, not a published guarantee. Cloudflare publishes no propagation estimate, so none is quoted.