Thứ Bảy, 1 tháng 7, 2017

Youtube daily google Jul 1 2017

Fetch as Google, part of the Google Search Console, lets you simulate how Google will

render a published page, and it'll also let you submit your pages to Google's index.

The goal of course being, to get your site or changes to your site up on Google as quickly

and efficiently as possible.

Now Google's pretty good at catching and indexing changes on its own.

But there are two really great tools that can help in this department:

Fetch… and Index.

Let's start with Fetch.

From the Search Console, you can run a Fetch under the Crawl category: specifically Fetch as Google.

This tool lets you see how Google renders pages from your website, which we know because

on the top of the page it says "see how Google renders pages from your website."

By default, the URL field is left blank.

And if we move forward without entering a specific path, the tool will fetch our homepage.

Now we have two options:

Fetch or Fetch and Render.

Fetch will let you see how Google views your code…and Fetch and Render will do the same

thing, plus give you a visual representation of what Google sees.

For right now, let's Fetch & Render so we can explore visually.

This can take a moment…but what you're looking for is a status of Complete.

You can see below some alternate statuses — these will display if Google can't access

your site or some of the resources on your page.

This will usually only happen if you've manually blocked content on your site — if Google

can't access something.

But now that it's complete, we can hover over and click the row to take a closer look.

And right there, we have a side-by-side: to the left, how Google sees the page; to the

right, how a visitor might see your page.

Of course, Google's looking for text, images — it's looking for content — things it

can add to its search index, so specific layout and style considerations aren't a factor here.

So don't worry if your layout and font selection look a bit odd.

Now you don't have to visually browse through every page, and you don't even have to do

it with your homepage.

This part can be helpful for troubleshooting, but the real killer feature here is indexing.

Once you've done a Fetch or Fetch and Render, you can request indexing.

Now this is great if we've made an update to our site or a specific page, and we want

to let Google know right away.

So if we've updated our site, and we've done a Fetch on our homepage, crawling our URL

and its direct links means Google will follow

links from your homepage and crawl those pages, too.

If we've only updated a specific page?

Or we're just looking to have Google update one URL only?

We have that option as well.

Now both requests have limited submissions inside a 30-day period,

so don't worry about re-indexing obsessively

every time you fix punctuation or update a font color.

And, thats it!

So we have Fetch and Render, which gives us info regarding Google's access to your site,

And we have Request Indexing.

Asking Google to re-crawl and re-index your URL.

That's…Fetch as Google.

For more infomation >> Fetch as Google - Duration: 2:38.

-------------------------------------------

google Adsense ADDRESS verification and Differences solution-Google adsense Google|YTGuide 2017 - Duration: 7:22.

google adsense

google

adsense

if yo want to verify your address through bank statement

then you have to take some documents like your bank statement

For more infomation >> google Adsense ADDRESS verification and Differences solution-Google adsense Google|YTGuide 2017 - Duration: 7:22.

-------------------------------------------

Google & EU: 2.4 Billion Fine Explained! - Duration: 7:34.

okay so in this video - I'm going to be talking and the EU

who charged google 2.4 billion this week so in this video and then I tell you what the

background was to that case and why it happened I'm going to talk about quite

actually happens and then finally I am I feel most interestingly I'll talk about

why this matters and where it might go from here and why I think it's a good

thing to be aware of and to know about so just before I start I in front of a

thank you very much to everybody who subscribed to the channel I'd love to

know if anybody have any suggestions for content and if you're new to the channel

thanks very much for listening I put up videos about two or three times every

week so please subscribe and I hope I see you again okay so what is the

background to this situation with Google and veu

well first of all I think it's just important to explain what the problem

watermark what the services that says have got itself into this situation

so Google offers a service called Google Shopping so if I type in blue handbag to

Google it will return results that show a bar of images with different blue

handbags in them and this bar is a basically Google shopping service so it

offers a whole load of different suggestions of shops that are selling

blue handbags if you want to buy them now it should be noted that each of of

