Skip to content

SEO: landing pages, comparisons, guides and entity schema - #7

Open
codellyson wants to merge 1 commit into
mainfrom
seo/landing-and-schema
Open

SEO: landing pages, comparisons, guides and entity schema#7
codellyson wants to merge 1 commit into
mainfrom
seo/landing-and-schema

Conversation

@codellyson

Copy link
Copy Markdown
Owner

Acts on the JustDB SEO recommendations. All new content pages reuse the existing design system and components; verified with a clean astro build (14 pages) and astro check (0 errors / 0 warnings).

What's included

Pillar 1 — Long-tail landing pages (/alternatives)

  • Hub + sqlite-viewer-macos, postgresql-gui, turso-libsql-client, each targeting one high-intent phrase with a live product mock.

Pillar 2 — Entity authority / technical SEO

  • @astrojs/sitemap → auto sitemap-index.xml; public/robots.txt.
  • Centralized JSON-LD in src/lib/seo.ts: linked Organization + WebSite + enriched SoftwareApplication (featureList, screenshot, applicationSubCategory) + breadcrumb/FAQ/article helpers.
  • Layout.astro gains noindex + ogType support.

Pillar 3 — Comparison / "versus" pages (/compare)

  • Hub + JustDB vs DBeaver, pgAdmin, Beekeeper Studio. Qualitative, verifiable tables (no invented benchmarks) with an honest "when the other tool is the better pick" section, plus per-page SoftwareApplication + FAQ + breadcrumb schema.

Pillar 5 — Knowledge base (/guides)

  • Hub + 3 how-tos: view SQLite tables locally, edit Postgres cells inline, connect to Postgres in Docker. TechArticle schema, cross-linked to landing pages.

Cross-cutting: Nav + Footer + homepage link the new sections for internal crawlability.

Not in scope

  • Pillar 4 (GitHub org, Product Hunt, directory backlinks) is off-site work.
  • Root package.json dev:marketing script and the apps/marketing/pnpm-lock.yaml deletion were pre-existing/unrelated changes, intentionally left out of this branch.

…hema

Acts on the JustDB SEO recommendations:

- Pillar 1 (long-tail): /alternatives landing pages — fast SQLite viewer for
  macOS, minimalist PostgreSQL GUI, Turso/libSQL desktop client.
- Pillar 2 (entity authority): centralized JSON-LD in lib/seo.ts — linked
  Organization + WebSite + enriched SoftwareApplication (featureList,
  screenshot, subcategory), plus breadcrumbs/FAQ/article helpers. Add
  @astrojs/sitemap and public/robots.txt.
- Pillar 3 (versus): /compare hub + JustDB vs DBeaver, pgAdmin and Beekeeper
  Studio — honest qualitative tables with a "when the other tool wins" section.
- Pillar 5 (knowledge base): /guides hub + 3 how-tos (view SQLite tables
  locally, edit Postgres cells inline, connect to Postgres in Docker).

Nav/Footer/homepage cross-link the new sections for crawlability. Layout gains
noindex + ogType support.
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.

1 participant