1
00:00:00,180 --> 00:00:09,030
How to optimize your technique, as you know, in this chapter, we will share the tactics we use to

2
00:00:09,180 --> 00:00:11,700
empower the technical your.

3
00:00:12,770 --> 00:00:23,210
When you managed to fix technical problems, you will usually get more traffic, get higher rankings

4
00:00:23,960 --> 00:00:29,240
and Google search console is something magnificent, magnificent.

5
00:00:29,240 --> 00:00:36,220
You can use, of course, with SEO Yoast, you should be safe a lot.

6
00:00:36,230 --> 00:00:38,730
But still, let's have a look.

7
00:00:39,410 --> 00:00:49,220
Use the new index coverage report to find and fix problems with indexing if everything on your website

8
00:00:49,220 --> 00:00:49,840
is set up.

9
00:00:49,880 --> 00:00:50,310
Right.

10
00:00:50,780 --> 00:00:51,590
Go, go, go.

11
00:00:51,590 --> 00:00:55,640
Find your page and quickly added to the index.

12
00:00:56,670 --> 00:01:00,210
But unfortunately, sometimes things go wrong.

13
00:01:01,160 --> 00:01:07,020
They think needs to fix if you want to go to index all of your pages.

14
00:01:07,550 --> 00:01:09,170
So let's dive in.

15
00:01:10,070 --> 00:01:13,160
What is this index committee report?

16
00:01:14,620 --> 00:01:23,650
It simply lets you know which pages from your side are in Google's index, it also lets you know about

17
00:01:23,650 --> 00:01:28,960
technical issues that prevent pages from getting index.

18
00:01:29,960 --> 00:01:38,270
As you can see, you can have some warnings or even, unfortunately, errors, but as I was showing

19
00:01:38,270 --> 00:01:48,410
you, if you just built a normal website, way to the guidance I am giving to you, you should be always

20
00:01:48,410 --> 00:01:50,160
very, very safe.

21
00:01:53,860 --> 00:02:00,400
New index coverage report is pretty complicated, but not so much for your.

22
00:02:02,720 --> 00:02:07,410
And we could just hand you a list of features and wish you luck.

23
00:02:07,430 --> 00:02:11,430
In fact, that's what the most and all the main guides do.

24
00:02:11,870 --> 00:02:20,700
Instead, we are going to walk you through an analysis of real side step by step this way.

25
00:02:20,720 --> 00:02:27,910
You can watch us using the index scritch report to uncover problems and fix them.

26
00:02:28,610 --> 00:02:38,970
So please have a look how to find the areas with the index which report at the top of the index.

27
00:02:39,530 --> 00:02:42,400
You've got four taps at all.

28
00:02:43,400 --> 00:02:52,010
Then you've got pages that are valid with warnings, then, of course, wide or unfortunately excluded.

29
00:02:53,600 --> 00:03:03,290
The most important is always to focus on being at odds, so if you scroll down, you get Deetz on each

30
00:03:03,290 --> 00:03:09,470
of the arrows so you can see like what might be the arrow.

31
00:03:09,890 --> 00:03:12,190
There's a lot to take in here.

32
00:03:12,470 --> 00:03:20,840
So to help you make sense of each reason, here is some quick definitions to help you understand.

33
00:03:21,350 --> 00:03:25,910
Submitted a address seems to be a salt for all for.

34
00:03:27,040 --> 00:03:34,810
This simply means that the page was not found, but delivered an incorrect status code in the header.

35
00:03:36,560 --> 00:03:47,260
Redirect their redirect for this page, but it ain't working, so you need to set up a correct redirection.

36
00:03:47,300 --> 00:03:53,290
You can use, for example, the redirection plugin and this is very useful.

37
00:03:54,290 --> 00:04:03,350
Submitted address, not from the page was informed and the server returned the correct status code.

38
00:04:03,350 --> 00:04:04,040
All good.

39
00:04:04,430 --> 00:04:12,260
While if you ignore the fact the page is broken, so it's always good to read, directed and correct.

40
00:04:13,520 --> 00:04:16,740
Submitted address has Sakuraba issue.

41
00:04:17,300 --> 00:04:22,850
This could be one of the different things you have to visit the page to see what's up.

42
00:04:24,770 --> 00:04:31,400
Or you can have some sort of an aura, so it means like Googlebot couldn't access the sediment.

43
00:04:32,020 --> 00:04:38,450
It might have crashed time out or been down when Google bought Stubblebine.

