# SEO-Copy Freeze Package — AI Coding Pricing / Cost Hub

Date: 2026-05-21
Domain: aicodingpricing.com
Tenant: site-aicodingpricing-20260521
Status: SEO copy frozen for P0 canonical indexable routes before design.

## Freeze decision

- seo_copy_frozen: true
- Freeze scope: P0 canonical indexable routes required before design are final for H1/H2/H3 outline, above-fold copy, FAQ, schema copy, target word count, CTA, disclaimers, semantic coverage, and design placement priority.
- Expansion/P1 pages are included as route-ready copy drafts or copy requirements, but should not be indexed until source rows and maintenance workflow are populated.
- Redirect aliases are not indexable and must be 301/no-sitemap.
- Design must not remove SEO body copy; it may place long content lower-page or in crawlable accordions.

## Global hard copy rules

- No provider logos, mascots, official screenshots, or official-looking visual treatment.
- No official/partner/certified/approved/endorsed language.
- No guaranteed/latest/exact/100% accurate/unlimited claims.
- Every pricing or limits row needs source_url, last_checked, confidence, and caveat.
- Calculator copy must say results are estimates, not billing quotes.
- Newsletter copy must be pricing/limits-alert specific, not generic updates.
- FAQ can be collapsible only if crawlable/server-rendered.
- Disclaimers must be visible near the relevant page module, not hidden only in footer.

## P0 page copy freeze

### /
- Page type: hub_tool
- Primary keyword: AI coding cost calculator
- Semantic keywords: AI coding cost calculator, Claude Code pricing, Codex pricing, Cursor pricing, GitHub Copilot pricing, AI coding usage limits, subscription vs API, pricing changelog, source-linked pricing, last checked, developer workflow cost
- SEO title: AI Coding Cost Calculator: Compare Claude Code, Codex, Cursor & Copilot
- SEO description: Compare AI coding tool costs, usage limits, and upgrade paths across Claude Code, OpenAI Codex, Cursor, and GitHub Copilot before you pay.
- H1: Compare AI coding tool costs before you upgrade
- Word count target: 900-1200
- Above-fold answer: AI Coding Pricing helps developers estimate the real monthly cost of Claude Code, OpenAI Codex, Cursor, and GitHub Copilot before choosing a plan. Enter your workflow, team size, and usage pattern to compare subscription, API, and limit-risk tradeoffs with source-linked pricing assumptions and visible update dates.
- Hero headline: Compare AI coding tool costs before you upgrade
- Hero subhead: Estimate real monthly cost across Claude Code, Codex, Cursor, and Copilot using current pricing, usage limits, and workflow scenarios.
- CTA primary: Estimate my AI coding cost
- CTA secondary: Get pricing change alerts
- Trust microcopy: Free calculator. No login. No provider account connection.
- Disclaimer: Independent comparison and calculator site. Brand names identify products being compared and do not imply affiliation, sponsorship, or endorsement.
- H2/H3 outline and section copy:
  - H2: How the calculator works | H3: Choose your workflow; Compare plans; Check limit risk | Placement: above_fold | Priority: high
    Copy: Choose your tool, plan, coding hours, sessions, team size, and API/subscription mode. The result should show monthly cost, likely plan fit, limit-risk level, and caveats.
  - H2: Compare the main AI coding tools | H3: Claude Code; OpenAI Codex; Cursor; GitHub Copilot | Placement: near_top | Priority: high
    Copy: Show neutral text cards for Claude Code, Codex, Cursor, and GitHub Copilot with current plan ranges, workflow fit, and source status. No provider logos.
  - H2: Latest pricing and limit changes | H3: Recent changes; Source confidence | Placement: near_top | Priority: high
    Copy: Display 3-5 dated changelog entries with provider, changed field, source URL, confidence, and checked date. If there are no seed entries, keep this module noindex or publish only after entries exist.
  - H2: Which cost model fits your workflow? | H3: Subscription fit; API fit; Team fit | Placement: lower_page | Priority: normal
    Copy: Explain subscriptions, usage pools, API billing, cloud tasks, local CLI usage, and team seats in plain language. Keep this SEO body below the tool, not removed.
- Table/module copy:
  - Module: Quick comparison cards
  - Columns: Tool, Best-fit workflow, Pricing model, Limit risk, Source status, CTA
  - Rule: Use provider names as plain text only.
  - Rule: Do not state a price unless source_url, last_checked, and confidence are present.
  - Rule: Link each row to its detailed pricing or usage page.
- FAQ:
  - Q: What is the cheapest AI coding tool for my workflow?
    A: It depends on your usage pattern. A light solo developer may prefer a lower monthly subscription, while a heavy agent user may need a higher usage pool or API billing. Use the calculator to compare cost and limit risk before choosing.
  - Q: Does the calculator connect to my Claude, OpenAI, Cursor, or GitHub account?
    A: No. P0 is designed to run from public pricing assumptions and your manual inputs. It should not collect provider account tokens, billing credentials, private usage dashboards, or API keys.
  - Q: Why not just check provider pricing pages?
    A: Provider pages are the source for facts, but they usually do not compare cross-tool workflows. This site links back to provider sources and adds scenario-based cost, usage-limit, and upgrade guidance.
  - Q: How fresh is the pricing data?
    A: Each pricing row should show a source link, confidence level, and last-checked date. Pricing and limits can change, so verify the provider source before purchasing.
  - Q: Can teams use this for reimbursement decisions?
    A: Yes, as a planning aid. Team leads can compare seat costs, usage pools, and workflow fit, but calculator results are estimates and not procurement, legal, or billing advice.
  - Q: Will you send alerts when pricing changes?
    A: Yes. The newsletter CTA is specifically for AI coding pricing and usage-limit alerts, not a generic newsletter.
