►
From YouTube: SEO status brief — 2020-10-02
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everybody:
it's
a
friday
about
4
30..
I
want
to
record
the
weekly
seo
update.
So
this
week
we
have
watched
the
impact
of
the
changes
we
made
to
cookiebot
and
lots
of
positive
movement
there.
The
you
know
we're
asking
for
personalization
as
a
default
option
and
requesting
everyone.
Opt-In
again
has
definitely
boosted
what
we're
able
to
see
in
google
analytics.
So
hypothesis
proved
correct
there.
You
know
we're
still
below
2019
numbers
for
september
and
as
we
move
into
october,
we
can
expect
that
that's
going
to
continue.
A
Part
of
that
is
because
there
were
some
trends
in
september
last
year.
We
just
can't
replicate
series
e
being
one
of
those
also
our
first
iteration
of
display
advertising
really
boosted
traffic.
During
that
time
frame,
we've
refined
our
targeting
and
improved
the
you
know
the
cost
there,
and
so
the
the
actual
traffic
coming
in
from
display
is
lower,
but
we're
improving
the
efficiency
so
yeah.
I
think
this
is
a
great
indicator
that
you
know.
A
Traffic
is
not
the
only
indicator
of
success,
so
we're
going
to
continue
to
you
know,
do
everything
we
can
to
grow
traffic
as
much
as
possible
in
organic
channels.
Demand
gen
focus
on
paid,
but
that
you
know
we're
also
going
to
be
looking
at
efficiency
with
conversion
and
other
areas
to
make
sure
we're
making
the
most
of
the
traffic
we're
getting
so
and
then
moving
on
to
the
302
to
301
redirect
everything
looks
good
there.
301
is
still
in
place.
A
You
know
just
setting
expectations
around
the
timeline,
so
you
know
basically
what
we
did
with
the
302
was
tell
google
that
anytime
somebody
linked
to
an
to
gitlab.com
in
a
news
article
or
any
other
place
that
they
got
sent
to
a
temporary
home
on
about.getlab.com.
So
our
hypothesis
is
that
those
links
were
not
passing
any
authority
to
about.getlab.com
all
that
authority
was
resting
with
gitlab
the
application.
A
So
now
with
the
301
that
is
seen
as
a
permanent,
like
you
know,
an
authoritative
passing
redirect
so
we're
passing
that
link
equity
into
about
nightgitlab.com.
So
this
is
going
to
be
a
slow
impact.
It's
not!
It's
not
like.
A
You
know
flipping
a
switch
and
everything
just
happens
because
google's
out
there
crawling
I'm
hitting
these
links
and
then
crawling
back
to
us
and
seeing
what
happens
so
my
expectation
is
it's
going
to
take
three
to
six
months
to
really
see
what
happens
there,
because
there's
always
a
chance
that
those
redirects
have
been
302
for
so
long
that
google
just
doesn't
really
refresh
that
doesn't
look
at
that
again.
You
know
we
can't
say
for
sure
my
expectation
is
that
they're
going
to
crawl
it
they're
going
to
give
us.
A
You
know
some
authority
based
on
that
redirect,
but
you
know
there's
always
that
outside
chance
that
they've
been
in
place
for
is
a
302
for
long
enough.
Where
there's
not
really
any
change,
so
you
know
not
quite
sure
what
to
expect
there.
But
I
do
expect
that
we'll
know
more
in
the
next
three
to
six
months
on
what
we
can
expect
from
or
what
we'll
see
there
from
the
change
from
that
302
to
a
301.
So
those
are
the
updates.
A
This
week
next
week,
we're
working
with
salt
to
begin
to
investigate,
moving
our
redirects
and
everything
to
sloth
cloud.
That's
going
to
require
the
migration
of
cloudflare
we're
going
to
look
at.
You
know
just
what
we'll
need
to
set
that
up,
and
I
will
update
you
on
that
at
the
end
of
the
week.
So
if
you
have
any
questions
in
the
meantime,
you
know
hit
me
up
on
slack
dive
into
one
of
the
issues
that
we're
talking
about
this
stuff,
I'm
more
than
happy
to
answer
any
questions
and
take
a
little
deeper
look.