the images that it shows are ads so if you see a blue handbag from you know

like Marks & Spencer is or something Marks and Spencers have paid for that to

be there so it's fold an ad but if also a search result and companies like

TripAdvisor Yelp and other price comparison websites brought a case to

the EU suggesting that what Google were doing was fundamentally anti-competitive

because all of these other price comparison sites that you can go to to

look at the different prices for blue handbags

or a TripAdvisor safer for holidays is an anti-competitive because Google is

showing just their own result first and some of these other companies that also

compare prices are much further down in the search results I think it's

important to remember that within the EU Google has something like 90 percent of

market share for search so that's across the 31 am countries

that are included in the EU economic area so we're talking about an

incredibly dominant presence in the worldwide web basically in in the EU and

Google listens to these charges and basically said that they were just

fundamentally providing users with the search term that they were looking for

so they were just giving the users what they wanted and second of all that and I

suppose again fundamentally Google is a advertising platform so it's not going

to have put up ads by other services it's under no obligation to advertise

them okay so this went to court and and it was realized during the week that

Google we're going to be fined 2.4 billion which is 3% of their was 3% of

their 2016 turnover and um the woman who is the Competition Commissioner Margaret

Thatcher and she's the comer sort of quite well-known face in the tech

community she said this and Google were systematically favoring their own

service and above all the service of others and that they what they were

doing was illegal because it was breaking the EU antitrust rules so

that's what the charge that's been laid against them and it has quite deep and

and wide-ranging implications so why are these implicate

I'm not going to happen next well I feel most simplistic way of explaining this

is that this might be the beginning of a much greater charge against Google but

first of all Google do have the option to appeal so they may appeal it and

those kind of appeals can take like 10 years it could be years or four before I

think really happens and interestingly the EU did impose a fine upon them but

they didn't actually say um class changes should be made to the furthest

or they didn't reclassify the changes that need to be made Google now have 90

days to pay off the 2.4 billion fine and if they don't pay it off within the 90

days they will then be charged a daily fine which is 5% of their daily revenue

that's a significant enough and dent in the Google coffers and now why this is

interesting is because there's been a huge amount of outcry across a variety

of industries about how much of an app our monopoly

google has on everything from search to maps etc etc etc so by bringing this

charge against Google some people believe that it might mean the beginning

of the EU treating Google as a monopolist and and getting into deep

legal challenges with them about their monopoly similar to what happened with

Microsoft in the 1990s so it could be the beginning of something huge here and

the beginning of may be a challenge to Google's huge diamonds over the online

world and they at the moment they also they still have to two other ongoing

court cases with Google and that are are yet to come to any conclusion and

another kind of export quite interesting aspect to this is that really to base

people believe in many ways Silicon Valley monopolists

like Google like Amazon have been protected by democratic governments like

Barack Obama Google founders like Eric Schmidt were very close with Hillary

Clinton and actually now that Donald Trump is in the White House maybe some

of these guys are going to lose the monopoly that they have and they will be

found to also be breaking antitrust rules in the US so I think this is

interesting as a new story and certainly for me the most interesting new story

this week because I think it might be a signifier of something much bigger than

design okay so thanks very much fit into this video and everybody for all your

comment I love getting them for not meeting them and replying when I can so

time very much for and the following and I hope I see you soon

For more infomation >> Google & EU: 2.4 Billion Fine Explained! - Duration: 7:34.

-------------------------------------------

Find cheap airfare with Google Flights - Duration: 1:45.

For more infomation >> Find cheap airfare with Google Flights - Duration: 1:45.

-------------------------------------------

Bam Bam Backlinks Review | How to Rank your Videos on Google by Adam Payne - Duration: 14:13.

For more infomation >> Bam Bam Backlinks Review | How to Rank your Videos on Google by Adam Payne - Duration: 14:13.

-------------------------------------------

Blind GQL injection and optimised binary search - A7 ~ Gee cue elle (misc) Google CTF 2017 - Duration: 14:25.