- Schema types: WebApplication, WebSite, FAQPage
- Internal links: /claude-code-pricing, /claude-code-usage-limits, /codex-pricing, /codex-usage, /cursor-pricing, /claude-code-vs-codex, /claude-code-vs-cursor, /pricing-changelog, /about, /contact
- Source links: https://claude.com/pricing, https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work, https://support.claude.com/en/articles/14552983-models-usage-and-limits-in-claude-code, https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan, https://openai.com/api/pricing/, https://openai.com/policies/service-terms, https://cursor.com/pricing, https://cursor.com/changelog, https://cursor.com/terms-of-service, https://github.com/features/copilot/plans, https://docs.github.com/en/billing/concepts/product-billing/github-copilot-premium-requests, https://docs.github.com/en/copilot/concepts/billing/copilot-requests
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /claude-code-pricing
- Page type: pricing_page
- Primary keyword: claude code pricing
- SEO title: Claude Code Pricing: Plans, Limits, Max vs Pro, and Real Cost
- SEO description: See Claude Code pricing, Pro and Max plan differences, usage limits, extra usage options, and when Claude Code may cost more than expected.
- H1: Claude Code pricing, limits, and real cost
- Word count target: 1000-1500
- Above-fold answer: Claude Code pricing depends on the plan, usage capacity, and whether your workflow fits subscription limits or API-style billing. This page should show source-linked plan facts, last-checked dates, and caveats, then help you estimate whether Pro, Max, team, or API usage is the better fit for your coding workload.
- Hero headline: Claude Code pricing, limits, and real cost
- Hero subhead: Use source-linked plan facts, visible last-checked dates, and workflow scenarios before choosing a paid AI coding setup.
- CTA primary: Estimate your monthly cost
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent guide. Source-linked facts. No account connection.
- Disclaimer: Independent guide. We are not affiliated with or endorsed by Anthropic. Prices and limits may change. Each claim below should link to a provider source and show a last-checked date.
- H2/H3 outline and section copy:
  - H2: Answer first: what this page helps you decide | H3: none | Placement: above_fold | Priority: high
    Copy: Claude Code pricing depends on the plan, usage capacity, and whether your workflow fits subscription limits or API-style billing. This page should show source-linked plan facts, last-checked dates, and caveats, then help you estimate whether Pro, Max, team, or API usage is the better fit for your coding workload.
  - H2: Plan and usage table | H3: Plan facts; Usage notes; Source and confidence | Placement: near_top | Priority: high
    Copy: Show plan rows with price_display, billing_period, usage_or_limit_notes, region/tax caveat, source_url, last_checked, confidence, and correction link.
  - H2: Real cost scenarios | H3: Light solo developer; Heavy agent user; Team or reimbursement case; API fallback case | Placement: body | Priority: high
    Copy: Compare light solo developer, heavy agent user, team lead, and API-heavy builder scenarios. State assumptions and link to calculator result.
  - H2: What may change | H3: Last checked policy; Submit a correction | Placement: lower_page | Priority: normal
    Copy: Explain that prices, usage pools, reset windows, model access, taxes, regional availability, and enterprise terms may change. Link to changelog and contact correction route.
- Table/module copy:
  - Module: Source-linked pricing / usage table
  - Columns: Plan or mode, Best fit, Public price or cost basis, Included usage or limit notes, What may change, Source, Last checked, Confidence
  - Rule: Never publish price_display without source_url, last_checked, confidence, and caveat.
  - Rule: Use “may vary” for regional, account-specific, promotional, or enterprise terms.
  - Rule: Use neutral plan labels; no provider logos.
- FAQ:
  - Q: Is this an independent Anthropic pricing guide?
    A: Yes. This is an independent guide and is not affiliated with or endorsed by Anthropic. Brand names are used only to identify the product being discussed.
  - Q: Can I rely on this as my final bill?
    A: No. Calculator and table outputs are estimates based on public assumptions. Your actual bill or account limits may vary by region, plan, taxes, promotions, and provider policy changes.
  - Q: What should I check before upgrading?
    A: Check plan price, included usage or credits, reset behavior, model access, team controls, overage or on-demand terms, source link, and last-checked date.
  - Q: Why do users hit usage limits even on paid plans?
    A: Paid plans can still have capacity, credit, model, or reset-window constraints. Heavy agent sessions, long context, cloud tasks, or advanced models may consume more capacity.
  - Q: Does this page collect my account usage?
    A: No. P0 should not connect to provider accounts or collect tokens, billing credentials, API keys, or private usage dashboards.
  - Q: How do I report outdated pricing?
    A: Use the contact or correction link with a source URL. Updated facts should create or update a changelog entry.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /contact, /about, /claude-code-vs-codex, /claude-code-vs-cursor, /codex-usage, /claude-code-usage-limits
