Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add seo guide #1059

Open
wants to merge 52 commits into
base: master
Choose a base branch
from
Open

docs: add seo guide #1059

wants to merge 52 commits into from

Conversation

CBID2
Copy link

@CBID2 CBID2 commented Feb 9, 2024

Description

This PR adds a guide to help people make their contributions more SEO-friendly.

Related issue(s)

Closes #1256

Signed-off-by: Christine Belzie <[email protected]>
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

EO-friendly URLs

Signed-off-by: Christine Belzie <[email protected]>
@quetzalliwrites
Copy link
Member

Hey there, @CBID2, thank you for contributing to our OSS project! 🐻 We appreciate your time.

Your PR is a good first draft, good work. I will leave you a review today and then simply address the feedback given.

@@ -0,0 +1,38 @@
---
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📣 Feedback for Draft 1

What is SEO?

The definition is accurate but could be slightly rephrased. For example, "SEO (Search Engine Optimization) refers to the methods and strategies used to enhance the visibility of a website's content in search engine results."

Why is it important in our Documentation?

Could you add a sentence about the potential for increased contributions and community growth through effective SEO?

Headings

  • The phrase "chronological order" is confusing because we're not discussing time. It's clearer to say, "hierarchical order".
  • Include an example of headings.

Alt Text

  • The phrase "avoid writing add every single detail" has a typo. It could be corrected to "avoid writing down every single detail."
  • Include an example of good alt text.

URLs

  • The guidance is generally good but simplifying the explanation could make it more accessible. For instance, "Use hyphens (-) instead of underscores (_) to separate words in URLs, as search engines treat hyphens as space."
  • Add examples of well-structured URLs from our different content buckets such as: asyncapi.com/docs/concepts/server

Additional Suggestions

  • Meta Descriptions: Our current docs and blog posts all use meta descriptions and titles. These summaries appear under the title in search results and can significantly impact click-through rates.
  • Mobile-Friendliness: Mention the importance of ensuring that documentation is mobile-friendly, as this is a factor in search engine rankings.
  • Internal Linking: Encourage the use of internal linking to other parts of the documentation or the AsyncAPI website to boost SEO and user navigation.
  • Content Quality: Emphasize the importance of high-quality, original content. Search engines favor content that provides value to users.
  • Anchor Text:
    • Be descriptive and relevant.
    • Avoid generic phrases like "click here" or "this page". (Instead, use meaningful phrases that give users and search engines an idea of what to expect on the linked page.)
    • Vary your anchor text. While it's important to be descriptive, using the exact same anchor text for every link to a particular page can appear spammy to search engines. Try to vary the phrasing while still being clear about the page content.

Copy link
Member

@quetzalliwrites quetzalliwrites left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking forward to Draft 2, @CBID2 🪄

@CBID2
Copy link
Author

CBID2 commented Feb 16, 2024

Looking forward to Draft 2, @CBID2 🪄

Hi @alequetzalli! :) I just finished Draft 2! :)

Comment on lines 60 to 68
#### Additional Suggestions
- **Meta Descriptions:** Our current docs and blog posts all use meta descriptions and titles. These summaries appear under the title in search results and can significantly impact click-through rates.
- **Mobile-Friendliness:** Mention the importance of ensuring that documentation is mobile-friendly, as this is a factor in search engine rankings.
- **Internal Linking:** Encourage the use of internal linking to other parts of the documentation or the AsyncAPI website to boost SEO and user navigation.
- **Content Quality:** Emphasize the importance of high-quality, original content. Search engines favor content that provides value to users.
**Anchor Text:**
- Be descriptive and relevant.
- Avoid generic phrases like "click here" or "this page". (Instead, use meaningful phrases that give users and search engines an idea of what to expect on the linked page.)
- Vary your anchor text. While it's important to be descriptive, using the exact same anchor text for every link to a particular page can appear spammy to search engines. Try to vary the phrasing while still being clear about the page content.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this? Why did you copy/paste my feedback comment into the documentation? You were supposed to apply the feedback for writing the missing content.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was under the impression that this information needed to be added to the guide. My mistake

- **Use keywords**: Like alt text, effectively adding keywords in the URL would make it easier for Google to find them.
- **Avoid using special characters and spaces:** Use hyphens (-) instead of underscores (_) to separate words in URLs, as search engines treat hyphens as space.

Here are some examples of SEO-friendly URLs from our documentation:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What makes these links SEO friendly? We should also explain how the URL clearly shows our content buckets.


SEO (Search Engine Optimization) refers to the methods and strategies used to enhance the visibility of a website's content in search engine results.

### Why is important in our Documentation?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there, just a reminder that we observe sentence capitalization in headers. Please update and correct all headers accordingly :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A reminder that the doc should be written to the audience via "you", not "we." Please go through your doc and update all mentions accordingly.

Headings are tags used to make sub titles distinctive from each other. When it comes to making them SEO-friendly, it's highly recommended to do the following:

- **Put them in hierarchcial order:** Since an `h1` tag tend to be titles, always start with this tag. From there, use `h2` and`h3` tags for the subsections and `h4` and `h5` tags for other sections in your tutorial or other piece of documentation.
- **Be descriptive:** Avoid using terms like "Conclusion" and "Introduction" due to their vagueness. Instead, make them specific and ensure they describe the section's content.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Be descriptive:** Avoid using terms like "Conclusion" and "Introduction" due to their vagueness. Instead, make them specific and ensure they describe the section's content.
- **Be descriptive:** Avoid using terms like "Conclusion" and "Introduction" due to their vagueness. Instead, make them specific and ensure they describe the section's content.

This advice contradicts our own documentation outline approach. All our tutorials intentionally have headers such as Introduction, Summary, and Next steps. Please remove this line.

@CBID2
Copy link
Author

CBID2 commented Apr 18, 2024

Hi @alequetzalli! :) I made more updates to the SEO guide.

@CBID2 CBID2 requested a review from quetzalliwrites June 2, 2024 23:00
@CBID2 CBID2 marked this pull request as ready for review June 2, 2024 23:03
Copy link

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content looks good to me, but a quick suggestion, please run the document through grammarly once. There are some minor fixes to be made here and there :)

Thanks @CBID2

docs/styleguide/seo.md Outdated Show resolved Hide resolved
@AnimeshKumar923
Copy link
Contributor

AnimeshKumar923 commented Jul 16, 2024

@TRohit20 is this ready for merge?

cc: @CBID2

@CBID2
Copy link
Author

CBID2 commented Jul 16, 2024

@TRohit20 is this ready for merge?

cc: @CBID2

Hi @TRohit20. I made the requested edits, so I'm ready to get this PR merged

@thulieblack
Copy link
Member

We need to have a content bucket for the style guides before merging. Once the docs automation from the community repo is done, Quetzalli will give the final go-ahead.

Please wait till then 😊

@thulieblack
Copy link
Member

Still waiting for the automation for the docs to be complete before merging this cc @quetzalliwrites

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docs: new style guide - SEO
5 participants