Skip to content

docs: add seo guide #1059

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

Closed
wants to merge 57 commits into from
Closed
Changes from all commits
Commits
Show all changes
57 commits
Select commit Hold shift + click to select a range
8f17680
docs: add seo guide
CBID2 Feb 9, 2024
995f474
feat: finish section on S
CBID2 Feb 9, 2024
a59d5e2
feat: add frontmatter
CBID2 Feb 9, 2024
30b0dbd
fix: omit heading 1
CBID2 Feb 9, 2024
29c82a2
Merge branch 'master' into seo-guide
quetzalliwrites Feb 13, 2024
5b9d282
feat: made improvements in the sections about SEO and headings
CBID2 Feb 16, 2024
873c3d7
feat: revise sections about URL and alt text
CBID2 Feb 16, 2024
ea636c0
feat: add examples of SEO-friendly URLs
CBID2 Feb 16, 2024
02c1621
feat: add section for other ways to make Asyncapi's documentation SEO…
CBID2 Feb 16, 2024
b038d16
Merge branch 'master' into seo-guide
CBID2 Feb 16, 2024
4dd2cbe
Merge branch 'master' into seo-guide
quetzalliwrites Feb 21, 2024
0ab1ee6
fix: remove addtional suggestions section
CBID2 Feb 22, 2024
a290e30
fix: omit bullet point
CBID2 Feb 22, 2024
1043e2d
fix: revise typos
CBID2 Feb 22, 2024
c5c2cb3
feat: created section for Anchor text
CBID2 Feb 22, 2024
e36abe0
feat: add explanation on what makes URL examples SEO-friendly
CBID2 Feb 29, 2024
dc7e656
feat add tips on making SEO-friendly anchor texts and a section for e…
CBID2 Feb 29, 2024
97ddcac
Merge branch 'master' into seo-guide
CBID2 Feb 29, 2024
f69a121
feat: add examples of SEO-friendly anchor texts
CBID2 Mar 3, 2024
cd32a5d
Merge branch 'master' into seo-guide
CBID2 Mar 3, 2024
91a9ba2
fix: revise meta description
CBID2 Mar 3, 2024
4d6a15f
feat: add explanation about what makes the example anchor text SEO-fr…
CBID2 Mar 3, 2024
ccbd863
fix: revise Markdown errors
CBID2 Mar 3, 2024
67082d4
Merge branch 'master' into seo-guide
CBID2 Mar 11, 2024
3810936
Merge branch 'master' into seo-guide
CBID2 Mar 13, 2024
a3d1deb
feat: add some comments
CBID2 Mar 13, 2024
1dc4c41
feat: finished adding more detail about headings and start another se…
CBID2 Mar 31, 2024
ae9d05d
feat: added new sections
CBID2 Mar 31, 2024
27225f7
fix: omit comment and revise markdown formatting
CBID2 Mar 31, 2024
100f76f
fix: revise headings
CBID2 Apr 1, 2024
6385f00
feat: finished section on meta descriptions
CBID2 Apr 1, 2024
4a75db2
Merge branch 'master' into seo-guide
CBID2 Apr 1, 2024
00944f1
feat: revise structure
CBID2 Apr 1, 2024
129986f
fix: remove period
CBID2 Apr 1, 2024
0f21cb8
docs: finished adding information about mobile and SEO-friendly techn…
CBID2 Apr 3, 2024
93580b4
docs: add Additional resources section
CBID2 Apr 3, 2024
8629680
docs: fix formatting issues
CBID2 Apr 3, 2024
c9c1068
Merge branch 'master' into seo-guide
CBID2 Apr 18, 2024
518fb48
docs: add section on image optimization
CBID2 Apr 18, 2024
3f67568
Merge branch 'master' into seo-guide
CBID2 May 26, 2024
21c7e1c
docs: made edits
CBID2 May 26, 2024
f551555
docs: fix explanation
CBID2 Jun 2, 2024
11a7898
Merge branch 'master' into seo-guide
CBID2 Jun 2, 2024
1e90fb7
Merge branch 'master' into seo-guide
CBID2 Jun 4, 2024
f3dc224
docs: revise description
CBID2 Jun 5, 2024
7bc89d6
Merge branch 'master' into seo-guide
CBID2 Jun 16, 2024
7c77e38
docs: change sentence
CBID2 Jul 1, 2024
c29c022
Merge branch 'master' into seo-guide
CBID2 Jul 1, 2024
8fde226
fix: revise errors
CBID2 Jul 1, 2024
8b21d9c
Merge branch 'master' into seo-guide
CBID2 Jul 14, 2024
18cb74d
Merge branch 'master' into seo-guide
CBID2 Jul 16, 2024
8d26291
Merge branch 'master' into seo-guide
CBID2 Oct 27, 2024
09c926d
Merge branch 'master' into seo-guide
thulieblack Feb 6, 2025
687787f
edit spelling, grammar and consistency
thulieblack Mar 6, 2025
200f4b9
Rewrite the sections for clarity
thulieblack Mar 6, 2025
6663fd9
Merge branch 'master' into seo-guide
thulieblack Mar 6, 2025
1318231
Merge branch 'master' into seo-guide
thulieblack Mar 6, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
146 changes: 146 additions & 0 deletions docs/styleguide/seo.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,146 @@
---
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.

