Google Search Console for Beginners: Set It Up and Read It
Search Console is Google's free tool for seeing how your site appears in search. How to verify your domain, submit a sitemap, read the Performance and Pages reports, fix 'Crawled — currently not indexed', and use URL Inspection to get a new page noticed.
If you want people to find your site through Google, Google Search Console is the one tool you need. It's free, and it shows you exactly what Google sees: which pages are indexed, what people search to find you, and what's broken.
(Background: how to get your website on Google and SEO basics.)
Step 1: Add and verify your site
Go to search.google.com/search-console and add a property. You'll choose between:
- Domain property (recommended): covers
yourapp.com,www.yourapp.com,http,httpsand every subdomain. Verified with a DNS TXT record. - URL-prefix property: covers one exact address, like
https://yourapp.com/. Verified with an HTML file, a meta tag, or Google Analytics.
For a domain property, Search Console gives you a TXT record like google-site-verification=abc123…. Add it at your DNS provider (DNS records explained), wait a few minutes, and click Verify. Leave the record in place — removing it un-verifies you.
Step 2: Submit your sitemap
A sitemap lists your pages so Google can find them. Most frameworks can generate one at /sitemap.xml. (robots.txt and sitemap.xml explained)
In Search Console: Sitemaps → enter sitemap.xml → Submit. Status should change to "Success." It can take days for pages to be crawled after that.
The Performance report
This shows how you appear in Google search results:
| Metric | Means |
|---|---|
| Impressions | How many times your pages appeared in results |
| Clicks | How many times someone clicked |
| CTR | Clicks ÷ impressions |
| Average position | Your typical ranking (1 = top) |
Click Queries to see the actual searches. This is gold:
- Queries with many impressions but few clicks → improve that page's title and description. (Social preview images is about sharing; your
<title>and meta description are what Google shows.) - Queries at position 8–20 → you're close; improving that page could move you onto page one.
- Queries you didn't expect → ideas for new content.
Data lags by a couple of days; new sites will see very little for the first weeks.
The Pages (indexing) report
Shows which pages are indexed and why others aren't. Common statuses:
- Indexed — in Google.
- Crawled — currently not indexed — Google saw it and decided not to include it (yet). Usually means the page looks thin, duplicate, or low-value. Improve the content, link to it from other pages, and be patient.
- Discovered — currently not indexed — Google knows the URL but hasn't crawled it. Common for new sites; more internal links and time help.
- Duplicate without user-selected canonical — several URLs show the same content (e.g. with and without
www, or with tracking parameters). Pick one with a canonical tag and redirects. (www vs non-www) - Excluded by 'noindex' tag — your page tells Google not to index it. Fine for admin pages; a disaster if it's on your whole site by mistake (a common leftover from staging).
- Not found (404) / Server error (5xx) — broken links or crashes. (HTTP status codes)
- Blocked by robots.txt — your robots.txt disallows it.
Not every page should be indexed. Focus on the ones that matter.
URL Inspection
Paste any URL from your site in the top search bar to see:
- Whether it's indexed, and when it was last crawled.
- The canonical Google chose.
- Any problems found.
Request indexing asks Google to crawl a new or updated page sooner. Use it for important pages; it's rate-limited and not a guarantee.
Test live URL shows how Googlebot sees the page right now — useful to check that a JavaScript-rendered page actually shows content to Google.
Other useful reports
- Core Web Vitals — real-user speed data. (Core Web Vitals explained)
- HTTPS — pages not served securely.
- Links — who links to you, and your most-linked pages.
- Manual actions — penalties (hopefully always empty).
A monthly routine
- Performance → Queries: note rising queries and pages close to page one.
- Pages: check for new errors or "not indexed" spikes.
- Core Web Vitals: anything turned red?
- Improve one or two pages based on what you found.
The summary
- Verify a Domain property with a DNS TXT record.
- Submit your sitemap.
- Performance shows the searches that find you; Pages shows what's indexed and why not.
- URL Inspection checks a page and requests indexing.
- Check monthly and act on what it shows.
EasySpawn serves your site on your own domain with automatic SSL and fast pages from a dedicated server — the technical basics Search Console checks for. See how it works or join the waitlist.
Related: How to Get Your Website on Google · SEO Basics for Your App · robots.txt and sitemap.xml · Core Web Vitals Explained
Keep reading
What Is TypeScript? JavaScript With Labels, Explained for Beginners
TypeScript is JavaScript plus types: labels that say what kind of value each thing holds, checked before your code runs. What it looks like, why AI tools default to it, what .ts and .tsx files are, and how to read the red squiggles.
What Is a Headless CMS? And Does Your App Need One?
A headless CMS is a content editor with no website attached — it stores your content and hands it to your app through an API. How it differs from WordPress, the popular options, when it beats Markdown files or your own database, and when it's overkill.