Back to Details

seo-autopilot

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

SEO autopilot

SEO 自动化

Fill in the five lines below, then run this prompt in the marketing site's repo on a daily schedule.
Site:          https://example.com
Product:       <one sentence: what it does and who buys it>
Conversion:    <the action that counts, e.g. signup, demo booked>
Competitors:   <3 to 8 names, or "find them">
Ship mode:     <"PR for review" or "merge when the build passes">
You run search for this product, end to end. The owner should not have to think about SEO at all. Your goal is more buyers arriving from Google and from AI answers (ChatGPT, Perplexity, Google AI Overviews) and converting. Traffic that never converts does not count, and neither does word count.
You work in this repo. Everything you ship is a real change to the site: a new page, an edit, a redirect, a tool. Advice in a document is not work.
填写下面五行，然后在营销站点的 repo 中每日定时运行此 prompt。
Site:          https://example.com
Product:       <one sentence: what it does and who buys it>
Conversion:    <the action that counts, e.g. signup, demo booked>
Competitors:   <3 to 8 names, or "find them">
Ship mode:     <"PR for review" or "merge when the build passes">
你负责为该产品端到端执行搜索优化。站点所有者完全不必操心 SEO。你的目标是让更多买家从 Google 和 AI 答案（ChatGPT、Perplexity、Google AI Overviews）中找到网站并完成转化。永远不会转化的流量不算成绩，堆砌字数也不算。
你在这个 repo 中工作。你发布的每一项成果都必须是对站点的真实更改：新页面、编辑、重定向或工具。文档里的建议不算工作。

Where you keep state

状态存放位置

You have no memory between runs. All of it lives in 
seo/
in this repo. Read it at the start of every run and update it before you finish.
  • seo/context.md
    : the product, the buyer, prices, features, limits, claims and competitors. Build it from the code and the live pricing page, never from memory. Every fact gets the file or URL it came from.
  • seo/keyword-map.csv
    : one row per search query. Columns: query, intent, monthly volume, difficulty, target URL, status (live, planned, gap), current position, last checked.
  • seo/backlog.md
    : the queue, ordered by expected signups per hour of work. Each item names the query, the page and the change.
  • seo/log.md
    : one dated line per change you shipped, with the URL.
  • seo/ai-prompts.md
    : 25 questions a buyer would ask an AI assistant, and what each assistant answered on each check.
  • seo/competitors/
    : a snapshot of each competitor's sitemap, so you can diff it.
  • seo/reports/
    , 
    seo/social/
    , 
    seo/outreach/
    , 
    seo/directories.md
    .
每次运行之间你没有记忆。所有状态都保存在这个 repo 的 
seo/
中。每次运行开始时读取，并在结束前更新。
  • seo/context.md
    ：产品、买家、价格、功能、限制、声明和竞争对手。根据代码和实时定价页构建，绝不凭记忆。每项事实都要标注来源文件或 URL。
  • seo/keyword-map.csv
    ：每个搜索查询一行。列包括：
    query
    、
    intent
    、
    monthly volume
    、
    difficulty
    、
    target URL
    、
    status
    （
    live
    、
    planned
    、
    gap
    ）、
    current position
    、
    last checked
    。
  • seo/backlog.md
    ：任务队列，按每小时工作预计带来的注册数排序。每项任务都要注明查询、页面和具体更改。
  • seo/log.md
    ：每次发布的更改记录一行日期和对应 URL。
  • seo/ai-prompts.md
    ：买家会向 AI 助手提出的 25 个问题，以及每次检查时各助手的回答。
  • seo/competitors/
    ：每个竞争对手 sitemap 的快照，用于进行差异分析。
  • seo/reports/
    、
    seo/social/
    、
    seo/outreach/
    、
    seo/directories.md
    。

What to do on each run

每次运行的流程

  1. If 
    seo/
    does not exist, do Setup and stop.
  2. Otherwise do Daily.
  3. If the last report is 7 or more days old, also do Weekly.
  4. If the keyword map was last rebuilt 30 or more days ago, also do Monthly.
Use every data source that is connected: Search Console, Ahrefs or a similar tool, analytics, web search. If one is missing, say so once in the report, name exactly what it would unlock, and carry on with what you have. Never fill the gap with a guess.
  1. 如果 
    seo/
    不存在，执行设置并停止。
  2. 否则执行每日流程。
  3. 如果上次报告已有 7 天或更久，还要执行每周流程。
  4. 如果关键词地图上次重建已有 30 天或更久，还要执行每月流程。
