Seo Flow

FLOW Framework — Find · Leverage · Optimize · Win

Shared Data Cache

Step 0 -- Check shared data cache:

Before gathering, check .seo-cache/ for reusable context from related SEO skills. Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.

Check these cache files when present:

• .seo-cache/site-meta.json for domain, business type, industry, and crawl context
• .seo-cache/audit-scores.json for prior full-audit priorities
• .seo-cache/pages/{url-slug}/page-analysis.json for page-level context when a URL is provided

• If found: parse and use clearly valid fields (note "Using cached [X] from [date]")
• If missing, corrupt, or irrelevant: continue with fresh evidence
• If the user says "refresh" or "re-run": ignore cache reads and overwrite on write

Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow

FLOW is an evidence-led SEO operating model built for the AI-search era. Codex SEO integrates the FLOW prompt library (41 prompts across 5 stages) so every analysis can be driven by structured, evidence-backed AI prompts rather than improvised queries.

Runtime context: Load references/flow-framework.md on every /seo flow activation. Load prompt files on demand — only for the stage the user requests.

---

Commands

---

Orchestration Logic

On /seo flow (no sub-command)

1. Read references/flow-framework.md 2. Show the FLOW stage overview with a one-line description of each stage 3. Ask: which stage matches the user's current situation?

On /seo flow find [url|topic]

1. Read all files in references/prompts/find/ 2. Apply each prompt to the URL or topic 3. Cross-reference: "For deeper SERP clustering, see /seo cluster <seed-keyword>"

On /seo flow leverage [url]

1. Read the file in references/prompts/leverage/ 2. Apply to the URL's current backlink context 3. Cross-reference: "For raw backlink data, see /seo backlinks <url>"

On /seo flow optimize [url]

1. Read all file names in references/prompts/optimize/ 2. Read prior analysis context (URL, industry vertical, any prior skill output in conversation) 3. Select 2-3 most relevant prompts; load only those files 4. Apply selected prompts; note the others are accessible via /seo flow prompts 5. Cross-reference: "For full content quality analysis, see /seo content <url> and /seo geo <url>"

On /seo flow win [url]

1. Read all files in references/prompts/win/ 2. Apply each prompt to the URL's conversion and BOFU context 3. Cross-reference: "For SXO persona scoring, see /seo sxo <url>"

On /seo flow local [url]

1. Read all files in references/prompts/local/ 2. Apply to the URL's local SEO context 3. Cross-reference: "For full local SEO analysis, see /seo local <url> and /seo maps [command]"

On /seo flow prompts

1. Read references/prompts/README.md 2. Display the full index: all 41 prompts with stage, name, trigger conditions

On /seo flow sync

1. Run: python scripts/sync_flow.py 2. Display the JSON summary (files added, updated, unchanged) 3. Show attribution notice after sync completes

---

Context Matching (Optimize stage)

The optimize stage has 21 prompts. Dumping all 21 is noise. Select by priority:

1. Industry vertical (SaaS → on-page + technical; local → citations + GBP; publisher → E-E-A-T + freshness) 2. Prior skill output (seo-technical flagged crawl issues → technical optimize prompts; seo-content flagged E-E-A-T gaps → content optimize prompts) 3. URL signals (product pages → conversion; blog → freshness + authority)

Always surface exactly 2-3 prompts. State which prompts you chose and why.

---

Reference Files

Load on-demand — do NOT load all at startup:

• references/flow-framework.md — FLOW operating model (load on every /seo flow activation)
• references/bibliography.md — Evidence sources; load when citing studies or statistics
• references/prompts/README.md — Prompt index; load for /seo flow prompts
• references/prompts/find/ — 5 prompts; load for /seo flow find
• references/prompts/leverage/ — 1 prompt; load for /seo flow leverage
• references/prompts/optimize/ — 21 prompts; load selectively for /seo flow optimize
• references/prompts/win/ — 3 prompts; load for /seo flow win
• references/prompts/local/ — 11 prompts; load for /seo flow local

---

Attribution

Every /seo flow activation (any sub-command) outputs before analysis:

