Publishing a Blogger post is only half the job. You also want Google to find it, understand it and show it to the right readers. Google Search Console is the free tool that connects your BlogSpot blog to Google Search. You can check which pages are indexed, submit a sitemap, request indexing for a new post and spot simple problems.
This beginner's guide walks you through adding Search Console to a free blogspot.com address, verifying ownership, submitting sitemaps and using URL Inspection. The steps use well-known Search Console and Blogger terms. If you are still creating your blog, start with our guide on how to start a free blog on Blogger, then come back here.
What Is Google Search Console?
Google Search Console (often called GSC) is a free dashboard from Google. It is not AdSense and it does not pay you. It shows how Google sees your site in search: which URLs are indexed, how people find you, and where there are errors.
For a new blogger in Nigeria or elsewhere in Africa, it answers questions like:
- Did Google discover my new post?
- Is my sitemap being read?
- Which search queries bring clicks?
- Which pages have indexing problems?
You do not need a custom domain. A free yourblog.blogspot.com address works fine.
Why Blogger Users Need Search Console
Blogger already hosts your files on Google's servers, but Search Console still matters. Without it you are guessing. With it you can confirm indexing, submit sitemaps, request indexing for important URLs, read Performance data and spot Pages report issues early.
Search Console does not replace good titles, helpful posts or a clear site. It helps you check the technical side while you improve content. For stronger titles, see our guide on writing SEO titles and search descriptions on Blogger.
Step 1: Open Search Console and Add Your Blog
- Sign in to the same Google account that owns your Blogger blog.
- Go to search.google.com/search-console.
- Click Start now or the property selector, then choose Add property.
- Choose the URL prefix option (not Domain). URL prefix is the simple choice for a free BlogSpot address.
- Enter your full blog address with
https://, for examplehttps://yourblog.blogspot.com/. - Click Continue.
Use the exact address people type in the browser. Prefer the https version, which is the default for most BlogSpot blogs today.
Step 2: Verify Ownership
Google must confirm you control the site. For many Blogger blogs on the same Google account, verification is quick or even automatic because Google already knows you own the blog.
When verification is automatic
If you are signed into the Google account that is the blog owner in Blogger, Search Console often verifies a BlogSpot URL-prefix property without extra HTML tags. You may see a success message right away. If that happens, skip ahead to sitemaps.
If Google asks you to verify
Follow the method Search Console shows for your property. Common options include an HTML tag in the page head or another ownership method listed on the verification screen. On Blogger, site-wide meta tags are usually added under Settings (look for search preferences / meta tags / HTML head) or via a careful theme edit if you are experienced. Prefer the simplest method Search Console offers for Blogger, and do not paste random third-party scripts.
- Save any required tag on Blogger.
- Return to Search Console and click Verify.
- Keep the verification tag in place after success so ownership stays confirmed.
If verification fails, wait a few minutes, confirm you saved the change, and try again while signed into the correct Google account.
Step 3: Submit Your Blogger Sitemaps
A sitemap is a list of your important URLs. Blogger creates sitemaps for you. You do not need to upload an XML file by hand for a normal BlogSpot blog.
- Open your property in Search Console.
- In the left menu, go to Sitemaps.
- Under Add a new sitemap, enter
sitemap.xmland click Submit. - Also submit
sitemap-pages.xmlthe same way. That covers static pages such as About or Contact.
You should see the sitemaps listed with a status such as Success once Google has fetched them. New blogs may show a pending or temporary fetch message; check again later. Do not keep resubmitting every hour.
For more on robots and sitemaps on BlogSpot, read how to set robots.txt and sitemap on BlogSpot.
Step 4: Use URL Inspection and Request Indexing
- At the top of Search Console, find the URL Inspection bar.
- Paste the full post URL, including
https://. - Press Enter and wait for the result.
- If the page is not on Google yet, and there is no hard block, click Request indexing.
- Wait for the request to finish. Use this for key new or updated posts, not for every small edit.
Indexing is not instant and is never guaranteed. Google decides what to crawl and when. Request indexing is a helpful nudge, not a ranking boost by itself.
Step 5: Read the Performance Report
Open Performance (sometimes shown as Search results under Performance). For a brand-new blog the charts may be empty for days or weeks. That is normal.
When data appears, look at total clicks, total impressions, average CTR and average position. Use the tabs for Queries, Pages, Countries and Devices. On phones in Nigeria and similar markets, Mobile often dominates Devices. Do not chase vanity numbers. Use queries to learn what people type, then improve those posts with clearer titles and better answers.
Step 6: Check the Pages Indexing Report
Open Indexing then Pages (sometimes labelled Page indexing). You will see counts of pages indexed and not indexed, with reasons.
- Discovered - currently not indexed — Google knows the URL but has not indexed it yet. Keep improving and be patient.
- Crawled - currently not indexed — Google fetched it but chose not to index it for now. Quality and uniqueness matter here.
- Excluded by 'noindex' tag — you (or a setting) told Google not to index it.
- Not found (404) — the URL is broken or removed.
- Soft 404 — the page looks empty or like an error to Google.
Fix real errors such as 404s or accidental noindex on posts you want ranked. Do not panic over every "not indexed" line on a new site. Focus on making each published post useful.
Common Mistakes to Avoid
- Adding a Domain property for a free BlogSpot URL. Domain properties need DNS records you may not control on
blogspot.com. Prefer URL prefix. - Using a different Google account from the Blogger owner account.
- Submitting the homepage URL as a sitemap instead of
sitemap.xmlandsitemap-pages.xml. - Requesting indexing dozens of times a day. It will not speed things up.
- Expecting overnight traffic. New blogs need consistent, helpful posts first.
- Ignoring titles and content while staring at charts. Search Console reports problems; it does not write the post for you.
Short FAQ
Do I need a custom domain for Search Console?
No. A free blogspot.com URL-prefix property is enough to start.
How long until Performance shows data?
It varies. Some blogs see early impressions within days; others take longer. Keep publishing and check weekly rather than hourly.
Should I submit both sitemap.xml and sitemap-pages.xml?
Yes. Posts and static pages are covered separately on Blogger, so submitting both is the usual beginner practice.
Will Request indexing make my post rank on page one?
No. It only asks Google to crawl or recrawl that URL. Ranking depends on relevance, quality and competition.
Is Search Console the same as Google Analytics?
No. Search Console focuses on Google Search visibility and indexing. Analytics focuses on on-site visitor behaviour.
Final Thoughts
Adding Google Search Console to Blogger is one of the best free habits you can start early. Use a URL-prefix property for your BlogSpot address, verify with the same Google account that owns the blog, submit sitemap.xml and sitemap-pages.xml, then use URL Inspection for important posts. Check Performance and Pages regularly, but spend most of your energy writing clear, helpful guides your readers can trust.
If something in your setup looks different from these steps, leave a comment and describe what you see. At Sam Trend Hub on GOJIST we are happy to help beginners in Nigeria and across Africa get the basics right, one careful step at a time.

0 Comments