44
00:04:38,930 --> 00:04:47,480
So this should not happen to you when you some good radwaste thing like Blue Horse for WordPress that

45
00:04:47,480 --> 00:04:49,340
I'm recommending to you.

46
00:04:49,860 --> 00:04:59,390
And when you click on Aerostats, you'll get a list of pages where that particular problem, 404 error

47
00:04:59,420 --> 00:05:00,990
should be easy to fix.

48
00:05:01,340 --> 00:05:03,320
So let's start with those.

49
00:05:03,920 --> 00:05:07,100
Click to the address on the list.

50
00:05:07,130 --> 00:05:11,480
This opens up a side panel with four options.

51
00:05:12,260 --> 00:05:21,400
As you can see past Roberts text the fetch as Google View search results, submit to index.

52
00:05:22,220 --> 00:05:25,970
But first, let's visit address with a browser.

53
00:05:26,510 --> 00:05:30,770
That way we can double check the pages through a down.

54
00:05:32,100 --> 00:05:37,140
Yup, it's down next, gulik such as Google, IndusInd Panner.

55
00:05:39,570 --> 00:05:44,070
And as you can see, Googlebot will rush over to your page.

56
00:05:44,130 --> 00:05:51,550
Sure enough, this page is still giving me for, oh, for some not fallen status.

57
00:05:52,020 --> 00:05:53,340
How do we fix it?

58
00:05:53,880 --> 00:05:55,650
Well, we have two options.

59
00:05:56,070 --> 00:06:00,900
Leave it as this Google eventually index the page.

60
00:06:01,410 --> 00:06:10,590
This makes sense if the page is down for a reason, or you can redirect the four or four page to similar

61
00:06:10,590 --> 00:06:18,030
product page, category page or blog posts so you can use the redirection plugin.

62
00:06:18,330 --> 00:06:19,650
That's quite easy.

63
00:06:20,700 --> 00:06:28,050
So let's just say you choose this page, you'll see that this page doesn't work.

64
00:06:28,050 --> 00:06:30,540
So you just put it in the right direction.

65
00:06:30,540 --> 00:06:33,270
Plug in and you can read directed.

66
00:06:33,280 --> 00:06:35,400
That's the most easy you can do.

67
00:06:36,390 --> 00:06:38,740
How to fix software for.

68
00:06:40,010 --> 00:06:48,090
Again, check out the address with that error, then visit each of these addresses in your browser.

69
00:06:48,740 --> 00:06:55,340
Looks like the first page on the list is loading fine, as you can see on the picture.

70
00:06:56,660 --> 00:06:59,780
Let's see if Google can access the page, OK?

71
00:07:00,200 --> 00:07:03,320
Again, we will use the fetch as Google.

72
00:07:04,750 --> 00:07:12,630
This time will choose, fight and surrender, as you can see, you click, fetch and Orender fetch and

73
00:07:12,640 --> 00:07:15,280
Orender sends Gogobot to the page.

74
00:07:15,760 --> 00:07:24,790
It also renders the page so you can see your page like Google sees it looks like Google from that page

75
00:07:24,790 --> 00:07:25,570
this time.

76
00:07:26,200 --> 00:07:28,990
Now, let's see how Google rendered the page.

77
00:07:31,260 --> 00:07:34,350
Looks pretty much the same as how visitors see it.

78
00:07:34,590 --> 00:07:35,240
That's good.

79
00:07:35,700 --> 00:07:37,380
Next, scroll down.

80
00:07:37,380 --> 00:07:42,960
Google shows your resources that users see, but Google can actually see.

81
00:07:44,190 --> 00:07:48,550
Google bought couldn't get all resources for this page.

82
00:07:48,960 --> 00:07:55,790
Here is the list that's calling like it's some blocked great sign down.

83
00:07:55,800 --> 00:08:03,990
There is a good reason to block certain resources from Google bought, but sometimes these blog resources

84
00:08:03,990 --> 00:08:08,700
can be too soft for all for errors in this case.

85
00:08:08,710 --> 00:08:12,620
So these five things are all meant to be blocked.

86
00:08:12,630 --> 00:08:13,920
So let's move on.

87
00:08:15,300 --> 00:08:21,450
Finally, click the fetching up to see delay htp start to sculpt.

88
00:08:22,080 --> 00:08:28,920
Nice due 200 status means that the page was found this time and it should be indexable.

89
00:08:29,400 --> 00:08:32,650
So we are good with this sort for all.

