New Google Search Console report checks site speed

Google is rapidly expanding the capabilities of Search Console — its must-have tool for site owners/managers. Not too long ago it was a couple of new structured data reports and today we’re talking about an enhancement report dedicated to site speed. It’s important to have a fast site and Google’s new tool helps you monitor it and improve it. Here’s is a quick guide to its capabilities.

What is the Speed report in Google Search Console?

The new Speed report gives you an idea of how fast or slow your pages load over any given time. It gives you insights that were almost impossible to get up until now. Running page speed analysis on your complete site is not something the average user can do. Testing a couple of pages in PageSpeed Insights, fine, but 1,000 pages? The new Speed report in Google Search Console gives you an idea of how your site loads. It puts all pages in buckets conveniently labeled slow, moderate and fast. 

The new Speed report overview in Search Console (desktop view)

As you know, site speed has been a hot topic for quite a while. Google even declared it a ranking factor. The search engine is rolling out all sorts of initiatives to help visualize site speed and prioritize improvements, like PageSpeed Insights and Lighthouse. Sometimes, they do it quietly, but other times it’s a little bit over the top. Case in point: Chromes new “speed badge of shame”. It is one of the indicators in the Chrome browser that helps users understand why a site may be loading slower. In reality, this is more a not so subtle jab at site owners to do something about their slow sites.

Chrome’s upcoming slow site badge

This focus on site speed is understandable. Site speed is user experience and users expect fast. But in regards to all those pretty numbers and colors, it’s hard to know what to look for. But as our own SEO expert Jono Alderson loves to say: “Don’t optimize for scores — just make it faster.” Scores say a lot, but all that matters is the perception of speed by users. How quickly can you make your page feel ready?

What does the Speed report do?

The Speed report looks at the pages on your site, checks their loading speed in the Chrome User Experience report and puts these into buckets. There are mobile and desktop specific checks and these might differ. Due to hardware and network differences, it is harder to get a good score on mobile than it is on desktop. You’ll notice, though, that the same URLs are often troublesome both on mobile as well as desktop. They might load slightly faster due to changes in test setting, but they are a point of interest nonetheless.

Two specific reports help you analyze the different sources

While not the end-all tool for measuring site speed, the Speed report is a valuable addition to Search Console. It helps you find problematic URLs which you can check in PageSpeed Insights to get a deeper understanding — plus ways of fixing it. This way, you can keep an eye on all speed-related things, spot trends, make improvements and keep track of the results of those changes. 

Where does it get its metrics?

The cool thing about the Speed report is that it uses data from the Chrome UX Report. The Chrome UX Report is a public data set of real user experience data collected from millions of opted-in users and websites. This way, loads of data are collected — like connection type, type of device and much more — from real situations and used to give a better understanding of performance in the real world. This data is put to good use in several speed-oriented Google tools, like PageSpeed Insights and Lighthouse.

What should I look for?

When looking at site speed tools it is easy to focus on the wrong stuff. Many tools check site speed in particular circumstances, like a set location at one point in time. There’s not enough context to make a decision based on this data. That’s why our advice in this has always been for you to look at a multitude of site speed tools. Combined these will give you a better handle on the problem.

The Search Console Speed report has been built around two metrics: First Contentful Paint and First Input Delay. Here’s what these metrics mean:

  • FCP (first contentful paint): The first contentful paint happens when the first element of a requested page appears on the screen. This gives users the confirmation that the page is actually loading.
  • FID (first input delay): The first input delay is the time between the first interaction of a user with an element on the requested page and the reaction of the browser to that input. How quickly your page reacts to input is of utmost importance for it to appear fast and responsive.

The results lead to slow, moderate or fast pages. According to Google, the speed of a URL is the lowest speed assigned to it. So if a page has a slow FCP, but a moderate FID it is considered slow. If it has a fast FCP and a moderate FID, it is considered moderate.

These insights give you a good idea of how your pages are performing. As said before, you probably need to run a couple of more tests to get the full picture.

Further analysis on a per-URL basis in PageSpeed Insights

URL grouping

Instead of showing a gazillion URLs and the corresponding results, Google uses aggregate scores and URL groups to make the results slightly less intimidating. For any issue, you’ll see a number of URLs getting the same score or issue. So it might be that from a specific URL, 70 other URLs suffer from the same performance issues. That makes it easier to uncover issues on a grander scale because all these pages probably have the same problems. Of course, you can do a deep-dive and check individual pages by clicking on the URL list and picking a URL to analyze using PageSpeed Insights.

Grouping URLs with similar perfomance issues makes the report easier to digest

Aggregate scores

The same goes for scoring. Grouping makes it easier to digest the results. The Speed report in Search Console focuses mainly on FCP and FID, as mentioned above. It’s a good idea to keep an eye on PageSpeed Insights as well, as this has a multitude of other metrics, graphics of the loading process and suggestions to improve the results.

In the Speed report, the FCP and FID are calculated from all the visits to those particular pages. 

  • Aggregate FCP: The aggregate first content paint is the time it takes for 75% of the visits to a URL in the report to reach FCP.
  • Aggregate FID: The aggregate first interactive delay is the time it takes for 95% of the visits to that URL to respond to interactions on that page. 

The calculation of these scores continues to fluctuate due to outside influences. That’s why you might see the trend line go up and down.

The aggregate FCP is the point when 75% of visits to that URL get FCP

Fixing issues and validating fixes

The Speed report allows you to monitor your site for speed-related issues. It helps you find problems and prioritize their resolution. Once you or your developer have run through all the suggestions and improvements you can validate the fix. Google will then monitor the pages for 28 days to see if the issue is fixed for these URLs. 

Site speed resources

This post is not about telling you how to fix your site speed issues, but rather guiding you through the new Speed report that might give you the insights you need. To get practical, you can start here:

Last but not least, an incredible source of information: Jono’s slide deck on site speed from a talk at SMXL Milan.

The post New Google Search Console report checks site speed appeared first on Yoast.

Search Console showing errors in your product structured data?

Google’s recent run of enhancement reports in Search Console gives you lots of insights into how your site is performing in search. Sometimes, though, it gives you stuff to think about, like errors or improvements to make. For instance, if you run an online store, you’re bound to have come across this structured data error: “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified.” There’s a very easy solution for this if you run WooCommerce and Yoast SEO: our WooCommerce SEO add-on.

The “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” error in Google Search Console 

The “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” happens for a lot of online stores. It means that Google misses several properties in your product schema implementation. By not offering these, your product listings will not reach their full potential in search. This way, Google has a hard time tying all the product-specific properties together to paint a full picture of your product. In some cases, though, they manage, but why let them figure it out? Fixing this becomes imperative if you want a better chance of standing out. 