A7 - gee cue elle was a hard misc challenge.

It combines a database query injection with optimizing the algorithm to perform the attack.

So also partially a programming or computer science challenge.

When I first read the title I mispronounced it as "gi que elle", so a more german

pronunciation and I totally didn't get what it tried to hint at.

But more about that later.

Let's get started.

A7 - gi que elle,

We installed a fancy automatic attack protection system to be more secure against automated

attacks from robots and hackers, so it can be fully A7 compliant.

And a hint with .yaml tilde.

So the first thing I did was look up a7 again.

because of the "fully a7 compliant" comment, I immediately thought it's probably that

OWASP thing.

So what is it again?

OWASP Top 10.

A7 insufficient attack protecion….

Ohhhh that thing.

What a bullshit item on that owasp list.

If you want to read about some infosec drama, search for a7 controversy.

And this challenge is certainly a reference to that.

Anyway, I took this as a hint that I should use some automated attack tool.

Which in retrospect I think was wrong.

But whatever.

The description has a few more hints, but we will get back to that in a minute.

Let's first check out the site.

The challenge here links a .html file with the following content.

So part of the subdomain can be random.

It's obviously to give every player a unique site.

We will see that come up later.

On the site itself we can find a simple login field and when we inspect the html, we see

a validation pattern that tells us the username has to be admin and the password has to follow

a more complex pattern.

It's basically a valid flag pattern.

CTF curly braces then some characters that start with quotas, and if you paid attention

you can see that the subdomain is basically that part here, and then followed by 64 characters.

So it seems like if we find the correct password for the admin user, we have found the flag.

Like I said I though the a7 hint meant to tell me to use some tool, so I used nikto

which basically does something like dirbuster and it found an app.yaml file.

It turns out I could have found that myself if I had looked into the robots.txt, oh well.

That qa entry here threw me a bit off but ignored it mostly.

And this is where the second hint comes into play.

The yaml tilde.

So if you didn't know what that means, some editors such as emacs or maybe vim create

files to track your current progress in case you don't save and it crashes or so.

Then it can be recovered.

And some editors create a file with the same name but append a tilde.

And that's basically what happened here, the developer apparently opened the file in

an editor and it created that tilde file and for some reasons it didn't get deleted.

The yaml file is really interesting, it's basically a web application config file for

google app engine and it tells us here where the app that handles the page lives.

I might also google a little bit to learn more about app engine to understand the structure

of this file.

So basically I'm hunting now for the application sources.

In the google app engine docs I find a hello world example using main.py, so I tried that.

And with the tilde there as well, I can leak the content.

So now we got the sources.

The code doesn't look too big, but there are some dense areas.

A first thing you might notice is, that there is something about quotas and an abuse detection

system.

Mhmh…

And when I looked at the code, there was a lot of time calculations and I hoped I didn't

have to understand that right now.

So I continued.

Here the login post request.

That must be a very important part.

And indeed, I immediately noticed a query language injection.

You see this here the colon 1 together with the parameter here is safe, but this direct

python string manipulation with percentage s is unsafe.

We can inject another single quote and break out of the string and screw with the query.

So is this an SQL injection?

Well.

kinda.

not really.

As you can see here in the function name it's gql.

Google query language.

At this point I still didn't get that the title of the challenge was supposed to hint

for that.

Gee cue elle.

But.

Oh well.

So what can we do with that, ideally we want to be able to log in.

So what kind of features could we use in the query language.

If you look up the grammar of the query language it's really short and there is not much

you can do.

So we are here in the WHERE condition and all we can do is append more conditions with

AND.

There is not even an OR.

And we could sort or limit the result but that's not really useful.

So no SQL UNION SELECT to inject a password we can control to bypass the authentication

or so.

The only output we have is either wrong username or wrong password.

So it's going to be a blind injection.

The idea is if we make the query return a password, then the password we supply would

be wrong and if we make the query return no password, we would get the wrong username

error.

We can play with this.

GQL doesn't have advanced string stuff like SQL.

