Search Console is the free tool where Google shows you how it sees your site: what it indexed, which searches bring people to you, and what problems it found. Setting it up takes one sitting, and the choice that matters most is made in the first minute: a Domain property or a URL-prefix property.
What Search Console is, and the property choice
Search Console is not an analytics suite and it is not a ranking tool. It reports on your site’s presence in Google Search, and it does not let you pay for or request better placement. I think of it as Google’s side of the conversation, while analytics tools tell you what visitors do once they arrive. Do not expect the two to show identical numbers.
When you add a site, Google asks you to pick a property type. According to Google’s Search Console Help:
- A Domain property includes all subdomains (such as m and www) and multiple protocols (http, https and ftp). It must be verified with a DNS record.
- A URL-prefix property includes only URLs that start with the exact prefix you enter, protocol included. So
https://example.com/does not coverhttp://example.com/orhttps://www.example.com/. It supports several verification methods.
For a bilingual site, the Domain property is usually the better starting point, because it catches everything in one place whatever your URL pattern is. You can add URL-prefix properties later for a single section if you want a narrower view.
Setting it up step by step
- Sign in and add a property. Open Search Console with the Google account that will own the site’s data, and choose Domain.
- Verify with DNS. Google gives you a verification record. Add it at your domain registrar or DNS host exactly as shown, save, and return to Search Console to confirm. DNS changes can take a while to spread, so if verification fails at first, wait and try again rather than adding the record twice.
- Leave the record in place. Treat it as permanent, not as a one-time step. Deleting it after setup is a common way to lose access later.
- Give your team their own access. If a developer or editor needs the data, add them as users from the settings rather than sharing your Google password. My rule: owners are people who would still be responsible for the site in five years; everyone else gets lesser access.
- Submit your sitemap. Google recommends submitting it through the Sitemaps report, which then shows you when Googlebot accessed it. If your CMS already generates one, submit that address.
- Open the Performance report. Google describes it as showing how much traffic you get from Google Search. You can see the search terms that bring people to your site (queries), along with pages and countries.
- Check Page indexing and URL Inspection. The Page indexing report lists which pages are indexed and why others are not. The URL Inspection tool gives the current index status of a single page, useful after you publish or fix something important.
- Look at Core Web Vitals. Google says this report shows how your pages perform based on real world usage data. It is field data from actual visitors, not a lab test.
- Let the emails come to you. Google states there is no need to sign in every day; if it finds new issues on your site, Search Console emails you.
Example: reading a bilingual site
Take a site with Arabic pages under /ar/ and English pages under /en/, verified as a Domain property. A few habits make the data far more useful.
In the Performance report, add a page filter for URLs containing /ar/, then another view for /en/. Compare the two sections separately, because they often have different audiences, different countries and different seasonal patterns. Ramadan, for example, can shift Arabic reading habits in ways your English section never shows.
In the queries list for the Arabic section, look for spelling and dialect variants of your main topics. Readers may search the same idea with different hamza forms, dialect words or English loanwords mixed with Arabic. That is real vocabulary from your own audience, and it is far more trustworthy than a translated keyword list.
If your Arabic pages use Arabic slugs, the Page indexing report and URL Inspection may display them percent encoded, as long strings of %D8 and %D9 codes. That is normal. Paste the URL into your browser and it will decode.
Monthly review checklist
| Check | How | Tool |
|---|---|---|
| Ownership is verified and stable | Confirm the DNS record still exists and verification is active | Search Console settings and your DNS host |
| Right people have access | Review the users list and remove old contractors | Search Console settings |
| Sitemap is being read | Check the last read date and any errors | Sitemaps report |
| Traffic trend by language section | Filter pages by /ar/ and /en/ and compare periods |
Performance report |
| New query variants | Sort Arabic queries by impressions and note new wording | Performance report |
| Important pages are indexed | Inspect key URLs after major edits | URL Inspection |
| Indexing reasons make sense | Read the reasons for not indexed pages before acting | Page indexing report |
| Real user experience | Review the URL groups flagged as not good | Core Web Vitals report |
| Alerts handled | Go through Search Console emails since the last review | Email inbox |
Common mistakes
- Verifying one URL prefix and missing data. If you verify only
https://www.example.com/but some traffic lands on the non-www or http version, those URLs sit outside that property. A Domain property avoids the gap. - Removing the verification record. It feels like cleanup, but it can cost you access.
- Treating every “not indexed” status as an error. Google says indexing is not guaranteed and not every page it processes is indexed. Redirects, duplicates you intentionally canonicalized, and pages you set to noindex will appear here by design. Read the reason first.
- Checking daily. Search traffic moves day to day. Reacting to every dip leads to rushed changes. Google itself says the emails will tell you when something needs attention.
- Expecting Search Console to match Analytics. They measure different things from different vantage points. Use each for what it answers.
Sources
- Google Search Central, documentation on getting started with Search Console, consulted 17 January 2026, https://developers.google.com/search/docs/monitor-debug/search-console-start
- Google Search Console Help, article on adding a website property (Domain and URL-prefix properties), consulted 17 January 2026, https://support.google.com/webmasters/answer/34592
- Google Search Central, documentation on building and submitting a sitemap, consulted 17 January 2026, https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
- Google Search Central, documentation on using Search Console and Google Analytics data, consulted 17 January 2026, https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console
- Google Search Central, documentation on how Google Search works (crawling, indexing, serving), consulted 17 January 2026, https://developers.google.com/search/docs/fundamentals/how-search-works