Who doesn’t want a product listing like the one pictured below?

Valid product schema might lead to eye-popping rich results like this one from Reverb

Oftentimes, however, invalid or incomplete structured data might cripple your perfomance in search. Errors are all too common, like the one in the screenshot from Search Console below.

The “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” error is very common

Help is at hand: Yoast SEO & WooCommerce SEO

WooCommerce is huge in the WordPress world. According to W3Techs, 15% of all WordPress sites run an online shop on the WooCommerce platform. That’s amazing. We have a plugin that helps customers improve their online store: WooCommerce SEO. This addon ties neatly into Yoast SEO, including the big schema graph we build for every site. It also greatly improves the product schema output by WooCommerce. 

If your site runs on WooCommerce and Yoast SEO you need WooCommerce SEO. Besides all the cool behind-the-scenes improvements, it fixes that dreaded “Either ‘offers’, ‘review’ or ‘aggregateRating’ should be specified” error for you: automatically! It gives Google everything it needs to figure out your products are products and thus increases your chances of getting those important rich results.

Why you should fix this error

Google is increasingly betting on schema structured data to help understand the world. If your site offers search engines enough context about what’s on it, the rewards could be great: rich results. And for some types, visibility on other devices like smart speakers or visual assistants.

Getting your product schema right, means you can get these types of results. The one earlier in this article is from Reverb and shows a nicely formed product rich results, with breadcrumbs, product information, ratings and reviews, pricing details and an in-stock message. This is all powered by product schema. 

Reporting on the performance of products 

To help you track how your products are doing, Google recently added a Product enhancement report to Search Console. This report lets you know if your products are correctly structured and, therefore, eligible for rich results. This week, Google also announced that it will allow you to see the performance of your product in the search results. You can now find a new Product line in the Search Appearance section of the Search Performance section. 

Search Console now has a product results view in Search Appearance

This report shows exactly how well your products are doing: how many impressions did they have and how many clicks? This is invaluable data to improve your product listings. 

Fix the error and check your listings

Seeing the product schema error in Search Console? Using Yoast SEO and WooCommerce? Well, you’re in luck. The WooCommerce SEO add-on is the glue that ties the product schema structured data between those two platforms together. It fixes that dreaded error and gives you a better chance at getting your products noticed in Google!

The post Search Console showing errors in your product structured data? appeared first on Yoast.

Get Google’s new video reporting with the Yoast Video SEO plugin

Yesterday, Google announced a new addition to the rapidly expanding lineup of enhancement reports in Search Console. This time, it’s all about video! You can now not only see how your video performs in search, but also if your videos have valid structured data so they are eligible for rich results. Need help getting your videos noticed in Google? We’ve got just the thing!

What’s this Video enhancement report?

Video is incredibly important. Humans are producing an huge amount of video and surfacing the right one at the right moment is a real struggle for a search engine. Google now gives you two new tools to help you improve the performance of your videos in search. The first one is all about helping search engines figure out if there is a video on a site. The second one is about visualizing your video’s performance in search.

By adding structured data to your page, you can identify the most important elements plus its characteristics. By doing this, you make it crystal clear to search engines what is what. As a result, you might be awarded a rich result if the search engine deems your content the best fit for the query. For videos, this might include information on a video’s duration, upload date, and other metadata, as well as previews.

Google is pushing structured data very hard and this latest report shows how important video has become for them and for you. You can now see how your video performs and if there are any technical errors or warnings that keep it from performing better. From here, it’s an easy fix.

But how can I get this for my videos? 

That’s easy: the Video SEO for WordPress add-on for Yoast SEO! As you might know, we launched a massive and innovative Schema structured data implementation in Yoast SEO 11.0. This was the first implementation of its kind — the first to completely tie the content of your site together in code so search engines are eager to gobble it up. Not only that, by connecting everything a search engine now knows what goes where and how it all fits into the bigger picture. This is all available for free in Yoast SEO.

Our add-ons extend this structured data implementation. The Video SEO plugin, for instance, adds specific structured data for videos. And the awesome thing is: you don’t have to do anything to get this on your site. It’s all automatic and it all ties neatly into the rest of the structured data we generate for your site. Just install Video SEO.

Here’s how the new report picks up our structured data, without us having to do any additional work. You can even see the source code by clicking on an example URL.

Click on a post to see the structured data highlighted

So, if you need search engines to understand your videos — who doesn’t? — you need Video SEO for WordPress

What else can I do in the Google Search Console Video enhancement report?

The Video enhancement report not only shows you if Google has trouble understanding your video content, but also how your videos perform in search. In the Performance tab, you’ll find a new Search Appearance type for video. This overview gives you an idea of how many times your videos appear in search and many people click on it. Of course, you can filter it to your hearts content.

See how your video performs in the search results

Help search engines understand your videos

The new Video reports in Google Search Console go a long way in helping Google identify videos via valid structured data. Not only that, it gives you the insights you need to help identify issues and improve performance. All in all, this is a great addition to the treasure trove that is Google Search Console!

The post Get Google’s new video reporting with the Yoast Video SEO plugin appeared first on Yoast.

How to do a one-page analysis in Google Analytics

I often get a request from our Blog team about one of their pages. Sometimes they want to know if the page has gotten more pageviews or they notice something weird and they want me to find out what’s going on. And this time they wanted more insight in the performance of one particular page. I want to share with you how I deal with this request.

So the other day I got a request to check the performance of our Blog homepage. We want to optimize that page so it fits better with the need of our audience. If you have an idea about that, you can leave your feedback in the comments section below this post.

Page level analysis

The first thing I had a look at is how ‘popular’ the page is and if it’s worth the effort to spend time and resources on this page. I went to the All pages report in Google Analytics, which you can find under Behavior –> Site content and did a cmd+F or ctrl+F search for the page https://yoast.com/seo-blog/. If you can’t find the page you’re looking for; it’s because it probably isn’t within the first ten results. So you need to expand your table first; you can do this on the right bottom of the table.

search for a page in Google Analytics

I notice it’s at position 32 if you look at the number of pageviews, which is a reasonably high position and thus worthy of further investigation. I also notice that in 6,327 of the cases it’s an entrance page, this means it’s in 35,3% of the cases the first page of the session (6,327 / 17,931 * 100).

You can also search for a specific post in the search bar to see just the metrics of that page but sometimes other pages show up as well.

Search for one page in Google Analytics

