AI Prompts for Content Writing and SEO

For [site or content project], extract keyword seed terms from actual customer questions for keyword idea discovery. Inputs: [sanitized customer questions or support transcripts], [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a table linking each quoted customer question to a seed term, the customer problem, likely search task and a source reference. Group repeated wording only when it appears in the supplied records; do not infer search volume or market-wide frequency from a small support sample. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], separate ideas by likely task for keyword idea discovery. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce hypotheses for learning, comparison and action-oriented searches. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], design keyword validation for keyword idea discovery. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce steps for confirming demand through actual tools and data. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], review a keyword export for keyword idea discovery. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce duplicates, irrelevant terms and data-supported opportunities. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], build a research backlog for keyword idea discovery. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce topics with reasoning, evidence gaps and next checks. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], analyze supplied search results for search intent review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce observed page types and apparent reader needs. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], map audience questions for search intent review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce brief-supported questions and uncertainty flags. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], compare page purposes for search intent review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce content-fit tradeoffs and evidence requirements. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], review an existing page's intent for search intent review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce mismatches between its stated purpose and actual content. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], draft an intent-led outline for search intent review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a useful structure without copying competing pages. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], create a focused brief for blog content brief. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce audience, purpose, questions and scope boundaries. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], build an evidence-aware outline for blog content brief. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce headings with required facts and source placeholders. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], plan practical examples for blog content brief. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce examples clearly hypothetical unless real evidence is supplied. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], create a writer research checklist for blog content brief. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce claims needing sources and questions to resolve. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], review an existing brief for blog content brief. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce missing reader needs, duplication and unsupported claims. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], audit article usefulness for existing article revision. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce specific gaps, contradictions and source requirements. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], rewrite one requested section for existing article revision. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce clear prose preserving facts and approved scope. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], improve the opening for existing article revision. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a direct introduction matching actual content. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], create an update plan for existing article revision. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce dated facts to verify and substantive revisions needed. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], review a revision for existing article revision. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce factual drift, readability and source-consistency checks. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], inventory existing pages for topic cluster planning. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a topic-to-URL map with duplication and missing coverage. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], design a cluster structure for topic cluster planning. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce hubs and support pages based on distinct reader tasks. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], identify consolidation candidates for topic cluster planning. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce evidence-based merge and redirect proposals. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], plan a publication batch for topic cluster planning. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce prioritized pages with purpose, evidence and dependencies. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], audit a cluster for topic cluster planning. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce overlapping intents, weak connections and missing useful coverage. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], define reader purpose for prompt category landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce an audience-task map and inclusion boundaries. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], write a truthful category introduction for prompt category landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a description based on actual published prompts. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], plan section navigation for prompt category landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce distinct subcategories and descriptive link text. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], draft prompt usage guidance for prompt category landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce editable inputs, output expectations and verification steps. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], audit prompt quality for prompt category landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce duplicates, thin entries, unsupported counts and missing instructions. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], extract product evidence for product page content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce an approved-fact list and unknown specifications. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], draft a product-page outline for product page content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce features, uses, limits and policy references. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], write a factual summary for product page content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce benefits tied to documented features. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], plan customer questions for product page content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce questions answerable from actual product facts. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], audit misleading product claims for product page content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce unsupported reviews, certification and outcome claims. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], map client needs for service landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a problem-scope matrix based on actual capabilities. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], draft the page structure for service landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce details, process, eligibility and contact placeholders. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], write the service introduction for service landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce bounded claims without invented outcomes or credentials. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], create an inquiry guide for service landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce questions needed to assess a project. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], review trust signals for service landing page. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce real evidence, missing explanations and unsupported proof claims. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], clarify actual offerings for homepage content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce a fact-based audience and navigation brief. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], draft headline options for homepage content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce accurate value statements without inflated counts. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], write homepage sections for homepage content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce clear descriptions linked to available resources. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], plan homepage links for homepage content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce important public destinations and descriptive anchors. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], audit homepage consistency for homepage content. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce brand, counts, service claims and navigation checked against actual pages. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], map supplied internal links for internal link review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce source, destination, anchor and relevance. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], recommend relevant links for internal link review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce context-specific additions using real available URLs. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], improve unclear anchor text for internal link review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce concise wording matching destination content. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], audit misleading destinations for internal link review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce an evidence table from supplied crawl results. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.

For [site or content project], create an implementation checklist for internal link review. Inputs: [actual page text or source files], [target audience], [reader's task], [available URLs], [brand tone], [language preference] and [supplied research or performance data]. Produce page-level changes and checks without site edits. Separate supplied facts from assumptions and ask for missing information that materially affects the result. Prioritize the reader's task over keyword repetition or unnecessary pages. Preserve verified facts, existing useful URLs and intended meaning. Do not invent search volumes, rankings, reviews, testimonials, first-hand experience, expertise, citations or product capabilities. Treat keyword and intent ideas as hypotheses unless supporting data exists. Attach source links only when they support the associated claim; if current platform guidance is needed, verify it against official documentation. Before finalizing, check factual consistency, originality, descriptive links and alignment with actual page content. Flag unsupported claims and unresolved inputs. Do not promise rankings, traffic or virality, or claim FAQ markup creates Google FAQ rich results. Return a reviewable draft or plan, without claiming changes are published.