2020 SEO chapter #1589
2020 SEO chapter #1589
Conversation
Add 25 out of 25 images for the SEO (2020) chapter.
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 42.2%, saving 343.59 KB.
405 images did not require optimisation. |
|
@antoineeripret @bazzadp is this PR meant to contain all of the chapter markdown or is this just a head start to get the figure images checked in? |
|
@rviscomi I thin we should do both in the same PR as they are linked. That way any image changes needed as we work on Chapter can be captured in this PR - for example I'd like to remove the figX from the beginning of the numbers. Will add an initial version of the markdown to this branch, check it's all working, and then let the authors finish it off. |
|
I've converted the chapter to Markdown. This is quite a manual process so please double check I didn't miss anything. I had to make some changes (for example we don't use nested lists like was in the Performance section and in the Conclusion) so converted those as best as I saw fit. I pushed a test version of the chapter here: https://20201129t114634-dot-webalmanac.uk.r.appspot.com/en/2020/seo aleyda @ipullrank @fellowhuman1101 @clarkeclark @natedame @catalinred @aysunakarsu @ashleyish @dsottimano @dwsmart @en3r0 @Gathea @rachellcostello and @ibnesayeed Can you all review please? As a reminder there will be an Editing stage after this so concentrate on the actual content rather than phrasing for now. For those not familiar with GitHub, the content is in the File tab at the top, and you are looking for the
GitHub will probably not show it by default as it's quite big but click 'Load Diff' to see it:
You will see changes from the original template on the left, and new version on the right with removals in red, and additions in green. You can edit the Markdown using the drop down in the top right:
Probably better that @aleyda is the only one who edits it now, and the rest of you suggest changes instead. To suggest changes click on a line, where you'll be able to add a comment:
You can then add that single comment, or Start a Review, which batches up all your comments and then releases them in one go (better to do this when you want to have a few comments to save spamming everyone). You can use the suggest feature by using the button in the toolbar, and it will insert the current text which you can edit:
And then click on the Preview tab and you'll see what it looks like:
Once you submit a single comment, or a review it will be put in this main conversation tab and everyone will be alerted to it. It's actually quite a nice way of working once you are used to it. Any questions give me a shout! |
src/content/en/2020/seo.md
Outdated
| #aleyda_bio: TODO | ||
| #ipullrank_bio: TODO |
There was a problem hiding this comment.
@aleyda , @ipullrank , @fellowhuman1101 can you add your Bios here which will appear at the bottom of the chapter? They should use HTML and not Markdown.
See last year's chapter as examples.
There was a problem hiding this comment.
Thanks @bazzadp ! I just added mine ... and now I'm seeing that they should use HTML and not markdown (I had used markdown). I will change that now :D
There was a problem hiding this comment.
Can you also remove the initial # as that is currently commenting out your bio since it wasn't there previously.
This is what it looks like when you do that:
I think it should be Twitter rather than twitter btw.
There was a problem hiding this comment.
@bazzadp thanks Barry! Just to confirm that I did this :)
There was a problem hiding this comment.
That's better. Did you see my comment about uppercasing the T in Twitter?
There was a problem hiding this comment.
@bazzadp I hadn't! Thanks for the heads up :D Just fixed it.
| @@ -23,3 +23,835 @@ queries: 07_SEO | |||
| #featured_stat_label_3: TODO | |||
There was a problem hiding this comment.
@aleyda can you think of a nice quote and three featured stats to entice people into the chapter. These will appear randomly on the home page.
There was a problem hiding this comment.
Hi @bazzadp, thanks for asking :)
@ipullrank @fellowhuman1101 - what do you think to include for:
-
The main quote: "The link discoverability for major JS frameworks used for SPAs increased dramatically compared to 2019. By testing mobile navigation links for hashed URLs, we saw -53% instances of uncrawlable links from sites using React, -58% fewer from Vue.js powered sites, and a -91% reduction from Angular SPAs."
-
The 3 featured stats:
-
10.84% of mobile home pages and 16.18% of desktop ones are not including the viewport tag at all, suggesting that they are not yet mobile friendly.
-
33.13% of websites scored 'Good' Core Web Vitals for desktop while only 19.96% of their mobile counterparts passed the Core Web Vitals assessment.
-
The median mobile site displays 11.5% more words when rendered than its raw HTML, showing a reliance on client side JavaScript to show web pages content.
Let me know what you think of these or if you would prefer to highlight other stats/findings! Thanks :)
There was a problem hiding this comment.
@aleyda I think the main quote talks about what's gotten better, but we should consider using our main quote as the opportunity to alert people to the big problem of their being a disparity between mobile and desktop.
There was a problem hiding this comment.
@ipullrank I see what you mean... especially due to the Mobile First Index. What about:
"Despite the growing use of mobile devices and Google’s move to a Mobile first index, non-trivial disparities were found across mobile vs. desktop pages, like the one between mobile and desktop links, illustrated in the 62 links on mobile versus the 68 links on desktop for the median web page."?
There was a problem hiding this comment.
@ipullrank gracias Mike!
@fellowhuman1101 Is it good for you too Jamie? :)
There was a problem hiding this comment.
@aleyda Looks good!
There was a problem hiding this comment.
Thanks for the confirmation @fellowhuman1101 :)
@bazzadp @rviscomi I just added the quote and stats and submitted them here. I noticed there were "labels" for them but didn't know what should I add there. Could you please let me know to include them too if necessary? :) Thanks again
There was a problem hiding this comment.
Thanks everyone! I've followed up in the linked PR about the next steps to get this included. To summarize, let's apply any further changes directly to the open PR to keep everything in one place.
BTW @fellowhuman1101 there's a TODO in the PR for you to add your bio, and I've also sent you an invite to join the Authors Team on GitHub, so we can assign issues/PRs to you.
Edit: Nevermind on the TODO! That's what I get for reading notification in sequential order 😁 but you've still got that pending invite.
|
Thanks SO much for generating the Markdown and all the explanations @bazzadp - this is amazing! Will start reviewing, adding my bio, and checking to make sure that the reviewers who have participated are listed too :) I'll let you know if I have any questions... thanks again for all your help! cc @ipullrank @fellowhuman1101 |
|
No problem. Keen to get the chapter into editing as it’s a big one! Also have a search through the markdown for the phrase “TODO” as there’s a few in there. Move the pull request out of Draft when you think it’s ready to merge and will have another look over it. |
There was a problem hiding this comment.
I skimmed through the rendered page and things look good to me other than stylistic and editorial issues.
I thought of an alternate representation of how we report statistics on headings (H1..H6) in SEO or Markup chapters that encapsulates their hierarchical distribution, but it is too late to incorporate that now for this year.
I am wondering, should the description of figures be visible by default on large screens?
Possibly getting a little late, but keen to hear more about your idea anyway?
No think that would be repetitive. They are meant as additional content for visually impaired who maybe can’t appreciate the graphs (they are also linked with |
Co-authored-by: Sawood Alam <[email protected]>
src/content/en/2020/seo.md
Outdated
| translators: [] | ||
| #aleyda_bio: TODO | ||
| aleyda_bio: SEO consultant, author, speaker and entrepreneur. Founder of <a href="https://www.orainti.com/">Orainti</a> (a boutique SEO consultancy working with some of the top Web properties and brands, from SaaS to marketplaces) and co-founder of <a href="https://remoters.net/">Remoters.net</a> (a free remote work hub, featuring remote jobs, tools, events, guides, and more to facilitate remote work). Aleyda enjoys sharing about SEO through her <a href="https://www.aleydasolis.com/en/blog/">blog</a>, the <a href="https://www.aleydasolis.com/en/seo-tips/">#SEOFOMO newsletter</a>, the <a href="https://www.aleydasolis.com/en/crawling-mondays-videos/">Crawling Mondays</a> video and podcast series and over <a href="https://twitter.com/aleyda">Twitter</a>. | ||
| #ipullrank_bio: TODO |
There was a problem hiding this comment.
@ipullrank could you suggest a bio?
| translators: [] | ||
| #aleyda_bio: TODO | ||
| aleyda_bio: SEO consultant, author, speaker and entrepreneur. Founder of <a href="https://www.orainti.com/">Orainti</a> (a boutique SEO consultancy working with some of the top Web properties and brands, from SaaS to marketplaces) and co-founder of <a href="https://remoters.net/">Remoters.net</a> (a free remote work hub, featuring remote jobs, tools, events, guides, and more to facilitate remote work). Aleyda enjoys sharing about SEO through her <a href="https://www.aleydasolis.com/en/blog/">blog</a>, the <a href="https://www.aleydasolis.com/en/seo-tips/">#SEOFOMO newsletter</a>, the <a href="https://www.aleydasolis.com/en/crawling-mondays-videos/">Crawling Mondays</a> video and podcast series and over <a href="https://twitter.com/aleyda">Twitter</a>. | ||
| #ipullrank_bio: TODO | ||
| #fellowhuman1101_bio: TODO |
There was a problem hiding this comment.
@fellowhuman1101 could you suggest a bio?
|
Marking this as ready for review since this is almost ready to merge. I think once the metadata is in (bios, featured quote/stats) we can merge it and open up a new PR for editing. Any outstanding TODOs can be resolved as suggestions by the content team in the editing PR. |
… level than other elements
|
Wow! Something very important @ipullrank - when reviewing the content section I realized there was no "structured data" info in there ... which is in the outline as part of the content section, and was also gathered here.! I don't know how we had all missed this before when writing/reviewing that section... but it can not be left out :( it was included last year too.. Mike, since you were in charge of the content section, could you please add it in the gdocs and let me know as soon as you have so I can take it to markdown? If you're not available to do it today, could you please let me know to do it myself? Thanks in advance! cc @bazzadp @fellowhuman1101 @rviscomi @Tiggerito @antoineeripret |
|
@aleyda no problem. I got it when I wake up (it's 4:45 am here). Is there data for this? |
Thanks @ipullrank - really appreciate it !! and yes, here's the data in the Google Sheets: - in two sheets:
Thanks in advance! As soon as you have it in the Gdocs ping me please so I can convert it to markdown and merge to see how it looks ... if it has graphs then ping also @antoineeripret / @Tiggerito too please! Thanks :) |
|
@bazzadp I'm working on the Structured Data section here. I'm looking to compare some of the features to the 2019 data, but only the top 5 was highlighted in the write up for last year. @aleyda recommended I contact you to see if you knew where I could find the spreadsheet for the structured data section of 2019. Please advise. Thanks! |
|
@ipullrank see here. You can also find the link to the 2019 results at the bottom of the chapter |
Excellent! Thank you. |
It's a tremendous bio!
cc @ipullrank - I reworded a bit/did minor changes and asked @catalinred and @ibnesayeed to review (as I saw they were connected in Gdocs) so it might go through additional changes.... but it good to have it here already :D Thanks for the fast, awesome effort Mike!
|
Thanks for the fast and awesome work on the structured data section @ipullrank ! You rock :) I just reworded a bit and asked @catalinred and @ibnesayeed to revise (their revision is in progress), however, I already took it to markdown here. and if there are any further changes I will do them there. Thanks again! |
…st Tool cc @catalinred Incorporated these changes after your review! Thanks
|
I just wanted to confirm that I've now incorporated changes based on @catalinred and @ibnesayeed comments that I saw viable to add. See here in the doc and here in the markdown version (both updated). cc @ipullrank you might want to take a look ... just in case :) |
|
I did another test deploy here: https://20201202t114418-dot-webalmanac.uk.r.appspot.com/en/2020/seo We good to merge this and pick up any further changes during editing? |
Hi @bazzadp , thank you very much! I revised again and realized the structured data objects didn't have the "code" format which I just added and then also included some structured data findings in the conclusions. Once that @fellowhuman1101 I think we should be good to merge! I wouldn't like her bio to be left out from it. |
|
OK Merging as still an opportunity to finish the TODOs in editing. Thanks all looks great and just one more step and we're good for the launch! |
|
Hi @bazzadp, I'm seeing there's something a bit outdated already in the AMP section that would be great to replace... but I can't do it myself anymore. It's the change of non-AMP content being able to be shown in Google's top stories since May 2021, which was announced back in November (before it was included but without a specific date): Here's the current paragraph: "Additionally, AMP is at the moment a requirement to be featured in Google’s Top Stories carousel in mobile search results–which is an important feature for news related publications, although this is expected to change sometime next year to be replaced by the new page experience metric, that will become a ranking factor for Top Stories, which was announced by Google earlier this year." Here's the new: "Additionally, AMP is at the moment a requirement to be featured in Google’s Top Stories carousel in mobile search results–which is an important feature for news related publications. However, this will change in May next year, when non-AMP content will become eligible as long as it meets the Google News content policies and provides a great page experience as announced by Google in November this year." Would it be possible to replace this text? Thanks :) |
|
Doubt this’ll be the last thing you wanna tweak, if you’re anything like me, so let’s show you how to do it yourself:
That should open a new pull request for this edit which @rviscomi or I will review and then accept. Small pull requests like this are quite normal and how git works. It’s the large pull requests for whole chapters that are unusual 😉 So go ahead and do this one to get yourself used to this flow, as editing has not started yet. However after that, it’s then best to leave your other changes for during the editing pull request so that you don’t end up both changing the same text in git, which requires a bit of extra effort to resolve the “merge conflict”. |
|
Thanks @bazzadp, really appreciate your help! I just did it :D Hopefully there won't be that many new changes! Thanks again |
Closes #908