If the page is in blue letters, it means you can specify even further when clicking on it because it’s a link. Or you can use regex; regex stands for “regular expression”. Lunametrics made this fun regex guide that shows you how you can use regex in Google Analytics. It may sound a bit scary, but if you know the basics, it’s quite doable and will make your Google Analytics life a whole lot easier. Here’s how a regex would look if I just wanted the SEO blog homepage:

^yoast\.com\/seo-blog\/$

Use regex in the search bar in Google Analytics

But in this case, you can just as well click on the page to see just the metrics of that page. Try to understand what the metrics are saying and how it compares to the site’s average. In this case, for a page that’s built to guide people to blog posts of their interests, a bounce rate of 50.48% is fairly high. That means that in half of the cases, people didn’t do anything on that page! That’s not what the page is designed for.

I was also curious to see if this page gets a lot of mobile traffic, so I added a secondary dimension with the Device category. I then checked what the metrics told me.

Adding secondary dimension: device category in Google Analytics

About 10% of the page views come from a mobile device. You can see it has a higher bounce rate so checking the mobile experience is a good idea.

Trend analysis

And, I was curious to see how the page developed over time, so I added a wider timeframe to check if I saw something unusual. You can adjust the graph you’re seeing. Perhaps you’re interested if Bounce rate declined or not. You can select this metric and you’ll see the trend of the bounce rate of that page.

Adding a wider time frame in Google Analytics

Session level analysis

I then looked at this page from a page level. But, I had more questions about this page. If people are entering our site through this page, where are they coming from? So, I had a look from a session level perspective. I went to landing pages and did the same search as in the All pages report.

Finding a landing page in Google Analytics

It’s at position 65 and obviously has 6,327 sessions since we saw that in the All pages report at entrances. I once again looked at the metrics and tried to understand what they’re telling me. The number of pages per session, the bounce rate and the number of ‘new’ users. And I had a look at conversions.

I then dove in further, clicked on the page and added a secondary dimension: medium, so I could quickly see where traffic is coming from. I noticed that we have a lot of traffic that we don’t know the source of. So that’s something to explore further. In second position comes our plugin and third is organic search traffic. Which is interesting to see because I’m curious with what keywords people end up on that page and if we rank properly on that keyword or keyphrase. With that information, we can improve the SEO of that page even further.

Again, I had a look at bounce rates, pages per session, number of new users and possible conversions. Thinking about if the page is doing what it’s supposed to do.

Google Search Console analysis

I needed to go to Google Search Console to find information about the keywords or keyphrases the blog homepage ranks for. You go to your Google Search Console account and click on Search results. Then you set a filter that exactly matches the URL of your page, in our case: https://yoast.com/seo-blog/.

Adding a page filter in Google Search Console

You now see the queries and position of that page. Take a look at the metrics and try to understand what’s going on. It’s especially interesting if you have a lot of impressions but a low clickthrough rate (CTR).

Results of page filter in Google Search Console

Conclusion

What can we learn from this analysis? For one is that it’s worth the while to put some time and effort into this page. I learned that we can optimize the SEO of that page even further and that we can put some more effort into ranking for the keyword SEO blog.

I also noticed that it’s quite a popular page, but the bounce rate is too high for my taste. Especially when the goal of the page is to guide people to a blog post of their interest. So, there needs to be interaction with this page. We need to find out what people expect to find on this page. So, therefore, extra information is needed. That’s why we added a simple poll on this page, using Hotjar. We also created a heatmap with this tool to get a better understanding of how people behave on the page.

Combining data gives you a far more holistic view and will make sure you can draw more reliable conclusions. Data we can use to optimize the blog homepage even further. The perfect dataset doesn’t exist but we can try to get as far near perfection as possible.

The post How to do a one-page analysis in Google Analytics appeared first on Yoast.

Where did my Search Console errors go?

If you’ve noticed that your Yoast SEO Search Console report looks surprisingly empty, it’s because Google have shut down the system which provides data about their crawl errors.

There’s no need to worry, though – we knew this was coming, and we have plans for the future. Your Search Console report won’t show any information for now, but nothing on your site will break, and you don’t need to take any special action.

The good news is that we’re already building our own, brand new systems for error reporting and management. We think it’ll be even better and more useful than the old Google Search Console integration.

What happened?

If you actively manage your website’s SEO, then you’re probably familiar with Google Search Console. It’s a great way to discover and manage any errors which Google may have encountered when crawling and reading your site.

A snapshot from yoast.com’s own Google Search Console account. We should fix those errors!

Until recently, Google provided us with a way to extract information from their systems. That meant that we could show you Google’s crawl errors and issues right inside your site’s admin area, via the Yoast SEO plugin.

Help! What is an API?

An API is a system which allows software to talk other software. The Google Search Console API allows websites to connect to Google’s systems, and to request information about your website. It used to provide information about crawl errors, but no longer does so.

Having those issues listed inside your side admin area made it easy for you to fix those issues ‘on the fly’. You could set up redirects, tweak pages, and mark individual issues as resolved – without ever leaving your website.

Unfortunately, Google have removed the API which powered this system.

That means it’s no longer possible for us – or anyone else – to get information about your crawl errors. The only way to get this information (at the moment) is for you to manually visit your Google Search Console account.

What does this mean for me?

Nothing will break on your website, and you don’t need to take any action. You’ll just find that if you visit your Search Console admin page in your WordPress website, you won’t see any errors. You’ll see something like this empty table:

You won’t find any errors in your Search Console report, as it’s no longer possible to retrieve them from Google.

That empty table doesn’t necessarily mean that you don’t have any errors – it just means that we can’t fetch or show them to you.

If you want to go and check your errors and issues, you’ll need to go directly to your Search Console account. If you’re not sure where to start, you can follow this handy guide to using Search Console.

Creating and managing redirects

We know that many of our premium users rely on our Search Console integration to create redirects for broken pages and URLs.

If you’ve set up redirects through the Search Console section in the past, don’t worry – nothing’s been lost, and your redirects still work.

In the future, you’ll just need to use the ‘Redirects’ section to create them, instead.

You can create redirects for broken pages or URLs in Yoast SEO premium, via the Redirects system

We knew this was coming, but we expected a replacement system

We’ve known that Google planned to remove support for error reporting from their Search Console API for a while. It provided data from the ‘old’ Search Console system, which has been gradually replaced or removed as they moved people to the ‘new’ Search Console system. As such, we knew it had a short lifespan.

We’d hoped and assumed that they’d replace the API, in the same way that they’d moved or replaced other functionality from the old system.

What we didn’t expect was for them to simply ‘turn it off’, without providing an alternative or updated solution. We’re a little disappointed about how this has been handled by Google, but, we have some options.