90
00:08:32,680 --> 00:08:42,480
For the next time Google stops by the page should get indexed how to fix other errors.

91
00:08:43,020 --> 00:08:52,470
You can use the same exact process we just use for select for force to fix any error you run into.

92
00:08:53,270 --> 00:09:02,370
Load up the page in your browser, fetch and render as Google read over the specific issues that the

93
00:09:02,370 --> 00:09:05,210
Google search console tells you about.

94
00:09:05,760 --> 00:09:10,050
Check the status of the page here.

95
00:09:10,080 --> 00:09:12,150
You can see a great example.

96
00:09:13,610 --> 00:09:17,670
Or you can see the example of kirova error.

97
00:09:17,690 --> 00:09:22,040
I don't see any issues here, so it might be great.

98
00:09:24,260 --> 00:09:32,330
The cerebral Arora has disappeared on its own, must have been a temporary issue with hosting, but

99
00:09:32,330 --> 00:09:37,070
you would want to keep an eye on that to make sure it doesn't happen again.

100
00:09:37,760 --> 00:09:46,480
Bottom line, with a bit of work, you can fix all the errors from the index coverage report.

101
00:09:46,850 --> 00:09:55,310
So this is really important to know and to use the redirection plug in and time by time.

102
00:09:55,670 --> 00:09:57,850
Visit the Google search console.

103
00:09:58,880 --> 00:10:03,590
How to fix warnings in the Index Global Reach Report.

104
00:10:08,020 --> 00:10:16,420
I truly don't like to leave anything to chance when it comes to snow, which means I don't mess around

105
00:10:16,420 --> 00:10:19,410
when I see a bright orange warning.

106
00:10:19,990 --> 00:10:26,140
So let's hit the white with warning stop in the index coverage report.

107
00:10:27,130 --> 00:10:36,560
This time there's just one more main index blocked by robots to the extreme.

108
00:10:37,090 --> 00:10:39,040
So what's going on here?

109
00:10:39,070 --> 00:10:40,220
Let's find out.

110
00:10:40,840 --> 00:10:48,220
The Google search console is telling us the page is getting blocked by our about 16.

111
00:10:49,160 --> 00:10:58,700
So instead of hitting fetch as Google, click on Test Robots 16 blocking, as you can see on the picture,

112
00:10:59,270 --> 00:11:05,500
this takes us to the robots test in the old search console.

113
00:11:06,200 --> 00:11:10,880
As it turns out, this address is getting blocked by robots.

114
00:11:12,480 --> 00:11:13,710
So what's the fix?

115
00:11:13,740 --> 00:11:19,890
Well, if you want a page indexed, you should unblock it from robots.

116
00:11:21,510 --> 00:11:24,210
But if you don't want it, index it.

117
00:11:24,450 --> 00:11:25,920
You have two options.

118
00:11:26,940 --> 00:11:36,150
And the noindex follow tack to the page and unblock it from robots, the extreme get rid of the page

119
00:11:36,150 --> 00:11:36,960
using the.

120
00:11:37,990 --> 00:11:50,370
A dress removal tool, let's see how to use the address removal to deal a dress removal to a quick and

121
00:11:50,370 --> 00:11:53,760
easy way to remove pages from Google's index.

122
00:11:54,420 --> 00:12:03,030
You just click on Google Index in the sidebar of the old Google search console, then click remove the

123
00:12:03,480 --> 00:12:04,320
address.

124
00:12:05,400 --> 00:12:09,810
Find our base in the address you want to remove.

125
00:12:12,050 --> 00:12:22,250
Triple check that you entered the right address and then click submit the request Cyrillic triple double

126
00:12:22,250 --> 00:12:28,220
check that you entered the right address and then click submit request.

127
00:12:29,160 --> 00:12:39,930
Irremovable is only active for 90 days after dead Googlebot will attempt to read Kajita page, but considering

128
00:12:39,930 --> 00:12:45,750
the page is blocked through Roberts, this page will be gone for about.

129
00:12:46,740 --> 00:12:50,190
Check index pages for possible issues.

130
00:12:51,000 --> 00:12:58,590
Now let's move on the wallet to the stars, how many pages are indexed in Google?

131
00:13:00,040 --> 00:13:02,060
What should you look for here?

132
00:13:02,440 --> 00:13:13,470
Two things unexpected drop or increase of index pages notice a sudden drop in the number of index pages.

133
00:13:14,080 --> 00:13:16,840
That could be a sign that something's wrong.

134
00:13:17,470 --> 00:13:21,310
Maybe a bunch of pages are blocking Googlebot.

