almanac.httparchive.org
almanac.httparchive.org copied to clipboard
HTTPArchive
SEO 2022
SEO 2022
If you're interested in contributing to the SEO chapter of the 2022 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 |
|---|---|---|---|---|---|
| @SophieBrannon | @SophieBrannon @itamarblauer | @mobeenali97 @dwsmart @patrickstox @johnmurch @TusharPol | @derekperkins @csliva @jroakes | @MichaelLewittes | @foxdavidj |
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
- [x] May 1: The content team has at least one author, reviewer, and analyst
1. Plan content
- [x] May 15 The content team has completed the chapter outline in the draft doc
2. Gather data
- [x] June 1: Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress
- June 1 - 15: HTTP Archive runs the June crawl
3. Validate results
- [ ] August 1: Analysts have queried all metrics and saved the output to the results sheet
4. Draft content
- [ ] September 1: The content team has written, reviewed, and edited the chapter in the doc
5. Publication
- [ ] September 15: The completed chapter and all required metadata and figures are converted to markdown and submitted to GitHub
- September 26: Target launch date 🚀
Chapter resources
Refer to these 2022 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 💬 #web-almanac-seo on Slack for team coordination
I would like to be part of "Publication" and edit the SEO chapter. I am a long-time editor and journalist, with 10 years of experience in SEO as well.
I'm happy to come back as a reviewer this year and also provide any guidance I can based on my experience last year.
Comment from @Tiggerito in #2911:
The SEO chapter could check the use of the new indexifembedded meta tag option if possible. The custom metrics code would have to look into iframe content.
The article also uses 'value' in place of 'content' for the meta tag. I wonder how many people make this mistake on their meta tags? Googlebot supports 'value', but the custom metrics code does not.
Great topic @Tiggerito. Read the documentation in January and all the subsequent takes on it from various industry trades (Search Engine Land, Search Engine Roundtable et al).
I will throw my hat in for Analyst again this year. Have a lot of clean up I want to do to make the queries more concise and readable.
Not sure how much we're wanting to rock the boat, but at a quick glance, a lot of queries are doing custom javascript functions that could be better represented with some newer BigQuery JSON functions. https://cloud.google.com/bigquery/docs/reference/standard-sql/json_functions
@derekperkins yeah that sounds great! That seems like it would make the queries much more readable and may even be a bit faster to run.
If you're up for it as a proof of concept, could you take a couple of last year's queries, copy them over to this year's SQL dir, and open a PR using the newer functions?
DM me on Slack if you need to get set up to use our BigQuery account.
Hey @SophieBrannon, would you be interested in taking the Chapter Lead role for the SEO chapter?
As the Chapter lead you'd be the primary author and the key person responsible for pulling the entire chapter together. Details on the role and commitment here
We'd love to have you 🎉 🎉
Hey @SophieBrannon, friendly ping. Would you be interested in being the Chapter Lead for SEO this year?
See my above comment for more info
Hey! So sorry for the delay, I’ve been here there and everywhere. I would love to be content lead and also have Itamar Blauer as a co-author on the chapter 🙌
Get Outlook for iOShttps://aka.ms/o0ukef
From: foxdavidj @.> Sent: Friday, April 29, 2022 6:26:09 PM To: HTTPArchive/almanac.httparchive.org @.> Cc: Sophie Brannon @.>; Mention @.> Subject: Re: [HTTPArchive/almanac.httparchive.org] SEO 2022 (Issue #2888)
Hey @SophieBrannonhttps://github.com/SophieBrannon, friendly ping. Would you be interested in being the Chapter Lead for SEO this year?
See my above comment for more info
— Reply to this email directly, view it on GitHubhttps://github.com/HTTPArchive/almanac.httparchive.org/issues/2888#issuecomment-1113551765, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYWJ77WQAWQRF3BH3KO54HLVHQLTDANCNFSM5TH7ZBAA. You are receiving this because you were mentioned.Message ID: @.***>
@SophieBrannon @itamarblauer @mobeenali97 @dwsmart @patrickstox @johnmurch @derekperkins @csliva @jroakes @MichaelLewittes @TusharPol please make sure you all have edit access to the SEO chapter planning doc and are members of the #web-almanac-seo channel on Slack. The next milestone is to complete the outline of the chapter by May 15.
Thank you all for contributing this year and I'm really excited to see a great team coming together!
@SophieBrannon @itamarblauer @mobeenali97 @dwsmart @patrickstox @johnmurch @TusharPol @derekperkins @csliva @jroakes @MichaelLewittes
Hey everyone, excited to see we've got a full team for the chapter!
To kick things off, I'd love to set up a 30 minute call within the next two weeks to put any new faces to names, and start the planning and brainstorming process.
@SophieBrannon as the Chapter Lead can you assist in finding a time that works for everyone? You can see my availability via my calendly here: https://calendly.com/foxdavid/30min
Also, here is an agenda for what we might want to discuss on the kickoff call: https://docs.google.com/document/d/17L74ytEJWnmq4aQkZOMMonh9wFOAqu3rWAcCtyUoQ44/edit
Hi all! @itamarblauer @mobeenali97 @dwsmart @patrickstox @johnmurch @TusharPol @derekperkins @csliva @jroakes @MichaelLewittes
Looking at @foxdavidj's availability, can everyone confirm if either of the following dates/times works for them and I will send through a calendar invite.
Friday 6th - 6.30pm UK time Wednesday 11th - 3.30pm - 5pm UK time.
We should only need 30 mins or so!
Wednesday is preferable, but can do whatever’s best for the group.
On Tue, May 3, 2022 at 8:28 AM Colt Sliva @.***> wrote:
I can swing either of those times.
— Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2888#issuecomment-1116042955, or unsubscribe https://github.com/notifications/unsubscribe-auth/AW6KSXPXJD4C35TKZOBNKPTVIELXDANCNFSM5TH7ZBAA . You are receiving this because you were mentioned.Message ID: @.***>
Either time works for me.
On Tue, May 3, 2022, 8:31 AM MichaelLewittes @.***> wrote:
Wednesday is preferable, but can do whatever’s best for the group.
On Tue, May 3, 2022 at 8:28 AM Colt Sliva @.***> wrote:
I can swing either of those times.
— Reply to this email directly, view it on GitHub < https://github.com/HTTPArchive/almanac.httparchive.org/issues/2888#issuecomment-1116042955 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AW6KSXPXJD4C35TKZOBNKPTVIELXDANCNFSM5TH7ZBAA
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2888#issuecomment-1116045516, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHYRLYUL6JHEHOZMZNXQ7RDVIEMCDANCNFSM5TH7ZBAA . You are receiving this because you were mentioned.Message ID: @.***>
@SophieBrannon i noticed you cancelled the meeting for this Friday. Are we rescheduling to a different time?
@foxdavidj hey! yes it looks like Wednesday next week is better for the majority, I'm just waiting on a few more responses then will book in your diary.
@foxdavidj hey! yes it looks like Wednesday next week is better for the majority, I'm just waiting on a few more responses then will book in your diary.
Sounds good. No need to book via my Calendly btw, just posted it as a quick view into my calendar.