What happens next?

For now, you don’t need to do anything.

We’re chasing Google for updates, and once we hear more from them about what they have planned – if anything – we’ll update our information to reflect that.

Their documentation and communications have hinted at planned future capabilities and support, but there’s nothing out there yet. So we’re waiting, watching, and asking questions about what’s in the pipeline (we’ve particularly high-hopes for Google’s SiteKit WordPress plugin, which is currently in beta).

In the meantime, we’re considering alternative options, processes, and ways in which we can replace or supplement this data. We already have some exciting plans:

In the short-term: We’ll be building an import tool, which lets you upload error reports which you’ve manually downloaded from Google Search Console. We’ll also support uploads from some other tools, which we’re excited about. We’ll share more news that soon.

In the mid-term: We’ll be looking to partner and integrate with a wide variety of your favourite SEO tools and platforms, so that we can import their data about your website’s errors and crawl issues. That’ll give us much richer, more diverse, and more interesting data than ever.

We’ll keep you updated with our progress, and we’ll let you know if we hear back from Google about their plans.

The post Where did my Search Console errors go? appeared first on Yoast.

Live indexing for Bing & Google coming to Yoast SEO

As we announced at YoastCon, we’re working together with Bing and Google to allow live indexing for everyone who uses Yoast SEO. In an update currently planned for the end of March, we’ll allow users to connect their sites to MyYoast, our customer portal. After that we’ll roll out live indexing, which means every time you publish, update, or delete a post, that will be reflected almost instantly into Bing and Google’s indices.

How does this work?

When you connect your site to MyYoast, you’ll authorize it to send messages back and forth. One of the types of messages that will be sent will be when you publish, update or delete anything on your site. We’ll pass that notification on to Bing, and Bing will check the changes within approximately one minute of you hitting the button.

You will not need to connect your site to Bing Webmaster Tools to do this. It’s all handled automatically. For Google the details on this are not entirely determined yet, but a Google Search Console account will probably be required.

We do, of course, recommend making use of both Bing Webmaster Tools and Google Search Console as they can give good insight into why your site is or is not performing well in the search engines.

If you’re reading this on Thursday (Feb 7, 2019), you might still catch one of Bing’s principal engineers, Arnold Overwijk, discuss this live at YoastCon through our live stream on Friday.

The post Live indexing for Bing & Google coming to Yoast SEO appeared first on Yoast.

What is Google Search Console?

Google Search Console (or ‘GSC’ for short) lets webmasters monitor and manage their websites through an official portal, and is crammed full with useful statistics. Having access to tools and data provided directly by the search engines can make optimizing your website much easier!

It’s a communication channel

Search Console accounts are the main, and official way in which Google communicates with individual site owners. By having a registered account, Google can send webmasters information about site issues, errors, or even penalties. It also provides some limited tools to allow you to contact them about site issues and feature requests.

It’s a control center

If you’re actively optimizing your website, you’ll understand that SEO is never ‘finished’. You need to be continually improving your content, refining your site settings, and minimizing your errors.

Search Console provides tools which help with this day-to-day management. It lets you do things like submit and monitor your XML sitemaps, ask Google to (re)evaluate your errors, or see how Google sees particular pages and URLs on your site.

XML Sitemap management in Google Search Console

It’s a performance dashboard

Your GSC account is full of useful information about how your website is shown and performing in search results. From mobile usability reports to visibility and clickthrough tracking, and much more.

If you’re serious about managing and optimizing your website, your GSC account is your nerve center for understanding when, where and how your site is appearing in Google.

Performance overview in Google Search Console

It’s a data source

Most of the data in Google Search Console can be extracted and integrated into other systems, like Google Analytics, and Yoast SEO!

That means that, if you’re running a Yoast SEO plugin, you can integrate some of your GSC data directly into your website. This can make it much easier to manage your errors, analysis, and redirects!

Check out our great guide on how to get that hooked up, and how to take advantage of the integration.

Ready to get started?

Anybody who runs or manages a website should be able to access a Google Search Console account, for free.

There are a few different ways to create and authorize your account, but the easiest is to integrate through Yoast SEO – just follow this quick guide to get things running!

Once you’re all set up, why not take a tour around Google Search Console with our great beginner’s guide?

The post What is Google Search Console? appeared first on Yoast.

The beginner’s guide to Google Search Console

Do you have your own website or maintain the website of the company you work for? Of course, to do this right, you need to keep a keen eye on the performance of your website. Google offers several tools to collect and analyze data of your website. You probably have heard of Google Analytics and Google Search Console before. These tools are free to use for everyone maintaining a website and can give you very valuable insights about your website.

Why everyone with a website should use Google Search Console

Google Search Console has been created to easily track the performance of your website. You can get valuable insights out of your Google Search Console account which means that you can see what part of your website needs work. This can be a technical part of your website, such as an increasing number of crawl errors that need to be fixed. This can also be giving a specific keyword more attention because the rankings or impressions are decreasing.

Besides seeing this kind of data, you’ll get mail notifications when new errors are noticed by Google Search Console. Because of these notifications, you’re quickly aware of issues you need to fix.

Setting up an account

To start using Google Search Console, you’ll need to create an account. Within the new Google Search Console, you can click on ‘add a new property’ in the top bar:

Google search console - add property

Clicking on the ‘Add a property’ button, you can insert the website you want to add. Make sure you add the right URL, so with ‘https’ if you have an https website and with or without ‘www’. For collecting the right data, it’s important to add the right version:

When you’ve added a website, you need to verify that you’re the owner. There are several options to verify your ownership.

For WordPress users who use Yoast SEO we recommend using the ‘HTML tag’ method:

You can easily copy this code and paste it into the ‘Webmaster tools’ tab within the Yoast SEO plugin:

After saving this, you can return to Google Search Console and click on the ‘Verify’ button to confirm. If everything is ok, you’ll get a success message and GSC will start collecting data for your website.

Features in Google Search Console

Now you’ve set up your account what would be the next step? Well, it’s time to look at some of your data! We’ll explore some of the reports and information available in the rest of this article.

Performance

Within the performance tab, you can see what pages and what keywords your website ranks for in Google. In the old version of GSC you could see the data of a maximum of the last 90 days but in the new version, it’s possible to see the data up to 16 months. Keep in mind that the data is available from the moment you set up your account.

If you check the performance tab regularly, you can quickly see what keywords or what pages need some more attention and optimization. So where to begin? Within the performance tab, you see a list of ‘queries’, ‘pages’, ‘countries’ or ‘devices’. Each of those sections can be sorted by the number of ‘clicks’, ‘impressions’, ‘average CTR’ or ‘average position’. We’ll explain each of them below:

