pseo-audit

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

pSEO Codebase Audit

pSEO代码库审计

Perform a structured audit of the codebase to assess readiness for programmatic SEO at 1000+ page scale. Produce a concrete gap analysis with actionable findings.
If pseo-discovery was run first, use its output to focus the audit: check whether the codebase can support the specific page types, data models, and URL structures the discovery proposed. If discovery was not run, audit generically.
对代码库进行结构化审计,以评估其是否具备支持1000+页面规模程序化SEO的就绪状态。生成包含可落地发现项的具体缺口分析报告。
如果已先运行pseo-discovery,请使用其输出结果聚焦审计:检查代码库是否能够支持发现阶段提出的特定页面类型、数据模型和URL结构。若未运行发现流程,则进行通用审计。

Audit Procedure

审计流程

1. Identify the Framework and Architecture

1. 识别框架与架构

  • Detect the framework (Next.js, Astro, Nuxt, Remix, etc.) from config files
  • Identify the rendering strategy: SSG, SSR, ISR, or client-side
  • Map the routing structure: file-based, dynamic segments, catch-all routes
  • Check for
    generateStaticParams
    ,
    getStaticPaths
    , or equivalent
  • 从配置文件中检测所使用的框架(Next.js、Astro、Nuxt、Remix等)
  • 确定渲染策略:SSG、SSR、ISR或客户端渲染
  • 梳理路由结构:基于文件的路由、动态分段、通配路由
  • 检查是否存在
    generateStaticParams
    getStaticPaths
    或等效机制

2. Assess Data Architecture

2. 评估数据架构

  • Locate data sources: CMS, database, API, local files (JSON, MDX, CSV)
  • Check for a centralized data-fetching layer vs. scattered inline fetches
  • Evaluate whether data models have the fields needed for SEO (title, description, slug, category, FAQ, etc.)
  • Look for a slug/URL generation strategy and whether it enforces uniqueness
  • 定位数据源:CMS、数据库、API、本地文件(JSON、MDX、CSV)
  • 检查是否存在集中式数据获取层,而非分散的内联数据获取
  • 评估数据模型是否包含SEO所需字段(标题、描述、slug、分类、FAQ等)
  • 查看slug/URL生成策略,以及是否强制保证唯一性

3. Evaluate Routing and Page Templates

3. 评估路由与页面模板

  • Count dynamic route segments and template pages
  • Check if templates produce unique content per page or rely on the same copy with minor variable swaps
  • Look for catch-all routes that may create orphan or thin pages
  • Verify 404 handling for invalid slugs
  • 统计动态路由分段和模板页面的数量
  • 检查模板是否为每个页面生成独特内容,还是仅依赖相同文案搭配少量变量替换
  • 查找可能产生孤立页面或内容单薄页面的通配路由
  • 验证无效slug的404处理机制

4. Review SEO Foundations

4. 审查SEO基础配置

  • Check for dynamic metadata generation (title, description, canonical)
  • Look for Open Graph and Twitter card tags
  • Search for JSON-LD structured data or schema markup
  • Check for a sitemap generator (static or dynamic)
  • Look for robots.txt configuration
  • Verify canonical URLs are set and self-referencing by default
  • 检查是否存在动态元数据生成(标题、描述、规范链接)
  • 查找Open Graph和Twitter卡片标签
  • 搜索JSON-LD结构化数据或Schema标记
  • 检查是否存在站点地图生成器(静态或动态)
  • 查看robots.txt配置
  • 验证规范链接是否已设置,且默认指向自身

5. Evaluate Internal Linking

5. 评估内部链接

  • Look for breadcrumb components
  • Search for related-pages or hub-spoke linking patterns
  • Check for programmatic cross-linking between pages
  • Assess whether link structures create topical clusters
  • 查找面包屑组件
  • 搜索相关页面或中心辐射式链接模式
  • 检查是否存在页面间的程序化交叉链接
  • 评估链接结构是否形成主题集群

6. Assess Performance at Scale