- Source links: https://claude.com/pricing, https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work, https://support.claude.com/en/articles/14552983-models-usage-and-limits-in-claude-code
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /claude-code-usage-limits
- Page type: limits_page
- Primary keyword: claude code usage limits
- SEO title: Claude Code Usage Limits: Pro, Max 5x, Max 20x, and Resets
- SEO description: Understand Claude Code usage limits, how plan capacity works, what affects usage, and when Max or usage credits make sense.
- H1: Claude Code usage limits explained
- Word count target: 1200-1600
- Above-fold answer: Claude Code usage limits are affected by plan capacity, model choice, conversation length, reset behavior, and product-specific rules. This page explains why you may hit limits, what can reduce usage pressure, and when upgrading, changing workflow, or using API billing may be more practical.
- Hero headline: Claude Code usage limits explained
- Hero subhead: Use source-linked plan facts, visible last-checked dates, and workflow scenarios before choosing a paid AI coding setup.
- CTA primary: Check my limit risk
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent guide. Source-linked facts. No account connection.
- Disclaimer: Independent guide. We are not affiliated with or endorsed by Anthropic. Prices and limits may change. Each claim below should link to a provider source and show a last-checked date.
- H2/H3 outline and section copy:
  - H2: Answer first: what this page helps you decide | H3: none | Placement: above_fold | Priority: high
    Copy: Claude Code usage limits are affected by plan capacity, model choice, conversation length, reset behavior, and product-specific rules. This page explains why you may hit limits, what can reduce usage pressure, and when upgrading, changing workflow, or using API billing may be more practical.
  - H2: Plan and usage table | H3: Plan facts; Usage notes; Source and confidence | Placement: near_top | Priority: high
    Copy: Show plan rows with price_display, billing_period, usage_or_limit_notes, region/tax caveat, source_url, last_checked, confidence, and correction link.
  - H2: Real cost scenarios | H3: Light solo developer; Heavy agent user; Team or reimbursement case; API fallback case | Placement: body | Priority: high
    Copy: Compare light solo developer, heavy agent user, team lead, and API-heavy builder scenarios. State assumptions and link to calculator result.
  - H2: What may change | H3: Last checked policy; Submit a correction | Placement: lower_page | Priority: normal
    Copy: Explain that prices, usage pools, reset windows, model access, taxes, regional availability, and enterprise terms may change. Link to changelog and contact correction route.
- Table/module copy:
  - Module: Source-linked pricing / usage table
  - Columns: Plan or mode, Best fit, Public price or cost basis, Included usage or limit notes, What may change, Source, Last checked, Confidence
  - Rule: Never publish price_display without source_url, last_checked, confidence, and caveat.
  - Rule: Use “may vary” for regional, account-specific, promotional, or enterprise terms.
  - Rule: Use neutral plan labels; no provider logos.
- FAQ:
  - Q: Is this an independent Anthropic pricing guide?
    A: Yes. This is an independent guide and is not affiliated with or endorsed by Anthropic. Brand names are used only to identify the product being discussed.
  - Q: Can I rely on this as my final bill?
    A: No. Calculator and table outputs are estimates based on public assumptions. Your actual bill or account limits may vary by region, plan, taxes, promotions, and provider policy changes.
  - Q: What should I check before upgrading?
    A: Check plan price, included usage or credits, reset behavior, model access, team controls, overage or on-demand terms, source link, and last-checked date.
  - Q: Why do users hit usage limits even on paid plans?
    A: Paid plans can still have capacity, credit, model, or reset-window constraints. Heavy agent sessions, long context, cloud tasks, or advanced models may consume more capacity.
  - Q: Does this page collect my account usage?
    A: No. P0 should not connect to provider accounts or collect tokens, billing credentials, API keys, or private usage dashboards.
  - Q: How do I report outdated pricing?
    A: Use the contact or correction link with a source URL. Updated facts should create or update a changelog entry.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /contact, /about, /claude-code-vs-codex, /claude-code-vs-cursor, /codex-usage
- Source links: https://claude.com/pricing, https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work, https://support.claude.com/en/articles/14552983-models-usage-and-limits-in-claude-code
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /codex-pricing
- Page type: pricing_page
- Primary keyword: codex pricing
- SEO title: OpenAI Codex Pricing: ChatGPT Plans, Credits, CLI, and API Cost
- SEO description: See how OpenAI Codex pricing works across ChatGPT plans, CLI usage, cloud tasks, credits, and API-key workflows.
- H1: OpenAI Codex pricing explained
- Word count target: 1000-1500
- Above-fold answer: OpenAI Codex pricing can involve ChatGPT plan access, CLI usage, cloud tasks, credits, and API-key workflows. This page separates public plan access from API billing and account-specific limits so developers can compare subscription fit, usage risk, and fallback options before upgrading.
- Hero headline: OpenAI Codex pricing explained
- Hero subhead: Use source-linked plan facts, visible last-checked dates, and workflow scenarios before choosing a paid AI coding setup.
- CTA primary: Estimate your monthly cost
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent guide. Source-linked facts. No account connection.
- Disclaimer: Independent guide. We are not affiliated with or endorsed by OpenAI. Prices and limits may change. Each claim below should link to a provider source and show a last-checked date.
- H2/H3 outline and section copy:
  - H2: Answer first: what this page helps you decide | H3: none | Placement: above_fold | Priority: high
    Copy: OpenAI Codex pricing can involve ChatGPT plan access, CLI usage, cloud tasks, credits, and API-key workflows. This page separates public plan access from API billing and account-specific limits so developers can compare subscription fit, usage risk, and fallback options before upgrading.
  - H2: Plan and usage table | H3: Plan facts; Usage notes; Source and confidence | Placement: near_top | Priority: high
    Copy: Show plan rows with price_display, billing_period, usage_or_limit_notes, region/tax caveat, source_url, last_checked, confidence, and correction link.
  - H2: Real cost scenarios | H3: Light solo developer; Heavy agent user; Team or reimbursement case; API fallback case | Placement: body | Priority: high
    Copy: Compare light solo developer, heavy agent user, team lead, and API-heavy builder scenarios. State assumptions and link to calculator result.
  - H2: What may change | H3: Last checked policy; Submit a correction | Placement: lower_page | Priority: normal
    Copy: Explain that prices, usage pools, reset windows, model access, taxes, regional availability, and enterprise terms may change. Link to changelog and contact correction route.
