AI Prompts for Content Writing and SEO

For [site or content project], draft titles for actual pages for search title drafting. 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 unique descriptive options matching 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], review repetitive titles for search title drafting. 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, boilerplate and keyword repetition with replacements. 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], align titles and headings for search title drafting. 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 and narrow wording revisions. 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 page-type title templates for search title drafting. 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 patterns using fields that actually exist. 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 title proposals for search title drafting. 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 truthfulness, distinctiveness and useful phrasing without ranking promises. 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 page descriptions for meta description drafting. 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 unique summaries grounded in visible 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], review misleading descriptions for meta description drafting. 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 promises, old counts and truthful replacements. 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], align summaries with reader tasks for meta description drafting. 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 descriptions stating the real purpose. 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 editor guidance for meta description drafting. 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 brief for accurate page-specific summaries. 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 final descriptions for meta description drafting. 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 clarity and consistency without assuming verbatim display by Google. 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 factual claims for content claim audit. 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 claim-evidence table and required sources. 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], check numerical claims for content claim audit. 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 units, dates, denominators and source-based calculations. 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 experience wording for content claim audit. 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 first-hand or testimonial claims and honest replacements. 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], check source support for content claim audit. 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 whether each supplied citation supports its attached statement. 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 publication fact checklist for content claim audit. 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 unresolved claims, needed confirmations and approval 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], inventory real author information for author and about 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 verified roles, qualifications and permitted details. 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 an honest biography for author and about 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 source-grounded prose without invented achievements. 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], explain content creation for author and about 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 accurate human and AI roles with review limits. 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 author-page links for author and about 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 work samples and relevant supplied profiles. 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 expertise claims for author and about 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 fabricated authority, missing evidence and correction wording. 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 service locations for local service 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 supported coverage and unsupported-area 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], draft a local page outline for local service 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 actual services, local questions and evidence 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], write location-specific copy for local service 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 factual differences without near-duplicate doorway 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], check contact consistency for local service 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 discrepancies across supplied public details. 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 local credibility for local service 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 unsupported reviews, affiliations and geography 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], describe supplied images for image alt text and captions. 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 alt text for visible meaningful 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], classify decorative images for image alt text and captions. 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 reasoned treatment table without keyword stuffing. 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 accurate captions for image alt text and captions. 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 and source-credit 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], review existing alt text for image alt text and captions. 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 redundancy, unsupported interpretation and clearer descriptions. 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 image publishing checklist for image alt text and captions. 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, attribution, file information and accessibility 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], map language needs for english and roman urdu 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 task-based plan without assumed search-volume 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], adapt guidance into roman urdu for english and roman urdu 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 practical natural instructions preserving meaning. 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 bilingual consistency for english and roman urdu 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 mismatched claims, unclear terms and corrections. 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 language navigation for english and roman urdu 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 options based on actual available versions. 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 translation quality for english and roman urdu 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 meaning, readability and source preservation without false review 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], plan a source-based video for educational video script. 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 storyline and source-to-scene mapping. 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 educational script for educational video script. 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 spoken lines, visual cues and fact-check 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 accurate video titles for educational video script. 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 options matching the actual script. 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 transcript structure for educational video script. 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 text reflecting the real video or supplied script. 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 video claims for educational video script. 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 demonstrations, evidence gaps and bounded wording. 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 supported takeaways for article-to-social 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 source-linked list suitable for reuse. 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 social post for article-to-social 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 claims and a relevant next step without guaranteed engagement. 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 carousel for article-to-social 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 slide messages based on the article with readable hierarchy. 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 newsletter summary for article-to-social 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 faithful recap with supplied links and no invented endorsement. 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 reused material for article-to-social 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 lost context, overstated conclusions and misleading quotes. 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], interpret a performance export for search console content 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 and query patterns with period and filter limits. 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 reporting periods for search console content 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 changes with seasonality and measurement caveats, avoiding invented causes. 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 investigation candidates for search console content 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 prioritized hypotheses from actual impressions, clicks and queries. 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 improvement backlog for search console content 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 specific page changes and checks grounded in supplied 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], plan content monitoring for search console content 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 baseline, review dates and decision criteria without guaranteed rankings. 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.