返回提示词目录第 1153 页

审查文档站搜索优化问题

检查技术文档站的收录与内容缺口,制定优先页面改进计划,并列出搜索效果跟踪指标。

完整提示词

<context>
Documentation is where developers learn most (the Stack Overflow developer survey puts technical documentation at the top), and docs are often the main search entry point for an open-source project. Developers search with tasks ("rate limit express routes"), error messages pasted verbatim, comparisons and "how to migrate from". Common docs-site problems: every version of every page indexed as a duplicate with no canonical; titles that repeat the product name and say nothing ("Introduction | Foo"); single-page apps that render nothing without JavaScript; reference pages with no prose; answers buried in Discord or GitHub Discussions where search engines reach them poorly. Diátaxis (tutorials, how-to guides, reference, explanation) is a widely used way to make sure each need has a page. Google's guidance rewards people-first pages and treats mass-produced pages made to rank as low quality.
</context>

<task>
<site>
{{site}}
</site>
{{#search_data}}
Search and question data:
{{search_data}}
{{/search_data}}
Priority: {{priority}}.

If you cannot see the site structure or page list, ask for a sitemap or nav tree and stop.

1. **Technical issues.** Check, from what you can see: indexability (robots, noindex, JavaScript-only rendering), canonical tags across versions and a "latest" alias, sitemap coverage and freshness, title and meta description patterns, heading structure, broken links and redirects after renames, page speed red flags, structured data if relevant, and whether the docs live on the project's own domain. Mark anything you could not check as UNVERIFIED and say how to check it.
2. **Content gaps.** Map the existing pages onto Diátaxis and onto the searches people make. Use the search data if given; otherwise derive likely queries from the project's features, its common errors and its alternatives, and label them as hypotheses. List missing pages: task how-tos, pages for the most common error messages (with the exact message in the title), migration guides from the main alternatives, comparison pages, and answers that exist only in chat or issues.
3. **Page plan.** The ten highest-value pages to create or fix, each with the target query, the page type, a title under 60 characters that starts with the task, a meta description, the outline and the internal links to and from it.
4. **Measuring.** What to watch monthly: impressions and clicks per page and query, the share of traffic landing on docs from search, docs-to-install clicks, and questions that stop recurring in issues. Use privacy-friendly analytics only.
</task>

<constraints>
- No keyword stuffing, doorway pages or auto-generated thin pages per keyword.
- Do not invent traffic numbers or search volumes; label estimates as estimates.
- Recommend moving answers out of chat only with the authors' consent or by rewriting them in your own words.
{{> output/uncertainty}}
</constraints>

<output_format>
## Verdict
The three changes that matter most.
## Technical issues
| Issue | Evidence | Fix | Effort |
## Content gaps
| Need or query | Existing page | Gap |
## Page plan
| # | Target query | Type | Title | Links |
Outlines below the table.
## Measuring
</output_format>

可替换内容

  • {{site}}
  • {{#search_data}}
  • {{search_data}}
  • {{/search_data}}
  • {{priority}}
  • {{> output/uncertainty}}

分类与标签

商业营销、文档站优化、搜索引擎优化、内容缺口、页面规划

前往 AI 图片创作