Google Search Console gives you a practical way to check whether Google can access your website, which pages are indexed, and what search queries bring visitors. This setup guide explains how to verify a property, submit a sitemap, inspect pages, read performance data, and create a simple monthly routine for improving a new website.
Overview
Google Search Console is a free service for monitoring a website’s presence in Google Search. It does not replace website analytics: analytics tools focus on what visitors do after arriving, while Search Console focuses on how people find your pages and how Google processes them.
For a new site, the most useful workflow is straightforward:
- Add and verify the correct website property.
- Submit the XML sitemap.
- Check important URLs with URL Inspection.
- Review indexing and page experience reports.
- Record performance trends and investigate meaningful changes.
Search Console data can take time to become useful, especially for a recently launched domain with few pages or little search visibility. Treat the first checks as a technical baseline rather than a final judgment about the website.
Choose the right property type
A Domain property groups versions of a domain, including protocols and subdomains, when verification through DNS is available. A URL-prefix property covers only the URL pattern you enter, such as a specific HTTPS version or subdirectory, and offers several verification options. For most site owners, a domain property is a useful broad view; a URL-prefix property can be appropriate when you need to monitor a particular site section or do not control DNS.
What to track
1. Property verification
Start by signing in to Search Console and adding your domain or URL prefix. Select a verification method that matches your access:
- DNS record: Add the TXT value provided by Search Console at your domain provider or DNS host. This is commonly used for a Domain property.
- HTML file: Upload the supplied file to the website’s top-level directory. This requires access to hosting files or a deployment process.
- HTML meta tag: Add the supplied tag to the homepage head section. A WordPress SEO or site-management plugin may provide a field for this.
- Connected service: In some cases, an existing Google service or tracking setup may offer another verification route.
DNS changes can take time to appear. If verification fails, confirm that the record was added to the authoritative DNS provider, that the value was copied exactly, and that you selected the intended property. Avoid deleting a verification record after success unless you have another verified method in place.
2. Sitemap status
An XML sitemap lists URLs you want search engines to discover. Many content management systems generate one automatically. Common locations include a sitemap index or a file such as /sitemap.xml, but the correct address depends on your platform and configuration.
Open the sitemap in a browser first. It should load without a login and should contain the canonical URLs you want considered for indexing. In Search Console, open the Sitemaps area for the selected property, enter the sitemap path, and submit it. Monitor the resulting status rather than repeatedly resubmitting the same file. Submission rules and interface details can change, so use the current instructions shown in the product if they differ.
A submitted sitemap is a discovery aid, not a guarantee that every URL will be indexed. Remove outdated, blocked, duplicate, or non-canonical URLs from the sitemap so it remains a clean description of your preferred pages.
3. Indexing and URL inspection
Use URL Inspection for important pages such as your homepage, main service page, contact page, and newly published articles. Check whether Google can access the URL, whether indexing is allowed, and which canonical URL Google selected when that information is available.
When a page is not indexed, read the stated reason before changing anything. Typical investigation areas include accidental noindex directives, password protection, server errors, redirect chains, canonical settings, and pages that are too similar to another URL. After correcting a genuine issue, use the available validation or recrawl request option where appropriate. Requests are not a substitute for fixing the underlying page, and repeated requests are unlikely to solve a technical problem.
4. Performance measurements
The Performance report usually lets you examine clicks, impressions, average click-through rate, and average position. You can filter the report by queries, pages, countries, devices, and search appearance when those dimensions are available.
Record these fields each month:
- Total clicks and impressions for the selected comparison period
- Queries that generated the most impressions
- Pages with the most clicks
- Pages with rising impressions but few clicks
- Pages whose clicks or impressions declined
- Indexing errors, warnings, or manual tasks that need attention
- New search opportunities related to pages you already publish
Cadence and checkpoints
Use a light schedule rather than checking reports several times a day. A new website can use the following checkpoints:
At launch
Verify the property, submit the sitemap, inspect the homepage and key conversion pages, and confirm that the preferred HTTPS URLs are accessible. This fits well alongside a broader website launch checklist.
After publishing or making a technical change
Inspect the affected URL, confirm that internal links point to it, and check that the sitemap includes it when appropriate. For a new landing page, review the page after publication and make sure its title, canonical setting, and indexability match your intent. The landing page guide can help with the content and structure side of that check.
Monthly
Compare the latest period with the previous comparable period, such as the prior month. Do not record numbers without the date range, property, search type, and filters used. A small spreadsheet is enough:
- Period: ____ to ____
- Clicks: ____
- Impressions: ____
- Indexing errors or warnings: ____
- Declining pages: ____
- New search opportunities: ____
- Next action and owner: ____
Limit the monthly review to a few decisions. For example, improve the title and introduction of one page receiving impressions but few clicks, add useful content for one relevant emerging query, and investigate one indexing issue.
Quarterly
Review the property setup, sitemap contents, redirects, canonical patterns, and important page templates. If DNS, hosting, email, or WordPress settings changed, confirm that those changes did not affect verification or crawling. DNS concepts and record types are covered in DNS Records Explained.
How to interpret changes
A change in one metric rarely explains itself. Use the following combinations as starting points:
- Impressions up, clicks flat: Your pages may be appearing for more searches without earning additional visits. Review the search queries, title, description, and how closely the page matches the search intent.
- Clicks down, impressions stable: Check whether average position, click-through rate, device mix, or the pages receiving impressions changed.
- Impressions and clicks down together: Compare the date range, inspect important URLs, and look for publication changes, technical errors, seasonality, or shifts in the topics people search for.
- Indexed pages fall: Confirm whether the change affects valuable pages or only removed, redirected, duplicate, or intentionally excluded URLs. Do not treat every exclusion as an error.
- A page is crawled but not indexed: Review its usefulness, uniqueness, internal links, canonical signal, and technical accessibility before requesting another check.
Average position is an aggregate estimate, not a fixed ranking for every person or search. Use it with query, page, device, and date filters. Also keep a record of site changes, because a theme update, URL migration, DNS change, or content rewrite can explain a trend that the report alone cannot.
When to revisit
Return to this guide after launching the site, publishing a group of pages, changing domains, moving hosting, redesigning WordPress templates, or modifying DNS and verification records. Recheck Search Console at least monthly while the site is actively growing, and perform a broader technical review each quarter.
Product labels, report locations, verification methods, and request limits can change. Before following an older screenshot or saved instruction, compare it with the current Search Console interface and Google’s on-screen guidance. Update your internal worksheet if a report name or available filter changes, but keep the underlying questions the same: Can Google access the site? Which pages are indexed? What searches produce visibility? Which page deserves the next improvement?
For your next review, complete these actions:
- Write down the property and date range being reviewed.
- Record clicks, impressions, indexing issues, declining pages, and new query opportunities.
- Inspect one important URL and one page showing a notable change.
- Choose no more than three concrete actions for the next period.
- After completing an action, annotate the worksheet so future changes have context.
Keep Search Console as part of your regular website maintenance rather than treating it as a one-time launch task. For WordPress sites, pair this routine with the monthly maintenance checklist, and revisit your hosting or domain configuration when technical changes affect how the site is delivered.
