Choose by the output you need to make

ChatGPT Prompts for SEO Specialists

SEO operators using ChatGPT to organize research, briefs, metadata, and refresh work.

Use ChatGPT for SEO by choosing the mode that matches the job: a normal prompt for briefs and snippets, deep research for multi-source research notes, ChatGPT agent for browser-assisted public page review, and a human SEO owner for final changes. Bring page copy and real search notes before asking for recommendations.

Copy a role-level prompt template

Template

Act as a careful SEO workflow assistant.
SEO job: [content brief | title tags | meta descriptions | internal links | content refresh | SERP analysis | schema outline | deep research packet | browser-assisted page review | niche edit review].
Page URL or page type: [page_or_type].
Main search question: [main_search_question].
Visible page copy or outline: [visible_copy].
Search Console or keyword rows I can share: [source_data].
SERP or competitor observations I checked manually: [serp_notes].
Internal pages available for links: [internal_pages].
If this is deep research, return a cited research packet with source-quality notes and questions to verify before briefing.
If this is ChatGPT agent or older Operator-style browser work, only inspect public pages and ask before taking any external action.
If this is a niche edit request, check reader fit, anchor wording, placement context, disclosure, rel attribute, and whether to decline.
Return: intent summary, recommended asset, input gaps, output quality checks, when to use, when not to use, and the next SEO prompt page to open.

Input example

SEO job: content brief and title refresh. Page: /chatgpt-prompts/seo/content-brief/. Main search question: ChatGPT content brief prompt. Source data: Search Console rows for impressions and average position. Visible copy: H1, intro, prompt template, example, and FAQ. SERP notes: top pages offer templates but often lack output review. Internal pages: title tags, meta descriptions, internal linking.

Expected output

A useful answer separates imported data from interpretation, gives a content brief or snippet set tied to visible page copy, flags any invented metric or unsupported promise, and links the next step to content brief, title tags, meta descriptions, internal linking, or SERP analysis.

Output quality checks

The answer never invents volume, rankings, CTR, CPC, backlinks, traffic, SERP features, or competitor facts.
Deep research output includes source-quality notes and turns research into a briefable packet instead of final SEO instructions.
ChatGPT agent or older Operator-style browser output lists public observations and asks before changing anything outside the chat.
Niche edit review explains whether the placement helps the reader, whether the anchor is natural, and what disclosure or rel choice is needed.
Every title, meta description, link suggestion, and schema idea matches content visible on the page.

Use it when

Use for content briefs, title tags, meta descriptions, internal links, refresh plans, SERP comparisons, and schema outlines based on real inputs.
Use deep research when the job needs multiple outside sources summarized before a brief or page refresh is written.
Use ChatGPT agent for browser-assisted review of public pages, visible page sections, and comparison notes.
Use for niche edit screening when the goal is to decide whether a link insertion is reader-helpful, natural, and worth declining if weak.

Skip it when

Do not use ChatGPT to invent keyword metrics, rankings, traffic, backlinks, reviews, schema properties, or Search Console findings.
Do not let ChatGPT agent or an Operator-style flow submit forms, change CMS content, buy links, or modify account settings without exact approval.
Do not use niche edit prompts to disguise paid placement, force exact-match anchors, or add links that do not help the reader.
Do not publish high-impact claims until a person checks the live page and source support.

Best next step

Open this next when the SEO work needs a page brief with source notes, output requirements, internal links, and a review checklist.

Build content briefsOpen this next when the SEO work needs a page brief with source notes, output requirements, internal links, and a review checklist.

Review boundary

Do not fabricate search volume, rankings, or SERP facts; import real data before analysis.

Where ChatGPT helps this role

Use standard ChatGPT prompts to turn Search Console rows, page copy, and SERP observations into briefs, titles, descriptions, internal-link maps, refresh plans, and schema outlines.
Use deep research when the SEO task needs multi-source synthesis, competitor pattern notes, citation-backed background, or a first research packet before the brief is written.
Use ChatGPT agent for browser-assisted SEO work such as opening public pages, comparing visible sections, collecting allowed observations, and preparing a review list. If you still use the older Operator name, treat it as this browser-action workflow inside ChatGPT.
Evaluate niche edits or link insertion requests by checking reader fit, anchor wording, placement context, rel attributes, and whether the request should be declined.
Rewrite an existing page only after the current page promise, main search question, visible copy, internal pages, and claims needing proof are named.
Create reusable SEO prompts only after the source data, page URL, live page text, and reviewer have replaceable fields.

Main Risks

