►
From YouTube: SEO status brief — 2020-10-16
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
y'all
shane
rice
here
with
a
weekly
update
on
seo
for
about.getlab.com
and
just
gitlab
in
general,
so
starting
right
off,
I
want
to
talk
about
the
301
to
302,
redirect
or
reverse
that
302
to
301,
redirect
that
we
just
made
for
logged
out
visitors
of
gitlab.com,
so
the
the
best
indicator
of
you
know
success
here
is
watching
what
happens
with
about.getlab.com
as
far
as
a
result.
So
we
want
to
see
how
often
people
get
served
this
in
impressions.
How
often
people
click
on
this?
A
So
we
see
a
big
drop
in
any
one
of
these,
then
we
would
know
that
people
are
being
sent
back
to
gitlab.com
from
search
results,
which
is
not
what
we
want
so
right
now,
everything's
stable
there
we're
keeping
a
close
eye
on
this
just
watching
to
see
if
we
you
know,
can
detect
any
movement
here.
You
know
part
of
what
we
are
looking
at
is
this
is
kind
of
an
edge
case.
It's
really
unique
to
gitlab
at
our
scale
and
kind
of
how
that
redirect
was
working.
A
We
don't
have
any
kind
of
clear
indicators
that
there
was
a
technical
reason
that
google
was
doing
that
from
our
infrastructure.
So
our
best
guess
right
now
is
that
that
flip-flop
was
driven
by
user
behavior
in
the
browser,
combined
with
the
fact
that
it
was
marked
as
a
temporary
redirect
so
everything's
still
looking
good
there
taking
a
step
back
bigger
picture,
I'm
working
with
salt-
and
you
know
the
internal
inbound
marketing
team-
is
focused
on
issues
on
about.getlab.com.
That's
something
we're
very
familiar
with
we're.
A
Looking
at
docs
as
well
a
little
bit
now
in
conjunction
with
the
docs
team,
but
we're
we're
not
really
as
conversant
on.
You
know
prop
seo
issues
within
com,
the
the
sas
product,
and
so
I've
asked
salt
to
take
a
look
at
the
sas
product
and
see
what
they
can
identify
as
areas
of
concern
and
then
also
looking
at
moving
forward.
Things
like
getting
cloud
flare
logs
in
place
for
the
product,
so
we
can
start
to
see
where
search
crawlers
drop
off.
A
So
if
we
get
those
logs,
what
we'll
be
able
to
see
is
like
so
hey
this
crawler
they
they
weren't
able
to
reach
this
page
or
when
they
reached
this
page.
They
weren't
able
to
access
this
asset
on
the
page,
and
so
we
can
start
to
identify
those
areas
where
you
know.
Google
may
not
be
serving
up
gitlab.com
pages
because
they're
not
able
to
access
the
content
so
and
then
also
looking
at
broader
kind
of
general
optimizations
we
can
make
on
page.
A
So
that's
something
that
you
know
we
talked
assault
about
last
week
and
we
have
a
bi-weekly
cadence
with
them.
So
I'm
going
to
talk
to
them
about
you
know
what
they
found
so
far
next
tuesday,
so
I'll
have
an
update
from
them
at
that
point,
just
with
either
initial
findings
or
next
steps
on
what
we
need
to
provide
to
them.
So
we
can
make
that
happen.
So
that's
a
quick
update,
you
know
happy
to
answer
any
questions.