For example there is no WHERE password Like A%.

Where password like B%.

to slowly bruteforce the first character.

But we can basically simulate that with greater or lower than.

So you can inject a compare if the password is bigger than A, and if that's the case

the query returns the password and we get wrong password error.

But if the password was not bigger than A, then the password might start with A or another

char that's lower than that, then the query would not return a password and we get the

wrong username error.

So we can in fact slowly bruteforce the password.

So I start writing some code to do that.

The comparison works by ascii value, so the order of chars is how they appear in ascii.

So lowercase a is bigger than capital A.

So I was writing that code but I quickly ran into the "Abuse detection system".

I was banned for 90 seconds because I either triggered two errors in 30 seconds, or made

more than 13 requests per 30 seconds or it took me longer than 2240 seconds.

Oh damn.

Because with every request we get an error, we can only perform one request every 15 seconds.

To not trigger the 2 errors in 30s rule.

And not only that, we only have 2240 seconds time for that.

That's only 150 requests.

But the flag is already at least 64 bytes long.

We know parts of the password just not the main part.

This means we have only like 2 requests per character.

We will never bruteforce the password with those restrictions.

So I started to review more of the code and long story short, I couldn't find a bypass

for the abuse detection system.

Also the password is dynamically generated, but it's safe.

It's hmac with a secret key and the first part of the hostname.

Which means if you know the secret key and I give you a valid flag, you can verify that

it's valid.

The first part generates the second part.

So also no tricks possible there.

Basically I had following options in mind: Bypass detection system

Find an issue in the dynamic flag/password generation

Better gql injection Try to optimize the bruteforce

Like I said first one lead nowhere, second one was also unlikely, third one too, the

query syntax is just so short, which means the only viable way is optimization.

So an obvious first improvement to the bruteforce with greater and lower is to do a binary search.

Basically we have an oracle that tells us with a guess of the password if the real password

is greater or lower.

Which means we can lower the amount of requests necessary.

My first implementation did this per character.

Each character has 64 options and with binary search you can find the right guess in about

log N steps.

So about 4.1 steps necessary per character.

Which means we need roughly 262 steps in total, which doesn't work, because we only can

do up to 150 requests in the time we have.

So I was stuck there for a while.

A lot of time went into fixing programming bugs and testing it and because it's so

slow.

with 1 request every 15s it is just took ages.

But then when I did another round of auditing the code I noticed something.

So error requests, of which you can only have two every 30 seconds, are only counted on

exceptions.

And if you look closely in the login code you can see that only a wrong password triggers

an exception.

Wrong username is just a regular request of which you can have 13 per 30 seconds.

That's the key!

We need to optimise the binary search to favor wrong username over wrong password.

So how do we do that?

Well in binary search you always select the center of your search area.

This means there is a 50:50 chance that your item is either greater or lower.

So how can we skew that chance.

Well instead of picking the center, we pick something more towards one side.

For example if we do a 75:25 split, we have a much higher probability that our item is

going to be lower than that new index.

In our case we can have 13 requests in 30 seconds but only 2 of those can be errors,

so we have 2 divided by 13, roughly a 85 to 15% split.

Awesome.

Also I optimised the string generation by working with numbers rather than a character

string.

So basically our string we want to brute force has an alphabet of 64 characters.

So it's like a base64 number system.

Which means we can convert between base10 and base64.

Don't confuse it with base64 encoding, I'm really talking here about the mathematical

numeral system base 64.

Maybe you had to convert base 10 to base 16 or base 3 in school, that's basically what

I did.

So I created two functions to convert a base64 number to a base10 number and vice versa.

So now I can treat the binary search as a search of a number.

The highest value is basically lowercase zzzzzz, which is a huge number.

And this is the code I came up with.

I use the requests module to perform the gql injection request.

Then I define the alphabet for the flag in ascii order.

Here are my functions to convert from base64 to base10 and vice versa.

And a function to display a number line to visualise the search.