- Table/module copy:
  - Module: Source-linked pricing / usage table
  - Columns: Plan or mode, Best fit, Public price or cost basis, Included usage or limit notes, What may change, Source, Last checked, Confidence
  - Rule: Never publish price_display without source_url, last_checked, confidence, and caveat.
  - Rule: Use “may vary” for regional, account-specific, promotional, or enterprise terms.
  - Rule: Use neutral plan labels; no provider logos.
- FAQ:
  - Q: Is this an independent OpenAI pricing guide?
    A: Yes. This is an independent guide and is not affiliated with or endorsed by OpenAI. Brand names are used only to identify the product being discussed.
  - Q: Can I rely on this as my final bill?
    A: No. Calculator and table outputs are estimates based on public assumptions. Your actual bill or account limits may vary by region, plan, taxes, promotions, and provider policy changes.
  - Q: What should I check before upgrading?
    A: Check plan price, included usage or credits, reset behavior, model access, team controls, overage or on-demand terms, source link, and last-checked date.
  - Q: Why do users hit usage limits even on paid plans?
    A: Paid plans can still have capacity, credit, model, or reset-window constraints. Heavy agent sessions, long context, cloud tasks, or advanced models may consume more capacity.
  - Q: Does this page collect my account usage?
    A: No. P0 should not connect to provider accounts or collect tokens, billing credentials, API keys, or private usage dashboards.
  - Q: How do I report outdated pricing?
    A: Use the contact or correction link with a source URL. Updated facts should create or update a changelog entry.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /contact, /about, /claude-code-vs-codex, /claude-code-vs-cursor, /codex-usage, /claude-code-usage-limits
- Source links: https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan, https://openai.com/api/pricing/, https://openai.com/policies/service-terms
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /codex-usage
- Page type: usage_page
- Primary keyword: codex usage
- SEO title: Codex Usage: Local Messages, Cloud Tasks, Credits, and Limits
- SEO description: Understand Codex usage across local CLI messages, cloud tasks, ChatGPT plan limits, credits, and API-token workflows.
- H1: Codex usage explained
- Word count target: 1200-1600
- Above-fold answer: Codex usage can mean different things: local CLI messages, cloud tasks, ChatGPT plan access, credits, or API-token billing. This page explains those modes separately, shows what may count against a plan, and helps developers decide when to use subscription access or API fallback.
- Hero headline: Codex usage explained
- Hero subhead: Use source-linked plan facts, visible last-checked dates, and workflow scenarios before choosing a paid AI coding setup.
- CTA primary: Check my limit risk
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent guide. Source-linked facts. No account connection.
- Disclaimer: Independent guide. We are not affiliated with or endorsed by OpenAI. Prices and limits may change. Each claim below should link to a provider source and show a last-checked date.
- H2/H3 outline and section copy:
  - H2: Answer first: what this page helps you decide | H3: none | Placement: above_fold | Priority: high
    Copy: Codex usage can mean different things: local CLI messages, cloud tasks, ChatGPT plan access, credits, or API-token billing. This page explains those modes separately, shows what may count against a plan, and helps developers decide when to use subscription access or API fallback.
  - H2: Plan and usage table | H3: Plan facts; Usage notes; Source and confidence | Placement: near_top | Priority: high
    Copy: Show plan rows with price_display, billing_period, usage_or_limit_notes, region/tax caveat, source_url, last_checked, confidence, and correction link.
  - H2: Real cost scenarios | H3: Light solo developer; Heavy agent user; Team or reimbursement case; API fallback case | Placement: body | Priority: high
    Copy: Compare light solo developer, heavy agent user, team lead, and API-heavy builder scenarios. State assumptions and link to calculator result.
  - H2: What may change | H3: Last checked policy; Submit a correction | Placement: lower_page | Priority: normal
    Copy: Explain that prices, usage pools, reset windows, model access, taxes, regional availability, and enterprise terms may change. Link to changelog and contact correction route.