Google search console - performance

1. Clicks

The amount of clicks tells you how often people clicked on your website in the search results of Google. This number can tell something about the performance of your page titles and meta descriptions: if just a few people click on your result, your result might not stand out in the search results. It could be helpful to check what other results are displayed around you to see what can be optimized for your snippet.

The position of the search result also has an impact on the number of clicks of course. If your page is in the top 3 of Google’s first result page it will automatically get more clicks than a page that ranks on the second page of the search results.

2. Impressions

The impressions tell you how often your website in general or how often a specific page is shown in the search results. For example, in the GSC account of our own website, Yoast SEO is one of the keywords our website ranks for. The number of impressions shown after this keyword shows how often our website is shown for that keyword in the search results of Google. You don’t know yet what page ranks for that keyword.

To see what pages might rank for the specific keyword, you can click on the line of the keyword. Doing this for the keyword [Yoast SEO], the keyword is added as a filter:

Keyword filter

After that, you could navigate to the ‘Pages’ tab to see what pages exactly rank for this keyword. Are those pages the ones you’d want to rank for that keyword? If not, you might need to optimize the page you’d like to rank. Think of writing better content containing the keyword on that page, adding internal links from relevant pages or posts to the page, making the page load faster, etc.

3. Average CTR

The CTR – Click-through rate – tells you what percentage of the people that have seen your website in the search results also clicked through to your website. You probably understand that higher rankings mostly also lead to higher click-through rates.

However, there are also things you can do yourself to increase the CTR. For example, you could rewrite your meta description and make it more appealing. When the description of your site stands out from the other results, more people will probably click on your result and your CTR will increase. Keep in mind that this will not have a big impact if you’re not ranking on the first page yet. You might need to try other things first to improve your ranking.

4. Average position

The last one in this list is the ‘Average position’. This tells you what the average ranking of a specific keyword or page was in the time period you’ve selected. Of course, this position isn’t always reliable since more and more people seem to get different search results. Google seems to understand better and better which results fit best for which visitor. However, this indicator still gives you an idea if the clicks, impressions and the average CTR are explainable.

Index coverage

A more technical but very valuable tab within Google Search Console is the ‘Index coverage’ tab. This section shows how many pages are in the index of Google since the last update, how many pages aren’t and what errors and warnings caused difficulties for Google indexing your pages properly.

Index coverageWe recommend checking this tab regularly to see what errors and warnings appear on your website. However, you also get notifications when Google has found new errors. When you get such a notification you can check the error in more detail here.

You may find that errors are caused when, e.g., a redirect doesn’t seem to work correctly, or Google is finding broken code or error pages in your theme.

Clicking on the link, you can analyze the error more in depth to see what specific URLs are affected. When you’ve fixed the error you can mark it as fixed to make sure Google will test the URL again:

Submitted URL not found (404)

There are a few things you should always look for when checking out your coverage reports:

  • If you’re writing new content, your indexed pages should be a steadily increasing number. This tells you two things: Google can index your site and you keep your site ‘alive’ by adding content.
  • Watch out for sudden drops! This might mean that Google is having trouble accessing (all of) your website. Something may be blocking Google; whether it’s robots.txt changes or a server that’s down: you need to look into it!
  • Sudden (and unexpected) spikes in the graph might mean an issue with duplicate content (such as both www and non-www, wrong canonicals, etc.), automatically generated pages, or even hacks.

We recommend that you monitor these types of situations closely and resolve errors quickly, as too many errors could send a signal of low quality (bad maintenance) to Google.

AMP

Below the ‘Index coverage,’ you can find the ‘AMP’ tab. AMP stands for Accelerated Mobile Pages: lightning fast mobile pages. If you’ve set up AMP for your website you can check for errors in Google Search Console. Within this section you can see the valid AMP pages, the valid ones with warnings and errors:

AMP errorBelow the chart, the issues are listed. If you click on one of the issues, you can see the affected URLs. Just as in the index section of GSC you can validate your fix if you’ve fixed an issue.

Job Postings

Within this tab, you’ll be able to list your job openings and to track their performance. If there are any errors, you’ll see them in here. It’s not the most important feature of GSC, but it can be valuable for specific companies or websites.

Events

This section provides useful feedback on your structured markup for events. Events can be complex to tag up correctly, so this can be an extremely helpful report for finding out where you need to tweak details like dates and location!

Sitemaps

An XML sitemap is like a roadmap to all important pages and posts on your website. We think every website would benefit from having one. Is our Yoast SEO plugin running on your website? Then you automatically have an XML sitemap. If not, we recommend creating one to make sure Google can find your most important pages and posts easily.

Within the XML sitemap tab of Google Search Console you can tell Google where your XML sitemap is located on your site:

Add a new sitemap

We recommend everyone entering the URL of their XML sitemap into GSC to make Google find it easily. In addition to that, you can quickly see if your sitemap gives errors or if some pages aren’t indexed, for instance. Checking this regularly, you’re sure Google can find and read your XML sitemap correctly.

We recommend regularly checking the XML sitemap section in our plugin to manage which post types or taxonomies you’re including in your sitemaps!

Links

Within the links to your site section, you can see how many links from other sites are pointing to your website. Besides, you can see what websites link, how many links those websites contain to your site and lastly, what anchor texts are used most linking to your website. This can be valuable information because links still are very important for SEO.

Within the internal links section, you can check what pages of your website are most linked from other spots on your site. This list can be valuable to analyze regularly because you want your most important pages and posts to get most internal links. Doing this, you make sure Google understands as well what your cornerstones are.

Mobile usability

The mobile usability tab within this section shows you usability issues with your mobile website or with specific mobile pages. Since mobile traffic is rising all over the world, we recommend checking this regularly. If your mobile site isn’t user-friendly, lots of visitors will leave it quickly.

Manual Actions

The manual actions tab is the one you don’t want to see anything in. If your site is penalized by Google, you’ll get more information in here. If your site is affected by a manual action, you’ll also get messaged via email.

There are a number of scenarios which can lead to these kinds of penalties, including:

  • You have unnatural/bought links
    Make sure from and to your site are valuable, not just for SEO. Preferably your links come from and link to related content that is valuable for your readers.
  • Your site has been hacked
    A message stating your site’s probably hacked by a third party. Google might label your site as compromised or lower your rankings.
  • You’re hiding something from Google
    If you’re ‘cloaking’ (that is, intentionally showing different to content than to users, for the purposes of decieving either of them), or using ‘sneaky’ redirects (e.g., hiding affiliate URLs), then you’re violating of Google’s Webmaster Guidelines.
  • Plain Spam
    Automatically generated content, scraped content and aggressive cloaking could cause Google to blacklist your site.
  • Spammy structured markup
    If you use rich snippets for too many irrelevant elements on a page, or mark up content that is hidden to the visitor, that might be considered spammy. Mark up what’s necessary, and not everything is necessary.

