How to Set Up Google Search Console and Verify Your Website
Published:
Last Updated:
Category: Marketing DX
Authors: Shusaku Yosa
Setting up Google Search Console means adding a property and proving that you control the website. Choose a DNS-verified Domain property for broad domain coverage, or a URL-prefix property for a specific protocol, host, or path. Having GA4 or GTM installed does not automatically meet every verification requirement.
Prepare access before starting
Confirm the public website URL, existing Search Console owners, current DNS provider, and the person who can publish website changes. Use individual Google accounts with appropriate permissions rather than a shared password. A domain registrar and the active DNS provider may be different organizations.
Separate the time needed to enter a record from DNS propagation, verification, and the accumulation of search data. There is no universal completion time. Follow the instructions shown for the selected method and your provider's current documentation.
Choose the property scope
Property | Coverage | Verification | Typical use |
|---|---|---|---|
Domain | Protocols and subdomains under the specified domain | DNS | Ongoing management of the whole domain |
URL prefix | The specified protocol, host, and path prefix | Supported HTML, GA, GTM, or DNS methods | A limited area or a team without DNS access |
A domain-only entry and a full website URL have different property scopes. For a URL-prefix property, check the protocol, host, and path you intend to monitor. Properties can coexist when their scopes serve different needs. Consult Google's verification guide for the current conditions.
Verify through DNS
- Add the Domain property and enter the domain.
- Copy the verification record displayed by Search Console.
- Add it at the active DNS provider without replacing unrelated website or email records. Follow the provider's conventions for the host field.
- Return to Search Console and verify. If it fails, check the provider, domain, record name, and value before allowing time for propagation.
- Retain the verification record and document its location and owner.
If you cannot edit DNS, send the exact record and domain to the responsible administrator, or choose an appropriate URL-prefix method. Do not guess at unrelated DNS changes to solve ownership verification.
Compare URL-prefix verification methods
Method | Requirements | Common failure |
|---|---|---|
HTML file | Publish the supplied file at the required location | Login protection, wrong host, changed file |
HTML tag | Place the verification meta tag in the public homepage head | Body placement or unpublished changes |
Google Analytics | Same Google account, required Analytics editing access, supported code and placement | Wrong account, insufficient access, confusing GTM delivery with direct tagging |
Google Tag Manager | Supported container installation and the required publishing permission | Read/Edit only, wrong container, incorrect placement |
DNS | Control of the applicable DNS records | Editing an old provider or the wrong record |
GA and GTM are separate verification methods. Review the actual GTM and Google tag configuration before selecting one. Keep the verification file, meta tag, or DNS token after success; ownership may be checked again.
Submit the real sitemap URL
Find the sitemap generated by your CMS or plugin. It is not always /sitemap.xml: Yoast documents sitemap_index.xml. Confirm the property scope and submit the actual address in the Sitemaps report.
A successful sitemap status means Google could retrieve and process that sitemap. It does not mean every listed page is indexed. Check important public URLs, exclude obsolete or incorrect host variants from the intended sitemap, and inspect individual pages when necessary.
Finish with an access and indexing checklist
Check | Completion evidence | Keep a record of |
|---|---|---|
Ownership | Verification succeeds for the intended property | Method, token location, owner |
Team access | Required people can access their assigned scope | Owners, users, responsibilities |
Sitemap | Correct submission and retrieval status | URL, date, errors |
Important pages | URL inspection state and canonical reviewed | Reasons and follow-up actions |
Initial reporting | Correct period and search type selected | Pending data and small samples |
Not every URL should be indexed. Duplicates and deliberately excluded URLs can be normal. Use the Page indexing report to distinguish reasons. When an employee or agency changes, confirm the new team's access and verification before removing old access, and review verification tokens as part of the handover.
Add GA4 linking only when useful
GA4 linking is optional for viewing Search Console data. The query report uses search metrics, while a landing-page report can combine Analytics and search data; it does not reveal conversions for each organic query. If linked reports are missing, check publication in the GA4 Library. Follow Google's integration requirements.
Continue with the Search Console analysis workflow and SEO priority checklist. Successful verification is the start of ongoing management, not proof of search visibility or business results.