- Table/module copy:
  - Module: Source-linked pricing / usage table
  - Columns: Plan or mode, Best fit, Public price or cost basis, Included usage or limit notes, What may change, Source, Last checked, Confidence
  - Rule: Never publish price_display without source_url, last_checked, confidence, and caveat.
  - Rule: Use “may vary” for regional, account-specific, promotional, or enterprise terms.
  - Rule: Use neutral plan labels; no provider logos.
- FAQ:
  - Q: Is this an independent OpenAI pricing guide?
    A: Yes. This is an independent guide and is not affiliated with or endorsed by OpenAI. Brand names are used only to identify the product being discussed.
  - Q: Can I rely on this as my final bill?
    A: No. Calculator and table outputs are estimates based on public assumptions. Your actual bill or account limits may vary by region, plan, taxes, promotions, and provider policy changes.
  - Q: What should I check before upgrading?
    A: Check plan price, included usage or credits, reset behavior, model access, team controls, overage or on-demand terms, source link, and last-checked date.
  - Q: Why do users hit usage limits even on paid plans?
    A: Paid plans can still have capacity, credit, model, or reset-window constraints. Heavy agent sessions, long context, cloud tasks, or advanced models may consume more capacity.
  - Q: Does this page collect my account usage?
    A: No. P0 should not connect to provider accounts or collect tokens, billing credentials, API keys, or private usage dashboards.
  - Q: How do I report outdated pricing?
    A: Use the contact or correction link with a source URL. Updated facts should create or update a changelog entry.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /contact, /about, /claude-code-vs-codex, /claude-code-vs-cursor, /claude-code-usage-limits
- Source links: https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan, https://openai.com/api/pricing/, https://openai.com/policies/service-terms
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /cursor-pricing
- Page type: pricing_page
- Primary keyword: cursor pricing
- SEO title: Cursor Pricing: Free, Pro, Pro+, Ultra, Teams, and Usage Pools
- SEO description: Compare Cursor pricing plans, included usage, on-demand billing, team features, and when Pro+ or Ultra is worth it.
- H1: Cursor pricing explained
- Word count target: 1000-1500
- Above-fold answer: Cursor pricing should be evaluated by included usage, on-demand billing behavior, model choice, and whether you need individual or team features. This page compares plan fit, usage-pool tradeoffs, and upgrade triggers while linking every factual row to Cursor sources and last-checked dates.
- Hero headline: Cursor pricing explained
- Hero subhead: Use source-linked plan facts, visible last-checked dates, and workflow scenarios before choosing a paid AI coding setup.
- CTA primary: Estimate your monthly cost
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent guide. Source-linked facts. No account connection.
- Disclaimer: Independent guide. We are not affiliated with or endorsed by Cursor. Prices and limits may change. Each claim below should link to a provider source and show a last-checked date.
- H2/H3 outline and section copy:
  - H2: Answer first: what this page helps you decide | H3: none | Placement: above_fold | Priority: high
    Copy: Cursor pricing should be evaluated by included usage, on-demand billing behavior, model choice, and whether you need individual or team features. This page compares plan fit, usage-pool tradeoffs, and upgrade triggers while linking every factual row to Cursor sources and last-checked dates.
  - H2: Plan and usage table | H3: Plan facts; Usage notes; Source and confidence | Placement: near_top | Priority: high
    Copy: Show plan rows with price_display, billing_period, usage_or_limit_notes, region/tax caveat, source_url, last_checked, confidence, and correction link.
  - H2: Real cost scenarios | H3: Light solo developer; Heavy agent user; Team or reimbursement case; API fallback case | Placement: body | Priority: high
    Copy: Compare light solo developer, heavy agent user, team lead, and API-heavy builder scenarios. State assumptions and link to calculator result.
  - H2: What may change | H3: Last checked policy; Submit a correction | Placement: lower_page | Priority: normal
    Copy: Explain that prices, usage pools, reset windows, model access, taxes, regional availability, and enterprise terms may change. Link to changelog and contact correction route.
- Table/module copy:
  - Module: Source-linked pricing / usage table
  - Columns: Plan or mode, Best fit, Public price or cost basis, Included usage or limit notes, What may change, Source, Last checked, Confidence
  - Rule: Never publish price_display without source_url, last_checked, confidence, and caveat.
  - Rule: Use “may vary” for regional, account-specific, promotional, or enterprise terms.
  - Rule: Use neutral plan labels; no provider logos.
- FAQ:
  - Q: Is this an independent Cursor pricing guide?
    A: Yes. This is an independent guide and is not affiliated with or endorsed by Cursor. Brand names are used only to identify the product being discussed.
  - Q: Can I rely on this as my final bill?
    A: No. Calculator and table outputs are estimates based on public assumptions. Your actual bill or account limits may vary by region, plan, taxes, promotions, and provider policy changes.
  - Q: What should I check before upgrading?
    A: Check plan price, included usage or credits, reset behavior, model access, team controls, overage or on-demand terms, source link, and last-checked date.
  - Q: Why do users hit usage limits even on paid plans?
    A: Paid plans can still have capacity, credit, model, or reset-window constraints. Heavy agent sessions, long context, cloud tasks, or advanced models may consume more capacity.
  - Q: Does this page collect my account usage?
    A: No. P0 should not connect to provider accounts or collect tokens, billing credentials, API keys, or private usage dashboards.
  - Q: How do I report outdated pricing?
    A: Use the contact or correction link with a source URL. Updated facts should create or update a changelog entry.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /contact, /about, /claude-code-vs-codex, /claude-code-vs-cursor, /codex-usage, /claude-code-usage-limits