Deep research can gather many sources, but the SEO owner still has to check dates, claims, source quality, and whether the final page visibly supports the recommendation.
ChatGPT agent or older Operator-style browser tasks should not change a CMS, submit forms, buy links, modify Search Console, or interact with private accounts unless the person responsible approves the exact action.
Niche edit workflows can become risky when they disguise paid placement, invent endorsements, force unnatural anchors, or ignore sponsored and nofollow choices.
A fluent SEO answer can invent traffic, volume, ranking movement, backlink signals, SERP features, or page facts unless the prompt makes supplied data and assumptions separate.

Recommended Workflow

Choose the mode first: normal prompt for a template, deep research for multi-source synthesis, ChatGPT agent for browser-assisted public page review, and human approval for final SEO changes.
Bring page URL, main search question, current title and description, visible page copy, Search Console rows if available, SERP notes, internal pages, and claims that need proof.
Ask ChatGPT to separate imported data, visible page facts, observed competitor patterns, and recommendations before it writes briefs or snippets.
Run the review pass against the live page: remove invented numbers, unsupported snippet promises, weak anchors, schema ideas not visible on the page, and link suggestions that do not help the reader.
Save prompts by SEO job, not as one broad SEO prompt: brief, title, meta, internal links, refresh, SERP analysis, schema, deep research, browser review, or niche edit review.

Choose the first task by situation

Start with Cluster keyword research when the user has source notes but does not yet know the right output structure, then move to Build content briefs or Write title tags only after the audience and review owner are clear.

Choose by situation

Choose Cluster keyword research when the main problem is shaping raw context into something a search user, editor, or SEO lead can inspect.
Choose Build content briefs when the user already has a first version and needs the next artifact in the same seo specialists loop.
Choose Write title tags when the risk is quality control, review consistency, or a clearer handoff to another person.
Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.

Avoid starting with

Do not start from a broad role prompt when the user already knows the concrete task.
Do not start from a writing prompt when the missing piece is source material or reviewer approval.
Do not reuse a seo specialists prompt across unrelated tasks without changing inputs, constraints, and review checks.

SEO Specialists pages are organized by the decision a person is trying to make, not by a long list of clever prompt phrases. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.

Pick the workflow by decision

Cluster keyword research

Use when the next decision is the shape, review path, or reuse rule for a keyword cluster plan.

Cluster keyword research needs seed keywords, Search Console data, page list, intent notes, and business priority; its review lens is keyword cluster plan quality, intent clusters and source data caveats, and SERP-fit proof, not a generic writing pass.

Build content briefs

Use when the next decision is the shape, review path, or reuse rule for a content brief.

Build content briefs needs main search question, SERP notes, audience, angle, outline, and internal links; its review lens is content brief quality, SERP angle and outline logic, and SERP-fit proof, not a generic writing pass.

Write title tags

Use when the next decision is the shape, review path, or reuse rule for title tag options.

Write title tags needs page topic, primary keyword, search intent, brand rule, and character target; its review lens is title tag options quality, primary query placement and intent match, and SERP-fit proof, not a generic writing pass.

Write meta descriptions

Use when the next decision is the shape, review path, or reuse rule for meta description options.

Write meta descriptions needs page value, main search question, call to action, intent, and length constraint; its review lens is meta description options quality, searcher value and length control, and SERP-fit proof, not a generic writing pass.

Plan internal links

Use when the next decision is the shape, review path, or reuse rule for an internal linking plan.

Plan internal links needs site sections, target URLs, anchor ideas, page priority, and crawl constraints; its review lens is internal linking plan quality, target URL priority and anchor context, and SERP-fit proof, not a generic writing pass.

Refresh existing content

Use when the next decision is the shape, review path, or reuse rule for a content refresh brief.

Refresh existing content needs current page copy, performance data, SERP changes, stale facts, and conversion goal; its review lens is content refresh brief quality, stale sections and ranking loss, and SERP-fit proof, not a generic writing pass.

Analyze SERP intent

Use when the next decision is the shape, review path, or reuse rule for a SERP intent analysis.

Analyze SERP intent needs ranking URLs, result types, query modifiers, user intent clues, and content gaps; its review lens is SERP intent analysis quality, result type mix and intent split, and SERP-fit proof, not a generic writing pass.

Outline schema markup

Use when the next decision is the shape, review path, or reuse rule for a schema markup plan.

Outline schema markup needs page type, visible content, entity details, required properties, and validation target; its review lens is schema markup plan quality, visible content match and entity properties, and SERP-fit proof, not a generic writing pass.

Open a prompt workbench