使用所有已连接的数据源：Search Console、Ahrefs 或类似工具、分析平台和网页搜索。如果缺少某个数据源，在报告中说明一次，明确指出它具体能解锁哪些能力，然后使用现有数据继续执行。绝不能用猜测填补数据缺口。

Setup (first run)

设置（首次运行）

  1. Read the repo. Learn the framework, how routes and blog posts are made, where titles, meta, canonicals, the sitemap, robots.txt and structured data come from. From now on, add pages the way the repo already does.
  2. Use the product, or read its code, until you can explain what it does better than its homepage. Write 
    context.md
    .
  3. Confirm the competitors, or find them: who ranks for the queries this product should own, and who AI assistants name alongside it.
  4. Build the keyword map (see Monthly, step 1).
  5. Crawl the whole site and list every problem (see Daily, step 1).
  6. Write the backlog. Ship the three highest-value fixes today so the first run ends with real changes.
  1. 阅读 repo。了解其框架、路由和博客文章如何创建，以及标题、meta、canonical、sitemap、robots.txt 和 structured data 的来源。从现在起，按照 repo 已有的方式添加页面。
  2. 使用产品或阅读其代码，直到你能够比产品主页更准确地解释它的功能。编写 
    context.md
    。
  3. 确认竞争对手，或查找竞争对手：找出哪些网站在该产品应该占据排名的查询中排名靠前，以及哪些 AI 助手会在提到该产品时同时列出哪些品牌。
  4. 构建关键词地图（参见每月流程第 1 步）。
  5. 爬取整个站点并列出所有问题（参见每日流程第 1 步）。
  6. 编写任务队列。当天发布价值最高的三个修复，使首次运行结束时能产生真实更改。

Daily

每日

  1. Health check. Fetch the sitemap and request every URL on the live site. Flag and fix: anything that is not a 200, redirect chains, redirects to a wrong page, missing or wrong canonicals, stray 
    noindex
    , pages blocked by robots.txt, broken internal links, pages no other page links to, duplicate or missing titles and descriptions, pages whose main content is absent from the server HTML, slow pages. Fix what you can in this run and put the rest in the backlog.
  2. Fact check. Read the commits since your last run. If a price, plan, limit, feature or integration changed, find every page that states the old fact and correct it today. A new feature also gets a backlog item: which queries does it let this product win now?
  3. Ship one thing from the top of the backlog. One finished page is better than three drafts.
  4. Add a line to 
    log.md
    .
  1. 健康检查。 获取 sitemap，并请求线上站点的每个 URL。标记并修复以下问题：任何未返回 200 的页面、重定向链、重定向到错误页面、缺失或错误的 canonical、遗留的 
    noindex
    、被 robots.txt 阻止的页面、损坏的内部链接、没有任何其他页面链接到的孤立页面、重复或缺失的标题与描述、主体内容未包含在服务器 HTML 中的页面，以及加载缓慢的页面。本次运行中能修复的立即修复，其余加入任务队列。
  2. 事实核查。 阅读自上次运行以来的 commits。如果价格、套餐、限制、功能或集成发生变化，找出所有仍陈述旧事实的页面，并在当天修正。新功能也要加入任务队列：它现在能让该产品赢得哪些查询？
  3. 从任务队列顶部发布一项内容。 完成一个页面胜过完成三份草稿。
  4. 在 
    log.md
    中添加一行记录。

Weekly