- Source links: https://cursor.com/pricing, https://cursor.com/changelog, https://cursor.com/terms-of-service
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /claude-code-vs-codex
- Page type: comparison_page
- Primary keyword: claude code vs codex
- SEO title: Claude Code vs Codex: Pricing, Limits, Workflow, and Best Fit
- SEO description: Compare Claude Code and OpenAI Codex by pricing, included usage, CLI/cloud workflow, model access, limits, and team fit.
- H1: Claude Code vs Codex
- Word count target: 1200-1800
- Above-fold answer: Claude Code and Codex serve overlapping but different AI coding workflows. Claude Code is often evaluated as a terminal-first agent experience, while Codex spans ChatGPT-plan access, CLI usage, cloud tasks, and API workflows. Compare pricing, limits, workflow fit, team controls, and source-backed caveats before choosing.
- Hero headline: Claude Code vs Codex
- Hero subhead: Compare cost, limits, workflow fit, and team controls with source-linked assumptions before you buy.
- CTA primary: Compare my workflow
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent comparison. No affiliation or endorsement implied.
- Disclaimer: This comparison is for informational purposes only. Brand names are used only to identify the products being compared and do not imply affiliation, sponsorship, or endorsement. Verify current pricing and limits with each provider before purchasing.
- H2/H3 outline and section copy:
  - H2: Quick verdict by workflow | H3: Best for CLI-agent work; Best for IDE-first coding; Best for team controls | Placement: above_fold | Priority: high
    Copy: Use scenario-specific guidance, not an absolute winner: heavy CLI agent use, IDE-first coding, cloud-task automation, API-heavy builder, small team lead.
  - H2: Pricing and limits comparison table | H3: Cost model; Usage limits; Team controls | Placement: near_top | Priority: high
    Copy: Compare plan model, usage pools or caps, reset behavior, API/cloud distinction, team/admin controls, and caveats. Each row needs sources and last checked.
  - H2: Scenario calculator | H3: Solo developer scenario; Heavy agent scenario; Team reimbursement scenario | Placement: body | Priority: high
    Copy: Embed calculator with both products preselected. Show monthly estimate, limit-risk level, and caveats for solo and team workflows.
  - H2: Decision checklist | H3: Before buying; Before switching | Placement: lower_page | Priority: normal
    Copy: Give a buyer checklist: source freshness, plan capacity, account-specific caveats, workflow fit, export/admin needs, and upgrade path.
- Table/module copy:
  - Module: Comparison table
  - Columns: Decision factor, Claude Code, Other tool, What it means, Source / last checked
  - Rule: Avoid “X is better than Y” as a universal claim.
  - Rule: Recommendations must start with “Choose X if…” and cite the workflow condition.
  - Rule: No logos or official-looking cards.
- FAQ:
  - Q: Which should I choose: Claude Code vs Codex?
    A: Choose based on workflow, not brand loyalty. If your work is terminal-agent heavy, one tool may fit better; if your workflow is editor-native or cloud-task heavy, another may be more practical.
  - Q: Which one is cheaper?
    A: It depends on plan, usage intensity, team size, and whether API or subscription billing is involved. Run the calculator scenario and verify each provider source before purchasing.
  - Q: Can one tool replace the other completely?
    A: Not always. Some developers use an IDE assistant for daily edits and a terminal or cloud agent for larger tasks. The comparison should show tradeoffs, not force a universal winner.
  - Q: Are limits the same for every user?
    A: No. Limits and availability may vary by plan, account type, region, model, promotion, or provider policy change. Treat public tables as planning guidance, not account-specific guarantees.
  - Q: Is this page sponsored by either provider?
    A: No P0 comparison should imply sponsorship or endorsement. If any sponsor or affiliate relationship is added later, it must be visibly disclosed and must not alter factual tables.
  - Q: How often should I re-check this comparison?
    A: Re-check before any paid upgrade or team rollout. AI coding pricing and usage policies change often enough that source links and last-checked dates matter.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /claude-code-pricing, /codex-pricing, /cursor-pricing, /contact
