Create an SEO content brief with AI

Target query: kubernetes requests and limitsReader: a developer writing their first Pod configurationCountry/language: United States / EnglishCompeting article titles: the original titles of the three public documents belowInternal link inventory (title + URL): none

Create an SEO content brief in English. Do not write the article.Target query: kubernetes requests and limitsReader: a developer writing their first Pod configurationCountry/language: United States / EnglishCompeting article titles (public documentation, not a ranking sample):- Resource Management for Pods and Containers- Assign CPU Resources to Containers and Pods- Assign Memory Resources to Containers and PodsInternal link inventory (title + URL): none Use only these inputs. Do not browse the web.Only titles are supplied; do not infer what the articles cover or omit.Label search intent as a hypothesis. Do not invent search volumes, rankings,performance figures, sources, or URLs.Do not promote a company or product or claim to know search engine preferences.Return these six items in order, keeping each concise:1. One proposed title.2. A search intent hypothesis and the information needed to check it.3. Four outline sections, each with one line stating what it should answer.4. Three reader questions. Do not propose a separate FAQ section.5. Internal links: select anchor text, URL, and placement only from the inventory.   If it is empty, write "No candidates — an inventory of existing articles is needed".6. Three evidence requests: claim to check, primary material needed, and   version or conditions to verify. Do not imply that you checked the material.   Mark unknowns as "Needs verification".Return the brief only. Do not write technical explanations, figures, or YAML examples.

1. Proposed titleKubernetes requests and limits: distinguish the settings before configuring a Pod 2. Search intentHypothesis: the reader wants to understand the difference and decide what to put in a first Pod configuration.Needs verification: the types of pages returned for the target query, the reader's Kubernetes version, and their runtime environment. 3. Outline- Distinguish requests from limits: explain the purpose of each setting and the common points of confusion.- Compare CPU and memory: identify which resource-specific behavior the reader needs to check.- Read a Pod configuration: show where to verify field names and units.- Review the chosen settings: identify the observations and test conditions needed before choosing values. 4. Reader questions- Why configure requests and limits separately?- Can I use the same reasoning for CPU and memory?- What should I observe to judge whether the settings fit my workload? 5. Internal linksNo candidates — an inventory of existing articles is needed 6. Evidence requests- Claim to check: how requests affect Pod scheduling decisions. Primary material needed: Kubernetes resource management documentation. Needs verification: Kubernetes version and scheduler configuration.- Claim to check: differences between CPU and memory limit enforcement. Primary material needed: Kubernetes CPU and memory resource documentation. Needs verification: Kubernetes version, operating system, and container runtime.- Claim to check: what applies when a resource field is omitted. Primary material needed: Kubernetes API and LimitRange documentation. Needs verification: Kubernetes version, namespace policies, and admission configuration.

Variation A: Change the reader to a developer encountering Kubernetes for the first time.Variation B: Change the reader to a developer reviewing resource settings for a running Pod.Variation C: Keep the reader unchanged and limit the outline to explaining the difference between requests and limits.