Framework and prompts © Daniel Agrici, CC BY 4.0 — github.com/AgriciDaniel/flow

Do not omit or modify the attribution.

---

Error Handling

Write to shared data cache

After completing all work, write a concise JSON summary to .seo-cache/ when the workflow produced durable findings. Use the schemas and naming rules in ../seo/references/shared-data-cache.md; include at least cache_type, analyzed_at, source URL/domain, key findings, issues, recommendations, and tool limitations. Add .seo-cache/ to .gitignore if it is missing.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Bibliography" description: "Bibliography" updated: 2026-04-25 tags:

• references

---

Bibliography

This bibliography lists the sources used for public claims. Web sources include retrieval date. PDF sources include hash and page count from the canonical manifest.

Web Sources

• https://ahrefs.com/blog/ai-overviews-reduce-clicks-update/ | retrieved 2026-04-25 | used for: 58% lower average CTR for position-one content when an AI Overview is present, using December 2025 Ahrefs data
• https://backlinko.com/google-user-behavior | retrieved 2026-04-25 | used for: 42% of local-query searchers click inside the Google Maps Pack
• https://gs.statcounter.com/search-engine-market-share/all/worldwide/2025 | retrieved 2026-04-25 | used for: Bing March 2026 share: 5.13% worldwide; 9.85% United States all-platform search share
• https://support.google.com/business/answer/10515606?hl=en | retrieved 2026-04-25 | used for: 70% more likely to visit; 50% more likely to consider purchasing
• https://www.brightlocal.com/resources/local-seo-statistics/ | retrieved 2026-04-25 | used for: 39%
• https://www.pewresearch.org/short-reads/2025/07/22/google-users-are-less-likely-to-click-on-links-when-an-ai-summary-appears-in-the-results/ | retrieved 2026-04-25 | used for: 8% with AI summary vs 15% without AI summary
• https://www.searchenginejournal.com/state-of-seo/ | retrieved 2026-04-25 | used for: 77.9% worry about AI reducing website clicks
• https://www.sec.gov/Archives/edgar/data/1652044/000165204426000018/goog-20251231.htm | retrieved 2026-04-25 | used for: 73.2% of FY2025 revenue from Google advertising: $294.691B / $402.836B
• https://www.semrush.com/blog/semrush-ai-overviews-study/ | retrieved 2026-04-25 | used for: 33.75% to 31.53%
• https://www.seoclarity.net/research/analysis-of-top-cited-pages-from-chatgpt | retrieved 2026-04-25 | used for: 25% of top 1,000 cited URLs have zero organic visibility in Google

PDF Sources

