rviscomi commented 3 years ago

Part II Chapter 8: SEO

SEO illustration

If you're interested in contributing to the SEO chapter of the 2021 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@patrickstox	@patrickstox @Tomek3c @ashleyish @wrttnwrd	@bh-siteobjective @nicoseosem @jdevalk @ipullrank @fili @excellenseo @jfontanez @SeoRobt @en3r0 @fellowhuman1101 @dwsmart @ibnesayeed @bergtaylora @schachin	@rvth @jessthebp @jroakes	@maria-amelie	@obto

Expand for more information about each role

- The **[content team lead](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report. - **[Reviewers](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly. - **[Editors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit. - The **[section coordinator](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule. _Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors._ For an overview of how the roles work together at each phase of the project, see the [Chapter Lifecycle](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

[x] May 31: The content team has at least one author, reviewer, and analyst

1. Plan content

[x] June 15 The content team has completed the chapter outline in the draft doc

2. Gather data

[x] June 30: Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress
July 1 - 31: HTTP Archive runs the July crawl

3. Validate results

[x] September 30: Analysts have queried all metrics and saved the output to the results sheet

4. Draft content

[x] October 31: The content team has written, reviewed, and edited the chapter in the doc

5. Publication

[x] November 15: The completed chapter and all required metadata and figures are converted to markdown and submitted to GitHub
December 1: Target launch date 🚀

Chapter resources

Refer to these 2021 SEO resources throughout the content creation process:

📄 Google Docs for outlining and drafting content 🔍 SQL files for committing the queries used during analysis 📊 Google Sheets for saving the results of queries 📝 Markdown file for publishing content and managing public metadata

gregorywolf commented 3 years ago

Hi. If possible I would like to sign up for the Analyst role

rviscomi commented 3 years ago

Thanks @gregorywolf! I've added you to the team. Great to have you back!

Tomek3c commented 3 years ago

I would love to join the #SEO team!

maria-amelie commented 3 years ago

Hi, I am new and I would like to sign up for the editor role. Thank you.

bh-siteobjective commented 3 years ago

Hi. I would love to sign up for a reviewer and/or author role in the #SEO chapter. :)

rviscomi commented 3 years ago

Thanks for your interest everyone! Updated the team assignments.

@Tomek3c what role interests you? (author, reviewer, analyst, editor)

Tomek3c commented 3 years ago

@rviscomi author.

nicoseosem commented 3 years ago

I am not a native English speaker, in this case, but have a strong background in SEO. Can I be an author or co-author?

rviscomi commented 3 years ago

@Tomek3c thanks! We'll leave the author spot open for a short while to allow others to sign up before selecting the lead (more info about that in #2165).

@nicoseosem being a native English speaker is not a requirement, so no worries. We can help with any English in the editing stage.

I'll tentatively put you both down as peer reviewers until we select the author.

jdevalk commented 3 years ago

I’d be happy to be an author of (a part of) this chapter!

ipullrank commented 3 years ago

Oooh! It's a party in here. I just wanted to endorse both @Tomek3c and @jdevalk as amazing choices for authors.

rviscomi commented 3 years ago

Thank you @ipullrank! It's super helpful to have your endorsement. Do you have any interest/availability to contribute again this year, maybe as a peer reviewer?

ipullrank commented 3 years ago

@rviscomi Yep peer review is probably the best that I could manage this year. I'm pretty tied up writing my SEO book

rviscomi commented 3 years ago

Sounds great, thanks -- and excited to see the book! Maybe it'll cite some stats from the Almanac? 😄

@Tomek3c @bh-siteobjective @nicoseosem @jdevalk @ipullrank @gregorywolf @maria-amelie even though we're still waiting on author assignments, I think we have critical mass to start collaborating on a chapter outline in the Doc. Could you all request edit access to the doc and work together to brainstorm some topics? You can refer back to the 2020 SEO doc for inspiration as needed.

bh-siteobjective commented 3 years ago

Yay! Excited to contribute as a reviewer (maybe author too?) this year. Looking forward to it. :D

fili commented 3 years ago

Happy to be a peer reviewer for this chapter

excellenseo commented 3 years ago

Hi! I would love to be a reviewer. Do you need translators too?

rviscomi commented 3 years ago

Great thanks @excellenseo! Yes, we have an ongoing need for more translators! See #923 to join the team and get started on previous years' content.

jfontanez commented 3 years ago

I would love to be part of the SEO Team as technical reviewer. I'm a Sr. Technical SEO, I can help in any topic below this too.

Thank you for the opportunity.

rvth commented 3 years ago

Hello! I'd love to sign up for an analyst and/or editor role if you're still looking for contributors :)

SeoRobt commented 3 years ago

Hey! Would be thrilled to participate as an editor or reviewer and get involved.

wrttnwrd commented 3 years ago

I'd love to be an author. Technical SEO, architecture and SEO, are both great but happy to contribute wherever is most helpful.

en3r0 commented 3 years ago

Would love to be a reviewer again this year!

rviscomi commented 3 years ago

Thank you for your interest everyone! Please head over to the collaborative doc and request edit access to begin brainstorming the contents for this year's chapter. We'll start selecting authors next week!

fellowhuman1101 commented 3 years ago

Delighted to assist this year in whatever capacity is most beneficial! @rvth would be an excellent author.

patrickstox commented 3 years ago

I'd love to be an author or reviewer.

rviscomi commented 3 years ago

This chapter by far has the most people interested in authoring; picking just one to be the lead is not an easy decision! Based on a recommendation from last year's content team lead @aleyda, we'd like to offer the 2021 lead role to @patrickstox. If previous year's chapters are any indication, there will be a lot of content to cover, so I definitely anticipate the need for multiple coauthors.

@patrickstox as the content team lead, you'll be responsible for the scope and direction of the chapter, assigning new coauthors as needed, and keeping it on schedule. We automatically monitor the staffing and progress of each chapter based on the state of the initial comment so please keep that updated as you add new contributors and meet each milestone.

We've created a Google Doc for this chapter, which you're encouraged to use to collaborate with the content team on the initial outline, metrics, and ultimately the final draft.

Next steps for this chapter are:

Due May 31: Complete Milestone 0: Form the content team—you can check this off now since you've already got at least one author, reviewer, and analyst ✨
Due June 15: Get started on Milestone 1: Plan content by brainstorming some content ideas in the doc (all contributors should be able to request edit access now)

@obto will be the section coordinator for this chapter, so they'll be periodically checking in with you directly to make sure the chapter is staying on schedule. Reach out to them here in this issue if you have any questions about the process.

More information about the content team lead and author roles and responsibilities are available for reference in the wiki if needed.

To anyone else still interested in contributing to this chapter, please comment below to join the team!

And a special note for the 2019/2020 SEO contributors that haven't already reached out: Let us know if any of you would be interested to join as a reviewer/analyst this year! It's great to have input from past years' contributors. cc @rachellcostello @ymschaap @AVGP @clarkeclark @andylimn @voltek62 @AymenLoukil @catalinred @natedame @aysunakarsu @ashleyish @dsottimano @dwsmart @Gathea @ibnesayeed @max-ostapenko @Tiggerito @antoineeripret

jessthebp commented 3 years ago

Hi! I'd love to join this chapter as an analyst.

dwsmart commented 3 years ago

I'd be very happy to act as a reviewer again.

ibnesayeed commented 3 years ago

@rviscomi, I can review this chapter!

ashleyish commented 3 years ago

I'm happy to review!

On Wed, May 5, 2021 at 2:59 PM Sawood Alam @.***> wrote:

@rviscomi https://github.com/rviscomi, I can review this chapter!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-833002952, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIL6BAYO32MUULIP7ICEDZTTMGWRJANCNFSM43UFMT6A .

bergtaylora commented 3 years ago

Hi! I'm happy to be a peer reviewer :)

rviscomi commented 3 years ago

I'll defer to @patrickstox to onboard all of the new contributors. As a reminder, everyone please start adding your ideas to the chapter doc.

patrickstox commented 3 years ago

The more help the better but I think this is a good time to cut off any additional help offers as it looks like we have quite a few people who want to contribute.

As for authors, these are the ones I see who were interested in being authors. Anyone else? @bh-siteobjective @Tomek3c @nicoseosem @jdevalk @wrttnwrd

wrttnwrd commented 3 years ago

Hi Patrick,

Also happy to be an editor if that's preferable.

Thanks!

Ian

bh-siteobjective commented 3 years ago

Hi Patrick,

I'm also happy to help out in other roles concurrently as well where it is needed.

Thank you!

All the best,

Brian Harnish

On Mon, May 10, 2021 at 7:24 AM Ian Lurie @.***> wrote:

Hi Patrick,

Also happy to be an editor if that's preferable.

Thanks!

Ian

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-836763851, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIWJGM2JPGPGRMRHTHF436DTM7UAPANCNFSM43UFMT6A .

fellowhuman1101 commented 3 years ago

@patrickstox I'd be delighted to join as a returning author

ashleyish commented 3 years ago

Peer-pressured (happily) by Jamie to move from reviewer to author if there's still a need.

On Mon, May 10, 2021 at 8:42 AM Jammer @.***> wrote:

@patrickstox https://github.com/patrickstox I'd be delighted to join as a returning author

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-836784294, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIL6BAZMPYUUK2FTVB6F6K3TM7WDTANCNFSM43UFMT6A .

SeoRobt commented 3 years ago

Happy to help wherever needed!

From: patrickstox @.> Reply-To: "HTTPArchive/almanac.httparchive.org" @.> Date: Monday, May 10, 2021 at 9:23 AM To: "HTTPArchive/almanac.httparchive.org" @.> Cc: Rob Teitelman @.>, Mention @.***> Subject: Re: [HTTPArchive/almanac.httparchive.org] SEO 2021 (#2146)

The more help the better but I think this is a good time to cut off any additional help offers as it looks like we have quite a few people who want to contribute.

As for authors, these are the ones I see who were interested in being authors. Anyone else? @bh-siteobjectivehttps://github.com/bh-siteobjective @Tomek3chttps://github.com/Tomek3c @nicoseosemhttps://github.com/nicoseosem @jdevalkhttps://github.com/jdevalk @wrttnwrdhttps://github.com/wrttnwrd

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-836694010, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AT4JQSNLNKPG6M3HWPKBRR3TM7M5NANCNFSM43UFMT6A.

dsottimano commented 3 years ago

Hey @patrickstox , glad to see you as the lead this year. I'd like to see some new contributors so I'm going to bow out. Appreciate the offer to contribute again @rviscomi , thank you.

Looking forward to the next edition, rock on folks.

rviscomi commented 3 years ago

@patrickstox are you able to edit the top comment to reflect the latest list of coauthors/reviewers and check off the 0th milestone? (it's helpful for us to see how all of the chapters are doing at a glance in https://github.com/HTTPArchive/almanac.httparchive.org/issues/2179)

patrickstox commented 3 years ago

@rviscomi I've updated the list and checked the milestone. I've wracked my brain thinking about author selection with so many amazing volunteers. After much deliberation and alcohol I've selected @Tomek3c @ashleyish & @wrttnwrd. Congrats to y'all and thanks to everyone for being a part of this project! I look forward to working with you all and I'm excited to see all the ideas we come up with!

foxdavidj commented 3 years ago

Hey @patrickstox excited to work with you and the rest of the group this year on the Almanac. I'm your go to guy if you've got any questions or need help so don't hesitate to reach out to me on github, the Slack (@obto) or email (david@davidjfox.com).

Few first steps:

All authors, reviewers and analysts should add themselves to the Google Doc in the format: Name (email@example.com). I've also added links within the doc to the previous years Google doc in case you'd like to mine it for ideas.
Would love to set up a 30 minute Zoom call in the next couple weeks to kick-start the chapter planning and brainstorming process, and put some faces to the names of the people we'll all be working with this year. I'll reach out again later this week to find a time that works.

Excited to work with you all this year.

gregorywolf commented 3 years ago

@obto - I think scheduling a 30 minute Zoom is a great idea!

foxdavidj commented 3 years ago

How does this Friday at 4p ET / 1p PT / 9p BST work for the 30m zoom/google meet chat? Timezones here

Or Monday (May 24) at 11a ET / 8a PT / 4p BST? Timezones here

ping @patrickstox @Tomek3c @ashleyish @wrttnwrd @bh-siteobjective @nicoseosem @jdevalk @ipullrank @fili @excellenseo @jfontanez @SeoRobt @en3r0 @fellowhuman1101 @dwsmart @ibnesayeed @bergtaylora @gregorywolf @rvth @jessthebp @maria-amelie

patrickstox commented 3 years ago

I've got a recording for a virtual conference on Friday at that time but Monday works for me.

fili commented 3 years ago

Neither days work for me.

On Wed, May 19, 2021 at 3:37 PM patrickstox @.***> wrote:

I've got a recording for a virtual conference on Friday at that time but Monday works for me.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-844113871, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA4EP76VLFQ5HUGDGO5QBDTOO5IFANCNFSM43UFMT6A .

--

Fili Wiese

@.***

Websites

● fili.com

● seo.consulting

● online.marketing

Registered Office: Friedrichstr. 123, 10117 Berlin, Germany

VAT: DE290388554

This email may be confidential or privileged. If you have received this communication in error, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks.

Non-binding language if applicable: The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.

bh-siteobjective commented 3 years ago

Friday is best for me.

All the best,

Brian Harnish

On Wed, May 19, 2021 at 6:21 AM David Fox @.***> wrote:

How does this Friday at 4p ET / 1p PT / 9p BST work for the 30m zoom/google meet chat? Timezones here https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=5&day=21&hour=20&min=0&sec=0&p1=64&p2=179&p3=224&p4=136

Or Monday (May 24) at 11a ET / 8a PT / 4p BST? Timezones here https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=5&day=24&hour=15&min=0&sec=0&p1=64&p2=179&p3=224&p4=136

ping @patrickstox https://github.com/patrickstox @Tomek3c https://github.com/Tomek3c @ashleyish https://github.com/ashleyish @wrttnwrd https://github.com/wrttnwrd @bh-siteobjective https://github.com/bh-siteobjective @nicoseosem https://github.com/nicoseosem @jdevalk https://github.com/jdevalk @ipullrank https://github.com/ipullrank @fili https://github.com/fili @excellenseo https://github.com/excellenseo @jfontanez https://github.com/jfontanez @SeoRobt https://github.com/SeoRobt @en3r0 https://github.com/en3r0 @fellowhuman1101 https://github.com/fellowhuman1101 @dwsmart https://github.com/dwsmart @ibnesayeed https://github.com/ibnesayeed @bergtaylora https://github.com/bergtaylora @gregorywolf https://github.com/gregorywolf @rvth https://github.com/rvth @jessthebp https://github.com/jessthebp @maria-amelie https://github.com/maria-amelie

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-844100760, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIWJGM6T5FKFGV66EVW6YV3TOO3OJANCNFSM43UFMT6A .

wrttnwrd commented 3 years ago

I can do Monday (sorry Brian)...

Ian Lurie Digital Marketing Consultant Nerd

Tw: @ianlurie Li: https://www.linkedin.com/in/ianlurie/ W: https://www.ianlurie.com

On May 19, 2021, 10:52 AM -0700, Brian Harnish @.***>, wrote:

Friday is best for me.

All the best,

Brian Harnish

On Wed, May 19, 2021 at 6:21 AM David Fox @.***> wrote:

How does this Friday at 4p ET / 1p PT / 9p BST work for the 30m zoom/google meet chat? Timezones here https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=5&day=21&hour=20&min=0&sec=0&p1=64&p2=179&p3=224&p4=136

Or Monday (May 24) at 11a ET / 8a PT / 4p BST? Timezones here https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=5&day=24&hour=15&min=0&sec=0&p1=64&p2=179&p3=224&p4=136

ping @patrickstox https://github.com/patrickstox @Tomek3c https://github.com/Tomek3c @ashleyish https://github.com/ashleyish @wrttnwrd https://github.com/wrttnwrd @bh-siteobjective https://github.com/bh-siteobjective @nicoseosem https://github.com/nicoseosem @jdevalk https://github.com/jdevalk @ipullrank https://github.com/ipullrank @fili https://github.com/fili @excellenseo https://github.com/excellenseo @jfontanez https://github.com/jfontanez @SeoRobt https://github.com/SeoRobt @en3r0 https://github.com/en3r0 @fellowhuman1101 https://github.com/fellowhuman1101 @dwsmart https://github.com/dwsmart @ibnesayeed https://github.com/ibnesayeed @bergtaylora https://github.com/bergtaylora @gregorywolf https://github.com/gregorywolf @rvth https://github.com/rvth @jessthebp https://github.com/jessthebp @maria-amelie https://github.com/maria-amelie

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2146#issuecomment-844100760, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIWJGM6T5FKFGV66EVW6YV3TOO3OJANCNFSM43UFMT6A .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Tomek3c commented 3 years ago

I'm excited to work with such an awesome team! Both days, Friday and Monday are fine with me.

HTTPArchive / almanac.httparchive.org

SEO 2021 #2146

Part II Chapter 8: SEO

Content team

Milestone checklist

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

Chapter resources