►
From YouTube: Q2 Blog Traffic Review
Description
A recap of Q2 blog traffic including highlights, lowlights, and learnings.
B
Thanks
erica,
let
me
share
my
screen,
so
you
should
all
be
looking
at
an
issue:
fy
21
q2,
blog
traffic
review.
This
is
based
on
a
spreadsheet
that
I
put
together,
which
is
linked
to
from
the
issue.
If
you
want
to
dive
really
deep
into
the
data,
it's
put
together
a
little
bit
manually
at
the
moment,
we're
figuring
out
if
there's
a
way
to
automate
some
of
this.
But
essentially
this
is
just
all
of
the
blog
posts
published
throughout
the
quarter.
B
We
add
in,
for
our
own
purposes
the
source
and
the
function
which
is
just
kind
of
who
at
gitlab
has
like.
Where
has
this
originated
from
within
gitlab?
What
sort
of
purpose
is
it
serving
on
the
blog
and
then
the
category
you
can
see
on
each
blog
post,
and
then
we
use
a
two-month
window
to
calculate
the
sessions.
This
is
just
because
there's
no
simple
way
to
sort
by
or
filter
by.
You
know
one
month
from
date
of
publishing.
There's
no
way
to
do
that
kind
of
automatically
on
google
analytics.
B
So
we
just
use
a
two-month
window
to
give
posts
time
to
accumulate
page
views
if
they
were
published
at
the
end
of
a
calendar
month,
for
example.
So
that's
the
sheet
there's
a
tab
here
with
a
pivot
table
where
you
can
see
blog
posts
sorted
from
most
trafficked,
to
least-
and
this
is
all
kind
of
distilled
in
this
traffic
review
here-
which
I
will
go
through
briefly
now
as
well,
but
I'm
going
to
pause
in
case
there
are
any
questions
so
far,
okay,
so
the
top
level
numbers
you
can
it's
pretty
self-explanatory.
B
B
So
there
are
some
takeaways
here.
Community
related
posts
are
often
big
hitters
for
us.
I
think
that's
because
we
have
the
the
kind
of
momentum
from
the
community
sharing
that
news
as
well.
In
addition
to
us
just
kind
of
teaching
our
horn
about
something
and
then
yeah
the
the
sorts
of
posts
that
tend
to
do
well
on
a
regular
basis,
kubernetes
ci
cd,
those
are
always
kind
of
big
hitters.
This
rust
programming
language
is
an
interesting
one.
B
B
A
One
comment
on
the
rest:
one,
I
think
that's
super
interesting,
because
it's
something
we've
been
talking
about
a
lot
in
terms
of
our
editorial
strategy,
where
you
know
we're
trying
to
migrate
away
from
every
thinking,
so
get
lab
focused
to
really
focus
on
topics
that
are
trendy
or
timely
for
our
audience.
So
to
me,
it's
really
encouraging
to
see
that
do
so
well
and
that
people
thought
like
hey.
A
I
trust
gitlab
on
this
topic,
even
though
it
has
nothing
to
do
with
their
product,
like
it's
a
really
affirming
result
to
see,
and
I'm
excited
to
see
like
the
strategy
that
you
set
for
q3,
which
I
think
incorporates
a
lot
more
posts
like
this
and
see
what
those
results
are.
But
it's
a
really
good
early
indicator
of
that
strategy.
Working.
B
B
If
we
publish
a
blog
post
and
it
doesn't
get
more
than
a
thousand
sessions
in
the
quarter,
we
then
look
at
that
and
say:
okay.
What
did
we
do
wrong
here?
Is
it
just
a
topic?
That's
not
interesting
to
our
audience
was
the
angle
not
optimized
for
our
audience
kind
of
yeah,
just
why?
Why
didn't
it
get
as
much
traction
as
we
expected
so
I've
grouped
these
into
category.
B
No,
that's
that's
something!
That's
good
to
call
out
these
are
posts
that
the
editorial
team
worked
on,
not
including
unfiltered
posts
that
went
straight
to
unfiltered
and
did
not
get
republished,
and
we
might
include
unfiltered
posts
that
were
then
edited
by
us
and
republished
on
the
main
blog
because
we
identified
them
as
one
that
would
be
a
good
fit
for
the
main
blog.
B
So
I've
grouped
these
into
kind
of
loose
categories
to
to
see
what
we
can
take
away
from
that
we
have
a
number
of
promotional
announcements
which
we
have
tried
to
do
kind
of
work
on
this
in
recent
months
to
to
sort
of
document
some
best
practices
to
make
sure
that
we're
offering
our
audience
something
that's
kind
of
more
valuable
than
just
tweeting
our
own
horn,
about
something
that
happened
at
gitlab.
That
we
think
is
amazing,
but
we
haven't
really
translated
for
our
audience
and
what
it
means
for
them.
B
So
that
is
something
that
I
will
be
documenting
in
our
handbook.
As
like
a
change
in
strategy
taking
away
from
this,
then
we
have
what
I
call
operational
announcements
where
it's
kind
of
it's
not
really
sharing
anything.
That's
like
promotional
about
gitlab,
but
it's
it's
purely
just
a
it's
more
of
a
comps
exercise
like
we
need
to
get
this
information
out
to
users.
They
need
to
know
about
a
deprecation
or
some
kind
of
change
that
affects
them.
B
So
we
will
apply
the
and
we
already
kind
of
do
apply
the
same
principle
where
it's
just
like
we're
just
there
to
proofread,
to
make
sure
that
it's
formatted,
correctly
etc
and-
and
we
will
be
working
on
kind
of
separating
those
out
from
our
editorial
posts.
As
part
of
this
issue,
that's
linked
here,
I'm
going
to
give
it
a
beat
for
any
questions
or
comments.
Otherwise,
I'm
going
to
move.
B
We're
running
out
of
time
quickly,
this
section
was
kind
of
interesting,
because
even
though
we
have
some
tutorial
and
how-to
and
some
kind
of
practical
content
here,
these
didn't
do
well.
The
thing
that
sticks
out
to
me
is
that
almost
all
of
them
have
gitlab
in
the
title,
so
it
is
very
kind
of
inward
focused
which
may
be
less
interesting
to
others.
B
I
think
the
I
noted
in
the
previous
review
that
we
should
maybe
be
more
selective
and
kind
of
only
focusing
on
the
sort
of
big
hitters
when
we
do
feature
posts
and
kind
of
saving
that
for
things
that
have
been
highly
requested
or
are
extremely
popular
with
the
community
and
it's
possible
that
some
of
them
just
needed
a
headline
tweak
to
make
it
kind
of
less
inward
focused.
So
I
gave
the
example
here
of
like
how
good
that
cai
helped
solve
commendable
challenges.
B
You
know
that
there
we
don't
necessarily
need
to
make
it
about
gitlab
ci
in
the
title
it
could
be
about
ci
in
general,
and
then
you
have
an
example
about
kit
lab
in
in
the
in
the
post
itself.
The
this
kind
of
year
in
review
roundup.
We
have
already
documented
a
suggestion
for
how
to
do
those
better,
because
those
kind
of
come
up
from
within
get
that.
A
So
do
you
feel
like
there's
an
opportunity
here
to
explore
with
dan
gordon
and
the
technical
marketing
managers,
whether
it's
getting
some
of
the
video
content
and
things
included
and
making
a
bigger
deal
out
of
them,
or
you
know
taking
these
posts
to
them
and
seeing
if
it
makes
sense
in
the
like
the
learn
environment
that
they're
creating?
Not
that
we
would,
you
know,
make
it
our
job
to
start
creating
that
content,
but
maybe.
B
B
It
feels
like
just
straight
marketing
material
where
it
is,
and
it
might
just
be
it's
in
the
wrong
home
and
like
we
do
something
you
know
different
to
highlight
those
capabilities
if
it's
a
blog
post,
but
if
you
you
just
want
to
like
expand
on
the
functionality
or
something
like
it,
it
could
be
like,
as
you
say,
in
the
learn
environment
or
on
the
you
know
the
product
or
feature
page.
That's
that's
relevant
to
that,
and
this
is
like
ongoing
work.
B
B
I
know
that
we
have
the
web
article
format
coming
soon,
so
it's
possible
that
some
of
these
might
have
been
better
suited
to
that
format,
because
it's
sort
of
like
foundational
knowledge-
or
you
know
just
basics,
and
it's
there's
not
necessarily
anything
timely
or
opinionated
about
it
and
then
yeah.
I
just
compared
it
to.
We
had
the
guide
to
ci
cd
for
beginners
that
did
really
take
off
for
us,
but
that
is
on
ci
cd,
which
is
a
known
popular
topic.
B
A
I
was
gonna
say
I
would
be
it.
The
devsecops
series
is
one
that
I
think
we
should
test
with
some
paid
social
behind,
because
I
have
a
untested
theory
that
maybe
we
just
haven't
attracted
an
audience
that
is
interested
in
this
topic
and
to
see
what
happens
to
those
sessions.
If
we
do
some
paid
social
and
targeting,
if
that
makes
a
difference,
if
maybe
tell
us
a
little
bit
about
this
of
the
content
or
the
audience,
because
we
do
want
this
audience.
B
B
B
I
think
possibly
something
that
could
have
affected
traffic
to
posts
that
we
would
expect
to
do
well.
Is
we
obviously
paused
for
pause
publishing
for
three
weeks
in
june,
which
created
a
bit
of
a
backlog
which
we
then
cleared
in
july,
but
then
created
kind
of
a
bottleneck
on
the
social
distribution
side,
and
that
is
where
most
of
our
initial
traffic
comes
from,
so
it's
possible
that
there
was
just
a
bit
too
much
crowding
around
some
of
these
posts
and
they
didn't
get
the
attention
that
they
would
normally
get.
B
B
It
was
obviously
important
to
publish
this
first,
one
which
did
a
little
bit
better,
but
I,
my
sort
of
challenge
to
our
team
going
forward
is
sort
of
what
what
is
git
lab,
bringing
that's
new
to
this
conversation
or
that
we
are
uniquely
positioned
to
talk
about,
and
my
suggestion
here
is
like
with
the
remote
work
stories.
There
might
be
kind
of
a
sort
of
engineering
angle
or
just
like
a
kind
of
data
analysis
angle.
B
C
I
do
have
one
question
and
it's
just
a
question
of
whether
or
not
we
might
be
doing
ourselves
a
disservice
by
looking
so
closely
at
like
why
not
review,
say
q4s
traffic
now,
because
then
you've
given
like
six
months
or
more
to
the
existing
traffic
like
you've,
said
that
we've
started
to
implement
more
seo
stuff.
So
I'm
curious
about,
if
you've
thought
of
looking
at
older
content,
to
see
how
well
it's
performed
with
a
six-month
timeline.
C
B
We
need
to
make
sure,
day
by
day
that
we're
spending
time
on
on
what
matters
and
so
to
look
at
the
most
recent
stuff.
Just
means
like
you
know
we
can.
We
can
pivot
quickly
and
if
we're
only
kind
of
getting
data
sort
of
six
months.
After
the
fact.
That's
like
sorry,
I'm
not
sure
if
I'm
explaining
this
this
very
well,
but
just
like
this
is,
are
we
learning
from
what
we've
been
doing
most
recently
versus
what
we
were
doing
six
months
ago?
B
A
And
we
do
a
12-month
review
at
the
end
of
the
year,
so
there's
a
quarter
reviews
and
then
12-month
review.
I
think
it'd
be
great
to
get
to
a
point
where
we're
doing
it
every
six
months.
I
think,
like
rebecca
just
said,
the
process
is
so
manual
right
now
that
doing
it
quarterly,
which
I
do
think
we
should
do
for
all
the
reasons
rebecca
just
described
plus
a
twice
a
year
six
month
review
is
just
a
lot
to
do
without
tools
and
automation.