• PPC_Trends_2026.pdf | tier A | pages 30 | sha256 609cbad8786070cf40290a86bdc9c16d5c5530b0460b91eb9f82fc14fe4d8122 | action: extract-and-consider
• SEJ_LeveragingGenerativeAI_F.pdf | tier C | pages 86 | sha256 26985b1ebdbd1b725b3a78bd4b26bd576c89dab7fdd19c4dfed06f8e697bda4c | action: extract-and-consider
• SEJ_SEOInTheAgeOfAI_F.pdf | tier C | pages 78 | sha256 a7142071e46c7461ef263ed5ac7da0e343f83d900e9c3ea74b18e05c8364311f | action: extract-and-consider
• SEJ_State_of_AI_in_Marketing_F.pdf | tier C | pages 13 | sha256 c099f7700d58b40f8c55e408c58f65f71ad5bc8981d266d3701363308cebb9af | action: extract-and-consider
• SEJ_StateofSEO2026.pdf | tier A | pages 31 | sha256 4cf17f9eb89a911ab17a9faf90f3d0069af8e4acc12a77d86023d0b318577791 | action: extract-and-consider
• SEJ_UX&SEO.pdf | tier C | pages 24 | sha256 8ac6a00e5cc1763191d852072d0f8e4223598a7c61ce52b84834840ba02850b9 | action: extract-and-consider
• SEO Books/CallRail_X_SEJ_BetterLeadsMoreSales_2025.pdf | tier B | pages 20 | sha256 1126aa175b8486dbe36bc6dcd83728cc2e93505545d11d6f16568ac90ef2e733 | action: extract-and-consider
• SEO Books/Hobo-Beginner-SEO-2025.pdf | tier B | pages 52 | sha256 eb16d509a75235adc0bdb3bf6e49d4e57044053a409f657c219dacea10da3355 | action: extract-and-consider
• SEO Books/Hobo-Strategic-AiSEO-2025.pdf | tier B | pages 294 | sha256 7885d7bd3cbe4e480c018b97640119f94d7f20744bcbfeb24ba9efee34f1442f | action: extract-and-consider
• SEO Books/SEJ_B2B_Lead_Generation_F.pdf | tier C | pages 61 | sha256 12bf9f5317fcc91bc94cf720f3a7522422526468c240691392054b408c7b9075 | action: extract-and-consider
• SEO Books/SEJ_PPC_Experts_Tips_2023.pdf | tier D | pages 57 | sha256 4d3a4db69556115b25f5bda9afc1ccb5affbdfbd419691ec99f998510329fee8 | action: extract-and-consider
• SEO Books/SEJ_SEO_Audit_2023.pdf | tier D | pages 76 | sha256 965ed0e620cd5624815530d8f7609d1d9ba44968da8189e3589f18224ebeab87 | action: extract-and-consider
• SEO Books/SEJ_TheDarkSideofLinkBuilding.pdf | tier C | pages 59 | sha256 cfa4c81c58d431923dce81ce2b3afb4c5e6db0fdd3a7aca6117c49b7e1eb1d65 | action: extract-and-consider
• SEO Books/SEJ_The_Future_of_AI_Search_F.pdf | tier C | pages 17 | sha256 4032124fd73160ae008e7d8598090c46b230641095fd2acb46c97b282c21bd43 | action: extract-and-consider
• SEO Press/10_tips_boost_site_speed-en.pdf | tier E | pages 11 | sha256 f9e07b750e738362ea624f2485a5c767d8db0c7bae61e9cb0f53d79cd7054c6b | action: skip-by-default
• SEO Press/ai-seo-copywriting-seopress-en.pdf | tier E | pages 59 | sha256 89683c171d379c6e6305d34e83da12d4b67a9ff5a31675246cca9d0c2f7f244c | action: skip-by-default
• SEO Press/ebook-seopress-beginners-guide-to-seo.pdf | tier E | pages 67 | sha256 cee1d0948ad1f03f90ef35db3dc2948c455f74c847424bab28d0edd1336743db | action: skip-by-default
• SEO Press/ebook-seopress-guide-local-seo-en.pdf | tier E | pages 37 | sha256 bd27e4dfb7af6fcd9b68f3a99e6df502ca4f75d896ba0ef0fd05e70e27250199 | action: skip-by-default
• SEO Press/ebook-seopress-guide-schemas-en.pdf | tier E | pages 39 | sha256 5a39a137e3a563ac73607fc8349d6f0dee7ffb1d5206f5583a28c4fc7213d076 | action: skip-by-default
• SEO Press/emergency-seo-en.pdf | tier E | pages 44 | sha256 51bfb7eb0fc2cfb5fb4f77bea2493c21b3287a4c3edfb96c3d5c28a06244d39c | action: skip-by-default
• SEO Press/first-site-seo-en.pdf | tier E | pages 58 | sha256 0ac67cbc71193da57226f8be8b253d5d84519504cc47cb865424403509dd2399 | action: skip-by-default
• SEO Press/google-search-console-en-compress.pdf | tier E | pages 49 | sha256 0a768cb025fba68afdea8786c35eec8f4c197d83f1516e926a3906dc99d45d65 | action: skip-by-default
• SEO Press/link_building_with_wp-en.pdf | tier E | pages 41 | sha256 27b5378f29807705ae86e86908d66074316f9914ef0b69438619bd8250fea3f3 | action: skip-by-default
• SEO Press/more-visibility-with-image-seo-by-seopress.pdf | tier E | pages 51 | sha256 71a1b9e05fc10a429e72f1aea579ed739664440d2d87cdf78bb30e4acd387f9b | action: skip-by-default
• SEO Press/optimizing-wordpress-speed-en-2.pdf | tier E | pages 48 | sha256 1e0d721836414e7e966b8bfa2622282547f8b85f4e54ea7d4cac6e586f1bc9ff | action: skip-by-default
• SEO Press/seopress-2hours-seo-en.pdf | tier E | pages 54 | sha256 7c98a0697cbe4e2b11e5eecddb2c5b742274858941e72346ef8814ee27526e6b | action: skip-by-default
• SEO Press/seopress-creating-multilingual-wordpress-site.pdf | tier E | pages 46 | sha256 2e09fb5ffead2935410b9d0244c7be89e5a0a9e1f20e4bcc89065648a8cccd99 | action: skip-by-default
• SEO Press/seopress-google-analytics-wordpress-en.pdf | tier E | pages 57 | sha256 6b0d8c4f86c7f2b7690f561dded9d6826d00fe169084abf6ed088b712b70013c | action: skip-by-default
• SEO Press/seopress-improve-your-ranking-with-on-page-seo.pdf | tier E | pages 42 | sha256 f3fd25109604af02539ce656a20b50689710ba7f9298667d26c66cc4bfbc0b45 | action: skip-by-default
• SEO Press/seopress-insights-en.pdf | tier E | pages 39 | sha256 6aec1450a8611164cf4f31cf98120b5afc220ceb828bdb97f4775f061863bdb5 | action: skip-by-default
• SEO Press/seopress-top-seo-tips-managing-multilingual-site.pdf | tier E | pages 9 | sha256 82d2561dab03451983116aa261b909347982f1ed07e8ba1316ccb9c6143b1c3c | action: skip-by-default
• SEO Press/wordpress-keyword-en.pdf | tier E | pages 54 | sha256 be2ea81c03892ff37fe37b676a6f371b9a43cc00d9eaa5e714d9c3ef1da12ea2 | action: skip-by-default
• SEO-Trends-2026-SEJ.pdf | tier A | pages 34 | sha256 fb75eda39dc31449e77fae22d1872f7d6338239209be5830fe438dcc6ebd14d4 | action: extract-and-consider
• SEO_Tools_2023_F.pdf | tier D | pages 124 | sha256 5b4a17b1f2eb5e3cb88c748b7aff84b1d78544620be2a5251ee4c8c133abf744 | action: extract-and-consider

Source Policy

• Public prose is freshly written from the Local SEO Knowledge Base, 2025-2026 PDFs, and verified web sources.
• Absolute local paths are intentionally omitted.
• Tier E PDFs are background by default unless a narrow operational gap requires them.
• Contradicted or unverifiable statistics are excluded from public guidance.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "FLOW Framework" description: "FLOW Framework" updated: 2026-04-25 tags:

• framework

---

!FLOW Operating Loop

FLOW Framework

What This Is

FLOW is a search-and-conversion loop for 2026 discovery. It treats rankings, AI citations, local visibility, and sales evidence as connected surfaces rather than separate channels.

FLOW uses four plain stages: Find demand, Leverage distributed evidence, Optimize owned assets for extraction and trust, and Win with pages and measurements that connect discovery to revenue. This page applies that loop to the framework layer.

Why It Matters In 2026

Ahrefs found a 58% lower average CTR for position-one content when an AI Overview was present in its December 2025 dataset.

seoClarity found that 25% of top cited ChatGPT URLs had no Google organic visibility in its cited-page sample.

Search is no longer one result page and one click path. A useful SEO system has to survive classic rankings, AI summaries, local packs, business profiles, community references, and sales feedback. The practical goal is not to chase every surface equally; it is to decide which surface can change the next business outcome and then build evidence there.

How To Apply

• Name the search surface before writing: organic result, AI answer, local pack, community discussion, paid landing page, or sales-assisted page.
• Separate observable evidence from assumptions. Claims with numbers must trace to the bibliography or be removed.
• Write from buyer language first, then add entity clarity, internal links, proof, and conversion next steps.
• Review the asset as an AI-readable document: clear headings, direct answers, concise tables where useful, source labels, and no hidden dependence on private examples.

Operating Workflow

1. Define the business outcome before choosing tactics. A page meant to create a qualified call should not be judged only by impressions, and a profile meant to reconcile business facts should not be judged only by post frequency. 2. Inventory the evidence already available: customer language, query data, profile details, reviews, analytics, call notes, sales objections, and any public source that can support a claim. 3. Decide which FLOW stage is blocking progress. If demand language is unclear, return to Find. If the brand is not corroborated off-site, work on Leverage. If the owned asset is hard to extract or trust, Optimize. If traffic exists but business impact is weak, move to Win. 4. Rewrite or rebuild only after the evidence is organized. The strongest assets usually come from a clear source table, not from a blank-page brainstorm. 5. Review the finished work against three readers: the buyer, the search engine, and the AI agent that may summarize or compare the business later.

Measurement

Use a balanced scorecard. Track visibility indicators such as rankings, impressions, local-pack presence, citations, and AI mentions, but connect them to business indicators such as qualified leads, calls, form completions, sales opportunities, assisted conversions, and recurring objections. If the page or profile cannot be measured, add the measurement event before judging performance.

Common Failure Modes

• Publishing a statistic because it sounds familiar instead of because the source was loaded and dated.
• Treating AI visibility as a formatting trick while ignoring brand evidence, entity consistency, and off-site corroboration.
• Writing pages around company preferences instead of buyer questions and decision risk.
• Optimizing for traffic without defining the next qualified action.
• Reusing old examples when a generic or newly created example would be cleaner and more durable.

AI Agent Prompt

You are an SEO strategist using the FLOW model. For the asset named "FLOW Framework", analyze the target audience, search surface, evidence needed, entity facts, conversion goal, and risks. Return: priorities, page or profile changes, source requirements, internal links, measurement plan, and a list of claims that need verification before publication.

Quality Bar

• Public claims use verified sources or stay qualitative.
• Examples are generic or newly created for this repository.
• Private editorial notes are used only to identify candidate concepts, never as public prose.
• The page should make sense to a human reader and to an AI agent that only has this repository.

See Also

• Start Here
• AI Search Surface Map
• Bibliography

Sources

• Search Engine Journal, State of SEO 2026 PDF and public landing page, retrieved 2026-04-25.
• Ahrefs, AI Overviews CTR update, retrieved 2026-04-25.
• seoClarity, ChatGPT cited-page analysis, retrieved 2026-04-25.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Content planning for Topical Relevance Prompt" description: "Content planning for Topical Relevance Prompt" updated: 2026-04-25 tags:

• prompts
• find

---

Content planning for Topical Relevance Prompt

Use This When

Use this prompt when you need a structured find deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a find deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Content Prioritization Prompt" description: "Content Prioritization Prompt" updated: 2026-04-25 tags:

• prompts
• find

---

Content Prioritization Prompt

Use This When

Use this prompt when you need a structured find deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a find deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Keyword research prompt" description: "Keyword research prompt" updated: 2026-04-25 tags:

• prompts
• find

---

Keyword research prompt

Use This When

Use this prompt when you need a structured find deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a find deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Keyword variations for topical relevance prompt" description: "Keyword variations for topical relevance prompt" updated: 2026-04-25 tags:

• prompts
• find

---

Keyword variations for topical relevance prompt

Use This When

Use this prompt when you need a structured find deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a find deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Prompt: Audience Avatar" description: "Prompt: Audience Avatar" updated: 2026-04-25 tags:

• prompts
• find

---

Prompt: Audience Avatar

Use This When

Use this prompt when you need a structured find deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a find deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Backlink competition prompt" description: "Backlink competition prompt" updated: 2026-04-25 tags:

• prompts
• leverage

---

Backlink competition prompt

Use This When

Use this prompt when you need a structured leverage deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a leverage deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "AI Homepage Rewrite Prompt" description: "AI Homepage Rewrite Prompt" updated: 2026-04-25 tags:

• prompts
• local

---

AI Homepage Rewrite Prompt

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Claude 'Deep Research' Prompt" description: "Claude 'Deep Research' Prompt" updated: 2026-04-25 tags:

• prompts
• local

---

Claude 'Deep Research' Prompt

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "GBP Categories Prompt" description: "GBP Categories Prompt" updated: 2026-04-25 tags:

• prompts
• local

---

GBP Categories Prompt

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "GBP Description Claude Prompt 1" description: "GBP Description Claude Prompt 1" updated: 2026-04-25 tags:

• prompts
• local

---

GBP Description Claude Prompt 1

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "GBP Description Claude Prompt 2" description: "GBP Description Claude Prompt 2" updated: 2026-04-25 tags:

• prompts
• local

---

GBP Description Claude Prompt 2

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "GBP Description Claude Prompt 3" description: "GBP Description Claude Prompt 3" updated: 2026-04-25 tags:

• prompts
• local

---

GBP Description Claude Prompt 3

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "GBP Services Prompt" description: "GBP Services Prompt" updated: 2026-04-25 tags:

• prompts
• local

---

GBP Services Prompt

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Prompt: Generating a Meta Description" description: "Prompt: Generating a Meta Description" updated: 2026-04-25 tags:

• prompts
• local

---

Prompt: Generating a Meta Description

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Prompt: Generating a Title Tag" description: "Prompt: Generating a Title Tag" updated: 2026-04-25 tags:

• prompts
• local

---

Prompt: Generating a Title Tag

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Prompt: Rewriting Existing Homepage" description: "Prompt: Rewriting Existing Homepage" updated: 2026-04-25 tags:

• prompts
• local

---

Prompt: Rewriting Existing Homepage

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Prompt : Rewriting Existing Service Page" description: "Prompt : Rewriting Existing Service Page" updated: 2026-04-25 tags:

• prompts
• local

---

Prompt : Rewriting Existing Service Page

Use This When

Use this prompt when you need a structured local deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a local deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "AI detector test follow-up Prompt" description: "AI detector test follow-up Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

AI detector test follow-up Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "AI Supporting Pages Rewrite Prompt" description: "AI Supporting Pages Rewrite Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

AI Supporting Pages Rewrite Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Basic Prompt" description: "Basic Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Basic Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Blog Post Outline Prompt" description: "Blog Post Outline Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Blog Post Outline Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Blog Post Writing Prompt" description: "Blog Post Writing Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Blog Post Writing Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Claude Prompt 1" description: "Claude Prompt 1" updated: 2026-04-25 tags:

• prompts
• optimize

---

Claude Prompt 1

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Claude Prompt 2" description: "Claude Prompt 2" updated: 2026-04-25 tags:

• prompts
• optimize

---

Claude Prompt 2

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "CTR AUDIT PROMPT" description: "CTR AUDIT PROMPT" updated: 2026-04-25 tags:

• prompts
• optimize

---

CTR AUDIT PROMPT

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Follow-up Prompt 1" description: "Follow-up Prompt 1" updated: 2026-04-25 tags:

• prompts
• optimize

---

Follow-up Prompt 1

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Follow-up Prompt 2" description: "Follow-up Prompt 2" updated: 2026-04-25 tags:

• prompts
• optimize

---

Follow-up Prompt 2

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Follow-up Prompt" description: "Follow-up Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Follow-up Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "PAA Question Rewording Prompt" description: "PAA Question Rewording Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

PAA Question Rewording Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Prompt: Core 30 Content Audit" description: "Prompt: Core 30 Content Audit" updated: 2026-04-25 tags:

• prompts
• optimize

---

Prompt: Core 30 Content Audit

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Property content with authority audit prompt" description: "Property content with authority audit prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Property content with authority audit prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Reddit Claude Prompt" description: "Reddit Claude Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Reddit Claude Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Schema Prompt 1" description: "Schema Prompt 1" updated: 2026-04-25 tags:

• prompts
• optimize

---

Schema Prompt 1

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Step 1: The ChatGPT Discovery Prompt" description: "Step 1: The ChatGPT Discovery Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Step 1: The ChatGPT Discovery Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Step 2: The Follow-Up Qualifying Prompt" description: "Step 2: The Follow-Up Qualifying Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Step 2: The Follow-Up Qualifying Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Technical Audit Prompt" description: "Technical Audit Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Technical Audit Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Visibility Follow Up Prompt" description: "Visibility Follow Up Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Visibility Follow Up Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Visiblity Prompt" description: "Visiblity Prompt" updated: 2026-04-25 tags:

• prompts
• optimize

---

Visiblity Prompt

Use This When

Use this prompt when you need a structured optimize deliverable and want the model to separate observations, assumptions, recommended actions, and claims that need verification.

AI Compatibility

Works with long-context reasoning models. For smaller models, provide narrower inputs and ask for one output section at a time.

Inputs

• Business or website name.
• Target page, profile, query set, or campaign.
• Audience and geography where relevant.
• Existing evidence: analytics, search results, calls, reviews, profile facts, or source notes.
• Constraints, exclusions, and required sources.

Prompt

Act as a senior SEO strategist using the FLOW model.

Task: create a optimize deliverable for: [BUSINESS OR ASSET].

Use only the supplied inputs and clearly label any assumption. Do not invent statistics. Do not reuse private examples. Build the answer around:
1. Searcher or buyer intent.
2. Evidence available now.
3. Gaps that block trust, extraction, or conversion.
4. Recommended changes in priority order.
5. Measurement events and review cadence.
6. Claims that require source verification before publication.

Return a concise working document the team can execute.

Output

• Executive summary.
• Priority table.
• Recommended copy, structure, or audit findings.
• Evidence needed.
• Measurement plan.
• Verification checklist.

Example

Input: a local service page with weak proof and inconsistent profile details.

Expected output: a prioritized rewrite brief, facts to reconcile, internal links to add, and the conversion event to measure.

See Also

• Prompt Library
• FLOW Framework
• Bibliography

Source Note

Derived from the Local SEO Knowledge Base structure and rewritten for public use with the repository evidence standard.

<!-- FLOW Framework — Operational Prompt Library © Daniel Agrici | License: CC BY 4.0 Source: github.com/AgriciDaniel/flow Attribution required when reproducing or adapting these prompts. -->

Flow Prompt Index

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "BOFU Page Brief Generator" description: "BOFU Page Brief Generator" updated: 2026-04-25 tags:

• prompts
• win

---

BOFU Page Brief Generator

Use This When

Use this when you need a bottom-funnel page brief for a service, product, location, comparison, pricing, demo, or lead-capture page.

AI Compatibility

Claude, GPT, Gemini, and other long-context models. Works best with current customer language and conversion evidence.

Inputs

• Offer, service, or product.
• Target audience and segment.
• Buying-stage intent.
• Known objections or hesitation points.
• Customer language from calls, chats, reviews, or surveys.
• Conversion goal.
• Required proof points.
• Existing page text, if any.

Prompt

Create a bottom-funnel page brief for [offer] targeting [audience].

Use only the inputs provided. Build the brief around what this audience needs to decide.

Analyze:
1. The immediate problem the visitor is trying to solve.
2. The decision factors they likely need before converting.
3. Objections, hesitation points, and missing clarity.
4. Customer-language phrases that should appear naturally.
5. Proof needed to support trust.
6. CTA angle and page sections needed to reduce friction.

Return: page goal, search/conversion intent, primary audience, buyer questions, objections, recommended H1, section outline, proof points, CTA strategy, FAQ topics, and tracking notes for form, call, chat, and qualified-lead measurement. Flag missing inputs.

Output

• A structured Win-stage working document.
• Prioritized recommendations.
• Evidence and measurement gaps.
• Claims or assumptions that require verification.

Example

Input: commercial repair page for facility managers with objections around response time, weekend availability, and pricing clarity. Output: a brief emphasizing urgency, service coverage, decision criteria, proof, FAQs, and call/form tracking.

See Also

• Prompt Library
• BOFU and Conversion Content
• Dual-Surface Scorecard

Source Note

Derived from SEJ State of SEO 2026, SEJ B2B Lead Generation, and CallRail/SEJ Better Leads More Sales 2025.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Conversion Audit Prompt" description: "Conversion Audit Prompt" updated: 2026-04-25 tags:

• prompts
• win

---

Conversion Audit Prompt

Use This When

Use this when a page, campaign, or funnel gets traffic but produces weak leads, low conversion rate, unclear attribution, or poor sales follow-up quality.

AI Compatibility

Claude, GPT, Gemini, and other long-context models. Works best with current customer language and conversion evidence.

Inputs

• Page or funnel copy.
• Traffic sources.
• Conversion goal.
• Analytics or conversion data.
• Call, chat, or form transcript samples.
• Known objections.
• Ad copy or campaign promise.
• Sales feedback, if available.

Prompt

Audit this conversion path for lead quality, friction, and measurement gaps.

Use the supplied page, campaign, and first-party conversation data. Identify:
1. Where visitor expectations may not match the page or offer.
2. Common objections and hesitation points.
3. Missing decision-making information.
4. Language mismatches between customers and the page.
5. CTA friction.
6. Tracking gaps across form, phone, chat, and offline outcomes.
7. Whether reporting connects to qualified leads or sales, not only traffic.

Return an executive summary, top blockers, lead-quality risks, messaging fixes, page/content fixes, tracking fixes, first-party data to collect next, and a ranked test backlog. Do not recommend more spend until content, offer clarity, and measurement gaps are assessed.

Output

• A structured Win-stage working document.
• Prioritized recommendations.
• Evidence and measurement gaps.
• Claims or assumptions that require verification.

Example

Input: paid search landing page with many calls but few booked appointments. Output: an audit of pricing clarity, qualification, phone attribution, repeated objections, CTA mismatch, and test priorities.

See Also

• Prompt Library
• BOFU and Conversion Content
• Dual-Surface Scorecard

Source Note

Derived from PPC Trends 2026, CallRail/SEJ Better Leads More Sales 2025, and SEJ State of SEO 2026.

<!-- Source: github.com/AgriciDaniel/flow | License: CC BY 4.0 | Synced: 2026-04-26 --> --- title: "Dual-Surface Content Scorecard" description: "Dual-Surface Content Scorecard" updated: 2026-04-25 tags:

• prompts
• win

---

Dual-Surface Content Scorecard

Use This When

Use this when you need to judge whether a page can perform in traditional search and AI-assisted discovery while still supporting conversion.

AI Compatibility

Claude, GPT, Gemini, and other long-context models. Works best with current customer language and conversion evidence.

Inputs

• Page copy.
• Target queries or topics.
• Intended conversion goal.
• Audience segment.
• Known first-party insights.
• Performance data, if available.
• Competing page examples, optional.

Prompt

Score this content for two discovery surfaces: traditional search and AI-assisted answer environments.

Evaluate:
1. Original usefulness and specificity.
2. Alignment with audience needs and decision stage.
3. Evidence, examples, data, or firsthand insight.
4. Clear answers to buyer questions.
5. Conversion support: CTA, proof, objection handling, and next step.
6. Refresh or update need.
7. Measurement readiness: traffic, engagement, qualified leads, sales conversions, and ROI indicators.

Return traditional search score, AI-assisted discovery score, conversion-readiness score, evidence strengths, gaps, risks, recommended updates, and the highest-impact next three actions. Use business-impact language, not traffic-only language.

Output

• A structured Win-stage working document.
• Prioritized recommendations.
• Evidence and measurement gaps.
• Claims or assumptions that require verification.

Example

Input: existing service page with traffic but low form submissions. Output: scores showing whether the page lacks buyer proof, direct answers, customer language, CTA clarity, or measurable conversion paths.

See Also

• Prompt Library
• BOFU and Conversion Content
• Dual-Surface Scorecard

Source Note

Derived from SEJ State of SEO 2026, verified AI-search evidence, and SEJ B2B Lead Generation.