These days, the first thing I do after setting up a new website is link it to Google Search Console. Previously known as Google Webmaster Tools, this free resource from Google shows how the search giant crawls and indexes websites. It is invaluable for anyone needing to monitor:
- Their site’s performance in search results
- Content accessibility
- Malware and spam issues
Frankly, anyone who has a website should use this excellent tool. If you’re not already using it, here’s how you can get started.
Note: If you find this guide to be outdated, please reach out to me on Twitter (@seanvwork) and I’ll have it updated.
Getting Started with Google Search Console
I’m going to assume that you are one of the millions of people who already has a Google account. If you don’t, get one. If you do, then go to the Google Search Console page and sign in.
Step 1: Add a Property
Before you can start using Google Search Console you have to add something to track. Google calls this a “property” and it can be either a website or an Android app. For this tutorial, we’ll be working with websites.
Click the “Add a property” button near the top of the homepage. Type in the name of the property and click the Add button.
Step 2: Verify Your Site
When you visit the verification page, you will get a number of verification options. Google usually recommends HTML file upload, but other choices are:
- Adding an HTML tag to your home page
- Signing into your domain name provider
- Verifying with your Google Analytics or Google Tag Manager account
When you select HTML file upload, you get a file to upload to your hosting provider. I’ve used this method in the past, and it’s reasonably straightforward to get it into the correct (usually root) folder using the file manager of your web hosting control panel.
However, if you’re running a WordPress-based site and have installed Yoast SEO, there’s an easier way to add the HTML tag to your site. Choose the HTML tag option in Google Search Console, and then copy the code that follows “content=”, excluding the quote marks.
Go to the Yoast dashboard and click on the “Webmaster Tools” tab. Paste the code into the appropriate box. Then return to the Google Search Console dashboard and hit the “Verify” button.
If verification works, you will see a big green check mark.
This time, I used another verification method. I clicked on the Google Tag Manager button, clicked again to login to my Google Tag Manager account and verification happened.
If verification fails, here’s a list of common issues that might be the cause.
Although I usually use a single verification method, Google recommends you use more than one method to make ownership more “resilient.”
Pro tip: You will need a different Google Search Console property for each version of your site. To get the most data, add them all. My Google Search Console account includes HTTPS and HTTP and WWW and non-WWW versions of my site, making four properties for a single site.
Step 3: Link Google Analytics
Once your site is verified, the next step is to link it to Google Analytics. This allows the two accounts to share information, providing even more data for you to analyze. To do this, click on the property name in the dashboard, select “Google Analytics property” from the drop-down menu under the gear, select the appropriate Google Analytics profile on the next screen, and press save.
Step 4: Add a Sitemap
One key benefit of Search Console is you can make sure Google is crawling your site properly and indexing all relevant pages. To do this, you need to add a sitemap in one of the formats supported by Google. Most people recommend an XML sitemap, which can also be submitted to other search engines.
One way to create a sitemap is to use an online tool like XML-Sitemaps.com. But for WordPress-based sites, it’s even easier to get your sitemap using Yoast SEO. Click on the “XML Sitemaps” link in the WordPress dashboard, ensure the sitemap function is enabled, and then click on the appropriate button to see links to your sitemaps.
Grab the URL you need (I usually upload the posts and pages sitemaps), and then go back to Search Console. Navigate to Crawl > Sitemaps > Add/Test Sitemap. Paste the relevant part of the URL (Google includes the start of this by default), and then refresh to see your sitemap data.
Tip: If you’re using Yoast, you can simply edit the URL of the sitemap to add it to a different property. Although my site is HTTPS and WWW, I was able to remove the WWW part of the URL in order to add the sitemap to the non-WWW property in Search Console.
Step 5: Submit Your Site to Google
If you’re anything like me, you probably submitted your site to Google when you set it up to ensure (or at least try to ensure) that the search bots were crawling your site. Google Search Console gives you another way to do this.
Go to Crawl > Fetch as Google, and then click the “Fetch” button. When it’s complete, hit the “Submit to Index” button.
When it’s done, it will report that the URL and linked pages have been submitted to Google’s index.
Exploring Google Search Console
Once you have those five steps out of the way, it’s time to explore Google Search Console in more detail and see what you can learn about your site’s search performance and how you can continue to improve it.
When you login to Google Search Console, there’s a list of all the sites you have added. The list includes messages relating to any recent issues Google has found with any of your sites.
If there’s a message, click on the link at the end to see more details and access help on resolving the issue.
Otherwise, click on your site’s URL to access Search Console features for that site. In addition to the Dashboard and Messages center, Search Console has four main sections: Search Appearance, Search Traffic, Google Index and Crawl. There are also additional links for Security Issues and Other Resources. Each of the main sections has several sub-sections addressing different aspects of your site.
This section deals with how your site looks in search results which can affect how many people click on your search listing. The first item under this heading is Structured Data. We’ve talked before about semantic search and schema markup; this section is where you can see how your content stacks up.
If you’ve just added your site, then there won’t be much to see but you can guide Google by using the Data Highlighter tool which is also in this section. This allows you to indicate the correct microformats for your content. For example, I used it to indicate that most of the content on my blog should be listed as Articles.
To use the Data Highlighter, click on the link, and then click “Start Highlighting”.
Add a URL for a recent post and select the type of post from the drop-down list. I chose “Articles.” There are several types to choose from including Reviews and Events.
Click “Tag this page and others like it.” This will tell Google to treat other similar pieces of content in the same way.
The content comes up in a window next to the highlighting interface. Highlight each piece of information on your content and apply the appropriate tag.
When you have finished, click the Done button and Google will attempt to find similar content for you to check. When you have checked that the pages look similar, click Create Page Set to get the chance to check a few sample pages.
When I did this, Google added my homepage, but it was easy to remove while checking the page set. Google wanted 10 example pages in all. Then I was able to publish the set.
Rich Cards can also be seen in this section. Introduced in May, this is another way to display schema markup, and it’s initially available for movies and recipes in mobile search results in English. It looks as if eventually, Google will migrate the structured data to this section. You can go back at any time and review your example pages or add new ones.
The HTML Improvements section is where Google highlights content issues such as duplicate meta tags or content, missing meta tags, and more. It’s a way to make sure that your search results look as good as possible.
Sitelinks shows you the different links that appear under your main listing in the search results. Here’s how the Crazy Egg site shows up in search.
Those links should appear in the Sitelinks section of Search Console. Mine have all disappeared since the switch to HTTPS but they never showed up in Search Console anyway.
The last part of the Search Appearance section looks at Accelerated Mobile Pages (AMP). Launched in October 2015, AMP aims to serve faster content to mobile users, and there’s speculation that it will become a ranking signal. This section points out any AMP errors and gives guidance on how to fix them.
See this guide from Yoast for help with setting up AMP for your WordPress site.
The Search Traffic section analyzes your site’s performance in Google search. The first sub-section is Search Analytics, which includes graphs and tables tracking clicks, impressions, click-through rate and position for the search queries that lead people to your site. You can click the table to change sort order. You can also look at data for pages, countries, devices, and search type and gain good insight into how your web visitors search for and find your site.
The stats aren’t always identical to the data found in your Google Analytics account. That’s because, as LunaMetrics explains, while there’s some overlap, the two tools may be reporting on different types of traffic.
Links to Your Site gives more detail on the sites linking in, the top content linked to and the main phrases used to link to your content.
You can click on any link to get more detail on the link profile. In the screenshot below, I can see which of my pages have been shared on Pinterest. This is useful data for marketing, as it’s one way to identify gaps in your strategy.
Next, the Internal Links section allows you to examine your internal linking profile. Again, click on a link to get details on which internal pages link to it.
The Manual Actions section tells you about any penalties imposed by Google for potential web spam. You will usually get an email warning as well. It’s very useful: when one of my sites had been compromised by a code injection, I first found out about it via my Search Console account.
International Targeting is useful for international SEO. If you are using hreflang meta tags to indicate a particular language, data on this will appear here. You can also set the country you want to target with your site. For example, although I don’t live in the US, most of my clients are there, so I set the US as my target country in this section.
Mobile Usability points out errors that will lead to loss of ranking in mobile search results. Page elements that are too close together, poor viewport settings, and other issues will appear here. You can click on the arrows to the right for more detail on each error found.
The third main section of Search Console is the Google Index section. It’s divided into four sub-sections.
Index Status shows you how many URLs from your site have been added to Google’s search index. If you click on the advanced tab, you can also see if your robots.txt file is blocking any URLs and whether any URLs have been removed. Data is for the past year.
Content Keywords shows the main words and phrases used within your content. It’s a good way to find out if there are overused terms.
Blocked Resources lists any URLs blocked via the robots.txt file, and Remove URLs is a tool to ask Google to temporarily de-index some of your content.
The last main section provides data on what Google’s search bots find when they crawl your site. It has six sub-sections:
Crawl Errors shows errors that the Googlebot found when trying to crawl your site. It shows errors both for desktop and smartphone.
Crawl Stats shows the past 90 days of Googlebot activity. Look out for spikes or drops. Spikes may mean you have added lots of new content; drops may mean the bot is blocked somehow. Google lists other reasons for spikes and drops in its help files. I believe the spike in the screenshot below was because I switched my site to HTTPS, forcing an increase in pages to crawl.
As we saw in Step 5 above, Fetch as Google lets you see how Google renders your site. The robots.txt tester shows you how Google sees that file, and it allows you to check if you are blocking the crawler in any way. As we saw in Step 4, Sitemaps lets you submit sitemaps to Google so its bots know where all your links are. Finally, URL Parameters lets you alert Google about which pages to crawl to help you avoid duplicate content. Learn more about this from Google.
If there are any security issues with your site, they will appear in the relevant section. Finally, Google rounds out Search Console with a collection of helpful tools.
Of these, I’ve found the structured data testing tool and page speed insights most useful for checking how my schema markup looks and assessing desktop and mobile page speed.
I’ve found Google Search Console to be an invaluable tool for managing and troubleshooting all aspects of my site’s search listing. It’s also helped me keep my sites more secure by highlighting potential malware and spam issues. Everyone should use it.
Let us know in the comments if we have missed anything or if you want a portion of this guide explained in more detail!
The first version of this guide was created by Sharon Hurley Hall.