How to verify your website in Google Search Console
Read the conclusion first
First confirm website access in native Search Console; then connect AISEO Site using the same Google account and the correct property. Ownership verification, Google sign-in, read permission and available search data are separate checks. Follow the step where your setup actually fails instead of creating new properties repeatedly.
Applicable conditions
For a website you own or are authorized to manage. Have its final public URL and your Google account ready. DNS or website deployment access is needed only if you must establish ownership yourself; an existing owner can grant access instead. This article covers website properties and the current read-only AISEO Site connection, not platform accounts or automatic SEO changes.
Before you open the report
The exact public URL, access to its DNS or verification method, and the Google account that will retain ownership.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Start with the account and the URL you actually manage
Open the website in a browser and copy its final address after redirects. Write down whether it uses HTTPS, www, another subdomain or a language directory. Then open Search Console and check the signed-in Google account. If the site is already in the property selector, open it instead of creating another property. If an agency owns the existing property, ask its owner to grant your named account access; sending the agency your Google password is unnecessary. Your first checkpoint is simple: the intended account can open the intended website property in native Search Console.
Choose a property by coverage, not by its label
For a whole website across protocols and subdomains, a Domain property such as example.com is useful if you can manage its DNS. Enter the domain without https:// or a path. For one specific host or directory, use a complete URL-prefix property, for example https://www.example.com/shop/. That prefix does not cover https://example.com/shop/ or the site's /blog/ directory. Before adding it, test your homepage and one important landing page against the proposed scope. Both types can coexist; choose one consistent monitoring scope rather than adding their overlapping totals together.
Verify Domain ownership in the DNS service that is actually authoritative
Choose the DNS method offered by Search Console and copy the supplied TXT value or CNAME name/value pair exactly. Add it where the domain's active nameservers are managed; that may differ from the company where you bought the domain. Use that provider's host/name instructions. Check the public TXT or CNAME response with Google's Admin Toolbox, then return to Search Console and verify. If the record is absent, check the DNS provider and record name before repeatedly clicking Verify. If present but different, correct the value. Keep the successful verification record in place and record who maintains it.
Without DNS access, use a supported URL-prefix verification method
If you can deploy site files but cannot edit DNS, select a URL-prefix property and use a verification method your platform supports. With an HTML file, upload Google's original file and test the exact address shown in the verification screen without signing in; do not send that address to the homepage or change the file contents. With an HTML tag, place the supplied tag in the homepage head and inspect the delivered HTML, not just the CMS editor. A login page, missing file or wrong tag requires a deployment correction. If you control neither DNS nor the website, ask an existing owner for access instead.
Connect AISEO Site with the same Google account
Return to AISEO Site, start its Google connection and choose the account that passed the native Search Console check. Review the consent screen: the current connection requests identity information and read-only Search Console access. Select the exact verified Domain or URL-prefix property. If it is missing, first check whether this Google account can still open it in Search Console. Native access missing means an account or property-permission issue; native access working but the tool failing means you should preserve the tool error and check its authorization. A successful Google sign-in alone does not establish website access, and reading data does not edit your site or submit indexing requests.
Check the first report and classify an empty result
Open native Search Console's Web performance report for a completed historical period and remove unintended filters. Record the property, dates and a known landing page. In AISEO Site, use the same property and the comparable date range supported by the tool. If native Search Console also has no data, recheck URL coverage and whether the site has search exposure; a newly added property may need time to populate. If native data exists but the tool returns an error or nothing, keep the time, selected property, date range and error for troubleshooting. Do not call a successful request with zero rows an authorization failure, or convert a failed request into zero clicks. Finish with a record of which checks passed and which remain unresolved.
Common mistake: Deleting verification evidence after connection
A completed tool connection does not replace Google's ownership checks. Keep the DNS record, file or tag used for verification and include it in site-migration and team-handover notes. If access disappears later, check native Search Console ownership and user access before changing the tool's connection.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| No DNS permission | Use an applicable URL-prefix verification instead, or have the owner grant user permission | Use the target account to confirm the property can be opened |
| Verification succeeds but there is no data | Check the scope and dates, and confirm whether there is real search performance | Select the same property in native GSC and the product |
| The site disappears after authorization | Check account switching and permission changes | Re-read after restoring the correct authorization |
Connect the right website, not just the right Google account
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Example: you manage https://example.com/, but the tool lists only https://www.example.com/. Signing in succeeds; the required property is still missing.
- What it establishes
- A URL-prefix property covers its specified protocol and host. Account login, property verification and third-party authorization are separate checkpoints.
- What to do next
- Open the exact property in native GSC first. Verify ownership through an available supported method, then reconnect the tool using that same account. Stop if the tool requests permissions unrelated to your task.
What counts as a checked result
Record the selected property string and authorization scope. Confirm that a report for a known page loads; a verified property with no performance data is not a failed connection.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A connection record separating account identity, URL coverage, ownership and a successful data read.
- Stop and resolve this first
- If you cannot open the property with your own permitted account, obtain access before authorizing another application.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Verification succeeded, but there are no clicks. Should I reconnect?
Not on that evidence alone. Check the same property and a completed date range in native Search Console first. No native search data can be a valid state. Reconnect only when you have evidence of an authorization problem; investigate tool errors separately when native data is available.
Do I need to share my Google password?
No. Use the Google authorization flow and review its scopes. Do not send passwords, verification tokens or OAuth credentials in a public support ticket.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationProperty coverage and adding a website ↗
Continue with the relevant tool
After verifying ownership, connect the same Google account to AISEO Site and confirm the property shown in your search report.
See how it works →