135
00:13:21,730 --> 00:13:25,710
Or maybe you added a no index stack by mistake.

136
00:13:26,230 --> 00:13:34,010
Either way, unless you purposely index a bunch of pages, you definitely want to check this out.

137
00:13:34,720 --> 00:13:36,040
On the flip side.

138
00:13:36,430 --> 00:13:41,410
What if you notice a sudden increase in index pages?

139
00:13:41,920 --> 00:13:45,940
Again, that might be a sign that something is wrong.

140
00:13:46,690 --> 00:13:53,890
For example, maybe you unblocked a bunch of pages that are supposed to be blocked.

141
00:13:55,060 --> 00:13:59,680
And unexpectedly high number of index pages.

142
00:14:00,880 --> 00:14:10,720
As you can see, for example, this is 41 post published, so when we take a look at the Valetta report

143
00:14:11,080 --> 00:14:17,250
in index coverage, we would expect to see about that many pages index.

144
00:14:18,130 --> 00:14:22,110
But if it's way higher than 41, that's a problem.

145
00:14:23,130 --> 00:14:24,860
And we have to fix it.

146
00:14:26,880 --> 00:14:31,320
As you can see, here are 61 one index.

147
00:14:33,640 --> 00:14:37,630
Make sure excluded stuff should be excluded.

148
00:14:37,810 --> 00:14:47,350
Now, there are plenty of good reasons to block search engines from indexing a page, maybe it's a login

149
00:14:47,350 --> 00:14:53,500
page, maybe the page contains a duplicate content or maybe the page is slow.

150
00:14:53,500 --> 00:14:54,130
Quite.

151
00:14:56,170 --> 00:14:56,520
No.

152
00:14:56,710 --> 00:15:01,000
When we say low quality, we don't mean the page is garbage.

153
00:15:01,210 --> 00:15:07,000
It could be that the page is useful for users, but not for search engines.

154
00:15:07,360 --> 00:15:14,280
That said, you definitely want to make sure Google doesn't exclude pages that you want index it.

155
00:15:15,640 --> 00:15:23,310
In this case, we have a lot of excluded pages, two hundred nineteen thousand.

156
00:15:23,980 --> 00:15:32,260
And if you scroll down, you'll get a list of reasons that each page is excluded from Google's index.

157
00:15:34,890 --> 00:15:36,880
So let's break this down.

158
00:15:37,230 --> 00:15:38,850
They should redirect.

159
00:15:39,780 --> 00:15:40,720
This is OK.

160
00:15:40,740 --> 00:15:49,140
You are redirecting to another address, this is totally fine, unless there are back links or internal

161
00:15:49,140 --> 00:15:55,710
links pointing to that address, they will eventually stop trying to index it.

162
00:15:56,760 --> 00:16:05,490
Out the night page with can only attack, Google found an alternative version of this page somewhere

163
00:16:05,490 --> 00:16:06,070
else.

164
00:16:06,630 --> 00:16:11,210
That's what a canonical address is supposed to do.

165
00:16:11,220 --> 00:16:12,280
So that's OK.

166
00:16:13,050 --> 00:16:16,620
This is mainly for teashops and for e-commerce.

167
00:16:16,920 --> 00:16:23,340
And this is totally fine when you have the similar products, Chuzzlewit, the same addresses, you

168
00:16:23,340 --> 00:16:29,480
are using the canonic attack not to get penalized for duplicate content.

169
00:16:30,060 --> 00:16:37,830
If you are wondering what all is this, you should definitely go for this e-commerce asmir or section

170
00:16:39,030 --> 00:16:40,710
kirova anomaly.

171
00:16:43,380 --> 00:16:51,450
Could be a number of things, so we need to investigate in this case, it looks like the page is listed

172
00:16:51,450 --> 00:16:58,860
as returning for all four korol, but currently not indexed.

173
00:16:59,910 --> 00:17:08,370
These are pages that Google has crawl up, but for some reason I'm not indexed, Google doesn't give

174
00:17:08,370 --> 00:17:12,030
you the exact reason they want index the page.

175
00:17:13,540 --> 00:17:21,190
But from our experience, this error means the page isn't good enough to warrant a spot in the search

176
00:17:21,190 --> 00:17:21,980
results.

177
00:17:22,600 --> 00:17:31,620
So what you should do to fix this, our advice work on improving the quality of any page is listed.

178
00:17:32,290 --> 00:17:40,690
For example, if it's a category page at some content that describes that category, if the page has

