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.

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.

How to check site speed

Learning how to check your site speed doesn’t need to be daunting. This short guide will give you the basics, and point you in the right direction.

There’s no single metric

The first thing to understand is that there is no single metric or measurement for ‘speed’. There’s no simple number which you can use to measure how quickly your pages load.

Think about what happens when you load a website. There are lots of different stages and many different parts which can be measured. If the network connection is slow, but the images load quickly, how ‘fast’ is the site? What about the other way around?

Even if you try to simplify all of this to something like “the time it takes until it’s completely loaded“, it’s still tricky to give that a useful number.

For example, a page which takes longer to ‘finish loading’ may provide a functional ‘lightweight’ version while the full page is still downloading in the background. Is that ‘faster’ or ‘slower’ than a website which loads faster, but which I can’t use until it’s finished loading?

The answer is, “it depends”, and there are many different ways in which we can think about or measure ‘site speed’.

Understanding the loading process

From the moment when you click on a link (or hit ‘enter’ in your URL bar), a process begins to load the page you requested.

That process contains many steps, but they can be grouped into broad stages which looks something like this:

The “one second timeline” from Google’s site speed documentation

While Google’s documentation might be a bit ambitious about the timings of these stages, the model is helpful. Essentially, the process can be described as three stages of loading.

1. Network stuff

First up, the physical hardware of your device needs to connect to the Internet. Usually, that involves moving data through transatlantic fibre cables. That means that you’re limited by the speed of light, and how quickly your device can process information.

It’s hard to measure or impact this part of the process!

2. Server stuff

Here, your device asks your server for a page, and the server prepares and returns the response.

This section can get a bit technical, as it’s focused on the performance of server hardware, databases and scripts. You may need to ask for help from your hosting provider or tech team.

We can measure the performance of the server with tools like NewRelic or DataDog, which monitors how your site behaves and responds from the ‘inside’.

They’ll provide charts and metrics around things like slow database queries and slow scripts. Armed with this information, you can get a better understanding if your hosting is up to scratch and if you need to make code changes to your theme/plugins/scripts.

The Query Monitor plugin for WordPress

WordPress has some great plugins for doing this kind of analysis, too – I’m a big fan of Query Monitor. This provides some great insight into which bits of WordPress might be slowing you down – whether it’s your themes, plugins, or environments.

3. Browser stuff

This stage is where the page needs to be constructed, laid out, colored in, and displayed. The way in which images load, in which JavaScript and CSS are processed, and every individual HTML tag on your page affects how quickly things load.

We can monitor some of this from the ‘outside-in’ with tools which scan the website and measure how it loads. We recommend using multiple tools, as they measure things differently, and are useful for different assessments. For example:

  • WebPageTest is great for providing a ‘waterfall’ view of the website, and how all of the assets load.
  • Google PageSpeed Insights is a bit simplistic, but it provides ‘real user metrics’ of your website, straight from Google.
  • Lighthouse for Chrome provides an incredibly sophisticated analysis of the performance and behaviour of the site, but it can be hard to digest!
  • Chrome Developer Console shows you exactly what’s happening as your site loads, on your computer, in your browser.

WebPageTest results for yoast.com

These kinds of tools are great for spotting things like images which need to be optimized, where your CSS or JavaScript is slow, or where you’re waiting for assets to load from other domains.

Universal metrics

Despite all of these moving parts, there are a few universal metrics which make sense for all sites to measure, and optimize for. These are:

  • Time until first byte, which is how long it takes until the server responds with some information. Even if your front-end is blazing fast, this will hold you up. Measure with Query Monitor or NewRelic.
  • Time until first contentful (and meaningful) paint, which is how long it takes for key visual content (e.g., a hero image or a page heading) to appear on the screen. Measure with Lighthouse for Chrome.
  • Time until interactive, which is how long it takes for the experience to be visible, and react to my input. Measure with Lighthouse for Chrome.

These are much more sophisticated metrics than “how long did it take to load”, and, perhaps more importantly, have a user-centric focus. Improving these metrics should correlate directly with user satisfaction, which is super-important for SEO.

A Lighthouse report for yoast.com showing key metrics

You can read more about these metrics in Google’s documentation.

Wrapping this into a process

  1. Use an ‘outside-in’ tool, like WebPageTest to generate a waterfall diagram of how the website loads.
  2. Identify bottlenecks with servers and the back end. Look for slow connection times, slow SSL handshakes, and slow DNS lookups. Use a plugin like Query Monitor, or a service like NewRelic to diagnose what’s holding things up. Make server, hardware, software and script changes.
  3. Identify bottlenecks with the front end. Look for slow loading and processing times on images, scripts and stylesheets. Use a tool like Google PageSpeed Insights or Lighthouse for Chrome for suggestions on how to streamline how the page loads.
  4. Use Lighthouse for Chrome to measure your key metrics, like time until first meaningful paint and time until interactive.

Have we missed anything? Let us know in the comments!

Read more: Improving site speed: Tools and suggestions »

The post How to check site speed appeared first on Yoast.