Study first
Review the ideas behind the questions
Check the setup choices that let a team read Search Console data and handle simple discovery tasks. Focus on property type, verification, user access, sitemap submission, URL Inspection, and core report metrics.
Pick the right property before reading data
Search Console reports are tied to the property that was added. A wrong property can make reports look empty or incomplete.
- Adding a property does not change how the site appears in Google Search; it enables tracking and management in Search Console.
- A Domain property covers all subdomains, protocols, and subpaths for the domain.
- A URL-prefix property covers only URLs with the specified prefix and protocol.
In Practice
Use Domain for whole-site reporting
If the team wants one view across http, https, www, non-www, and subdomains, a Domain property fits that scope.
Use URL-prefix for a narrow section
If the team needs only one protocol or path prefix, use a URL-prefix property instead of assuming the whole domain is included.
Common mistakes
Adding `http://example.com` when the site actually reports under `https://example.com`.
Use the property type and URL scope that match the reporting need before judging missing data.
Q&A
Does adding a Search Console property improve ranking?
No. It lets the team track performance and manage the property; it does not change the site in Google Search.
Which property type covers all subdomains?
A Domain property covers the domain across subdomains, protocols, and subpaths.
Verify ownership and assign access carefully
A team can only trust Search Console setup when ownership and user roles are clear.
- A Domain property requires DNS record verification unless it is on a supported Google product.
- An HTML verification tag must be placed in the page head of the non-logged-in home page used for the property URL.
- Only a property owner can grant Search Console permissions to another user.
In Practice
Do not edit the verification token
Copy the exact tag or DNS value from Search Console; changing it can make verification fail.
Keep an owner on the property
If the only verified owner leaves, another person should verify ownership so the team keeps access.
Common mistakes
Asking a full user to add the new agency account.
Ask a property owner, because only owners can grant permissions to other users.
Q&A
Where should an HTML verification tag go?
Put it in the head section of the non-logged-in home page that matches the property URL.
Use beginner reports for the right job
Sitemaps, URL Inspection, and performance metrics answer different questions. A basic audit should not use one report as a substitute for all others.
- The Sitemaps report submits a sitemap URL; it does not upload the sitemap file to Google.
- URL Inspection can show Google index information for a specific URL and can test the live URL.
- Search Console performance reports include impressions, clicks, average position, and click-through rate.
In Practice
Submit a sitemap only after it can be fetched
Post the sitemap on the site, test that Google can access it, and then submit the tested URL in the Sitemaps report.
Use URL Inspection for one page
When one page is missing or recently fixed, inspect that URL instead of reading a sitewide count as the whole answer.
Common mistakes
Treating a sitemap submission as a guarantee that all URLs will be indexed.
A submitted sitemap can be fetched and used for discovery, but crawling and indexing can still take time and are not guaranteed for every URL.
Q&A
What does click-through rate mean in Search Console?
It is clicks divided by impressions for the reported Search Console data.