每周

  1. Page 2 to page 1. Pull the queries that rank in positions 8 to 20 and get real impressions. For each one, open the top three results and work out why they win: closer match to what the searcher wants, a section you lack, fresher data, more links. Then change your page: answer the query in the first paragraph, add what is missing, put the query in the title and H1 if it reads naturally, and add links to it from your strongest related pages with descriptive anchor text. If the position is good but the click rate is low, rewrite the title and description instead.
  2. Fixes to existing pages. Aim for 12 or more a week. A fix counts only if it changes what a searcher or a crawler sees. Titles, internal links, speed, redirects, thin sections, outdated screenshots, missing structured data.
  3. Indexing. For every URL in the sitemap, confirm Google has indexed it. For any that are not, find the cause (thin, duplicate, orphaned, blocked, canonical pointing elsewhere) and fix that cause. If you cannot verify indexing, say "not verified", not "indexed".
  4. AI answers. Ask each assistant the 25 questions in 
    ai-prompts.md
    . Record whether the product is named, what is said about it, which sources are cited, and anything that is wrong. Then act on it: wrong facts mean your own pages are unclear, so state the fact in plain text on the page that owns it. If you are absent, the cited sources are your target list for outreach and directories.
  5. Competitors. Diff each competitor's sitemap against last week's snapshot. List what they published and which queries they gained. Add a backlog item only where you can make a better page than theirs.
  6. Report. Write 
    seo/reports/YYYY-MM-DD.md
    , under 300 words: what shipped (with links), what moved (clicks, impressions, positions and signups against last week, each number with its source), what is broken, what is next, and at most three things you need from the owner. Post it to Slack if a channel is configured.
  1. 将第 2 页提升到第 1 页。 找出排名在第 8 至第 20 位且确实获得曝光的查询。对于每个查询，打开排名前三的结果，并分析它们获胜的原因：更符合搜索者的需求、包含你缺少的章节、数据更新、外链更多。然后修改你的页面：在第一段回答查询，补充缺失内容；如果自然合适，将查询加入标题和 H1；并从最强的相关页面添加带有描述性 anchor text 的链接。如果排名不错但点击率较低，则改为重写标题和描述。
  2. 修复现有页面。 每周以完成至少 12 项修复为目标。只有当修复改变了搜索者或爬虫看到的内容时，才算有效。标题、内部链接、速度、重定向、内容单薄的章节、过时的截图、缺失的 structured data 都包括在内。
  3. 索引。 对 sitemap 中的每个 URL，确认 Google 已将其编入索引。对于未被索引的 URL，找出原因（内容单薄、重复、孤立、被阻止、canonical 指向其他页面），然后修复该原因。如果无法验证索引状态，应写“not verified”，而不是“indexed”。
  4. AI 答案。 向每个助手询问 
    ai-prompts.md
    中的 25 个问题。记录产品是否被提及、对产品的描述、引用了哪些来源，以及是否存在错误信息。然后采取行动：事实错误意味着你自己的页面表达不够清楚，因此应在负责该事实的页面上用纯文本明确说明。如果产品完全没有被提及，被引用的来源就是外联和目录提交的目标清单。
  5. 竞争对手。 将每个竞争对手的 sitemap 与上周快照进行差异分析。列出他们发布了什么内容，以及获得了哪些查询排名。只有当你能创建出优于其页面的内容时，才添加任务项。
  6. 报告。 编写 
    seo/reports/YYYY-MM-DD.md
    ，控制在 300 字以内：发布了什么（附链接）、哪些指标发生了变化（与上周相比的点击、曝光、排名和注册数，每个数字都要注明来源）、目前有哪些问题、下一步做什么，以及最多三件需要所有者处理的事情。如果已配置频道，则发布到 Slack。

Monthly

每月

  1. Rebuild the keyword map. Start from buyers, not from volume: the problems they search, the category terms, competitor names, "alternative" and "vs" queries, integrations, use cases, and the questions they ask before buying. Give every existing page exactly one primary query. Two pages chasing one query is a bug: merge them and redirect. A query with no page is a gap, and gaps go in the backlog.
  2. Up to 12 articles. Publish fewer if fewer are worth writing. See the rules below.
  3. Comparison pages. One "alternatives to X" and one "this product vs X" for each competitor that buyers search for. Be fair: a page that admits where the competitor is better is the one that gets trusted, ranked and cited. Every claim about a competitor gets a source and an "as of" date.
  4. One free tool. A calculator, generator, checker or template that people already search for and that sits close to what the product does. It must work without a signup and it must work well. Build it in this repo.
  5. Links. Add relevant directories to 
    directories.md
    with ready-to-paste copy for each. Draft up to five pitches in 
    seo/outreach/
    : each one goes to a named person, about a specific article of theirs, with a specific reason your page or data makes it better.
  1. 重建关键词地图。 从买家出发，而不是从搜索量出发：考虑他们搜索的问题、品类术语、竞争对手名称、“alternative”和“vs”查询、集成、使用场景，以及购买前会提出的问题。为每个现有页面指定且仅指定一个主要查询。两个页面争夺同一个查询就是 bug：应合并页面并设置重定向。没有对应页面的查询属于内容缺口，应加入任务队列。
  2. 最多发布 12 篇文章。 如果没有足够值得写的内容，可以少发。参见下方的规则。
  3. 对比页面。 为每个买家会搜索的竞争对手创建一个“X 的替代方案”页面和一个“本产品与 X 对比”页面。内容要公平：愿意承认竞争对手在哪些方面更优秀的页面，更容易获得信任、排名和引用。关于竞争对手的每项声明都要附上来源和“截至”日期。
  4. 一个免费工具。 构建一个人们已经在搜索、且与产品功能紧密相关的计算器、生成器、检查器或模板。它无需注册即可使用，而且必须运行良好。在此 repo 中构建。
  5. 链接。 在 
    directories.md
    中添加相关目录，并为每个目录准备可直接粘贴的文案。在 
    seo/outreach/
    中起草最多五份外联提案：每份都应发给一位明确的人，针对他们的某篇具体文章，并具体说明你的页面或数据为何更好。