- Source links: https://claude.com/pricing, https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work, https://support.claude.com/en/articles/14552983-models-usage-and-limits-in-claude-code, https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan, https://openai.com/api/pricing/, https://openai.com/policies/service-terms
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /claude-code-vs-cursor
- Page type: comparison_page
- Primary keyword: claude code vs cursor
- SEO title: Claude Code vs Cursor: Pricing, Limits, IDE vs Terminal Workflow
- SEO description: Compare Claude Code and Cursor by price, usage limits, coding workflow, model access, team controls, and best-fit use cases.
- H1: Claude Code vs Cursor
- Word count target: 1200-1800
- Above-fold answer: Claude Code vs Cursor is mainly a workflow and usage-model decision. Claude Code is terminal-agent oriented; Cursor is an AI IDE with plan-based and usage-pool behavior. Compare cost, included usage, team controls, source freshness, and whether your coding style favors terminal automation or editor-native assistance.
- Hero headline: Claude Code vs Cursor
- Hero subhead: Compare cost, limits, workflow fit, and team controls with source-linked assumptions before you buy.
- CTA primary: Compare my workflow
- CTA secondary: Get pricing change alerts
- Trust microcopy: Independent comparison. No affiliation or endorsement implied.
- Disclaimer: This comparison is for informational purposes only. Brand names are used only to identify the products being compared and do not imply affiliation, sponsorship, or endorsement. Verify current pricing and limits with each provider before purchasing.
- H2/H3 outline and section copy:
  - H2: Quick verdict by workflow | H3: Best for CLI-agent work; Best for IDE-first coding; Best for team controls | Placement: above_fold | Priority: high
    Copy: Use scenario-specific guidance, not an absolute winner: heavy CLI agent use, IDE-first coding, cloud-task automation, API-heavy builder, small team lead.
  - H2: Pricing and limits comparison table | H3: Cost model; Usage limits; Team controls | Placement: near_top | Priority: high
    Copy: Compare plan model, usage pools or caps, reset behavior, API/cloud distinction, team/admin controls, and caveats. Each row needs sources and last checked.
  - H2: Scenario calculator | H3: Solo developer scenario; Heavy agent scenario; Team reimbursement scenario | Placement: body | Priority: high
    Copy: Embed calculator with both products preselected. Show monthly estimate, limit-risk level, and caveats for solo and team workflows.
  - H2: Decision checklist | H3: Before buying; Before switching | Placement: lower_page | Priority: normal
    Copy: Give a buyer checklist: source freshness, plan capacity, account-specific caveats, workflow fit, export/admin needs, and upgrade path.
- Table/module copy:
  - Module: Comparison table
  - Columns: Decision factor, Claude Code, Other tool, What it means, Source / last checked
  - Rule: Avoid “X is better than Y” as a universal claim.
  - Rule: Recommendations must start with “Choose X if…” and cite the workflow condition.
  - Rule: No logos or official-looking cards.
- FAQ:
  - Q: Which should I choose: Claude Code vs Cursor?
    A: Choose based on workflow, not brand loyalty. If your work is terminal-agent heavy, one tool may fit better; if your workflow is editor-native or cloud-task heavy, another may be more practical.
  - Q: Which one is cheaper?
    A: It depends on plan, usage intensity, team size, and whether API or subscription billing is involved. Run the calculator scenario and verify each provider source before purchasing.
  - Q: Can one tool replace the other completely?
    A: Not always. Some developers use an IDE assistant for daily edits and a terminal or cloud agent for larger tasks. The comparison should show tradeoffs, not force a universal winner.
  - Q: Are limits the same for every user?
    A: No. Limits and availability may vary by plan, account type, region, model, promotion, or provider policy change. Treat public tables as planning guidance, not account-specific guarantees.
  - Q: Is this page sponsored by either provider?
    A: No P0 comparison should imply sponsorship or endorsement. If any sponsor or affiliate relationship is added later, it must be visibly disclosed and must not alter factual tables.
  - Q: How often should I re-check this comparison?
    A: Re-check before any paid upgrade or team rollout. AI coding pricing and usage policies change often enough that source links and last-checked dates matter.
- Schema types: Article, FAQPage, BreadcrumbList
- Internal links: /, /pricing-changelog, /claude-code-pricing, /codex-pricing, /cursor-pricing, /contact
- Source links: https://claude.com/pricing, https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work, https://support.claude.com/en/articles/14552983-models-usage-and-limits-in-claude-code, https://cursor.com/pricing, https://cursor.com/changelog, https://cursor.com/terms-of-service
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

### /pricing-changelog
- Page type: changelog_hub
- Primary keyword: AI coding pricing changelog
- SEO title: AI Coding Pricing Changelog: Claude Code, Codex, Cursor, Copilot
- SEO description: Track pricing, limit, and usage-policy changes across major AI coding tools with dated source links.
- H1: AI coding pricing changelog
- Word count target: 500-900 plus entries
- Above-fold answer: The AI Coding Pricing changelog tracks public pricing, usage-limit, credit, plan, and billing-policy changes across Claude Code, Codex, Cursor, and GitHub Copilot. Each entry should show the provider, changed field, observed date, source URL, confidence, and whether users should re-check before upgrading.
- Hero headline: AI coding pricing changelog
- Hero subhead: Track public pricing and usage-limit changes with dates, sources, and confidence labels.
- CTA primary: Get change alerts
- CTA secondary: Submit a correction
- Trust microcopy: Public observations only. Verify provider sources before buying.
- Disclaimer: Changelog entries summarize public pricing or limit changes we observed. They may not capture every regional, enterprise, promotional, or account-specific change.
- H2/H3 outline and section copy:
  - H2: Latest changes | H3: Provider; Changed field; Confidence | Placement: above_fold | Priority: high
    Copy: Show the newest 10 entries with provider, changed field, date observed, date checked, source URL, confidence, and caveat. If no entries exist, do not launch as an empty indexable page.
  - H2: How we verify changes | H3: Source type; Confidence rules | Placement: body | Priority: high
    Copy: Explain source types: provider pricing page, provider help doc, terms/policy page, public support note, or observed public report. Core factual tables should prefer provider sources.
  - H2: Get pricing and limit alerts | H3: Alert preferences; Provider interest | Placement: body | Priority: normal
    Copy: Newsletter form copy should be provider-specific and store source_path/provider_interest. Do not use generic newsletter copy.