Review-first run

Cluster Keyword Research: avoid fabricate search volume, rankings, or SERP

A prompt set for keyword research that keeps a keyword cluster plan, intent clusters, source data caveats, page mapping, and priority scoring, and the final human check tied to the same source note. keyword research stays close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, which keeps ChatGPT from drifting into generic advice.

Turn seed keywords, Search Console data, page list, intent notes, and business priority into a keyword cluster plan for a search user, editor, or SEO lead.

Bring first: Need clusters, intent labels, suggested page type, cannibalization notes, and priority. Do not make up volume or rankings. keyword cluster table with page intent needs the source note, output shape, and review owner in the same pass. The answer should protect the real constraint before polish. a keyword cluster plan should use the note as its source. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Build content briefs Write title tags Write meta descriptions

Ready-to-run path

Build Content Briefs: use main search question and SERP notes

Move from a rough content briefs request to a content brief formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. content briefs catches the failure point where the brief can look complete while missing the SERP angle, internal-link target, or claim boundary, because that is where polished answers usually fail.

Turn main search question, SERP notes, audience, angle, outline, and internal links into a content brief for a search user, editor, or SEO lead.

Bring first: Need H2 outline, search intent, must-answer questions, internal links, metadata angle, and what not to claim without local pricing data. Reviewer approval for build content briefs has to compare the first answer with the supplied note. A useful version should keep the task boundary visible. Start build content briefs from the rough request before shaping a content brief. A usable build content briefs input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.

Cluster keyword research Write title tags Write meta descriptions

Ready-to-run path

Write Title Tags: work from organic-search workflow where page intent, sources,

A practical title tags workflow for seo specialists, with variable prompts, a messy-note example, quality checks, and next-step links. title tags treats title option table with intent notes as the asset to check, not as decorative output.

Turn page topic, primary keyword, search intent, brand rule, and character target into title tag options for a search user, editor, or SEO lead.

Bring first: Need 10 options for water heater repair page, primary query near front, under 60 characters if possible, no fake 24/7 claim. In write title tags, the rough note has to lead because role-level advice would flatten the situation. A reviewer needs those notes kept separate from assumptions. Carry the write title tags note into title tag options. For write title tags, paste the source as bullets, constraints, and audience notes so the model has enough shape for copy options grouped by angle, audience, proof point, and revision note.
Reject if: Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.

Cluster keyword research Build content briefs Write meta descriptions

Review-first run

Write Meta Descriptions: prep search user, editor, or SEO lead handoff

A copy-ready meta descriptions workflow that starts with page value, main search question, call to action, intent, and length constraint, produces copy options grouped by angle, audience, proof point, and revision note, and flags what humans must verify. meta descriptions examples stay close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, so the prompt has a real work setting.

Turn page value, main search question, call to action, intent, and length constraint into meta description options for a search user, editor, or SEO lead.

Bring first: Need options around 150 characters, include who the page helps, avoid best/guaranteed claims, and mention comparison criteria. description variants with value and limit checks would be weak without the source details, so the evidence has to stay attached. The prompt should keep the approval point close to the output. SEO Specialists should use the note as the base for meta description options. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Do not use the answer if it hides unsupported claims about real search data, visible page content, and query intent or treats uncertainty as fact.

Cluster keyword research Build content briefs Write title tags

Ready-to-run path

Plan Internal Links: work from organic-search workflow where page intent, sources,

Start the internal links run with the working case, then copy prompts that preserve target URL priority, anchor context, crawl depth, and topical bridge and surface real search data, visible page content, and query intent. internal links treats source-target link map with anchor rationale as the asset to check, not as decorative output.

Turn site sections, target URLs, anchor ideas, page priority, and crawl constraints into an internal linking plan for a search user, editor, or SEO lead.

Bring first: Use page list with URLs, target pages, current anchors, and intent notes. Need link opportunities, anchor suggestions, and cannibalization warnings. In plan internal links, the rough note has to lead because role-level advice would flatten the situation. The working copy should expose what is known and unknown. Carry the plan internal links note into an internal linking plan. For plan internal links, paste the source as bullets, constraints, and audience notes so the model has enough shape for an internal linking plan formatted as clear sections, bullets, and a review checklist.
Reject if: Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.

Cluster keyword research Build content briefs Write title tags

Ready-to-run path

Refresh Existing Content: avoid fabricate search volume, rankings, or SERP

A refresh existing content page for people who need a content refresh brief, not loose advice: source prep, examples, prompts, and review steps. refresh existing content stays close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, which keeps ChatGPT from drifting into generic advice.

