SEO Optimisations

未关闭
#323 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
github-actions

调研方向

首先对照 repository 检查 checklist,重点查看 src/layouts/Layout.astro、robots.txt 和 deploy GitHub Action。将工作划分为可独立验证的项目,然后使用 audit 的 SEO、性能、可访问性和内容标准,确认每个选定项目都已完成。

由索引模型根据 Issue 内容生成。

描述

ipfs.tech SEO Audit

Schema / Structured Data

  • [Critical] Add Organization + WebSite + SoftwareApplication JSON-LD to src/layouts/Layout.astro

On-page / Search Experience (SXO)

  • [Critical] Add a self-contained "What is IPFS" definition block near the H1 (~150–250 words, must include the literal phrase "InterPlanetary File System," must stand alone without pronouns referring outside the passage)
  • [High] Add a decision-stage section for technical evaluators (CTO/decision-maker persona currently scores 40/100) — comparison framing vs. Filecoin/Arweave, business-outcome case studies, separate from the existing logo carousel
  • [Medium] Add a short trust/security passage — a Check Point phishing article ranks in the top 10 for "IPFS" itself, and nothing on-page addresses it
  • [Medium] Turn the "pick the tool" link list into a decision table (use case → recommended tool → one-line why)

AI Search Readiness (GEO)

  • [High] Rewrite hero stats ("400k+ public nodes," "1B+ CIDs," "17.1K GitHub stars") as full, source-attributed, dated sentences instead of bare <dl> pairs
  • [Medium] Differentiate AI crawler policy in robots.txt — decide deliberately whether to keep training-only bots (CCBot, anthropic-ai, cohere-ai) allowed alongside answer-engine bots (GPTBot, ClaudeBot, PerplexityBot)
  • [Medium] Surface the existing YouTube channel (@IPFSbot) and add LinkedIn to nav/footer — YouTube mentions carry the strongest documented correlation with AI citation likelihood
  • [Low] Add an optional llms.txt mirroring key homepage facts and doc links

Performance / Core Web Vitals

  • [Critical] Simplify or defer the hero's 393-node SVG gradient mesh (g.mesh) — it accounts for 2.35s of the 3.28s mobile LCP via pure element-render-delay, not resource loading
  • [High] Trim unused Commit Mono font weights from the render-blocking critical chain; preload only the weight used above the fold
  • [High] Right-size and convert oversized images to WebP/AVIF (worst offender: a 176.8KB portrait served at 70×70 display — ~360KB total savings available)
  • [Low] Add <link rel="preconnect" href="https://plausible.io">
  • [High] Set Cache-Control: public, max-age=31536000, immutable on all content-hashed assets under /_astro/* and /fonts/* (~534KB avoidable repeat-visit transfer today)

Technical SEO

  • [High] Evaluate fronting the apex domain with a header-capable CDN (e.g. Cloudflare) to add CSP, HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy — GitHub Pages has no config file for these; alternatively, explicitly accept and document the risk
  • [Medium] Add an IndexNow key + a one-line ping step to the deploy GitHub Action

Content Quality / E-E-A-T

  • [High] Add a Privacy Policy / Terms link to nav or footer — the newsletter signup collects user data with no on-site link to data-handling terms
  • [Medium] Re-source the "Using IPFS in production at Wikipedia" claim — currently links to IPFS's own blog post, not an independent third-party confirmation
  • [Medium] Add author/maintainer attribution or a "reviewed by" signal for technical claims (CIDs, DHT, Bitswap, transport protocols)
  • [Low] Fix "Join the disussions" typo in the community footer CTA
  • [Low] Lengthen the meta description to use the full ~155-character budget

Visual / Mobile

  • [High] Enlarge mobile tap targets on the hamburger menu and theme toggle (currently 34×34 CSS px, used on every page load — under the 44×44/48×48 recommended minimums)
  • [High] Enlarge and space out the testimonial carousel's prev/next arrow buttons (same 34×34px issue, ~8px apart)
  • [Medium] Check contrast of the "Using IPFS in production" logo strip in dark mode (renders grey-on-near-black)

Sitemap & Content Architecture

  • [Medium] Resolve duplicate intent between docs.ipfs.tech/how-to/pin-files/ and docs.ipfs.tech/quickstart/pin/ — both compete for "how to pin files on IPFS"
  • [Medium] Build a blog.ipfs.tech comparison/use-case content cluster ("IPFS vs Filecoin," decentralized storage landscape, use cases beyond NFTs) to reclaim commercial-investigation queries currently owned by Filebase, Coinbase, and Medium
  • [Low] Add a real <lastmod> to ipfs.tech's own sitemap entry, tied to actual content edits
  • [Info] specs.ipfs.tech has no sitemap or robots.txt at all — external subdomain, not fixable from this repo; flag to whoever owns that deployment

Backlinks

  • [Low] Add a free Moz API key (MOZ_API_KEY / .config/claude-seo/backlinks-api.json) to unlock referring-domain count, DA/spam score, and anchor-text distribution — current read is Common-Crawl-only and reported as insufficient data for a health score
主要语言
Astro
星标
35
派生
18
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ipfs/ipfs-website 的其他 Issue

查看 ipfs/ipfs-website 的全部 Issue

相似的 Issue

更多 Content Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。