6. 评估大规模场景下的性能

  • Check build configuration for page generation limits or timeouts
  • Look for image optimization (next/image, sharp, etc.)
  • Check for code splitting and lazy loading
  • Identify large dependencies that bloat the bundle
  • Look for caching headers or ISR/revalidation configuration
  • 检查构建配置中的页面生成限制或超时设置
  • 查找图片优化机制(next/image、sharp等)
  • 检查是否存在代码分割和懒加载
  • 识别导致包体积臃肿的大型依赖
  • 查看缓存头或ISR/重新验证配置

7. Check Content Quality Safeguards

7. 检查内容质量保障机制

  • Look for content length or quality validation
  • Search for duplicate content detection or prevention
  • Check if pages have sufficiently differentiated titles and descriptions
  • Look for noindex rules on thin or utility pages
  • 查找内容长度或质量验证机制
  • 搜索重复内容检测或预防机制
  • 检查页面是否具备充分差异化的标题和描述
  • 查找针对单薄页面或工具页面的noindex规则

Output Format

输出格式

Structure the audit report as:
undefined
审计报告请按以下结构撰写:
undefined

pSEO Audit Report

pSEO Audit Report

Framework & Rendering

Framework & Rendering

  • [findings]
  • [findings]

Data Architecture

Data Architecture

  • [findings]
  • Readiness: [Ready | Needs Work | Missing]
  • [findings]
  • Readiness: [Ready | Needs Work | Missing]

Routing & Templates

Routing & Templates

  • [findings]
  • Readiness: [Ready | Needs Work | Missing]
  • [findings]
  • Readiness: [Ready | Needs Work | Missing]

SEO Foundations

SEO Foundations

  • [findings]
  • Readiness: [Ready | Needs Work | Missing]
  • [findings]
  • Readiness: [Ready | Needs Work | Missing]

Internal Linking

Internal Linking

  • [findings]
  • Readiness: [Ready | Needs Work | Missing]
  • [findings]
  • Readiness: [Ready | Needs Work | Missing]

Performance at Scale

Performance at Scale

  • [findings]
  • Readiness: [Ready | Needs Work | Missing]
  • [findings]
  • Readiness: [Ready | Needs Work | Missing]

Content Quality Safeguards

Content Quality Safeguards

  • [findings]
  • Readiness: [Ready | Needs Work | Missing]
  • [findings]
  • Readiness: [Ready | Needs Work | Missing]

Priority Actions (ordered)

Priority Actions (ordered)

  1. [most critical gap]
  2. [next priority] ...
  1. [most critical gap]
  2. [next priority] ...

Recommended Skill Sequence

Recommended Skill Sequence

Based on findings, recommend which pseo-* skills to run and in what order. If discovery was run, confirm which proposed page types are feasible given codebase state.
undefined
Based on findings, recommend which pseo-* skills to run and in what order. If discovery was run, confirm which proposed page types are feasible given codebase state.
undefined

Scope Parameter

范围参数

If
$ARGUMENTS
specifies a scope, narrow the audit:
  • full
    (default): Run all sections
  • routing
    : Sections 1, 3 only
  • data
    : Sections 1, 2 only
  • seo
    : Sections 4, 5, 7 only
  • performance
    : Sections 6 only
如果
$ARGUMENTS
指定了范围,请缩小审计范围:
  • full
    (默认):运行所有章节
  • routing
    :仅运行第1、3章节
  • data
    :仅运行第1、2章节
  • seo
    :仅运行第4、5、7章节
  • performance
    :仅运行第6章节

Important Constraints

重要约束

  • Read files and analyze; do NOT modify any code during audit
  • Be specific: cite file paths and line numbers for every finding
  • Flag risks that would surface only at 1000+ pages (build time, memory, URL collisions)
  • Distinguish between "not implemented" and "implemented incorrectly"
  • 仅读取文件并分析;审计过程中不得修改任何代码
  • 内容需具体:每个发现项都要引用文件路径和行号
  • 标记仅在1000+页面规模下才会显现的风险(构建时间、内存占用、URL冲突)
  • 区分“未实现”和“实现错误”两种情况