Turn current page copy, performance data, SERP changes, stale facts, and conversion goal into a content refresh brief for a search user, editor, or SEO lead.

Bring first: Need refresh brief from current page, GSC queries, competitor notes, outdated claims, internal links, and what not to change. refresh brief with stale-section notes needs the source note, output shape, and review owner in the same pass. A practical answer should keep the handoff decision visible. a content refresh brief should use the note as its source. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Cluster keyword research Build content briefs Write title tags

Review-first run

Analyze SERP Intent: prep search user, editor, or SEO lead handoff

A prompt workbench for analyze serp intent, covering ranking URLs, result types, query modifiers, user intent clues, and content gaps, a structured analysis table with claims, evidence, gaps, and recommended next step, review checks, and follow-up fixes. analyze serp intent examples stay close to an organic-search workflow where page intent, sources, and handoff details decide usefulness, so the prompt has a real work setting.

Turn ranking URLs, result types, query modifiers, user intent clues, and content gaps into a SERP intent analysis for a search user, editor, or SEO lead.

Bring first: Need result type summary, recurring sections, PAA themes, missing proof, local intent clues, and content risks. No volume or rank claims. SERP pattern table with page-type gaps would be weak without the source details, so the evidence has to stay attached. A usable first pass has to preserve those constraints. SEO Specialists should use the note as the base for a SERP intent analysis. Before seo specialists run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Do not use the answer if it hides unsupported claims about real search data, visible page content, and query intent or treats uncertainty as fact.

Cluster keyword research Build content briefs Write title tags

Ready-to-run path

Outline Schema Markup: work from organic-search workflow where page intent, sources,

Use this page when schema markup needs page type, visible content, entity details, required properties, and validation target, a clear output shape, and a review pass before sharing with a search user, editor, or SEO lead. schema markup treats schema property checklist tied to visible content as the asset to check, not as decorative output.

Turn page type, visible content, entity details, required properties, and validation target into a schema markup plan for a search user, editor, or SEO lead.

Bring first: Need schema recommendation, required fields, visible-content match check, JSON-LD example, and validation checklist. Do not invent reviews. In outline schema markup, the rough note has to lead because role-level advice would flatten the situation. The answer should show which details still need checking. Carry the outline schema markup note into a schema markup plan. For outline schema markup, paste the source as bullets, constraints, and audience notes so the model has enough shape for a schema markup plan formatted as clear sections, bullets, and a review checklist.
Reject if: Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.

Cluster keyword research Build content briefs Write title tags

Where to go next

Cluster keyword researchCluster keyword research fits when the next decision is the shape, review path, or reuse rule for a keyword cluster plan. Keep it separate because cluster keyword research needs seed keywords, Search Console data, page list, intent notes, and business priority; its review lens is keyword cluster plan quality, intent clusters and source data caveats, and SERP-fit proof, not a generic writing pass.Build content briefsBuild content briefs fits when the next decision is the shape, review path, or reuse rule for a content brief. Keep it separate because build content briefs needs main search question, SERP notes, audience, angle, outline, and internal links; its review lens is content brief quality, SERP angle and outline logic, and SERP-fit proof, not a generic writing pass.Write title tagsWrite title tags fits when the next decision is the shape, review path, or reuse rule for title tag options. Keep it separate because write title tags needs page topic, primary keyword, search intent, brand rule, and character target; its review lens is title tag options quality, primary query placement and intent match, and SERP-fit proof, not a generic writing pass.Write meta descriptionsWrite meta descriptions fits when the next decision is the shape, review path, or reuse rule for meta description options. Keep it separate because write meta descriptions needs page value, main search question, call to action, intent, and length constraint; its review lens is meta description options quality, searcher value and length control, and SERP-fit proof, not a generic writing pass.Plan internal linksPlan internal links fits when the next decision is the shape, review path, or reuse rule for an internal linking plan. Keep it separate because plan internal links needs site sections, target URLs, anchor ideas, page priority, and crawl constraints; its review lens is internal linking plan quality, target URL priority and anchor context, and SERP-fit proof, not a generic writing pass.Refresh existing contentRefresh existing content fits when the next decision is the shape, review path, or reuse rule for a content refresh brief. Keep it separate because refresh existing content needs current page copy, performance data, SERP changes, stale facts, and conversion goal; its review lens is content refresh brief quality, stale sections and ranking loss, and SERP-fit proof, not a generic writing pass.How to Use ChatGPT for SEO SpecialistsUse this when the user needs a role-level workflow before opening a single task page.