SEO And Website Copy Prompts

INPUTS
[keyword or query]; [audience]; [provided search results]; [product relevance]; [sources]

PROMPT
Create a content brief centered on the searcher's actual question. Analyze the supplied results for recurring intent, useful formats, unanswered questions, and differences between informational and commercial needs. Propose a title, outline, supporting examples, internal-link opportunities, and a relevant next action. Identify evidence the writer needs and claims that require current verification. Avoid keyword stuffing and ranking guarantees. Deliver a brief a writer can execute, followed by a quality checklist that prioritizes completeness, accuracy, and usefulness over arbitrary word count.

INPUTS
[current copy]; [offer]; [audience]; [proof]; [brand voice]; [primary action]

PROMPT
Rewrite the homepage as a clear path from understanding the offer to taking the next step. Create a hero section, concise value explanation, benefits, supporting proof, process overview, objections, and final call to action. Use the customer's language where supplied and connect features to realistic outcomes. Keep factual details consistent and leave placeholders for missing proof. Provide a section-by-section draft with a short purpose note for each. End with three headline alternatives and a check for ambiguity, repetition, and unsupported promises.

INPUTS
[product details]; [audience]; [specifications]; [use cases]; [proof]; [purchase conditions]

PROMPT
Write a product page that helps a suitable buyer make an informed choice. Include a clear description, key benefits tied to specific features, relevant specifications, common use cases, limitations, compatibility requirements, and frequently asked questions. Preserve all supplied measurements and conditions. Draft a concise call to action and three title options. Do not invent reviews, availability, or performance claims. End with an information-gap checklist and suggestions for supporting visuals that demonstrate the product rather than merely decorate the page.

INPUTS
[service]; [target client]; [scope]; [process]; [proof]; [next step]

PROMPT
Create a service page that clarifies fit, scope, and expectations. Lead with the client's problem and a credible outcome, then explain deliverables, process, responsibilities, timing, exclusions, and supporting evidence. Include questions that help a prospective client decide whether the service is appropriate. Draft a full page in a professional voice and suggest where diagrams or examples would improve understanding. Avoid vague claims such as being the best. Finish with a concise inquiry form outline and a consistency check against the actual offer.

INPUTS
[core topic]; [audience]; [existing pages]; [offer]; [content capacity]

PROMPT
Design a topic cluster that answers related audience questions without creating duplicate pages. Identify a central page and supporting pieces, each with a distinct purpose and reader intent. Map logical internal links and explain the information each link adds. Recommend which existing content to update before creating new pages. Provide titles, brief outlines, required sources, and a production order. Avoid treating estimated search volume as known. End with a review method for checking whether the cluster helps visitors find complete, relevant answers.

INPUTS
[page text]; [audience]; [primary query]; [brand]; [length preferences]

PROMPT
Create five page-title and meta-description pairs based on the actual page content. Make each pair clear, specific, and aligned with the reader's intent. Avoid claims or benefits the page does not support. Respect the requested length preferences while noting that display length can vary. Explain the angle of each pair and recommend one for clarity and relevance. Also suggest a consistent on-page heading. End with a checklist ensuring the metadata accurately represents the page and does not promise a different experience.

INPUTS
[customer questions]; [page purpose]; [policies]; [product facts]; [tone]

PROMPT
Turn the supplied customer questions into a useful FAQ. Merge true duplicates while preserving important differences in intent. Write direct answers that begin with the information the reader needs, then add conditions or exceptions. Use only supplied policies and product facts, and flag unresolved questions. Organize the FAQ into logical groups and suggest where each answer belongs in the wider website journey. Avoid inventing questions solely to insert keywords. Finish with the five missing details most likely to prevent customers from acting confidently.

INPUTS
[page copy or screenshots]; [visitor intent]; [desired action]; [analytics]; [constraints]

PROMPT
Review the page for barriers between visitor intent and the desired action. Assess message clarity, proof, navigation, information hierarchy, effort, and expectation-setting. Distinguish observed issues from hypotheses requiring user testing. Rank recommendations by likely importance and implementation effort, using the available evidence rather than invented uplift estimates. Provide a revised section sequence and sample copy for the three highest-priority changes. End with a small testing plan that checks whether users understand the offer and can complete the intended action.

INPUTS
[pages]; [publication dates]; [source links]; [current product facts]; [update capacity]

PROMPT
Create a freshness audit for the supplied website content. Identify time-sensitive claims, outdated product details, broken references, obsolete screenshots, and statements that need verification. Do not mark a page outdated simply because it is old. Recommend a priority based on potential reader harm, business relevance, and maintenance effort. Deliver an audit table with the exact passage or issue, required evidence, action, owner, and review date. Finish with a lightweight process for tracking future updates and preventing unsupported changes during editing.

INPUTS
[page inventory]; [page summaries]; [audience journeys]; [priority pages]

PROMPT
Recommend internal links that help readers continue a relevant information journey. Match source passages to destination pages using subject relevance and the reader's likely next question. Provide the source page, proposed placement, natural anchor text, destination, and reason for each link. Avoid forced repetition, excessive links, and destinations that do not deliver what the anchor promises. Flag pages with insufficient context for a reliable recommendation. End with a review checklist and identify any missing supporting page that would improve the journey.