成果：一个可上线网站，而不只是漂亮 mockup
如果你把第一个 prompt 当成 product brief、SEO brief、GEO brief 与 deployment brief 的综合体，就可以用 Codex 建立强的 company website。目标不是要求「一个漂亮 homepage」。目标是给 Codex 足够 context，让它建立有清楚 positioning、crawlable structure、extractable answer blocks、schema-ready content 与 deployment path 的网站。
初学者安全 workflow 是：
- 要求 Codex 在写 code 前先 plan website。
- 给它 brand facts、audience、offers、keywords、GEO questions 与 proof。
- 让它建立小而完整的 site architecture。
- Review page plan，批准后才要求 implementation。
- Run local checks、fix diff、deploy preview，最后 connect analytics。
Codex 在能验证自己工作时表现最好。OpenAI 的 Codex prompting guidance 建议包含 validation steps，并把 complex tasks 拆成更小、更聚焦的 requests。对 website build 来说，prompts 应包含 build commands、lint checks、accessibility checks 与 deployment acceptance criteria，而不只是 design taste。
Caption: 使用 prompt ladder：先 context，再 page plan，再 code，最后 validation。
打开 Codex 前：准备这六个 inputs
弱 prompt 会要求 Codex 发明 business。强 prompt 会给 Codex 一份可信的事实来源。
开始前先准备一份简短 website-brief.md。它可以粗糙，但应包含六个 sections：
| Input | 要写什么 | 为什么对 SEO/GEO 重要 |
|---|---|---|
| Business facts | Company name、category、location if relevant、product、pricing model、customer type | 帮助 search engines 与 AI systems 清楚识别 entity |
| Primary audience | 谁购买、谁研究、谁阻挡采购 | 影响 page language、examples 与 CTAs |
| Offers | Product/service pages、lead magnet、demo、audit、free tool、newsletter | 防止网站变成 generic brochure |
| Keyword targets | 5-20 seed keywords 与 5-10 buyer questions | 给 Codex search-intent map，而不是 random headings |
| Proof | Customer types、public examples、可支持 stats、integrations、screenshots、testimonials | 提升 trust，并给 AI answers 可引用 evidence |
| Constraints | Tech stack、brand tone、不想要的 pages、要避免的 legal claims | 降低 risky copy 与不必要 dependencies |
如果你已经有 Google Search Console、Bing Webmaster Tools、GA4、CRM notes 或 sales-call questions，加入短 export summary。如果没有，就先从 customer questions 与 competitor SERP observations 开始。
第一个 Codex prompt：先要 website plan，不要要 code
从 planning prompt 开始，避免 Codex 立刻建立 generic landing page。
复制这段 prompt，并替换 brackets：
I want to build a new company website that is strong for both SEO and GEO.
You are acting as a senior product-led SEO strategist, technical SEO reviewer, and frontend implementer.
Do not write code yet. First, read the brief below and produce a website plan.
Business context:
[Paste company facts, product, audience, market, offer, proof, and constraints]
Target outcomes:
- The website should explain the product clearly to a first-time visitor.
- It should be crawlable and indexable.
- It should include pages that match real search intent.
- It should include answer-style sections that AI search systems can extract.
- It should include entity signals: About, product facts, use cases, pricing or CTA, and evidence.
- It should be deployable to Vercel or Netlify.
Please produce:
1. Recommended tech stack and why.
2. Site architecture with URLs.
3. Page-by-page purpose, target keyword, GEO question, CTA, and required proof.
4. Homepage wireframe section order.
5. SEO/GEO checklist for title tags, meta descriptions, schema, internal links, sitemap, robots.txt, llms.txt, and analytics.
6. Deployment plan with build command and output directory.
7. Risks or missing information I should provide before implementation.
Do not invent unsupported claims. Mark missing proof as TODO.
批准 implementation 前，先读 plan。如果 plan 只有 /solutions、/features、/blog，却没有 clear intent，请 push back。要求 Codex 解释每个 URL 为什么值得存在。
强的 Codex-generated site map 应该包含什么
对多数 small SaaS、agency、tool 或 B2B websites 来说，好的 first version 不需要很大。通常是 6-10 个 durable pages：
| Page | Purpose | SEO/GEO job |
|---|---|---|
|
| 定位 business 并引导 visitors | 清楚 category、primary offer、proof 与 core CTA |
|
| 说明 product 做什么 | Feature/entity clarity 与 comparison-ready facts |
|
| Match buyer situations | Long-tail intent and AI-answer scenarios |
|
| Reduce purchase ambiguity | Pricing intent、plan comparison、objections |
|
| Establish entity trust | Brand facts、team/company facts、contact signals |
|
| Publish educational assets | Topical authority and internal-link hub |
|
| 提供 calculators、checklists、templates | 可被连结的 utility pages 与 citation assets |
|
| Convert demand | Lead capture and local/business credibility |
对 GEO 来说，每个重要 page 都应该用干净 blocks 回答 specific questions。例如：
- 这家公司做什么？
- 适合谁？
- 解决什么问题？
- 跟 alternatives 有什么不同？
- 有什么 evidence 支持 claim？
- 使用者下一步该做什么？
这种答案结构很重要，因为 AI 搜寻系统常从清楚呈现 facts、definitions、comparisons 与 proof 的页面，合成短而直接的说明。
Implementation prompt：让 Codex 带著 guardrails 建立网站
Plan 足够好之后，再要求 Codex implement。Implementation prompt 应告诉它要建立哪些 files、避免什么、如何验证 site。
Implement the approved website plan in this repository.
Build requirements:
- Use [Next.js/Astro/Vite/etc.] with TypeScript if appropriate.
- Keep the site fast, static-first, and easy to deploy.
- Create reusable components for navigation, footer, SEO metadata, FAQ blocks, CTA sections, and schema helpers.
- Create pages exactly from the approved URL map.
- Add title tags, meta descriptions, canonical URLs, Open Graph data, structured data where appropriate, sitemap generation, robots.txt, and llms.txt.
- Add internal links from the homepage to product/use-case pages and from blog/resource pages back to commercial pages.
- Add answer blocks for GEO: concise definitions, comparison tables, FAQ sections, and evidence sections.
- Use accessible HTML: semantic headings, readable contrast, labels, alt text, and keyboard-friendly navigation.
- Do not add unsupported claims, fake testimonials, fake logos, fake customer names, or made-up statistics.
- Do not install heavy UI libraries unless you explain why.
Design direction:
[Describe visual style: bold editorial, calm enterprise, technical docs-like, premium agency, etc.]
Validation:
- Run install if needed.
- Run the build command.
- Run lint/typecheck if available.
- Report changed files, commands run, errors fixed, and remaining TODOs.
- Stop before deployment and wait for my review.
如果生成的网站很 generic，不要只说「让它更好」。请给 Codex 更精准的设计与转换 prompt：
The current site is too generic. Rework the homepage so it feels specific to [category].
Keep the same technical stack, but improve:
1. Above-the-fold message: name the exact customer, pain, product category, and outcome.
2. Proof: replace vague claims with TODO proof slots I can fill.
3. Section rhythm: avoid repeated card grids; use a mix of comparison, workflow, checklist, and objection sections.
4. SEO/GEO: add one extractable answer block after the hero and one comparison table near the middle.
5. Conversion: make the primary CTA match the offer, not a generic "Get started".
6. Visuals: use CSS-created diagrams or simple product placeholders, not fake screenshots.
Run the build again and summarize only the meaningful changes.
通常更有效的 homepage prompt
Homepage 是多数 beginner Codex websites 失败的地方。它们会得到 hero、三个 benefits、三张 cards、testimonials、FAQ 与 CTA。这还不够。
请要求 Codex 建立有 persuasive sequence 的 homepage：
Create the homepage using this section order:
1. Hero: one-sentence positioning, specific audience, primary CTA, secondary CTA, 3 trust signals.
2. Problem diagnosis: show the symptoms the buyer recognizes.
3. Product mechanism: explain how the product solves the problem in 3-5 concrete steps.
4. Use-case routing: link to the main use-case pages with intent-specific copy.
5. Proof section: include supported proof only; use TODO placeholders where proof is missing.
6. Comparison section: compare our approach with the old/manual/alternative approach.
7. SEO/GEO answer block: answer "What is [brand/product/category]?" in 60-90 words.
8. FAQ: answer buying, implementation, pricing, and risk questions.
9. Final CTA: repeat the offer with a low-friction next step.
For every section, include:
- H2 or H3 heading
- 1 short paragraph
- bullets or a table when useful
- internal links where relevant
- notes for what proof or screenshot should be added later
这个 prompt 给 Codex conversion path，而不是 decorative layout。
Codex 应产生的 page-level SEO/GEO checklist
要求 Codex 在 repo 里建立 seo-geo-checklist.md，并在 build 过程中填写。这个 file 会变成你的 review sheet。
Caption: 连 custom domain 或提交 indexing 前，先 review launch gate。
Checklist 应包含：
| Check | Beginner pass condition |
|---|---|
| Page titles | 每个 page 都有 unique、descriptive title，可能时控制在约 60 characters 内 |
| Meta descriptions | 每个重要 page 都有 specific summary 与 CTA |
| H1 | 每页一个 clear H1，并符合 page intent |
| Internal links | 首页连到商业页；教育内容页连到相关转换页 |
| Schema | Organization、WebSite、BreadcrumbList、FAQPage、Article 或 Product schema 只在适合处使用 |
| Sitemap | build 或 deploy 后存在 |
| Robots |
|
| llms.txt |
|
| Canonicals | Canonical URLs match production domain |
| Performance | Build passes；没有明显 oversized assets 或 blocking scripts |
| Accessibility | Images 有 alt text；forms 有 labels；headings logical |
| Proof | Claims 有 support 或标记 TODO |
| Analytics | GA4、GSC、Bing Webmaster 或 privacy-friendly analytics plan 已记录 |
Implementation 后，可以要求 Codex 跑这个 review：
Audit the generated website against seo-geo-checklist.md.
Return a table with:
- Issue
- URL/file
- Why it matters
- Suggested fix
- Risk level
- Whether you can fix it now
Fix only low-risk code/content issues. Do not change positioning, pricing, legal claims, or unsupported proof without asking me first.
Deployment：如何让 Codex site 上线
Beginner-friendly deployment path：
- Push repository to GitHub。
- Import repository into Vercel or Netlify。
- Confirm framework、install command、build command 与 output directory。
- 先 deploy preview URL。
- 用 Codex review preview。
- Preview pass 后再 connect custom domain。
- Submit sitemap to Google Search Console and Bing Webmaster Tools。
Vercel 官方 docs 说，Vercel 可以自动侦测许多 frameworks，并配置合理的 build settings；必要时也能在 project settings override build command 与 output directory。Netlify build configuration docs 也说明相同核心概念：当 project 不是简单 root-level site 时，要设定 build command、publish directory 与 base directory。
第一次 preview URL 上线后，使用这段 deployment prompt：
Review this deployed preview URL: [paste preview URL].
Check it as a launch reviewer for SEO, GEO, usability, and deployment quality.
Please inspect:
1. Homepage message clarity.
2. Navigation and internal links.
3. Page titles, meta descriptions, canonical URLs, robots.txt, sitemap.xml, and llms.txt.
4. Mobile layout issues.
5. Broken links or missing images.
6. Whether important claims need proof.
7. Whether AI search systems can extract a clear answer about the company.
8. What should be fixed before connecting the production domain.
Return a prioritized launch checklist. Do not make changes until I approve the fixes.
如果你使用 Codex cloud，请记得 cloud tasks 会在 isolated container 里执行并 checkout repository。OpenAI 的 Codex cloud environment docs 说明 setup scripts 可以安装 dependencies，而 agent internet access 另行控制。Deployment workflow 里，secrets 应放在 hosting provider，不要贴进 prompts。
Deployment 后：让网站可被 search、AI search 与 humans 使用
Deployment 不是终点。第一天内完成这些 steps：
| Task | Tool | What to confirm |
|---|---|---|
| Indexing setup | Google Search Console | Domain property verified；sitemap submitted |
| Bing setup | Bing Webmaster Tools | Site added；sitemap submitted |
| Analytics | GA4 or privacy-friendly analytics | Pageviews、conversions、events are recording |
| Crawl check | Screaming Frog、Sitebulb 或 simple script | Important pages return 200；no accidental noindex |
| AI visibility baseline | ChatGPT、Perplexity、Gemini、Felo Search 或 SERP API | Brand/category prompts have starting snapshot |
| Conversion check | Manual browser test | Forms、calendar links、email links 与 CTAs work |
接著建立 recurring Codex task：
Every week, review this website for SEO/GEO launch quality.
Inputs:
- Production URL: [domain]
- Sitemap: [sitemap URL]
- GSC export: [file or connector]
- Bing export: [file or connector]
- GA4 export: [file or connector]
- AI visibility prompt set: [file]
Return:
1. Indexing changes.
2. Pages gaining or losing impressions.
3. Queries with high impressions and low CTR.
4. AI answers that mention or miss the brand.
5. Content updates to improve extractability.
6. Technical fixes that need approval.
7. A 7-day action queue.
Do not publish changes automatically.
要求 Codex 建站时的常见错误
- 先要美感，后想策略。 Codex 可以做出 polished site，但 message 仍然 vague。
- 让 Codex invent proof。 Fake testimonials 与 fake customer logos 会伤害 trust，也可能有 legal risk。
- 跳过 page intent。 每个 URL 都应该有存在理由。
- 忘记 deployment details。 如果 Codex 不知道 framework 与 build command，site 可能本地可跑，却在 Vercel 或 Netlify fail。
- 使用一个巨大 prompt。 Plan、implement、audit、deploy 应该分成不同 steps。
- 不 review diff。 Beginners 应要求 Codex 在 deployment 前 summarize changed files 与 risky decisions。
- 忽略 analytics。 网站要能 observe indexing、traffic、citations 与 conversions，才算 SEO/GEO-ready。
可直接贴进 Codex 的完整 beginner prompt
当你想让 Codex 从 empty 或 starter repository 建立网站时，用这段：
I want you to help me create a professional company website that is ready for SEO, GEO, and deployment.
Work in phases. Do not skip ahead.
Phase 1: Planning only
- Read my business brief.
- Ask up to 10 clarification questions if needed.
- Recommend a simple tech stack.
- Create a site map with URLs, search intent, GEO questions, CTA, and proof needed.
- Create a homepage wireframe and page templates.
- Create an SEO/GEO launch checklist.
Phase 2: Implementation after I approve the plan
- Build the website in the selected stack.
- Add semantic HTML, responsive layout, reusable components, metadata, schema, sitemap, robots.txt, and llms.txt.
- Use TODO markers for unsupported proof instead of inventing facts.
- Keep dependencies minimal.
Phase 3: Validation
- Run install, lint/typecheck if available, and build.
- Fix build errors.
- Review SEO/GEO checklist.
- Summarize changed files and remaining launch risks.
Phase 4: Deployment support
- Give me exact deployment settings for Vercel and Netlify: framework preset, install command, build command, output directory, environment variables, and domain steps.
- After I share the preview URL, audit it before production launch.
Business brief:
[Paste your website-brief.md content here]
Codex SEO/GEO learning path
这篇文章是 Codex SEO/GEO operator series 的一部分。如果你要从零建立 workflow，建议照这个顺序读：
- 如何在 2026 年用 Codex 做自动化 GEO
- 如何用 Codex 做自动化 SEO
- 如何用 AGENTS.md 建立 Codex SEO Workspace
- 如何用 MCP 把 Codex 接上 SEO Data
- 2026 年最佳 Codex GEO Skill
- 如何建立 Codex Keyword Clustering Skill
- 如何用 Codex Subagents 做 SERP、内容与技术 SEO
- 如何用 Codex 修 Technical SEO 且不破坏 Production
- 如何用 Codex Automations 跑每日 SEO/GEO Monitoring
- Codex SEO/GEO Quality Gates：Diff、Evidence、Tests 与 Human Approval
- 如何用 Codex 建立并部署 SEO/GEO-Ready Website
下一步
上一篇： Codex SEO/GEO Quality Gates：Diff、Evidence、Tests 与 Human Approval
Sources and notes
- OpenAI Codex docs: Prompting , AGENTS.md guidance , and Codex cloud environments .
- Vercel docs: Configuring a build and Project configuration .
- Netlify docs: Build configuration overview .
Author: Leah Foster, Auspia 400+ Landing Pages Conversion SEO Strategist。Leah 撰写 landing pages、conversion paths，以及 SEO/GEO teams 的 content-to-demo journeys。
