►
From YouTube: Daily SEO status brief — 2020-09-23
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,
today's
update
on
the
daily
seo
status
so
looking
at
cookiebot
and
302
to
301,
redirect
on
gitlab.com
for
users
that
are
not
signed
in
so
starting
with
cookiebot.
Good
news
here
is
that
sarah
daley
updated
some
text
and
added
the
personalization
checkbox
as
a
default
in
cookiebot,
so
going
forward.
Anyone
that
accepts
our
cookies
in
cookiebot
and
gdpr
countries
are
going
to
show
up
in
google
analytics.
A
A
You
know
I
I
I
don't
know
how
long
this
update's
been
in
in
place
where
we
had
that
check
box
unchecked
as
a
default,
but
I
you
know,
I
think
that
until
we,
you
know,
go
through
a
full
year
cycle,
we're
not
going
to
get
everybody
that
had
accepted
cookies
previously,
so
I
don't
know
if
we
can
do
like
a
roll,
a
rolled
request
like
where
we
say
okay,
so
last
you
know
three
months.
A
You
accepted
we're
gonna,
send
now
and
then
just
kind
of
work
back
from
there
or
if
we
can
do
any
kind
of
targeting
like
where
we
say
if
you've
accepted
we're,
gonna
ask
you
to
re-accept,
but
if
you've
rejected
we're,
not
gonna,
ask
you
again,
you
know,
I
don't
I
don't.
I
don't
know
how
much
impact
we
would
have
like
just
asking
again
everybody.
A
I
just
want
to
throw
that
out
there
as
a
question
and
get
your
thoughts
on
the
best
way
to
move
that
forward,
so
that
we
can
capture
as
much
of
that
immediate
traffic
as
possible
in
google
analytics
further
update
moving
forward
with
one
trust
as
a
possible
cookie
bot
replacement.
A
There's
an
issue
in
the
agenda
that
links
out
to
that
where
you
can
see
that
and
then
moving
on
to
the
302
to
301,
redirect
infrastruc
infrastructure
team,
a
shared
plan
cameron
is
working
on
this,
so
building
a
new
release
of
the
terraform
workers,
module
testing
that
comparing
it
to
and
removing
the
old
one,
getting
a
production
issue
written
up
for
change
management
to
make
sure
that
something
goes
wrong.
Whoever
sees
it
can
roll
it
back
and
then
creating
a
terraform
merge
request
to
prep
for
roll
forward.
A
So
if
there's
an
issue,
they'll
have
their
merge,
requests
ready
to
just
replace
this
and
and
move
everything
out
so
todd
yes
about
timing.
You
know,
I
think,
when
they
shared
the
timeline
of
next
week,
I
feel
like
that
was
building
in
time
for
unplanned
work.
So
if
you
know,
there's
outage
or
something
like
that,
that
comes
up
they'll
still
have
time
to
complete
this
without
missing
a
deadline.
I
think
that
we'll
get
it
sooner,
but
we
may
not.
I
don't
have
a
definitive
answer
on
on
that.
A
A
You
know
cameron
is
pairing
with
people
to
you
know,
improve
the
code
already
found
some
ways
to
improve
a
kind
of
a
302
like
an
edge
case
where
some
302s
are
still
there
for
some
reason
showing
up
in
the
analytics
that
he's
looking
at
for
the
staging
environment.
So
they've
come
up
with
a
solution
for
those
you
know
remaining
302
edge
cases,
so
I
feel,
like
you
know,
having
the
time
to
work
through
this,
and
you
know
make
the
changes
that
are
going
to
set
us
up
for
long-term
success.
A
That's
what's
that's
what's
happening
now,
so
I
feel
good
about
this
process,
just
kind
of
as
a
personal.
Take
on
your
question.
As
far
as
you
know,
can
we
speed
this
up?
I
think
we're
we're
going
at
the
correct
pace,
for
you
know
the
potential
impact
this
could
have
to
visitors.
So
with
that
I
am
going
to
sign
off
for
today
happy
to
answer
any
questions.