layer5io
SEO Enhancement for Kanvas Designer Page
Current Behavior
This PR/issue proposes several SEO improvements for the Kanvas Designer page at https://layer5.io/cloud-native-management/kanvas/design, based on an analysis from Seobility’s SEO Checker.
Desired Situation
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.
- 📚 See contributing instructions.
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.
Join the Layer5 Community by submitting your community member form.
Findings from SEO Analysis:
Critical Issues:
Multiple H1 headings: The page should use only one H1 tag.
Words in the H1 heading (“400+ Built-in Integrations”) are not reflected in the main content. H1 content and page content should align.
Warnings:
Many images (48) lack alt attributes. These should be descriptive for search engines and accessibility.
Duplicate heading texts occur—headings (h2-h6) should be unique.
Anchor texts are repeated, and one link lacks anchor text.
Mobile optimization: Multiple viewport tags present, only one should be used for proper mobile rendering.
SEO Recommendations / Tasks:
Limit to a single H1 tag per page and ensure the H1 text matches main page keywords and content.
Add descriptive alt attributes to all images for improved accessibility and on-page SEO.
Remove duplicate heading texts (ensure h2-h6 are unique and topic-relevant).
Expand the meta title to use more descriptive and keyword-rich language.
Improve mobile optimization: Check and remove duplicate viewport tags.
Add/Enhance social sharing options for the page.
Review anchor texts—avoid duplicates and ensure all links have descriptive anchor texts.
Consider adding structured data (schema.org, Open Graph, Twitter cards) if applicable.
Encourage backlinks for better external SEO.
Evidence and References:
Seobility SEO report for /cloud-native-management/kanvas/design
@Namanv0509 ,I have setup the repo locally and would like to work on this issue.
