Best Gemini Prompts: A Copy-Paste Library for Chat, SEO, Gems and Images (2026)

1Work as [relevant specialist].
2
3Your assignment: [specific outcome].
4Background: [company, product, audience and situation].
5Use these inputs: [source material or known facts].
6Return: [format, sections, length and language].
7Requirements: [must include, must avoid, tone and deadline].
8
9Before answering, ask me for any detail that would materially change the result. Do not invent missing facts.

1Act as the content strategist for a B2B SaaS project-management company.
2
3Generate [number] blog-post ideas for [target audience] who struggle with [workflow problem]. For each idea, provide:
4- a working title;
5- the reader’s underlying question;
6- funnel stage;
7- one non-obvious angle;
8- the product capability that can be mentioned without forcing a sales pitch.
9
10Group related ideas into themes and flag overlaps. Use only these product facts: [verified product facts]. Ask for missing audience or product context before answering.

1Create a detailed outline for an article titled “[working title]”.
2
3The reader is [job role] at [company type]. Their goal is [goal], and they already know [baseline knowledge]. The article should help them [practical outcome] while naturally connecting to our project-management feature [feature].
4
5Include a direct-answer introduction, H2s phrased around reader questions, evidence or examples needed under each section, and a concise conclusion. Target [word count] words. Do not draft unsupported statistics or customer claims; mark where evidence is still needed.

1Use the launch brief below to create three distinct posts:
2
31. LinkedIn: [length] words for [professional audience], with a clear point of view and one CTA.
42. X: one post under [character limit], led by the sharpest product benefit.
53. Instagram: a caption plus a five-card carousel outline, written for [audience].
6
7Launch brief:
8[paste approved launch brief]
9
10Keep product names, dates, capabilities and quoted figures exactly as supplied. Adapt the angle to each channel instead of shortening the same paragraph three times. If the brief lacks a claim needed for the copy, ask me for it.

1Rewrite the copy below in a [tone] voice for [reader].
2
3Length: [word range]
4Reading level: [level]
5Keep unchanged: product name, feature behavior, dates, prices, numbers and links.
6Improve: sentence rhythm, specificity and the transition into the CTA.
7Avoid: hype, invented benefits, generic opening lines and claims of guaranteed results.
8
9Copy:
10[paste copy]
11
12Return the revision first, followed by a short list of meaningful editorial changes. Do not invent data.

1Cluster the following keywords for a B2B project-management website:
2[keyword list with any available volume, market and difficulty data]
3
4Return a markdown table with:
5| Cluster | Search intent | Primary keyword | Supporting keywords | Suggested target page | Existing URL to review | Cannibalization risk |
6
7Use semantic intent, not shared words alone. Separate feature-page opportunities from educational articles. Do not estimate missing search volumes; label unavailable values as “not provided” and ask about the target market if it is unclear.

1Create [number] SEO title and meta-description pairs for this page:
2
3Page purpose: [purpose]
4Primary query: [query]
5Secondary concepts: [concepts]
6Audience: [audience]
7Confirmed page facts: [facts]
8
9Keep each title at or below [title limit] characters and each description at or below [description limit] characters. Put the useful distinction near the beginning, avoid duplicate pairs, and never add features or outcomes that are absent from the confirmed facts. Show character counts.

1Review the page copy below against the search intent “[search intent]” for the query “[primary query]”.
2
3Assess:
4- whether the opening gives a direct answer;
5- which reader questions are answered or missed;
6- whether each section earns its place;
7- where product detail supports the intent;
8- claims that need evidence;
9- likely overlap with [related URL or page].
10
11Return a prioritized table with Issue, Evidence from the copy, Recommended change and Expected reader benefit. Then propose a revised outline, not a full rewrite.
12
13Page copy:
14[paste current page]

1Design a [number]-email welcome sequence for new users of a B2B project-management tool.
2
3Audience segment: [segment]
4Signup trigger: [trigger]
5First-value action: [action]
6Product facts you may use: [verified facts]
7Voice: [voice]
8
9For every email, give the send timing, objective, subject-line options, preview text, message structure, primary CTA and the behavioral signal for the next email. Prevent repeated arguments across the sequence. Ask me for any missing lifecycle or product detail before writing body copy.

1Write one re-engagement email for [user segment] who have not [meaningful action] in [period].
2
3Their likely objections are:
4- [objection one]
5- [objection two]
6- [objection three]
7
8Use [approved incentive or useful resource], explain what has changed using only [verified updates], and offer one low-friction next step. Provide two subject lines and one complete email under [word count] words. Acknowledge objections without sounding defensive, and do not invent urgency.

1You are the in-house editor for [company], a B2B project-management software company.
2
3For every draft I send:
41. identify the audience and intended action;
52. preserve verified product facts, links, prices, dates and quotations;
63. rewrite in this voice: [voice principles];
74. enforce this style guide: [house rules];
85. flag unsupported claims instead of repairing them with invented detail;
96. return Clean copy, Questions for the author, and Editorial notes.
10
11Never change the factual meaning to improve the line. If audience, channel or evidence is missing, ask me before editing.

1Convert my project meeting notes into an execution brief.
2
3Produce:
4- decisions made, with the named decision owner;
5- action items with owner and stated due date;
6- blockers and dependencies;
7- open questions;
8- items discussed but not decided.
9
10Use the participants’ names exactly as written. Do not infer owners, dates or decisions from vague discussion: mark them “unassigned”, “no date stated” or “open”. End with a short follow-up message I can post to the project channel.
11
12Notes:
13[paste meeting notes]

1Create a photorealistic campaign image of a calm operations lead reviewing a project-management dashboard on a large monitor in a bright, credible mid-size company office. Natural window light, muted blue and warm grey palette, documentary photography, landscape [aspect ratio]. Keep screen details abstract and legible-looking; no logos, no fake interface text, no extra fingers.

1Design a clean social-media visual announcing “[feature name]” for a B2B project-management tool. Show an orderly flow of task cards moving from an at-risk state to an on-track state, signaled by color and simple status icons — a warning glyph resolving into a check mark — rather than written labels. Use [brand colors], generous negative space and a crisp editorial-illustration style. Reserve a clear text-safe area in the [position]; do not render words or brand marks. Output [aspect ratio].

1Assess whether our B2B project-management company should build a feature page for “[candidate feature]”.
2
3Work through these ordered steps:
41. restate the decision and list the supplied evidence;
52. map [customer interviews], [support themes] and [search data] to user needs;
63. separate facts, assumptions and unanswered questions;
74. compare “new feature page”, “expand an existing page” and “do not publish”;
85. recommend one option with reasons, risks and the next validation step.
9
10Return a concise decision memo. Do not expose private hidden reasoning; show the evidence and decision criteria needed to audit the conclusion. Ask for any missing input that could reverse the recommendation.

1Turn feature notes into concise release-note entries. Follow these examples:
2
3Example 1
4Input: Workload alerts notify a project owner when assigned capacity crosses a chosen threshold.
5Output: “Spot overloaded teammates sooner. Set a capacity threshold and notify the project owner when assigned work crosses it.”
6
7Example 2
8Input: Guests can now comment on shared project timelines without seeing internal budget fields.
9Output: “Collect timeline feedback from guests while keeping internal budget fields private.”
10
11Now rewrite:
12[feature notes]
13
14Use one benefit-led sentence followed by one precise behavior sentence. Keep every limitation in the source, remove internal implementation language, and do not add a benefit that the notes cannot support.