And here are the important search variables.

At the beginning the highest number is basically zzzzzzz

And lowest is obviously 0.

The current flag we will check, so the search index is initialized with 85% from the top.

So that it's skewed towards higher values and our real password is probably lower.

And those are lists to count the exceptions, so wrong passwords and regular requests I

make.

At the beginning of the search loop I have a look at the lists that remember all exceptions

and requests and remove the requests that are older than 30 seconds, because they don't

matter anymore.

But if we have had more than 1 exception in the past 30 seconds, or had more than 11 regular

requests, we are going to sleep for a second.

Then we clean up the list again and maybe sleep again, until the condition is not true

anymore.

Then we are allowed to perform another request.

So we convert the current search index to the flag string and perform the request.

Some nice log output And then we check the result.

If it was wrong username, then our guess was bigger than the real password, so we can set

the highest possible value to that and move the search index down a little bit.

But always move it in the 85:15% ratio.

If we get wrong password, we get an exception, so we rememebr the time we had the exception

and we also know our password was greater than our guess, so we take the upper part

and move the search index higher.

And that's it.

We just have to let it run now.

Doesn't it look beautiful?

Here you can see how the search index, the X always skews to the higher values and how

the search space is narrowed down.

And there is a nice ratio now of wrong username and wrong password requests.

This takes now a while.

Basically 2240 seconds or 37 minutes.

But we will still just barely make it in that time.

So I started many instances in parallel and hoped that at least one will succeed.

And this is where I started to become nervous.

Because the end of the CTF was approaching and I was not sure if it will work, I didn't

have one successful run yet.

Will the flag I find work or will it break?

Will I do my calculations right?

Do I have bugs?

And about 10 minutes before the end two processes approach the final guesses.

There we go, search space is apparently now 0.

We found our flag.

hopefully.

So I tried to enter the flag, super shaky hands because I had to be fast with minutes

left but it didn't work.

Wrong flag.

Also I couldn't login with this flag.

It was not correct.

DAMN.

But I had a hunch what the problem was.

I probably didn't quite get the calculations correct, so I was probably 1 or 2 numbers

off.

So i just adjusted the last character of the flag and after a few attempts, I got the right

flag.

Damn that was close.

But really happy at the end, because just FYI, I spend probably like 12 hours on this

challenge.

For more infomation >> Blind GQL injection and optimised binary search - A7 ~ Gee cue elle (misc) Google CTF 2017 - Duration: 14:25.

-------------------------------------------

