How to optimize your technique, as you know, in this chapter, we will share the tactics we use to
empower the technical your.
When you managed to fix technical problems, you will usually get more traffic, get higher rankings
and Google search console is something magnificent, magnificent.
You can use, of course, with SEO Yoast, you should be safe a lot.
But still, let's have a look.
Use the new index coverage report to find and fix problems with indexing if everything on your website
is set up.
Right.
Go, go, go.
Find your page and quickly added to the index.
But unfortunately, sometimes things go wrong.
They think needs to fix if you want to go to index all of your pages.
So let's dive in.
What is this index committee report?
It simply lets you know which pages from your side are in Google's index, it also lets you know about
technical issues that prevent pages from getting index.
As you can see, you can have some warnings or even, unfortunately, errors, but as I was showing
you, if you just built a normal website, way to the guidance I am giving to you, you should be always
very, very safe.
New index coverage report is pretty complicated, but not so much for your.
And we could just hand you a list of features and wish you luck.
In fact, that's what the most and all the main guides do.
Instead, we are going to walk you through an analysis of real side step by step this way.
You can watch us using the index scritch report to uncover problems and fix them.
So please have a look how to find the areas with the index which report at the top of the index.
You've got four taps at all.
Then you've got pages that are valid with warnings, then, of course, wide or unfortunately excluded.
The most important is always to focus on being at odds, so if you scroll down, you get Deetz on each
of the arrows so you can see like what might be the arrow.
There's a lot to take in here.
So to help you make sense of each reason, here is some quick definitions to help you understand.
Submitted a address seems to be a salt for all for.
This simply means that the page was not found, but delivered an incorrect status code in the header.
Redirect their redirect for this page, but it ain't working, so you need to set up a correct redirection.
You can use, for example, the redirection plugin and this is very useful.
Submitted address, not from the page was informed and the server returned the correct status code.
All good.
While if you ignore the fact the page is broken, so it's always good to read, directed and correct.
Submitted address has Sakuraba issue.
This could be one of the different things you have to visit the page to see what's up.
Or you can have some sort of an aura, so it means like Googlebot couldn't access the sediment.
It might have crashed time out or been down when Google bought Stubblebine.
So this should not happen to you when you some good radwaste thing like Blue Horse for WordPress that
I'm recommending to you.
And when you click on Aerostats, you'll get a list of pages where that particular problem, 404 error
should be easy to fix.
So let's start with those.
Click to the address on the list.
This opens up a side panel with four options.
As you can see past Roberts text the fetch as Google View search results, submit to index.
But first, let's visit address with a browser.
That way we can double check the pages through a down.
Yup, it's down next, gulik such as Google, IndusInd Panner.
And as you can see, Googlebot will rush over to your page.
Sure enough, this page is still giving me for, oh, for some not fallen status.
How do we fix it?
Well, we have two options.
Leave it as this Google eventually index the page.
This makes sense if the page is down for a reason, or you can redirect the four or four page to similar
product page, category page or blog posts so you can use the redirection plugin.
That's quite easy.
So let's just say you choose this page, you'll see that this page doesn't work.
So you just put it in the right direction.
Plug in and you can read directed.
That's the most easy you can do.
How to fix software for.
Again, check out the address with that error, then visit each of these addresses in your browser.
Looks like the first page on the list is loading fine, as you can see on the picture.
Let's see if Google can access the page, OK?
Again, we will use the fetch as Google.
This time will choose, fight and surrender, as you can see, you click, fetch and Orender fetch and
Orender sends Gogobot to the page.
It also renders the page so you can see your page like Google sees it looks like Google from that page
this time.
Now, let's see how Google rendered the page.
Looks pretty much the same as how visitors see it.
That's good.
Next, scroll down.
Google shows your resources that users see, but Google can actually see.
Google bought couldn't get all resources for this page.
Here is the list that's calling like it's some blocked great sign down.
There is a good reason to block certain resources from Google bought, but sometimes these blog resources
can be too soft for all for errors in this case.
So these five things are all meant to be blocked.
So let's move on.
Finally, click the fetching up to see delay htp start to sculpt.
Nice due 200 status means that the page was found this time and it should be indexable.
So we are good with this sort for all.
For the next time Google stops by the page should get indexed how to fix other errors.
You can use the same exact process we just use for select for force to fix any error you run into.
Load up the page in your browser, fetch and render as Google read over the specific issues that the
Google search console tells you about.
Check the status of the page here.
You can see a great example.
Or you can see the example of kirova error.
I don't see any issues here, so it might be great.
The cerebral Arora has disappeared on its own, must have been a temporary issue with hosting, but
you would want to keep an eye on that to make sure it doesn't happen again.
Bottom line, with a bit of work, you can fix all the errors from the index coverage report.
So this is really important to know and to use the redirection plug in and time by time.
Visit the Google search console.
How to fix warnings in the Index Global Reach Report.
I truly don't like to leave anything to chance when it comes to snow, which means I don't mess around
when I see a bright orange warning.
So let's hit the white with warning stop in the index coverage report.
This time there's just one more main index blocked by robots to the extreme.
So what's going on here?
Let's find out.
The Google search console is telling us the page is getting blocked by our about 16.
So instead of hitting fetch as Google, click on Test Robots 16 blocking, as you can see on the picture,
this takes us to the robots test in the old search console.
As it turns out, this address is getting blocked by robots.
So what's the fix?
Well, if you want a page indexed, you should unblock it from robots.
But if you don't want it, index it.
You have two options.
And the noindex follow tack to the page and unblock it from robots, the extreme get rid of the page
using the.
A dress removal tool, let's see how to use the address removal to deal a dress removal to a quick and
easy way to remove pages from Google's index.
You just click on Google Index in the sidebar of the old Google search console, then click remove the
address.
Find our base in the address you want to remove.
Triple check that you entered the right address and then click submit the request Cyrillic triple double
check that you entered the right address and then click submit request.
Irremovable is only active for 90 days after dead Googlebot will attempt to read Kajita page, but considering
the page is blocked through Roberts, this page will be gone for about.
Check index pages for possible issues.
Now let's move on the wallet to the stars, how many pages are indexed in Google?
What should you look for here?
Two things unexpected drop or increase of index pages notice a sudden drop in the number of index pages.
That could be a sign that something's wrong.
Maybe a bunch of pages are blocking Googlebot.
Or maybe you added a no index stack by mistake.
Either way, unless you purposely index a bunch of pages, you definitely want to check this out.
On the flip side.
What if you notice a sudden increase in index pages?
Again, that might be a sign that something is wrong.
For example, maybe you unblocked a bunch of pages that are supposed to be blocked.
And unexpectedly high number of index pages.
As you can see, for example, this is 41 post published, so when we take a look at the Valetta report
in index coverage, we would expect to see about that many pages index.
But if it's way higher than 41, that's a problem.
And we have to fix it.
As you can see, here are 61 one index.
Make sure excluded stuff should be excluded.
Now, there are plenty of good reasons to block search engines from indexing a page, maybe it's a login
page, maybe the page contains a duplicate content or maybe the page is slow.
Quite.
No.
When we say low quality, we don't mean the page is garbage.
It could be that the page is useful for users, but not for search engines.
That said, you definitely want to make sure Google doesn't exclude pages that you want index it.
In this case, we have a lot of excluded pages, two hundred nineteen thousand.
And if you scroll down, you'll get a list of reasons that each page is excluded from Google's index.
So let's break this down.
They should redirect.
This is OK.
You are redirecting to another address, this is totally fine, unless there are back links or internal
links pointing to that address, they will eventually stop trying to index it.
Out the night page with can only attack, Google found an alternative version of this page somewhere
else.
That's what a canonical address is supposed to do.
So that's OK.
This is mainly for teashops and for e-commerce.
And this is totally fine when you have the similar products, Chuzzlewit, the same addresses, you
are using the canonic attack not to get penalized for duplicate content.
If you are wondering what all is this, you should definitely go for this e-commerce asmir or section
kirova anomaly.
Could be a number of things, so we need to investigate in this case, it looks like the page is listed
as returning for all four korol, but currently not indexed.
These are pages that Google has crawl up, but for some reason I'm not indexed, Google doesn't give
you the exact reason they want index the page.
But from our experience, this error means the page isn't good enough to warrant a spot in the search
results.
So what you should do to fix this, our advice work on improving the quality of any page is listed.
For example, if it's a category page at some content that describes that category, if the page has
lots of duplicate content, make it unique.
If the page doesn't have much content on it.
Bifida basically made a page worth of Google's index submitted page, not selected as canonical.
This is Google telling you this page has the same content as a bunch of other pages, but we think another
page is better, so they have excluded this page from the index.
If you have duplicate content on a number of pages at the noindex, metal robots stack to all duplicate
pages except the one you want to index it.
Blocked by robots, these are pages that robots blocking Google from crawling its walls, double checking
these errors to make sure what you are blocking is meant to be blocked if it's all good.
Then robots is doing its job and there is nothing to worry about.
Duplicate page without canonical tech debate is part of a set of duplicate pages and doesn't include
a canonical.
A dress can only go back in this case, it's pretty easy to see what's up.
We've got a number of pages of documents, and this PDF contained content from other pages on this site.
Honestly, this isn't a big deal.
But to be on the safe side, you ask your web developer to blog DPD using robots.
That way, Google only indexes the original content.
Discovered currently not indexed.
Google has kirova these pages, but hasn't included them in the index here.
Excluded by no index stack, all good, the no index is doing its job, so that's the index coverage
report.
We are sure you agree.
It's a very impressive to check the HCM, our Improvement's report.
I am honestly no coder.
That's why I love so much Imada.
And that's why I'm showing you how to create complete website with Awada, how to use as we all how
to call it, analytics and Google search console.
Even that if you don't have correct HDMI, it can hard your AC or it should not happen to you anyway
with Imada.
And this is especially true for your tither and ascription tax.
In short, every page on your side should have a unique, well-written title, up to approximately 70
characters, a unique, well-written meta description, up to 300 characters, every single page unique.
Yes, even if you run an e-commerce site with a bazillion pages, Fortunata, it's extremely easy to
spot HMO problems in the search console to load up the HMO improvement's report.
And Google will tell you what's up.
As you can see, search appearance and HMO improvements on the you need specifics.
Just click on a category for a full list of pages with issues, as you can see on the page.
And now the most important.
We have managed to understand all this technical, ethical issues and you just understand them.
But you will probably not use your knowledge unless you become a professional as your consultant.
But you might become so it's useful for you.
But now the most important, how to get more organic traffic with the performance report.