title: SEO
description: This guide gives advice on how to implement SEO when creating tutorials and other forms of content for Asyncapi.
---

## What is SEO?
Search Engine Optimization (SEO) encompasses various techniques and strategies to improve a website's visibility in search engine results. Effective SEO can increase organic traffic by ensuring relevant content reaches the intended audience.

## Why is SEO important in technical documentation?

Integrating SEO practices into technical documentation makes it easier for users and contributors to discover valuable resources and ultimately fosters community engagement and collaboration, enhancing the overall knowledge base.

## SEO best practices

### Headings?

Headings are HTML tags that create a structured hierarchy in content, making it easier for readers to navigate and for search engines to index.

#### Strategies for making SEO-friendly headings

- **Use Hierarchical Order:** Begin with the `<h1>` tag for the main title, followed by `<h2>` for major subsections, `<h3>` for sub-subsections, and so forth, ensuring a clear structure throughout the documentation.
- **Incorporate Relevant Keywords:** Utilize keywords strategically, particularly within `<h1>` and `<h2>` tags, as these are among the first elements users engage with.

### Examples of SEO-friendly headings from AsyncAPI's documentation

```md
# Server
## What is a Server?
## What is the purpose of servers?
### Client and Server
```

### What are URLS?

URLs serve as the addresses for web pages and other online resources. An SEO-friendly URL structure improves user experience and enhances discoverability.

#### Strategies for making SEO-friendly URLs

- **Keep It Short:** Short URLs are simpler for users to remember and share.
- **Include Keywords:** Effective keyword incorporation helps search engines index the URL successfully.
- **Avoid Special Characters and Spaces:** Use hyphens (-) instead of underscores (_) to separate words, as search engines interpret hyphens as spaces.

Here are some examples of SEO-friendly URLs from AsyncAPI's documentation:

- `https://www.asyncapi.com/docs/concepts/application`
- `https://www.asyncapi.com/docs/concepts/server`
- `https://www.asyncapi.com/docs/concepts/message`

These URLs are concise and relevant to the documentation's topics, avoiding special characters.

### What is Anchor Text?

Anchor text refers to the clickable text in a hyperlink, providing context about the linked webpage's content.

#### Strategies for making SEO-friendly anchor texts

- **Use Descriptive Phrases:** Ensure the anchor text is relevant to the linked content, incorporating keywords without overstuffing.
- **Consider User Intent:** Tailor the anchor text based on what users will likely search for within the documentation.
- **Update Regularly:** As AsyncAPI evolves, it is important to refine the anchor text regularly to match updated content.

### Examples of SEO-friendly anchor texts from AsyncAPI's documentation