179
00:17:40,690 --> 00:17:44,350
lots of duplicate content, make it unique.

180
00:17:44,890 --> 00:17:47,710
If the page doesn't have much content on it.

181
00:17:48,130 --> 00:17:58,510
Bifida basically made a page worth of Google's index submitted page, not selected as canonical.

182
00:17:59,740 --> 00:18:08,530
This is Google telling you this page has the same content as a bunch of other pages, but we think another

183
00:18:08,530 --> 00:18:14,050
page is better, so they have excluded this page from the index.

184
00:18:15,320 --> 00:18:24,860
If you have duplicate content on a number of pages at the noindex, metal robots stack to all duplicate

185
00:18:24,860 --> 00:18:28,490
pages except the one you want to index it.

186
00:18:30,450 --> 00:18:39,390
Blocked by robots, these are pages that robots blocking Google from crawling its walls, double checking

187
00:18:39,390 --> 00:18:46,300
these errors to make sure what you are blocking is meant to be blocked if it's all good.

188
00:18:46,680 --> 00:18:51,630
Then robots is doing its job and there is nothing to worry about.

189
00:18:52,650 --> 00:19:01,830
Duplicate page without canonical tech debate is part of a set of duplicate pages and doesn't include

190
00:19:01,830 --> 00:19:02,970
a canonical.

191
00:19:04,220 --> 00:19:10,170
A dress can only go back in this case, it's pretty easy to see what's up.

192
00:19:11,860 --> 00:19:20,280
We've got a number of pages of documents, and this PDF contained content from other pages on this site.

193
00:19:20,950 --> 00:19:23,170
Honestly, this isn't a big deal.

194
00:19:23,590 --> 00:19:30,850
But to be on the safe side, you ask your web developer to blog DPD using robots.

195
00:19:31,600 --> 00:19:36,160
That way, Google only indexes the original content.

196
00:19:37,190 --> 00:19:40,040
Discovered currently not indexed.

197
00:19:40,760 --> 00:19:46,900
Google has kirova these pages, but hasn't included them in the index here.

198
00:19:48,760 --> 00:19:58,810
Excluded by no index stack, all good, the no index is doing its job, so that's the index coverage

199
00:19:58,810 --> 00:19:59,510
report.

200
00:19:59,890 --> 00:20:01,450
We are sure you agree.

201
00:20:01,450 --> 00:20:08,870
It's a very impressive to check the HCM, our Improvement's report.

202
00:20:09,850 --> 00:20:11,560
I am honestly no coder.

203
00:20:11,590 --> 00:20:14,380
That's why I love so much Imada.

204
00:20:14,380 --> 00:20:22,930
And that's why I'm showing you how to create complete website with Awada, how to use as we all how

205
00:20:22,930 --> 00:20:26,410
to call it, analytics and Google search console.

206
00:20:29,700 --> 00:20:40,080
Even that if you don't have correct HDMI, it can hard your AC or it should not happen to you anyway

207
00:20:40,080 --> 00:20:40,960
with Imada.

208
00:20:41,610 --> 00:20:46,150
And this is especially true for your tither and ascription tax.

209
00:20:46,920 --> 00:20:57,630
In short, every page on your side should have a unique, well-written title, up to approximately 70

210
00:20:57,630 --> 00:21:07,840
characters, a unique, well-written meta description, up to 300 characters, every single page unique.

211
00:21:08,460 --> 00:21:17,340
Yes, even if you run an e-commerce site with a bazillion pages, Fortunata, it's extremely easy to

212
00:21:17,340 --> 00:21:26,820
spot HMO problems in the search console to load up the HMO improvement's report.

213
00:21:26,820 --> 00:21:28,860
And Google will tell you what's up.

214
00:21:29,550 --> 00:21:38,520
As you can see, search appearance and HMO improvements on the you need specifics.

215
00:21:38,940 --> 00:21:46,820
Just click on a category for a full list of pages with issues, as you can see on the page.

216
00:21:48,000 --> 00:21:50,220
And now the most important.

217
00:21:50,940 --> 00:21:58,140
We have managed to understand all this technical, ethical issues and you just understand them.

218
00:21:58,590 --> 00:22:05,720
But you will probably not use your knowledge unless you become a professional as your consultant.

219
00:22:06,450 --> 00:22:09,140
But you might become so it's useful for you.

220
00:22:09,600 --> 00:22:16,410
But now the most important, how to get more organic traffic with the performance report.