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

Improve SEO #204

Open
zugdev opened this issue Feb 20, 2025 · 0 comments
Open

Improve SEO #204

zugdev opened this issue Feb 20, 2025 · 0 comments

Comments

@zugdev
Copy link
Collaborator

zugdev commented Feb 20, 2025

We should definitely do some search engine optimization (SEO) for both work.ubq.fi and devpool.directory.

  1. For work.ubq.fi the title and description aren't properly rendered like in devpool.directory.

Image

Image

  1. I don't find the current description good, we should target our audience: talents in blockchain. Perhaps something more invocative like: Discover blockchain development jobs and opportunities in the DevPool network. Browse, apply, and connect with top Web3 projects at Ubiquity DAO..

  2. Canonical tag is outdated, since devpool.directory has become the standard.

<link rel="canonical" href="https://work.ubq.fi" />
  1. Keyword targeting is bad, as in 2.

  2. We should probably have one descriptive header <h1> within the <body>, even if not rendered. Reference

  3. Implement JSON-LD Schema Markup for better indexing, GPT suggested something like:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Ubiquity DAO",
  "url": "https://work.ubq.fi",
  "logo": "https://work.ubq.fi/favicon.svg",
  "description": "Find blockchain and Web3 development jobs in the DevPool Directory.",
  "sameAs": [
    "https://twitter.com/UbiquityDAO",
    "https://dao.ubq.fi"
  ]
}
</script>
  1. Add alt attribute to all images and icons. This is important not only for SEO but accessibility.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants