10 Claude Workflows for GEO: The Prompts to Track and Win AI Citations
Ten scheduled tasks in Claude that track your AI citations, find the gaps and draft the fixes. Every prompt is here, ready to copy, with the setup and the limits.
The answer
Generative engine optimization (GEO) gets your business named and cited in AI answers. You can run it with 10 scheduled tasks in Claude, one prompt each. The tasks track citations, find gaps, fix wrong facts and draft better pages. Check often: ChatGPT Search replaced 74% of its cited domains every week (SISTRIX, 2026). All 10 prompts are below.
A popular post listed these 10 workflows by name. It did not give the prompts. This guide gives you each prompt, the setup, a schedule and the limits that the post left out.
Why does GEO need a scheduled check?
AI answers change every week, so a check once a quarter misses most of the change. SISTRIX measured this in its study AI Citation drift: How stable are sources in AI search results? (Johannes Beus, May 1, 2026). The team tracked 82,619 prompts in six countries for 17 weeks, from December 17, 2025 to April 8, 2026. That gave 1,548,213 snapshots of AI answers. Then they compared the cited domains from week to week.
- ChatGPT Search
- 74%
- Google AI Mode
- 56%
- Google AI Overviews
- 5%
In AI Overviews, the sources for 53% of prompts did not change in 17 weeks. ChatGPT Search and AI Mode changed most of their sources every week.
Two more findings from the same study matter for a business:
- Your own site is not safe. For only 43% of brand questions, the brand's own domain appeared in all 17 weeks.
- The pages around you change fastest. The other domains cited next to a brand changed by about 70% each week.
AI answers also change from one run to the next. SparkToro and Gumshoe.ai ran 2,961 prompts through ChatGPT, Claude and Google's AI in Search, in November and December 2025. Search Engine Journal reported the results on January 30, 2026. ChatGPT and Google's AI gave the same list of brands less than 1 time in 100. The same list in the same order came back less than 1 time in 1,000. But strong brands still appeared often: four headphone brands showed up in 55% to 77% of the answers.
So do not track an "AI rank." Track your mention share: the share of many answers that name you. That is why workflow 1 asks each question three times per engine.
Two limits apply to this data. SISTRIX sells search data, and its ChatGPT numbers cover only prompts with a stable source list. Gumshoe.ai sells AI tracking, and the SparkToro study is not peer reviewed. Both studies show the same pattern: AI answers move fast.
Do most marketers track AI visibility today?
Many marketers check it, but few track it in a system. In a Semrush study of 481 marketers, business owners and SEO professionals (June 3, 2026):
- 40% check whether their brand appears by typing prompts into AI tools by hand.
- 13% have no consistent approach.
- 45% find it hard to measure their visibility in AI answers.
- Only 9% can measure all the metrics that matter to them.
A manual check gives you one answer from one day. The data above shows why that answer can be wrong a week later. A scheduled task asks the same questions every day and keeps the record.
Your buyers already use these tools. In the BrightLocal Local Consumer Review Survey 2026, 45% of 1,002 US adults used ChatGPT or other AI tools to find local businesses. In 2025, the figure was 6%.
How do you set up the workflows in Claude?
Make one log, fill in one context block, then make one scheduled task for each prompt. Scheduled tasks in Claude run in the cloud on a schedule that you set: hourly, daily, weekdays or weekly. Each run starts a new session, so each prompt must hold all the context that it needs. The Claude Help Center lists the plans and the setup steps.
What you need
- A paid Claude plan. Scheduled tasks are on the Pro, Max, Team and Enterprise plans.
- Google Drive, connected to Claude. The tasks write to one Google Sheet and save drafts as Google Docs.
- A way to get answers from each engine. Claude cannot read a ChatGPT or Perplexity answer unless you give it a way. Pick one option from the table.
| Engine access | How it works | Trade-off |
|---|---|---|
| AI visibility tool | Connect a tracking tool to Claude. For example, Profound has a Claude connector. | Most reliable. The tool has a monthly cost. |
| Claude in Chrome | Claude opens each engine in your Chrome browser and asks the questions. | No extra cost. The task runs only when your computer is on, and it is slower. |
| Engine APIs | Your own script asks the questions through each engine's API and writes the answers to the log. | Needs a developer. API answers can differ from the answers that people see in the apps. |
The log
Make one Google Sheet with seven tabs. You fill in the first two. The workflows fill in the rest.
| Tab | Filled in by | What it holds |
|---|---|---|
| Questions | You | 10 to 30 questions that your buyers ask AI tools, one per row |
| Facts | You | True facts about your business: name, address, phone, prices, services, founder and service area |
| Citations | Workflow 1 | One row per answer: engine, question, named, cited, URLs and competitors |
| Coverage | Workflow 2 | Each question as Covered, Weak or Missing, with the best page |
| Sources | Workflow 4 | Third-party domains that the engines cite, and the next action for each |
| Competitors | Workflow 7 | Mention share and citation share for each brand, week by week |
| Entity | Workflow 5 | Wrong or missing facts in AI answers, and where to fix them |
The steps
- Make the Google Sheet. Add your questions and your facts.
- Type your details in the fields above the prompts. The prompts on this page update.
- In Claude, open Scheduled in the sidebar and make a new task. Or type
/schedulein a chat. - Click Copy task prompt for a workflow. Paste it into the task. The copy has the context block on top.
- Run the task one time by hand. Check the rows in the log. Fix the prompt if a field is wrong.
- Set the schedule from the table below. Then do the next workflow.
Start small. 10 questions, 2 engines and 3 runs give 60 answers a day. 30 questions, 4 engines and 3 runs give 360. Large runs use more of your Claude usage and more of your tracking tool's credits. Add questions and engines after the first month.
The schedule
| Workflow | When | Needs |
|---|---|---|
| 1. AI citation tracker | Daily | Engine access |
| 2. Prompt-coverage check | Weekly, Monday | Workflow 1 log |
| 3. Answer-gap finder | Weekly, Wednesday | Web search |
| 4. Source-authority map | Monthly | Workflow 1 log |
| 5. Entity audit | Monthly | Engine access |
| 6. llms.txt builder | Monthly | Website access |
| 7. Competitor-mention pull | Weekly, Monday | Workflow 1 log |
| 8. Freshness watch | Daily, after workflow 1 | Workflow 1 log |
| 9. Quotable-rewrite pass | Weekly, Thursday | Workflows 1 and 2 logs |
| 10. Weekly visibility report | Weekly, Monday, last | All logs |
Run workflow 8 one hour after workflow 1. On Mondays, run workflow 10 last, after workflows 2 and 7.
What are the 10 prompts?
Each prompt is one scheduled task. Each task also needs the context block on top. The context block holds your brand facts and the rules. The rules stop Claude from publishing, sending or guessing.
The context block
Fill in this block once. Each scheduled run starts with no memory of the last run, so every task needs it.
## Context
- Brand: [BRAND]
- Website: [WEBSITE]
- Category: [CATEGORY]
- Our buyers: [BUYERS]
- Competitors: [COMPETITORS]
- Engines: ChatGPT, Perplexity, Google AI Mode, Claude
- Engine access: [ENGINE ACCESS]
- Log: the Google Sheet "[LOG]". Tabs: Questions, Facts, Citations, Coverage, Sources, Competitors, Entity.
- Questions: the tab "Questions" has one buyer question per row.
- Facts: the tab "Facts" has one true fact about [BRAND] per row: name, address, phone, prices, services, founder and service area.
## Rules
- Do not publish, post, send or upload anything. Write drafts and log rows only.
- Do not change or delete old rows in the log. Add new rows.
- Give the URL for every source that you use.
- Do not guess. If you cannot get an answer, write "no data" and say why.
- Do not invent numbers, quotes, customers or results.
1. AI citation tracker
Asks each engine your buyer questions every day. Logs where AI names or cites you, and where it names a competitor in your place.
Run the daily AI citation check.
1. Read the tab "Questions".
2. Ask each engine each question 3 times. AI answers change from run to run, so one run is not enough.
3. For each run, record these fields:
- date, engine, question, run number (1 to 3)
- named: "yes" if the answer names [BRAND], else "no"
- cited: "yes" if the answer links to a page on [WEBSITE], else "no"
- the [BRAND] URLs that the answer cites
- all other URLs that the answer cites
- the competitors that the answer names
4. Add one row per run to the tab "Citations".
5. Calculate today's mention share for [BRAND]: the runs that name [BRAND], divided by all runs. Calculate it for each engine and for all engines. Do the same for each competitor.
6. List the lost questions: questions where the answer names a competitor and does not name [BRAND].
7. End with a summary of 5 lines or less: the total mention share, the best engine, the worst engine, the top 3 lost questions with the competitor that won each one, and each engine that you could not reach.
2. Prompt-coverage check
Takes your buyer questions and flags each question where the AI answer never names you.
Run the weekly prompt coverage check.
1. Read the rows from the last 7 days in the tab "Citations".
2. For each question, calculate the mention share for [BRAND] across all engines and runs.
3. Give each question one status:
- Covered: the answers name [BRAND] in 50% of runs or more.
- Weak: the answers name [BRAND] in 1% to 49% of runs.
- Missing: the answers never name [BRAND].
4. For each Weak or Missing question, find the page on [WEBSITE] that answers it best. Use [WEBSITE]/sitemap.xml. If no page answers it, write "no page".
5. Add one row per question to the tab "Coverage": week, question, mention share, status, best page, and the competitor that the answers name most often.
6. End with a summary: the count of Covered, Weak and Missing questions, and the 5 Missing questions that are closest to a decision to buy.
3. Answer-gap finder
Finds the questions about your category that AI tools answer badly. Each gap becomes the brief for your next page or post.
Find the questions about [CATEGORY] that AI tools answer badly.
1. Make a list of 20 questions that buyers ask about [CATEGORY] and that are not in the tab "Questions". Use web search results, "People also ask" boxes, Reddit and forum threads, and review sites. Write each question in the words that a buyer uses.
2. Ask 2 engines each question one time.
3. Score each answer from 1 to 5 on each of these 4 tests:
- Correct: the facts are true.
- Specific: the answer gives names, numbers and steps, not general advice.
- Current: the facts are from the last 12 months.
- Sourced: the answer cites a strong source.
4. Mark an answer as a gap if its total score is 12 or less, or if it has a wrong fact, an old price or no source.
5. For the 5 biggest gaps, write a content brief:
- Title: the question, in the buyer's words.
- What the AI answers get wrong or leave out.
- A draft answer of 40 to 60 words for [BRAND] to check. Mark each claim that needs a source.
- The proof that we need: data, examples, quotes or our own results.
- 4 to 6 related questions for an FAQ.
6. Save the 5 briefs in one Google Doc named "Answer gaps [date]".
7. List the other questions that fit what [BRAND] sells. Do not add them to the tab "Questions". I decide which questions to track.
4. Source-authority map
Shows which third-party pages the engines cite for your category, so you know where to get mentioned.
Map the third-party pages that AI engines cite for [CATEGORY].
1. Read the rows from the last 30 days in the tab "Citations". List each cited URL that is not on [WEBSITE] and not on a competitor's website.
2. Group the URLs by domain. For each domain, count the questions and the engines that cite it.
3. Give each domain one type: review site, directory, list article, forum, video, news, Wikipedia, industry group, or other.
4. For the top 20 domains, open the cited pages. Record whether each page names [BRAND], and which competitors it names.
5. For each top domain that does not name [BRAND], write one next action. Examples: claim a listing, ask the author to review [BRAND] for a list article, answer a forum thread with real help, offer data to a writer, or ask customers for reviews. Do not suggest paid links or fake reviews.
6. Add the results to the tab "Sources" with this month's date: domain, type, citation count, engines, names [BRAND] (yes or no), competitors named, next action.
7. End with the 5 domains where one action can bring the most citations.
5. Entity audit
Checks how AI engines describe your brand, and flags each wrong fact with the place to fix it.
Check how AI engines describe [BRAND].
1. Ask each engine these 6 questions, with no other context:
- What is [BRAND]?
- What does [BRAND] sell, and what does it cost?
- Who is [BRAND] for?
- Where is [BRAND], and who runs it?
- What do customers say about [BRAND]?
- What are the best alternatives to [BRAND]?
2. Compare each answer with the tab "Facts".
3. Mark each claim in each answer as correct, wrong, out of date, or missing. For each wrong claim, copy the exact words and name the engine.
4. For each wrong or out-of-date claim, find the source that the engine cites. If the engine shows no source, write "no source shown".
5. For each problem, write the fix and the place to make it: a page on [WEBSITE], a profile (Google Business Profile, LinkedIn, Crunchbase, review sites, directories), or the schema on the home page.
6. Add the results to the tab "Entity" with today's date.
7. End with the 3 wrong facts that can cost [BRAND] a sale, and the fix for each.
6. llms.txt builder
Writes and checks your llms.txt file, then checks that your brand facts match on every page. Few AI crawlers read llms.txt today, so the fact check is the main value.
Build and check the llms.txt file for [WEBSITE].
Note: Few AI crawlers request llms.txt today. Keep this task small. The facts on the pages of [WEBSITE] and in its schema matter more.
1. Read [WEBSITE]/sitemap.xml. Then read the home page, the About page, the pricing page, the service pages and the contact page.
2. Write a draft llms.txt in the format from llmstxt.org:
- An H1 with the brand name.
- A summary of one sentence in a blockquote.
- 5 to 10 short facts: what [BRAND] sells, for whom, where, the prices if they are public, and how to make contact.
- H2 sections with links. Add only the pages that a buyer needs: services, pricing, proof, FAQ and contact. Give each link one plain sentence.
3. If [WEBSITE]/llms.txt exists, compare it with your draft. List the links that return an error, the pages that are missing, and the facts that changed.
4. Check that these facts match in 4 places: the llms.txt draft, the About page, the Organization schema on the home page, and the tab "Facts". The facts are: name, address, phone, prices, founder and service area. List each mismatch.
5. Save the draft in Google Drive as "llms.txt draft [date]". Do not upload it to the website.
6. End with a summary: what changed since last month, and each mismatch to fix.
7. Competitor-mention pull
Lists the sources that the engines cite for your category, and shows which competitor wins each one.
Run the weekly competitor mention report.
1. Read the tab "Citations". Use 2 periods: the last 7 days, and the 7 days before that.
2. For [BRAND] and each competitor, calculate these values for each period:
- Mention share: the runs that name the brand, divided by all runs.
- Citation share: the runs that cite the brand's website, divided by all runs.
- The 5 questions where the answers name the brand most often.
3. For each competitor, list the sources that the engines cite when they name that competitor. Mark each source that does not name [BRAND].
4. Compare the 2 periods. Flag each brand whose mention share went up or down by 10 points or more. Flag each brand that is not in the competitor list and that appears in 3 answers or more.
5. Open the page that won the biggest new citation for a competitor. In 3 sentences, say what the page gives that our page does not: a direct answer, data, a newer date, a comparison, or a strong source.
6. Add the results to the tab "Competitors" with this week's date.
8. Freshness watch
Flags the day that your citation drops out of an answer, with the page that replaced you.
Run the daily freshness watch. Run this task after the daily AI citation check.
1. Read the tab "Citations" for today and for the 7 days before today.
2. Find each drop. A drop is a question and an engine where both of these are true:
- The answers named or cited [BRAND] in 50% of runs or more over the 7 days before.
- The answers did not name or cite [BRAND] in any run today or yesterday.
Use 2 days, not 1, because AI answers change from day to day.
3. For each drop, record the engine, the question, the [BRAND] URL that the answers cited before, and the URLs that the answers cite now.
4. Open the [BRAND] URL. Check that the page loads, that it does not have a noindex tag, and that robots.txt does not block it. Note the date that the page shows.
5. Open the top URL that replaced it. Note its date and what it answers that our page does not.
6. If there is one drop or more, start your result with "ALERT: [number] citation drops" and list them. If there are no drops, write only "No drops today."
9. Quotable-rewrite pass
Drafts a rewrite of each slipping page, so it gives the clear answer that an engine can quote. You approve every change.
Draft rewrites for the pages that lose AI citations.
1. Read the tabs "Coverage" and "Citations". Pick 3 pages on [WEBSITE]. First pick pages with a drop in the last 7 days. Then pick the best pages for Weak questions.
2. For each page, read the full page. Then read the top 2 pages that the engines cite in its place.
3. Write a new draft of the page in this order: answer, explain, prove, expand.
- Answer: put a direct answer of 40 to 60 words under the H1.
- Make each H2 a question. Answer it in the first sentence under the heading.
- Prove: give each main claim a number with its source, its date and its sample. Use only sources that you can link.
- Where the page needs our own data, write [ADD OUR DATA: what is needed]. Do not invent numbers, quotes, customers or results.
- Use the names of the brand, the product and the place. Do not use "it" or "this" when the subject is not clear.
- Expand: add 4 to 6 FAQ questions with answers of 2 to 4 sentences, and FAQPage schema that matches them.
4. Keep the URL, the search intent of the title and the brand voice. Keep every true fact from the old page.
5. Save each draft as a Google Doc named "Rewrite: [page title]". Put a list of the changes at the top.
6. Do not publish. End with the 3 doc links and the question that each rewrite targets.
10. Weekly visibility report
Shows your citation share across the engines and gives you three moves for next week.
Write the weekly AI visibility report.
1. Read the tabs "Citations", "Coverage", "Sources", "Competitors" and "Entity".
2. Write a report of one page in a Google Doc named "AI visibility report [date]":
- First line: one sentence with the change in mention share and the top move. Example: "Mention share went from 18% to 23%. Top move: update the pricing page."
- A table: mention share and citation share for this week and last week, for each engine and for all engines, for [BRAND] and each competitor.
- Wins: the questions where the answers name [BRAND] now and did not name it last week.
- Losses: the questions where [BRAND] dropped out, with the page that replaced it.
- Open problems: the wrong facts from the tab "Entity" that are not fixed.
- 3 moves for next week. For each move, name the page or the source, the action, and the question that it targets. Rank the moves by the gain that you expect for the work.
3. Use only numbers from the log. If an engine has no data this week, say so.
What are the limits of these workflows?
The workflows measure and draft. People still decide, publish and earn the mentions. The popular post said that the workflows run without you. They do run on their own, but every result needs a person to act on it. Keep these limits in mind:
- llms.txt has little proof behind it. In an Ahrefs study of 137,210 domains (June 15, 2026), 97% of llms.txt files got no requests in May 2026. Search bots from OpenAI and Perplexity almost never asked for the file. Google's guide for its AI features says that you do not need it. So workflow 6 keeps the file small and spends its effort on the fact check.
- There is no AI rank. Answers change from run to run. Report mention share across many runs. Treat a change of less than 10 points in one week as normal movement, not as a trend.
- Engine access costs money or time. A tracking tool has a fee. Claude in Chrome needs your computer to be on. APIs need a developer.
- Drafts are not fixes. Workflow 9 drafts rewrites. A person must check the facts, add your own data and publish. Workflow 4 finds the sources. A person must earn the mention.
- Small samples are noisy. Three runs per question is a minimum. For a decision with a budget, look at a month of data, not one day.
Why does this matter for your leads?
A buyer who asks an AI tool gets a short list of names. If your name is not on it, you do not get the call. The buyer may never see a page of links or an ad. The answer is the shortlist.
AI visibility is one of the fastest places to start, because the first fixes are often small. A profile with an old price. A service page that does not answer the question in its first sentence. A list article that names three competitors and not you. Workflows 4, 5 and 9 find these problems for you. You do not need a new website or a bigger ad budget to fix them.
Start here:
- See where you stand. Run the free AI Visibility Score. It runs 37 checks on your home page in about 20 seconds.
- Copy the prompts. Start with workflows 1, 5 and 10. Add the others in the second week.
- Get help with the fixes. Our fractional AI Search & Content Growth Marketer runs these workflows and makes the fixes every week. To start with your home page, see Done For You.
Common questions
What is GEO?
GEO means generative engine optimization. It is the work that gets your business named and cited in answers from AI tools such as ChatGPT, Perplexity, Google AI Mode and Claude. It covers your own pages, your brand facts and the third-party pages that AI tools cite.
Can Claude check what ChatGPT and Perplexity say about my business?
Yes, if you give Claude a way to reach them. You have three options. Connect an AI visibility tool to Claude. Let Claude use your Chrome browser on a computer that is on. Or call the engines' APIs from your own script. Without one of these, a scheduled task can only search the web as Claude.
How often should I check my AI citations?
Check every day, and report every week. SISTRIX found that ChatGPT Search replaced 74% of its cited domains every week, and Google AI Mode replaced 56%. Ask each question several times per check, because AI answers change from run to run.
Does an llms.txt file help AI visibility?
There is little proof that it does. Ahrefs found that 97% of llms.txt files got no requests in May 2026. Google says that its AI features do not need the file. Keep the file small, and spend more time on the facts on your pages and profiles.
How many buyer questions should I track?
Start with 10 to 30 questions. Write them in the words that your buyers use. Include questions that lead to a purchase, such as comparisons, prices and the best option near a place. Add more questions after the first month.
Do these workflows change my website?
No. Each prompt tells Claude not to publish, post, send or upload anything. The workflows write log rows, briefs, a draft llms.txt file and draft rewrites. A person checks each draft and then makes the change.
Sources
- Johannes Beus, AI Citation drift: How stable are sources in AI search results?, SISTRIX, May 1, 2026.
- Rand Fishkin and Patrick O'Donnell, research on AI brand recommendations, SparkToro and Gumshoe.ai, January 2026. Summary: Search Engine Journal, January 30, 2026.
- Margarita Loktionova, Only 22% of marketers have fully integrated AI search and SEO, Semrush, June 3, 2026.
- Louise Linehan, We Analyzed 137K Sites: 97% of llms.txt Files Never Get Read, Ahrefs, June 15, 2026.
- Google Search Central, Optimizing your website for generative AI features on Google Search, updated July 10, 2026.
- BrightLocal, Local Consumer Review Survey 2026 (our summary), February 11, 2026.
- Claude Help Center, article on scheduled tasks, checked October 26, 2026.
- Profound, Connect the Profound MCP server, checked October 26, 2026.
- Jeremy Howard, The /llms.txt file (proposal and format), llmstxt.org.