- Table/module copy:
  - Module: Changelog entry list
  - Columns: Date observed, Provider, Product, Changed field, Old value, New value, Source, Confidence, Impact
  - Rule: No blank changelog hub at launch. Seed entries must have source_url and checked date.
  - Rule: If old/new value is not known, write “not confirmed” rather than guessing.
- FAQ:
  - Q: What changes are tracked here?
    A: Pricing, usage limits, credit rules, plan availability, billing-policy changes, and source-page updates for AI coding tools.
  - Q: Is every provider change captured?
    A: No. Entries summarize public changes we observe. Regional, enterprise, promotional, or account-specific changes may not be captured.
  - Q: Can providers submit corrections?
    A: Yes. Providers and users should use the contact route to submit a correction with a source URL.
  - Q: How do confidence labels work?
    A: High confidence should come from provider pricing, docs, or terms. Medium may combine provider sources. Low should be treated as anecdotal and not drive core pricing tables.
  - Q: Can I subscribe to only one provider?
    A: The newsletter form should capture provider interest so users can ask for Claude Code, Codex, Cursor, Copilot, or all pricing alerts.
  - Q: Should I verify before purchasing?
    A: Yes. Use changelog entries as a discovery aid and verify the provider source before buying or changing plans.
- Schema types: CollectionPage, ItemList, BreadcrumbList, FAQPage
- Internal links: /, /claude-code-pricing, /codex-pricing, /cursor-pricing, /claude-code-usage-limits, /codex-usage, /contact, /about
- Source links: https://claude.com/pricing, https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work, https://support.claude.com/en/articles/14552983-models-usage-and-limits-in-claude-code, https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan, https://openai.com/api/pricing/, https://openai.com/policies/service-terms, https://cursor.com/pricing, https://cursor.com/changelog, https://cursor.com/terms-of-service, https://github.com/features/copilot/plans, https://docs.github.com/en/billing/concepts/product-billing/github-copilot-premium-requests, https://docs.github.com/en/copilot/concepts/billing/copilot-requests
- Design placement priority:
  - above_fold: ['H1', 'short answer', 'primary CTA', 'disclaimer', 'calculator/table hook']
  - near_top: ['pricing/comparison table', 'source links', 'last checked']
  - lower_page: ['SEO body', 'FAQ', 'internal links', 'newsletter CTA']
  - crawlability: FAQ may be collapsible only if server-rendered/crawlable; do not remove body copy for design cleanliness.

## Expansion and legal routes included in machine matrix
- /claude-code-cost — expansion_copy_frozen_not_p0_design_blocker — Claude Code Cost Calculator: Estimate Monthly Usage Before Upgrading — target 1000-1500
- /codex-limits — expansion_copy_frozen_not_p0_design_blocker — Codex Limits: Plus, Pro, Credits, Local Messages, and Cloud Tasks — target 1000-1500
- /codex-vs-cursor — expansion_copy_frozen_not_p0_design_blocker — Codex vs Cursor: ChatGPT Coding Agent vs AI IDE Pricing — target 1200-1800
- /api-vs-subscription — expansion_copy_frozen_not_p0_design_blocker — API vs Subscription for AI Coding Tools: Which Costs Less? — target 1000-1500
- /github-copilot-pricing — expansion_copy_frozen_not_p0_design_blocker — GitHub Copilot Pricing: Free, Pro, Pro+, Business, Enterprise — target 1000-1500
- /github-copilot-vs-cursor — expansion_copy_frozen_not_p0_design_blocker — GitHub Copilot vs Cursor: Pricing, Requests, IDE Workflow, and Agents — target 1200-1800
- /claude-max-vs-pro — expansion_copy_frozen_not_p0_design_blocker — Claude Max vs Pro: Usage Capacity, Price, and Claude Code Fit — target 1200-1800
- /codex-pricing-changelog — expansion_copy_frozen_not_p0_design_blocker — Codex Pricing Changelog: Plan, Credit, and Usage Limit Updates — target 500-900 plus entries
- /claude-code-pricing-changelog — expansion_copy_frozen_not_p0_design_blocker — Claude Code Pricing Changelog: Plan, Limit, and Usage Updates — target 500-900 plus entries
- /chatgpt-pro-vs-claude-max — expansion_copy_frozen_not_p0_design_blocker — ChatGPT Pro vs Claude Max: Codex and Claude Code Cost Comparison — target 1200-1800
- /about — legal_copy_frozen — About AI Coding Pricing — target 500-900
- /contact — legal_copy_frozen — Contact AI Coding Pricing — target 500-900
- /privacy-policy — policy_copy_requirements_frozen — Privacy Policy — target 1000-1600
- /terms-of-service — policy_copy_requirements_frozen — Terms of Service — target 1000-1600

## Redirect aliases
- /codex-vs-claude-code -> /claude-code-vs-codex, 301, no sitemap, no duplicate indexable copy.
- /cursor-vs-claude-code -> /claude-code-vs-cursor, 301, no sitemap, no duplicate indexable copy.

## Machine-readable source
- /root/.hermes/kanban/boards/site-factory/reports/site-pipeline/site-aicodingpricing-20260521/aicodingpricing/copy/page-copy-matrix.json