SEO 2024

[nrllh]

SEO 2024

If you're interested in contributing to the SEO chapter of the 2024 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. You might be interested in exploring the changes to this year's version here.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@AVGP	@patrickstox, @AVGP, @dwsmart, @fellowhuman1101	@amandeepsinghvirdi, @en3r0	@henryp25, @guaca, @cnichols013	@MichaelLewittes	@tomvangoethem

Expand for more information about each role 👀

• The content team lead is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress.
• Authors 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 are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases.
• Analysts 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 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 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 doc.

Milestone checklist

0. Form the content team

• 📆 April 15 Complete program and content committee - 🔑 Organizing committee
  • The content team has at least one author, reviewer, and analyst.

1. Plan content

• 📆 May 1 First meeting to outline the chapter contents - 🔑 Content team
  • The content team has completed the chapter outline.

2. Gather data

• 📆 June 1 Custom metrics completed - 🔑 Analysts
  • Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
• 📆 June 1 HTTP Archive Crawl - 🔑 HA Team
  • HTTP Archive runs the June crawl.

3. Validate results

• 📆 August 15 Query Metrics & Save Results - 🔑 Analysts
  • Analysts have queried all metrics and saved the output.

4. Draft content

• 📆 September 15 First Draft of Chapter - 🔑 Authors
  • Authors has written the chapter.
• 📆 October 10 Review & Edit Chapter - 🔑 Reviewers & Editors
  • Reviewers and Editors has processed the the chapter.

5. Publication

• 📆 October 15 Chapter Publication (Markdown & PR) - 🔑 Authors
  • Authors has converted the chapter to markdown and drafted a PR.
• 📆 November 1 Launch of 2024 Web Almanac 🚀 - 🔑 Organizing committee

6. Virtual conference

• 📆 November 20 Virtual Conference - 🔑 Content Team

Chapter resources

Refer to these 2024 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
💻 Collab notebook for collaborative coding in Python - if needed
💬 #web-almanac-seo on Slack for team coordination

[patrickstox]

I'd be happy to be an author or reviewer again for the SEO chapter.

[MichaelLewittes]

And I'd be happy to be the editor of the SEO section again. Know the drill -- and ready to do it once more.

[amandeepsinghvirdi]

Happy to contribute as Reviewer.

[AVGP]

Happy to join as content lead.

[henryp25]

I would love to put myself forward as an analyst or author.

[en3r0]

Happy to contribute as a reviewer again!

[dwsmart]

Be honoured to be either a author or reviewer

[fellowhuman1101]

I'd be delighted to return to this chapter as an author or reviewer. Bonus points for a 3rd go coauthoring with @dwsmart

[guaca]

Happy to contribute as analyst!

[nrllh]

We have another great team here! Thank you all!

[cnichols013]

Happy to help as an analyst.

[nrllh]

Happy to help as an analyst.

Thanks!

[MichaelLewittes]

I'm traveling internationally on May 1 -- the Plan Content meeting -- but happy to discuss/meet beforehand (or right afterwards).

…

On Tue, Apr 9, 2024 at 6:07 PM Nurullah Demir ***@***.***> wrote: Happy to help as an analyst. Thanks! — Reply to this email directly, view it on GitHub <#3600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW6KSXMKPBSD6OPUEDTAHXDY4RRDVAVCNFSM6AAAAABEDJDPACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGEZDGNBWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tomvangoethem]

It looks like we don't have a lead for this chapter yet. Are any of the authors interested in taking up that role? @patrickstox, @AVGP, @dwsmart, @fellowhuman1101? A first step would be to set up a quick call with the different contributors of this chapters (preferably early this upcoming week) to align with everyone on the outline of the chapter. Thanks!

[dwsmart]

@AVGP indicated he wanted to take the lead role above, and I happen to think that is a winning idea.

[MichaelLewittes]

Winning idea, indeed!

…

On Sun, Apr 28, 2024 at 10:52 AM Dave Smart ***@***.***> wrote: @AVGP <https://github.com/AVGP> indicated he wanted to take the lead role above, and I happen to think that is a winning idea. — Reply to this email directly, view it on GitHub <#3600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW6KSXOVFQNXIJCY5Q3VDDDY7UELZAVCNFSM6AAAAABEDJDPACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGUYTCMJXGE> . You are receiving this because you were assigned.Message ID: ***@***.***>

[AVGP]

Yep, still up for it, though I won't be available for the call tomorrow, if that's a problem?

[dwsmart]

Perhaps we can do a call on the following Mon, Tue or Wed? Although a few days late, I think that having the content lead there outweighs that. I..m.h.o.

[MichaelLewittes]

Agree. What works next week for you Martin?

…

On Tue, Apr 30, 2024 at 3:03 PM Dave Smart ***@***.***> wrote: Perhaps we can do a call on the following Mon, Tue or Wed? Although a few days late, I think that having the content lead there outweighs that. I..m.h.o. — Reply to this email directly, view it on GitHub <#3600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW6KSXPE3TIXJQBUDCFS4CLY76CCLAVCNFSM6AAAAABEDJDPACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBVGE2DSOBVGA> . You are receiving this because you were assigned.Message ID: ***@***.***>

[patrickstox]

I have some travel coming up but will do my best to make it whenever y'all want. Also endorsing @AVGP for lead.

[AVGP]

I could set something up for May 15th?

[dwsmart]

That's good for me

[MichaelLewittes]

Will be at Google I/O but can work around it, if I’m needed this early.

…

On Fri, May 10, 2024 at 5:37 AM Dave Smart ***@***.***> wrote: That's good for me — Reply to this email directly, view it on GitHub <#3600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW6KSXIT7JNAYA2G66DUMX3ZBSIN7AVCNFSM6AAAAABEDJDPACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUGI4DMNRUG4> . You are receiving this because you were assigned.Message ID: ***@***.***>