Top 10 Hidden Google Features (You've Never Heard Of) - Duration: 10:22.

Google, we use it all the time, probably even every day.

And Google obviously isn't just a search engine, they have a ton of other projects that are

really awesome that you've probably never even heard of.

So in this video I'm going to tell you about 10 cool features and services by Google that

I bet you didn't know existed.

And these won't really be in any particular order.

Let's jump right in.

Starting off, we have a feature built right into Google search, which basically lets you

use Google as a proxy.

All you have to do is type in the search box, "Cache:WhateverWebsite.com".

This will take you directly to Google's cached version of the site.

As you may or may not know, Google takes a cache of all the websites it indexes for search,

and in regular search you can usually click the down arrow next to a result to go to it.

But with this, you don't have to look through the results to find the right page you want

to access.

And this cached version can be useful in a lot of situations.

Like if you're behind a firewall at school or work that is blocking the website.

You obviously can't log into the site because it's just a static page, but at least you

can see it.

Another reason might be if the website is down or taking forever to load, you can look

at the cached version to see what was on it.

And it will tell you at the top what time the cache was taken, which is usually pretty

recent.

Next up is another basic feature you can do in the search, which is tracking flight status.

All you do is do a search for the name of the flight, like "Flight 999" which is apparently

a real flight, and it will bring up all sorts of information.

You'll see the departure and destination locations obviously, when it departed, when it's going

to arrive, and a little plane symbol to show the current progress.

And if the flight has multiple legs, or you want to look at it for another day, you can

look that up too.

So it's really just a neat little feature maybe if you're waiting for a flight, or want

to check on a friend's progress.

Number three is for Gmail, and it's a feature that makes replying to some emails a lot easier.

It's not enabled by default, so you want to go to Gmail settings, then the Labs tab, and

look for the one that says "Quote Selected Text" and click enable, then save changes.

What this does is allows you to quote only part of an email instead of the whole thing

when replying to an email.

You just highlight a certain portion of any email with your mouse, and then click the

reply button as usual.

And now you'll see that it displays a quote just for what you've highlighted.

Could be a good way to avoid accumulating huge email unecessary email chains.

Moving on, number 4.

I'm sure you all know about Google Maps, and Google Earth, but did you know about Google

Sky?

Yes, it's a thing, just go to Google.com/sky and you'll see what I'm talking about.

It's a really cool page that lets you explore the entire night sky just like you might with

Google maps.

You can zoom in pretty far, and you'll notice in some spots there are images that are higher

resolution than the surrounding areas.

But that's not the only way you can look at the night sky, because it also has options

to view in Infrared, Microwave, and even Historical images.

With Infrared and Microwave it's especially cool because you're able to see parts of the

light spectrum beyond regular visible light, and it looks awesome.

You can even adjust the opacity so it just overlays the view a little bit, and you're

still able to see the regular view.

And with the historical view, it's pretty funny, you can get a look at how the stars

were mapped hundreds of years ago, with all the constellations drawn out as animals and

objects.

Very strange and interesting at the same time.

Alright next up, is a neat Google Project called "Project Sunroof", and the purpose

is to help you figure out if maybe you should consider getting a solar panel.

You type in your address, and it will show you all sorts of useful information.

Like how many hours of usable sunlight your location has per year to generate electricity,

and based on satellite imagery, how much space it thinks you have to place a solar panel.

Even if you don't plan to get a solar panel, it is still pretty interesting to see.

It will show you how much you might save by getting on based on your current electric

bill, and how much it might cost to actually get one.

This is apparently not available in all locations, but even if it isn't for you, they still have

a few sample addresses you can choose to at least see the basic idea.

And just looking at the map is cool, because it shows you exactly what parts of the roof

get the most sunlight, and where is the most shade, so you even know exactly where you'd

put it.

Not something I see myself doing, but still super cool.

Alright, number 6 is the "Google Public Data Explorer", which is a service that does exactly

as the name suggests.

You just click "Explore the data", on the left you'll see a huge list of statistics

you can search through and graph.

And it lets you display the information in all sorts of ways, whether it's a bubble graph,

or on a map, bar graph, or line graph.

And below the graphs you can even use the slider to change the time frame, to see how

the data has changed over time.

Using can be a bit confusing but it doesn't just let you look at a statistic one at a

time.

It also lets you compare any two, even if they don't make much sense.

For example, I can pick a random value for the Y axis like, the deposit interest rate,

and for the X axis, the total surface area of the country.

Obviously this is ridiculous, but you get the idea.

Then you can also change what the size and color of the circles represent in the bubble

graph.

By default circle size is population and color is region.

So needless to say, you could easily kill some hours on this site.

Moving on, we have another one for you data junkies out there called Google "nGram" Viewer.

This one is a lot easier to understand than the previous one, and pretty much all it does

is show you how often certain phrases has appeared in books and publications throughout

history.

For example, you might think the phrase "what's up" is a relatively modern thing to say, but

if we type that in, you can see that people have been saying that even since the 1800s!

You can also change the time frame to anything between way back in 1500 through 2008.

Some of the results are actually pretty surprising.

For example, if we type in WTF and search between 1900 and today, apparently that's

been around for a while.

And if you go back to 1500...

Whoa!

What the heck happened in 1650?

Our usage of WTF barely even registers on the chart!

Now I think it's pretty obvious whatever they meant by WTF back then was a lot different

than today, but still funny to see weird anomalies like that, and just mess around with it.

Ok, number 8 is a relatively new service that Google is actually starting to push recently,

called "Google Express".

And it seems like they made it to be some sort of Amazon competitor.

The main idea is you use Google Express to order stuff from their partner retailers all

through this site, and then they ship it straight to you within a couple days.

And there's apparently same day shipping in some areas too.

Right now the selection of stores is pretty limited, so I don't see myself using this

too often if at all.

But I think it could be a good alternative maybe if Amazon doesn't have something but

a local store does.

Unfortunately shipping isn't free unless you pay for a Google Express membership, which

is 10 bucks a month or 95 a year.

I personally think that's way too much for such a small number of stores, and even fewer

that I'd even go to, especially since Amazon Prime is about the same price.

Still, might be something you're interested in.

Alright coming near the end we have a couple apps by Google that you might not have heard

of.

So number 9 is the "Google Goggles" app, where you point your camera at any object in front

of you, and Google will analyze it, try to figure out what it is, and maybe display some

extra information too.

Unfortunately it seems like the the live camera view function is broken, and the app hasn't

even been updated since 2014.

But I was able to get it to work with already existing photos you pick from your gallery,

so that's good.

Maybe if you have an older phone it will all work.

Also, I bet this app is going to be replaced by the upcoming "Google Lens" that Google

announced this year, so be on the lookout for that.

And finally, we have Google's "Crowdsource" app.

This app was made to help train Google's Artificial Intelligence by asking humans about stuff

it doesn't know.

I wouldn't say it's particularly useful, but it is a bit amusing and can kill some time

if you're really bored.

There are a bunch of catagories, one example being Handwriting Recognition, where you try

to identify what the heck someone was trying to write.

Another interesting one is "sentiment evaluation", where it gives you a bit of text and you just

have to identify whether the text is happy, unhappy, or neutral.

Reading these are actually kinda funny because it seems like they're taken from online reviews,

because half of them are complaints about random products and apps.

Once you do enough tasks in a catagory, you actually "level up" and get a participation

ribbon.

Completely useless but might make you feel like you accomplished something.

So, that's about it.

10 cool Google features you probably had no idea existed, or at least a few of them.

If I missed anything, feel free to let us know in the comments below.

If you want to keep watching, here are a couple other videos you'll like, such as a list of

cool free windows programs, you can just click on those.

And if you want to subscribe, I make new videos tuesday, thursday, saturday.

Looking forward to hearing from you guys, so thanks for watching, I'll see you next

time, have a good one.

For more infomation >> Top 10 Hidden Google Features (You've Never Heard Of) - Duration: 10:22.

-------------------------------------------

TensorFlow Estimators: Managing Simplicity vs. Flexibility in High-Level ML Frameworks - KDD 2017 - Duration: 1:59.

For more infomation >> TensorFlow Estimators: Managing Simplicity vs. Flexibility in High-Level ML Frameworks - KDD 2017 - Duration: 1:59.

-------------------------------------------

Google Verification - Duration: 1:08.

Google Verification lets us verify ownership of a particular property (like a website or

an app) with Google.

Once we're verified, we're able to submit our property to Google so it can get listed

in their search index.

This, of course, is the preferred way to do it, even though Google might stumble across

your property from a link on another website.

Let's do a quick search for the Google Search Console and bring that up.

You'll want to start here by logging in to your Google account, typing in the URL for

the website you're wanting to verify, and you'll arrive at a page that looks like this.

What we're looking for here is the HTML Tag method.

In this instance, it's found under Alternate methods, right under HTML Tag.

Click "Show me an example" and select the content between the quotes, so you can copy

it right to your clipboard.

In our Webflow project, we can navigate over to Project Settings, and visit our SEO tab.

Once there, we can scroll down to Google Site Verification, and paste our copied.

Save those changes we just made?

And head on over to publish, so Google can recognize that we've added the verification.

Finally, back on Google?

We can simply verify.

And that's it!

We've successfully verified our website in Google.

For more infomation >> Google Verification - Duration: 1:08.

-------------------------------------------

Google Launch Data Saver App | TRIANGLE | Save Mobile Data On Go - Duration: 1:29.

CLICK ON SUBSCRIBE FOR MORE

For more infomation >> Google Launch Data Saver App | TRIANGLE | Save Mobile Data On Go - Duration: 1:29.

-------------------------------------------

New assistant function of the "Google Photos" "share of the candidate" - Duration: 1:44.

New assistant function of the "Google Photos" "share of the candidate"

Hello everyone

This time, we will explain the new assistant function of the "Google Photos" "share of the candidate"

"Google Photos" is added to 2017 June 29, the "Shared Library" feature, you can now use the ability to share photos automatically to other users

And the combined in this assistant function of the "Google Photos" "share of candidate" also has been newly added

This "sharing of the candidate", the image quality, time, location, is a function that will display the photos to be shared candidate based on the updated information in the Assistant tab

Depending on the frequency of use of "Google Photos" of the user, automatically learn, looks like us to display a candidate photo

And it will be able to easily share photos from Assistant tab

The "share of the candidate" is similar to other assistant function, it is also possible to turn off from the set

You can if you do not need them keep off easily function

Assistant function of the "Google Photos" such as "share of the candidate" is a convenient us to display and select the photos to be a candidate in the automatic function

In particular, since there is no merit to keep off the set, we recommend that you use remains on

Above, it was the explanation of the new assistant function of the "Google Photos" "share of the candidate"

For more infomation >> New assistant function of the "Google Photos" "share of the candidate" - Duration: 1:44.

-------------------------------------------

The Difference Between Google's Manual and Algorithmic Penalties - Duration: 2:50.

You're looking at the analytics for your website and, to your horror, you see that

organic traffic from Google has severely dropped or stopped completely. In a panic

you check if your site still, up if the analytics tracking code is still

installed, or if you accidentally blocked search engines from indexing your site.

Everything checks out, but you don't know what the problem is. If the stop or drop

in traffic was sudden, then congratulations, you may have a penalty

to deal with. There are different penalties that can have negative effects

on your site and all of them are either an algorithmic or manual penalty. Google

uses a mathematical equation called an algorithm to rank websites. This

algorithm checks your web pages against more than 200 on and off-page factors.

How your pages compare with the competition determines your place in

search results. An algorithmic penalty is when Google changes or updates their algorithm

and that change could cause a sudden drop in rankings and website

traffic. If you think an algorithm update caused your site's drop in performance,

check the SEO or digital marketing blogs for any info on a new update. If there

was one, look into what the update changed and when it was launched. If the

launch date is around the time your traffic and rankings dropped, then that

update may be your problem. It's also a good idea to track recent changes to

your website, as the change may have triggered a pre-existing algorithmic

penalty. Since there are multiple algorithmic penalties to deal with

you'll have to spend time researching the problem and finding the solution. If

you can't find news about an update or you haven't made any changes to your

site, then you may have been hit by a manual penalty. Your site gets a manual

penalty when it violates Google's webmaster guidelines. These guidelines

cover what is and is an acceptable behavior regarding your website.

Basically Google doesn't want you to use specific strategies to game their

algorithm to improve your site's position in search results.

Unlike an algorithmic penalty, Google sends a message to your site's search

console account telling you your site was penalized. You may need additional

tools and more time to fix a manual penalty, but that depends on what your

site is penalized for. Keep in mind that the negative effects from a penalty, both

manual and algorithmic, can affect your site well after

the penalty is removed. That's why you, someone on your staff, or your marketing

agency should keep up to date on rumored Google algorithm updates or periodically

audit your sites on and off page SEO strategy. And that's it. Those are the

differences between Google's two types of penalties. We put links below if you

want more info. And if you have any questions, comments, concerns, or sarcastic

remarks leave a comment or reach out to us on Facebook, Twitter, or our website.

And as always, thanks for watching.

Không có nhận xét nào:

Đăng nhận xét