Google Search Console Setup Checklist

Use this checklist to add a website to Google Search Console, verify ownership, submit a sitemap and confirm that Google can access your most important pages.

What Search Console setup accomplishes Search Console gives you direct reports about how Google discovers, crawls, indexes and displays your website. Setting it up does not guarantee indexing or rankings, but it gives you the information needed to identify problems and monitor search performance.

Quick setup checklist

Confirm the preferred site URL
Choose a property type
Verify ownership
Add a backup verification method
Check users and permissions
Locate and test the sitemap
Submit the sitemap
Inspect the homepage
Inspect important pages
Review indexing reports
Review security and manual actions
Wait for performance data

Complete Search Console setup

Step 1

Confirm your website's preferred version

Before creating the property, confirm which public URL visitors and search engines should use.

Confirm that the website loads through HTTPS.
Decide whether the preferred hostname uses www.example.com or example.com.
Confirm that alternate versions redirect to the preferred version.
Check that the homepage does not require a login.
Confirm that important pages are linked from the website.

Why this matters A URL-prefix Property covers only the exact protocol and hostname you enter. A Domain Property is more forgiving because it includes the domain's protocols and subdomains.

Step 2

Choose the correct property type

Choose a Domain Property when you control DNS and want broad coverage.
Choose a URL-prefix Property when you need exact scope or another verification method.
Do not use a Platform Property for your own website.

General recommendation Use a Domain Property for the main website when possible. Additional URL-prefix Properties can be added later for specific subdomains or directories.

Step 3

Add the property to Search Console

Sign in with the Google account that should own the property.
Open the property selector.
Select Add property.
Enter the domain or full URL prefix carefully.
Check for spelling, protocol and hostname mistakes before continuing.

Step 4

Verify ownership

Verification proves that you control the website. The available methods depend on the selected property type.

For a Domain Property, add the verification record through your DNS provider.
For a URL-prefix Property, use an available method such as DNS, an HTML file, an HTML meta tag, Google Analytics or Google Tag Manager.
Follow the exact token placement instructions shown in Search Console.
Leave the verification record, file or tag in place after verification succeeds.

Useful safeguard Add a second verification method when practical. This can help preserve ownership if a site redesign, analytics change or hosting migration removes the original verification method.

Step 5

Review users and permissions

Open Settings → Users and permissions.
Confirm that the correct Google account is listed as an owner.
Remove accounts that should no longer have access.
Give collaborators only the level of access they need.
Make sure the property will retain a verified owner if a team member leaves.

Step 6

Find and test your sitemap

Many content-management systems and hosting platforms create a sitemap automatically.

Look for a sitemap at a common location such as https://example.com/sitemap.xml.
Open the sitemap in a browser and confirm that it is publicly accessible.
Confirm that it contains canonical, indexable URLs from the correct domain.
Remove broken, redirected or obsolete URLs when possible.
Confirm that robots.txt does not block Google from fetching the sitemap.

Small-site note A very small, well-linked website may be discovered without a sitemap, but submitting one gives you a direct way to report its location and monitor processing errors.

Step 7

Submit the sitemap

Open the Sitemaps report.
Enter the sitemap location.
Select Submit.
Confirm that the status eventually shows success.
Open any reported error for more information if the sitemap cannot be fetched or parsed.

Remember Search Console does not host or upload the sitemap. The sitemap must already exist on your website at a URL Google can access.

Step 8

Inspect the homepage

Enter the full homepage URL into the URL Inspection search bar.
Confirm whether Google knows about the URL.
Run a live test when you need to check the current page.
Confirm that page fetching succeeds.
Review robots, canonical and indexing information.
Request indexing when the page is eligible and newly published or meaningfully updated.

Step 9

Inspect several important pages

Do not test only the homepage. Check a small representative group.

A major product, tool or service page
A recently published page
A page several clicks away from the homepage
A page using structured data
A page that has previously had an indexing problem

Step 10

Review Page Indexing

Review the number of indexed and non-indexed pages.
Open the main exclusion or indexing-reason groups.
Determine whether excluded URLs are intentionally excluded.
Inspect individual URLs when a status seems incorrect.
Avoid treating every non-indexed URL as an error.

Interpretation matters Redirects, duplicate URLs, alternate canonical URLs and intentionally blocked pages may correctly remain outside the index.

Step 11

Review security and manual-action reports

Open the Manual actions report.
Open the Security issues report.
Confirm that no unresolved warnings are present.
Enable or retain useful Search Console email notifications.

Step 12

Allow time for performance data

A new property may not show meaningful Performance data immediately. Search Console needs time to collect and process information.

Check again after several days.
Confirm that the selected property matches the live site.
Remember that a new website may have few or no search impressions initially.
Do not repeatedly change the property because the first dashboard is empty.

What to expect after setup

Time after setup	What you may see	What to do
Immediately	Verified property, settings, sitemap submission and URL Inspection access	Confirm property scope and inspect important URLs
First few days	Initial sitemap processing, indexing information and partial performance data	Check for fetch, sitemap or verification errors
Up to about one week	More complete initial reports for a newly added property	Confirm that the property matches the website if data is still absent
Following weeks	Search queries, impressions, clicks and clearer indexing trends	Look for patterns rather than reacting to one day's data

Search Console setup is not an indexing guarantee. Submitting a sitemap or requesting indexing tells Google where a page is and asks Google to consider crawling it. Google may still decide not to crawl or index every submitted URL.

Monthly maintenance checklist

Review changes in clicks, impressions, CTR and average position.
Check whether important new pages are receiving impressions.
Review Page Indexing for new or growing problems.
Confirm that submitted sitemaps remain successful.
Inspect pages that unexpectedly lost search visibility.
Review manual actions, security issues and Search Console messages.
Check users and verification methods after staff or hosting changes.
Record meaningful ranking and indexing changes over time.

Frequently asked questions

Do I need Google Analytics before using Search Console?

No. Search Console can be used independently. Google Analytics can be one possible verification method for a URL-prefix Property when the account and tracking-code requirements are satisfied.

Do I need to submit every page manually?

No. Use a sitemap and internal links to help Google discover groups of pages. URL Inspection is better suited to checking or requesting indexing for individual important URLs.

Why is the Performance report empty?

Data may still be processing, the property may not match the live protocol or hostname, or the website may not yet have measurable Google Search visibility.

Should I remove the verification record after setup?

No. Search Console periodically checks verification. Removing the token, record, file or tag can eventually cause ownership access to expire.

Should more than one person be an owner?

For an organization or important business website, maintaining more than one appropriate owner can prevent the property from becoming inaccessible when one person leaves or loses account access.

How often should I check Search Console?

A weekly review is reasonable for a growing website, while a more detailed monthly review is useful for identifying trends. Check sooner after launches, migrations, major site changes or Search Console warnings.

Setup, verification, sitemap and URL Inspection guidance was reviewed against Google's Search Console getting-started guide, ownership-verification documentation, Sitemaps report documentation and URL Inspection documentation. Features may change. Last reviewed: July 30, 2026.