seo: generate "free alternatives to …" pages from tags, each with recorded licence terms

Aberta
  • Algo errado?
#189 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
55/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
content, frontend

Direção de pesquisa

Start by reading the category-page generation and sitemap entry points, then define the proposed site/alternatives.json mapping for search terms, tags or IDs, and context. Check how category pages handle structured data and licence verdicts; done means at least five pages list only active entries with verdicts, appear in the sitemap, and link from relevant category pages.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement marketing priority: low

Who it's for and why

This targets search traffic with commercial intent. Developers often search for "free alternative to Synty", "free Unity Asset Store alternatives for X" or "free alternative to Mixamo". Existing results are listicles with no licence detail. A generated page that lists catalog options with their dated licence verdicts is more useful than those pages, and it plays to the catalog's real differentiator.

Suggested approach

  • Define a small mapping file, e.g. site/alternatives.json: paid product or category → tags/subcategories/ids, plus one sentence of human-written context.
  • Generate /alternatives/<slug>/ pages from it with the same head, structured data and licence glance as category pages.
  • Start with 5-8 well-known searches, and cross-link them from category pages.
  • Avoid comparative claims about the paid product beyond what it is; name it only to describe the search.

Done when

At least five alternatives pages are in the sitemap, each listing only active entries with their licence verdict, and they are linked from the relevant category pages.

Linguagem predominante
JavaScript
Estrelas
58
Forks
15
Merge médio
1d 15h
PRs com merge (30d)
12

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/Free-Game-Dev-Assets

Todas as issues de TMHSDigital/Free-Game-Dev-Assets

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.