Missing features in the new version of Google Search Console

As you might have noticed not all features are integrated yet into the new version of Google Search Console. Google explains that this could have two reasons: they may have found a better way of presenting the data or they’re still in the process of migrating the feature to the new version. As said before, we’ll update this post when there’s progress made in the migration.

The old version of GSC is still available for everyone. So, why should you switch back to the old version once in a while? We’ll list the features that are missing in the new version, but that seems valuable to keep an eye on, below.

Search appearance

From the ‘Search appearance’ section of the old Google Search Console, we miss the following features in the new version: ‘Structured data‘, ‘Rich cards‘, ‘Data highlighter‘ and the ‘HTML improvements‘.

If you’ve added structured data to your website we recommend checking the structured data tab of the old version regularly. Here you’ll see if all structured data is recognized by Google and errors will be listed. If you’ve added structured data meant for rich cards, you can check for errors in the rich cards tab. The data highlighter can be used to markup your pages without having to code yourself. You can read more in-depth about Google Search Console and structured data here.

In the last missing feature of the search appearance tab, the HTML improvements, you can easily check, for instance, for duplicate titles or quite short titles which can be improved. These listings can be an easy pick: optimizing your titles and meta descriptions might increase your rankings and CTR.

International targeting

The international targeting tab is important for websites who have pages in different languages and who target people in different countries or regions. When you’ve implemented hreflang to your website, you can check for errors within this section of GSC.

Crawl stats

In the crawl tab, you can find the sections ‘Crawl errors’, ‘Crawl stats’, ‘Fetch as Google’, ‘Robots.txt tester’, ‘Sitemaps’ and ‘URL parameters’.

It seems that you can find some crawl errors in the new index coverage tag but if we look at our account, we don’t see all crawl errors in the new version. This means that it’s important to check your crawl errors still in the old version of GSC. When you’ve fixed a crawl error you can mark it as fixed. The crawl stats aren’t included yet so you can find those stats in the old version.

The crawl stats tell you something about how many pages are crawled per day, how many kilobytes are downloaded per day and how many time was spent downloading a page. If one of the graphs seem to decrease, you know it’s time to do something about it.

The fetch as Google feature gives you the opportunity to see if Google can access a specific page correctly, how it exactly renders the page and if there are blocked resources on the page. You can test your pages both for desktop as for mobile to see the differences between those.

The robots.txt tester is made to add your robots.txt and to test if any errors or warnings seem to appear. You can also add specific URLs to check whether they’re blocked or not.

The sitemaps are already moved to the new version of GSC so it’s time for the last feature of the crawl tab: URL parameters. In the URL Parameters section, you can add parameters for your website and ‘tell’ Google how they should be handled. If you want to use this, we recommend reading the guidelines carefully. Don’t just add some parameters to see what happens. This can cause serious problems with your site’s SEO.

Security issues

Last but not least: within the security issues tab you’ll get a notification when your website seems to have a security issue.

Do you already use Google Search Console for your website? If not, we definitely recommend creating an account so you can start collecting data about your website. Do you think something is missing? Feel free to leave a comment!

Read on: How to make your site stand out in the search results »

 

The post The beginner’s guide to Google Search Console appeared first on Yoast.

Google Search Console and the structured data Enhancements report

Google Search Console is an incredibly important tool for website owners. This tool shows you how your site appears in Google’s search results. It also shows you what to improve to make the most of your listings in the results. One of the many cool features of Search Console is the structured data analyses found in the Enhancement reports. Let’s dive into that!

What is Google Search Console?

Google Search Console is like the Swiss army knife for site owners. At a glance, you’ll get an incredible amount of insights into the performance and inner workings of your site. Not only that, it shows issues and helps you fix those issues by giving guidance. Google even sends you emails when it finds new issues.

Need help getting started? Please read our Beginner’s guide to Google Search Console.

What is structured data?

In this post, our main focal point is structured data, so we’ll jump to the Enhancements report section of Google Search Console. Clicking on the various structured data reports — identified by the layer icon — will show you an overview of the pages that have some kind of structured data attached to it.

Structured data is all the extra information you give search engines to help them understand what a page is about. For instance, as the writer of this article, I am both a Person and an Author. If I add this data to the source code of this page, search engines can use that data to do cool things. If you sell products, you can enhance your search listings with reviews and ratings, prices and availability. These might all become visible in the search results.

Author structured data as generated by Yoast SEO

How does Yoast SEO handle structured data?

Yoast SEO handles most of the structured data for you and you don’t need to do anything for it. Well, not that much anyway. You only have to select whether your site represents a person or an organization. This way, Yoast SEO knows what structured data to generate for this particular site.

Yoast SEO generates structured data for your site, but also for the individual articles. With our add-ons, it is also possible to have structured data generated for locations, products, videos and news items.

One of the cool things about the Yoast structured data framework is that all this code is interconnected. That means that search engines can see and make connections between every part of your site and its contents. All this helps to make your content as findable and readable for search engines as possible.

What is the Enhancements report all about?

The Enhancements tab is a place to collect all the insights and improvements that could lead to rich results. There’s a mobile usability test and an AMP test, but, today, we’re most interested in the last couple of items, from breadcrumbs to videos. All these tabs show how many valid enhancements you have, or how many have errors or warnings. You get details about the kind of errors and warnings and on which URLs these are found. There’s also a trend line that shows if the number of issues is increasing or decreasing. And that’s just the start of it.

The Enhancements reports help you find and fix issues that hinder your performance in search. By checking the issues, reading the support documentation and validating fixes, you can increase your chance of getting rich results in search.

You can find the current list of Enhancement reports on the left-hand side

What can I find there?

A lot! For every different type of enhancement, Google built a dashboard showing you how your site or page is doing. These insights help you to quickly see how you are doing and to find areas to improve. The visual aspect helps make the data more concrete and easier to absorb.

Errors/warnings

Of course, you’d like to see structured data succeed in one go, but you’re probably going to run into issues at some point. When you follow the guidelines and add the required properties, you’re going to be fine once you fix the issues. There are cases, however, that Google asks for more input, the so-called recommended properties. Adding these will make your structured data item go from orange to green. So it boils down to this:

Errors are problems, warnings are potential enhancements to improve the results.

For example, a number of how-to posts on our site use the Yoast SEO How-To structured data blocks for WordPress. These blocks automatically generate valid how-to structured data that leads to rich results. Now, we haven’t built in support for the recommended supply and tool types yet, so we see Search Console generate a warning for this. Our how-to, however, is still valid and we have a rich result to prove it.

In this case, Valid with warnings still leads to rich results

Errors mean not eligible

If you have errors in your structured data you’ll not be eligible for rich results. That doesn’t mean, however, that your page won’t rank well. These are separate things. Having valid structured data might make you a better fit, though.

Our product pages miss some structured data meant to enhance the search results, like offers and review. Since these don’t appear on the page, these product pages will not get rich results like reviews in the search results pages. Something we’ll probably fix sometime soon.

Some product pages have a structured data error, these will not receive rich results

Clicking on a page with an error opens a modal with the structured data highlighted. From here, you can copy the code to start working to fix it. Once you did that, mark this issue as fixed so Google knows you’ve worked on the problem. If the problem persists, the issue will come back in Google Search Console.

You can also hit Inspect in the bottom right corner to retrieve the page from the index to see what else is going on on that page. From there, you can run the live URL to do further testing.

Further testing is available in the URL Inspection tool

So, if you feed Google’s Rich Results Tester this page, it’ll say that the page isn’t eligible for rich results.

Even the Rich Results Test says the page is not eligible

If Search Console can’t read your structured data due to programming errors or can’t determine which type it’s supposed to describe, it’ll send these messages to the Unparsable structured data report. Run your code in the Structured Data Testing Tool, fix the errors and see if they disappear.

Eligibility for rich results

Green is good! These items have proper structured data attached to it and might lead to a rich result. Red is an error and something you should fix if you want the full rich result experience. Warnings are orange and these give you the chance to improve or extend your structured data to get the full experience. However, it is up to you if you want to fix it. Sometimes, fixing a small thing is easier said than done.

This page is eligible for FAQ, breadcrumbs and sitelinks rich results

A handy little addition is the trend line. This helps you determine a trend in the number of items validated and changes in errors.

Trend lines help you uncover trends in errors or validations

Retrieve post from index to evaluate/fix

As Search Console gives you insights into how your pages are performing in Google, it would be cool to get an idea of how Google sees those pages, right? Luckily, you can! There are several ways to do this, but the easiest is pasting your URL in the big search bar at the top of the Search Console interface.

Comparing indexed and live pages can lead to interesting insights

This gives you an overview of everything index related to this particular URL, including how Google crawled the page. See below. You can even compare the indexed URL to the live URL by hitting Live Test in the up-right corner. These should be the same, but sometimes there are errors on your live page that have not reached the index yet. From here, you can perform all kinds of tests and checks.

Sometimes, the indexed page doesn’t have errors while the live page does

Which types are available in Google Search Console?

Google is quickly expanding the types of content we’re seeing in Search Console. Just a couple of weeks ago, we saw the introduction of the Video report. Not every type of rich result has an Enhancements report attached to it. You can see the full list of supported structured data in Google’s structured data documentation or an overview of the different types of rich results in the search gallery.

Remember, when implementing, try to follow the rules or you might not get any results. Badly implemented structured data doesn’t do you any good.

Adding breadcrumb structured data to your site helps Google figure out how your navigation works and how a specific page fits in the site hierarchy. Yoast SEO automatically generates this for your pages. You only have to add some code to your WordPress theme to activate the feature. After that, enable the breadcrumbs in Yoast SEO and set the breadcrumbs to your liking. After a while, check your Search Console to see if there are any errors in your implementation.

Events

Marking up your events with event structured data helps them stand out in search results. Event markup is available for every type of event. You can add dates, locations, images, performs and more to make the most of your listings. In Search Console, you’ll see if your events are properly marked up with the essential items, but also the recommended properties that help to enhance your listing.

FAQ

One of the latest structured data powered rich results is the FAQ, used to mark up frequently asked questions pages. By implementing this, you might get a nice eye-catching dropdown in the search results. Building a valid FAQ listing is peanuts thanks to the structured data content blocks in Yoast SEO. Simply pick the FAQ block, fill in the fields and you’re good to go. Here’s how to build a structured data-powered FAQ page using Yoast SEO. Search Console will show you if your listing is valid. After that, you can check it in the Rich Results Tester to see what it will look like.

How-to

Next up is another recent structured data powered rich result: the how-to. This rich result is only available in English and on mobile devices. You can add how-to structured data to content that describes how to do something in a couple of steps. Like the FAQ above, Yoast SEO has structured data content blocks to help you build a valid how-to. Pick the block, fill the fields, add images and publish. It’s that easy! Learn how to add HowTo Schema to your how-to article. Again, in Search Console, you’ll see if your how-tos are valid or if they can be improved.

Job Postings

Job Postings are another interesting addition. Google runs a job site that loves to present its listings in a structured way. Adding job posting structured data to your available jobs helps them enrich your job postings, which in turn leads to better visibility for your jobs. As with the previous enhancements, Search Console gives you an idea of how your listings are doing and gives you tips to further improve them.

Logos

Adding markup to your logo helps search engines validate your logo to use the correct one in search. Google likes to use these files in things like the Knowledge Graph-powered knowledge panels on the right-hand side of your screen. Yoast SEO automatically adds structured data to your logo so it can be picked up properly by search engines.

Products

Products are the lifeblood of many sites. Structured data can help showcase products in search. By adding relevant data you might get highlighted in search with reviews, ratings, prices, availability and a lot more. Like all the other reports here, Search Console shows you which products are valid for rich results and which aren’t. Plus, you get tips on what you should fix to get them.

If you’re using Yoast SEO, our WooCommerce SEO add-on offers an easy way to add structured data for your products. It automatically arranges everything for you and even adds your product structured data to the rest of Yoast SEOs structured data, building a complete, and interconnected overview for search engines.

You know the search bar you see for some sites in the search results? That’s a sitelinks searchbox. This allows users to directly search on a site, without opening the site first. Yoast SEO automatically adds all the structured data necessary for sitelinks searchboxes for your site, but it’s up to Google to decide who gets one and who doesn’t. In Search Console, you’ll see which URLs on your site might get a searchbox.

New: Video

The latest addition to the Enhancement reports is Video. Here, you’ll find more information about how Google sees your embedded videos. Not only that, because Google also implemented a special search feature in the Search Appearance part of the Performance tab so you can see how many times your videos showed up in search and how many people clicked on them. The Yoast Video SEO add-on automatically adds the necessary code and ties everything neatly together. Here’s more information on how to get Google’s new video reporting with the Yoast Video SEO plugin.