- [AsyncAPI](https://github.com/asyncapi)
- [Server Object](https://www.asyncapi.com/docs/reference/specification/latest#serverobject)
- ["The many meanings of Event-Driven Architecture"](https://www.youtube.com/watch?v=STKCRSUsyP0)

These links include relevant keywords such as "AsyncAPI", "Server Object", and "the many meanings of Event-Driven Architecture", which accurately describe the content they are linked to.

### What is Internal Linking?

Internal linking involves creating hyperlinks within a document that connect to other sections or relevant resources. The practice enhances navigation within AsyncAPI's content.

#### Strategies for making SEO-friendly internal links

- **Develop an internal link structure**: Consider deciding the types of internal links to use when writing a blog post or documentation for AsyncAPI. Doing so would help increase the chances of the content appearing in the search results. To learn more about the different styles of internal links, check out the [Types of Internal Links section in "Internal Links for SEO: An Actionable Guide"](https://ahrefs.com/blog/internal-links-for-seo/#types-of-internal-links).
- **Create unique anchor texts:** Use distinct text for different links to avoid user confusion and clarify the destination content.
- **Include keywords in your anchor text**: Including relevant keywords in internal links helps search engines understand the content's focus.

### Examples of SEO-friendly anchor texts from AsyncAPI's website

- "In this case, in your AsyncAPI file, you describe the `server`, and therefore, the [Server Object](https://www.asyncapi.com/docs/reference/specification/latest#serverObject) holds information about the actual server, including its physical location."
- "JSON Schema Draft 07 is 100% compatible with AsyncAPI schemas. You can also use other standards to describe payload schema, such as [Avro](https://github.com/asyncapi/avro-schema-parser#usage)."
- "Furthermore, the [Pub/sub](/docs/tutorials/getting-started/event-driven-architectures#publishersubscriber) is appealing for IoT use cases due to two key features: support for flexible coupling between publishers/subscribers and inherent support for point-to-multipoint transmission."

### What are meta descriptions?

Meta descriptions are short snippets of HTML that briefly summarize a web page's content. They appear below the page title in search results and can influence click-through rates.

>[!NOTE]
> Meta descriptions are often written in YAML format for AsyncAPI's documentation.

#### Strategies for making SEO-friendly meta descriptions

- **Be Concise and Informative:** Summarize the content, keeping it under 160 characters to ensure it displays fully in search results.
- **Include Keywords:** Use relevant keywords to improve search visibility while accurately reflecting the page content.
- **Engage the Reader:** Write compelling descriptions encouraging search engine results clicks.

### Examples of SEO-friendly meta descriptions from AsyncAPI's website

- `title: Kafka bindings
description: Learn how to configure Kafka bindings in your AsyncAPI document.`
- `title: "Validate AsyncAPI documents"
description: In this guide, you'll learn multiple ways to validate AsyncAPI documents.`
- `title: Generate code
description: In this tutorial, you'll learn how to generate code from your AsyncAPI document.`

In addition to having information that correlates to the content's topic, these meta descriptions are concise and contain keywords.

### Why is mobile-friendliness important to technical documentation when making it SEO-friendly?

With most online content consumed on smartphones, tablets, and computers, ensuring that AsyncAPI's mobile-friendly content is essential. Research shows that **users are more likely to return to and positively view a website if it is mobile-friendly**. Additionally, technical documentation that is optimized for mobile devices tends to rank higher in search results.

#### Strategies for making mobile and SEO-friendly content

Here are some ways to make blog posts and documentation for AsyncAPI's website mobile and SEO-friendly.

- **Use Smaller Images and Videos**: Large media files can slow down page loading times, leading to a poor user experience. Opt for smaller, optimized files whenever possible.

- **Select Mobile-Friendly Fonts**: Some fonts can be difficult to read on smaller screens. Choose adaptable font styles for body text, and it should ideally be between 14-16 points for headings and 12 points for body text.
- **Create Individual Pages or Sections for Each Topic**: Providing dedicated pages or sections for different topics and links to related content will enhance navigation and usability.

### Why is quality important when making technical documentation that is SEO-friendly?

Search engines prioritize content that delivers real value to users. Therefore, ensuring that your content is of high quality is crucial.

#### Strategies for making high-quality and SEO-friendly content

When writing for AsyncAPI's blog or documentation, ask yourself the following questions to ensure your content meets quality standards:

- Is the content interactive and engaging?
- Is the information presented accurate?
- Is the content too technical for its intended audience?

### Images

How images are incorporated into technical documentation can significantly impact search engine rankings. Therefore, it is vital to optimize images effectively.

### Strategies for making images SEO-friendly

To make SEO-friendly images, it is recommended to use the following methods:

- **Create Descriptive Alt Text**: Ensure each image has alt text that accurately describes its context and purpose. It helps with SEO and improves accessibility for users who may not see the image.
- **Use Supported Image Formats**: Formats such as **WEBP** are widely used throughout AsyncAPI and are recognized by search engines, making them preferable for web use.
- **Optimize File Sizes**: Large image files can slow a website's loading times. Compress and reduce the file sizes before including them in your documentation or blog posts to enhance performance.

By implementing these best practices, you can enhance the SEO of your technical documentation, making it more accessible and valuable to users and contributing to a thriving community.
Loading