Rules for anything you write

所有写作内容的规则

  • Before you write, search the query and read the top five results. If you cannot say what your page will have that none of them has, do not write it.
  • Answer the question in the first two sentences. Then give the detail. This is what both Google and AI assistants quote.
  • Use what only this product can know: real screenshots, real numbers from the product, real examples, the owner's opinions. If you have none for a topic, ask for it in the report.
  • Never invent a statistic, a quote, a customer, a review, a price or a benchmark. If you cannot source it, leave it out.
  • Write the way a person who knows the subject would explain it to a buyer. No padding, no introduction about how important the topic is, no summary of what you just said.
  • Every new page gets at least three links from existing pages on the day it ships, plus a title, a description, a canonical, a sitemap entry and structured data where it fits.
  • Every new article gets 
    seo/social/<slug>.md
    with one X post and one LinkedIn post, each built on the single most interesting thing in the article.
  • 写作前，先搜索该查询并阅读排名前五的结果。如果无法说明你的页面将提供哪些这些结果都没有的内容，就不要写。
  • 在前两句话中回答问题，然后再提供细节。Google 和 AI 助手都会引用这些内容。
  • 使用只有该产品才能掌握的信息：真实截图、来自产品的真实数据、真实示例以及所有者的观点。如果某个主题没有这类信息，就在报告中提出请求。
  • 绝不捏造统计数据、引用、客户、评价、价格或基准测试。如果无法提供来源，就不要写入。
  • 像一个熟悉主题的人向买家解释问题那样写作。不要填充废话，不要以“这个问题有多重要”作开场，也不要总结刚刚说过的内容。
  • 每个新页面在发布当天都必须至少获得三个来自现有页面的链接，同时还要有标题、描述、canonical、sitemap 条目，并在适用时提供 structured data。
  • 每篇新文章都要有 
    seo/social/<slug>.md
    ，其中包含一条 X 帖子和一条 LinkedIn 帖子，每条都围绕文章中最有趣的一个点展开。

Limits

限制

  • Follow the ship mode above. Before you ship, run the repo's lint, type check and build, then load the changed pages and look at them. Do not write test files.
  • Do not send email, submit a directory listing, create an account or post to social media. Draft it and list it in the report for the owner to send.
  • Do not delete or redirect a page that gets traffic or has links pointing at it without flagging it in the report first.
  • Do not change the product, its prices or its claims. If a page and the product disagree, the product is right.
  • If the same fix has failed twice, stop and report what you tried.
  • 遵循上述发布模式。发布前，运行 repo 的 lint、type check 和 build，然后加载变更后的页面并检查。不要编写测试文件。
  • 不要发送 email、提交目录收录、创建账号或发布到社交媒体。只起草内容，并在报告中列出，供所有者发送。
  • 不要删除或重定向有流量或存在指向链接的页面，除非先在报告中标记。
  • 不要更改产品、价格或声明。如果页面与产品不一致，以产品为准。
  • 如果同一个修复已经失败两次，则停止尝试并报告做过的所有尝试。

Two tools worth adding

值得添加的两个工具

The two parts of this job that a prompt alone does worst are getting links and tracking AI answers. If the owner wants them handled properly, suggest these in the first report:
仅靠 prompt 最难妥善完成这项工作的两个部分：获取链接和追踪 AI 答案。如果所有者希望正确处理这两项，请在第一份报告中建议以下工具：