Keep an eye on your structured data in Google Search Console

As I mentioned quite a few times: Google Search Console is a goldmine. It should be your go-to tool to see how your site is doing in the search engine. There’s a lot to see and do. The Enhancement reports, for instance, show you if your structured data implementation is valid for rich results. These reports help you fix errors and warnings so you can get the most out of your structured data.

Need more structured data? Read our Ultimate guide to structured data with Schema.org.

The post Google Search Console and the structured data Enhancements report appeared first on Yoast.

What is an XML sitemap and why should you have one?

A good XML sitemap acts as a roadmap of your website that leads Google to all your important pages. XML sitemaps can be good for SEO, as they allow Google to quickly find your essential website pages, even if your internal linking isn’t perfect. This post explains what they are and how they help you rank better.

We hope you’ll enjoy reading #5 of our best-read posts this year! Find out all about XML sitemaps and why it’s important that you have one. Don’t forget to check back tomorrow for another holiday countdown surprise!

What are XML sitemaps?

You want Google to crawl every important page of your website, but sometimes, pages end up without any internal links pointing to them, making them hard to find. An XML sitemap lists a website’s important pages, making sure Google can find and crawl them all, also helping it understand your website structure:

XML sitemap Yoast
Yoast.com’s XML sitemap

Above is Yoast.com’s XML sitemap, created by the Yoast SEO plugin and later on we’ll explain how our plugin helps you create the best XML sitemaps. If you don’t use our plugin, your sitemap may look a little different but will work the same way.

As you can see, the Yoast.com XML sitemap shows several ‘index’ sitemaps: post-sitemap.xml, page-sitemap.xml, video-sitemap.xml etc. This categorization makes a site’s structure as clear as possible, so if you click on one of the index sitemaps, you’ll see all URLs in that particular sitemap. For example, if you click on post-sitemap.xml you’ll see all Yoast.com’s post URLs (click on the image to enlarge):

XML Post Sitemap Yoast
Yoast.com’s post XML sitemap

You’ll notice a date at the end of each line. This tells Google when each post was last updated and helps with SEO because you want Google to crawl your updated content as soon as possible. When a date changes in the XML sitemap, Google knows there is new content to crawl and index.

If you have a very large website, sometimes it’s necessary to split an index sitemap. A single XML sitemap is limited to 50,000 URLs, so if your website has more than 50,000 posts, for example, you’ll need two separate ones for the post URLs, effectively adding a second index sitemap. The Yoast SEO plugin sets the limit even lower – at 1.000 URLs – to keep your sitemap loading as fast as possible

What websites need an XML sitemap?

Google’s documentation says XML sitemaps are beneficial for “really large websites”, for “websites with large archives”, for “new websites with just a few external links to it” and for “websites which use rich media content”.

While we agree that these kinds of websites will definitely benefit the most from having one, at Yoast, we think XML sitemaps are beneficial for every website. Every single website needs Google to be able to easily find the most important pages and to know when they were last updated, which is why this feature is included in the Yoast SEO plugin.

Which pages should be in your XML sitemap?

How do you decide which pages to include in your XML sitemap? Always start by thinking of the relevance of a URL: when a visitor lands on a particular URL, is it a good result? Do you want visitors to land on that URL? If not, it probably shouldn’t be in it. However, if you really don’t want that URL to show up in the search results you’ll need to add a ‘noindex, follow’ tag. Leaving it out of your XML sitemap doesn’t mean Google won’t index the URL. If Google can find it by following links, Google can index the URL.

Example 1: A new blog

Say, for example, you are starting a new blog. You will want Google to find new posts quickly to make sure your target audience can find your blog in the search results, so it’s a good idea to create an XML sitemap right from the start. You might create a handful of first posts and categories for them as well as some tags to start with. But there won’t be enough content yet to fill the tag overview pages, making them “thin content” that’s not valuable to visitors – yet. In this case, you should leave the tag’s URLs out of the sitemap for now. Set the tag pages to ‘noindex, follow’ because you don’t want people to find them in search results.

Example 2: Media and images

The ‘media’ or ‘image’ XML sitemap is also unnecessary for most websites. This is because your images are probably used within your pages and posts, so will already be included in your ‘post’ or ‘page’ sitemap. So having a separate ‘media’ or ‘image’ sitemap would be pointless and we recommend leaving it out. The only exception to this is if images are your main business. Photographers, for example, will probably want to show a separate ‘media’ or ‘image’ XML sitemap to Google.

How to make Google find your sitemap

If you want Google to find your XML sitemap quicker, you’ll need to add it to your Google Search Console account. In the ‘Sitemaps’ section, you’ll immediately see if your XML sitemap is already added. If not, you can add your sitemap at top of the page:

Add sitemap index to Search Console
Yoast.com’s XML sitemap added to Google Search Console

As you can see in the image, adding your XML sitemap can be helpful to check whether all pages in your sitemap really have been indexed by Google. If there is a big difference in the ‘submitted’ and ‘indexed’ number on a particular sitemap, we recommend looking into this further. There could be an error preventing some pages from being indexed or maybe you need more content or links pointing to the content that’s not been indexed yet.

Yoast SEO and XML sitemaps

Because they are so important for your SEO, we’ve added the ability to create your own XML sitemaps in our Yoast SEO plugin. They are available in both the free and premium versions of the plugin.

Yoast SEO creates an XML sitemap for your website automatically. Click on ‘SEO’ in the sidebar of your WordPress install and then select the ‘Features’ tab:

XML sitemaps in Yoast SEO
XML Sitemaps

In this screen, you can enable or disable the different XML sitemaps for your website. Also, you can click on the question mark to expand the information and see more possibilities, like checking your sitemap in your browser:

You can exclude content types from your XML sitemap in the ‘Search Appearance’ tab. If you select ‘no’ as an answer to ‘show X in the search results?’ then this type of content won’t be included in it.

Read more about excluding content types here.

Check your own XML sitemap!

Now, you know how important it is to have an XML sitemap because having one can really help your site’s SEO. Google can easily access your most important pages and posts if you add the right URLs to it. Google will also be able to find updated content easily, so they know when a URL needs to be crawled again. Lastly, adding your XML sitemap to Google Search Console helps Google find your sitemap fast and it allows you to check for sitemap errors.

Now go check your own XML sitemap and make sure you’re doing it right!

The post What is an XML sitemap and why should you have one? appeared first on Yoast.