# SEO & AI Search: An Ongoing Strategy Playbook

> Build and maintain an evidence-led SEO and AI-search strategy with a foundation cycle for new programs, capacity-aware current or next cycles for established programs, measurement limits, and a portable agent skill.

- Version: 1.1.2
- Reviewed: 2026-09-13
- Author: Markethink
- Canonical page: https://markethink.ai/ai-marketing-strategies/seo-aio-playbook/
- Portable skill: https://markethink.ai/downloads/markethink-seo-aio-playbook.zip

## Purpose

Adapt a reviewed SEO and AI-search method to a real business. Start a new program with an initial foundation cycle, or resume an established program from its existing records with a current or next capacity-aware cycle. Preserve work-item IDs and status history while keeping available evidence separate from assumptions and delivery separate from results.

## Who it fits

Businesses with a live website, a defined offer, and enough internal knowledge to verify facts, review recommendations, and authorize any execution separately.

## Complete standalone AI brief

SEO & AI SEARCH: ONGOING STRATEGY BRIEF
Version: 1.1.2
Reviewed: 2026-09-13
Source: https://markethink.ai/ai-marketing-strategies/seo-aio-playbook/

ROLE
Help me adapt and maintain an evidence-led SEO and AI-search strategy for my business. For a new program, produce the initial 30-day foundation cycle. For an established program, resume from its existing records and produce the current or next capacity-aware cycle without restarting day 1. Support planning, review, and only the execution I separately authorize. Ongoing does not authorize scheduled tasks, continuous monitoring, paid tool calls, publishing, or outreach. It also does not authorize spending, sending, account changes, or any action outside my permissions.

OPERATING RULES
1. Reuse supplied context and ask only for material missing information.
2. Keep observed facts, source estimates, business hypotheses, and recommendations visibly separate.
3. Label unavailable measurements as Not available, not zero.
4. Keep search-volume estimates, organic difficulty, ad competition, indexing, traffic, conversions, and sampled AI citations in separate fields.
5. Keep delivery completion separate from rankings, traffic, leads, citations, and revenue outcomes.
6. Preserve the receiving user's permissions. Planning or review does not authorize publishing, spending, sending, outreach, or account changes.
7. Ongoing means the method can be repeated when a user starts a new authorized cycle. It does not authorize scheduled tasks, continuous monitoring, paid tool calls, publishing, or outreach.

CONTEXT TO COLLECT
Reuse anything I already supplied. Ask only for material missing information, grouped into one concise request when possible.
- Website: Primary domain and any priority URLs or sitemap.
- Business and offer: What the business sells, its differentiators, pricing posture, and claims it can support.
- Audience and geography: Ideal customer, buying situation, languages, locations, and service limits.
- Objective: The business action the search program should support and the planning horizon.
- Current pages: Known commercial, educational, comparison, proof, contact, and conversion pages.
- Constraints: Capacity, approvals, compliance, technical limits, publishing access, and protected claims.
- Available evidence: Search exports, analytics, CRM observations, customer questions, research, approved examples, and first-party expertise.

TOOL AND DATA CHECK
- Inspect connected tools and supplied exports before recommending research work.
- Use Search Console, analytics, DataForSEO, Semrush, Ahrefs, or another source only when it is actually connected or the user supplied an export.
- Record each source as available, supplied export, unavailable, or not needed for this scope.
- Do not treat a general language-model answer as live search-result, indexing, traffic, conversion, or citation evidence.

FOUNDATION OR CURRENT/NEXT IMPLEMENTATION CYCLE
For a new program, use the initial 30-day sequence as the foundation cycle, not the lifespan or completion deadline of the strategy. For an established program, preserve its records and use these phases only as a method for the current or next capacity-aware cycle; do not restart day 1.
Days 1 to 5: Baseline, research, and technical access
  - Inventory current indexable and priority URLs, then assign each a visible audience, intent, offer, and next-step job.
  - Register available tools and exports. Record collection dates, filters, geography, device, and denominators where relevant.
  - Build a query-to-existing-URL intent map from customer language, supplied evidence, and live search research when available.
  - Check technical access, crawl controls, canonicals, status responses, sitemap inclusion, internal discoverability, and important rendered text.
  - Create a dated baseline without filling unavailable fields with invented values.
Days 6 to 12: Improve the right pages and factual entity or offer information
  - Prioritize existing pages by business value, evidence gap, technical risk, effort, and confidence in the diagnosis.
  - Prepare page-improvement briefs covering intent, audience, direct answer, proof, factual entity or offer details, structure, internal links, and next step.
  - Resolve inconsistent business names, categories, service areas, offer details, contact paths, and supported structured data where the evidence allows.
  - Keep recommendations scoped to available capacity and approval paths.
Days 13 to 22: Create useful sourced answer-ready content and contextual links
  - Create or improve only the content required by the intent map and page briefs.
  - Lead with a direct answer where it helps the reader, then add context, original expertise, sources, limits, and a useful next step.
  - Add crawlable contextual links with descriptive anchors where the destination genuinely helps the reader.
  - Attribute borrowed methods and preserve readable original-source URLs.
  - Do not manufacture mentions, citations, reviews, examples, or scaled pages to imitate authority.
Days 23 to 30: Verify shipped changes and review comparable observations
  - Verify each authorized release on its canonical production URL, including response, crawlability, metadata, structured data, links, accessibility, and responsive rendering.
  - Record delivery evidence for every planned item and list anything not shipped with its dependency.
  - Repeat only comparable search or AI-answer samples with the same question, geography, language, device, source, and collection method where possible.
  - Review indexing, organic discovery, sampled AI citations, referral activity, and conversions as separate observations.
  - Choose the next cycle from the strongest verified gap, not from a promised ranking or an isolated favorable answer.

REPEAT CYCLE BEYOND DAY 30
1. Update the evidence baseline: Review available first-party data, supplied exports, live technical checks, and dated search observations. Keep unavailable measures as Not available.
2. Review delivery and results separately: Confirm what was delivered and verified before reviewing rankings, traffic, citations, inquiries, or revenue observations on their own timelines.
3. Carry unfinished work forward: Keep each existing work item’s original ID, current status, recorded status history or evidence-transition reference, dependencies, owner, and acceptance checks visible. Never renumber it, overwrite past delivery or status evidence, or auto-complete it because a target date passed. Give proposed new work distinct proposed IDs.
4. Add newly justified opportunities: Add an opportunity to the maintained backlog only when current evidence and available capacity make it specific enough to scope.
5. Prioritize the next capacity-aware cycle: Choose the smallest useful set of next actions, with owners, dependencies, effort, target URLs, and delivery acceptance evidence.
6. Append a dated decision and change log: Record the evidence reviewed, delivery status, result status, lessons, carry-forward work, and the next review checkpoint.

REQUIRED OUTPUTS
Return every section below. Use tables where they improve readability.
1. Concise business brief: business and offer; audience and geography; objective; priority conversion action; constraints; known evidence; unresolved material inputs
2. Tool and data-availability register: source; status; scope; date range; filters or denominator; what it can support; what remains unavailable
3. Query-to-existing-URL intent map: query or question family; intent; audience or location; existing primary URL; page job; evidence; gap; recommended action
4. Prioritized foundation or current/next capacity-aware cycle: existing work-item ID or proposed new ID; current status; recorded status history or evidence-transition reference; window or cycle; action; owner; reviewer; dependency; effort; target URL; delivery acceptance evidence; outcome observation and timing
5. Page-improvement briefs: target URL; current job; observed issue; recommended change; facts or sources required; contextual links; approval need; acceptance check
6. Measurement baseline: measurement lane; value or Not available; source; collection date; scope; denominator or filters; limitation; next comparable review
7. Review log: date; decision; owner; evidence reviewed; delivery review; results review; lesson; next action
8. Next-cycle backlog and review checkpoint: existing work-item ID or proposed new ID; current status; recorded status history or evidence-transition reference; carried-forward task; newly justified opportunity; scope evidence; priority; capacity; owner; dependency; acceptance check; review date or trigger

MEASUREMENT SEPARATION
Never collapse these into one visibility score.
- Search-volume estimate: An estimate from a named source and scope. It is not observed site traffic.
- Organic difficulty: A vendor-specific estimate. It is not Google data or a guarantee of ranking effort.
- Ad competition: Paid-search advertiser competition. It is not organic ranking difficulty.
- Indexing: Observed or reported eligibility and index state. It is not ranking or traffic.
- Organic traffic: Visits or clicks attributed by the named source and filters. It is not a conversion.
- Conversions: Defined business actions with a named tracking source. They do not prove SEO caused the result.
- Sampled AI citations: Dated observations from a fixed question and environment. They are directional, not a universal rank.

ACCEPTANCE RULES
- Adapt the number of pages, queries, and actions to the stated capacity.
- Every action must have an owner, reviewer where needed, dependency, effort, target URL or asset, and delivery acceptance evidence.
- Mark unavailable data as Not available and state what would be needed to measure it.
- Treat a completed deliverable as delivery evidence only. Keep rankings, traffic, leads, conversions, and citations pending until observed from a named source.
- Review delivered work and results in separate fields.
- Carry unfinished work forward with its original work-item ID, current status, recorded status history or evidence-transition reference, dependency, and acceptance check. Never renumber it, overwrite past delivery or status evidence, or auto-complete work because a date passed.
- Label newly justified work with distinct proposed new IDs so it cannot be mistaken for or overwrite an existing record.
- Add a newly justified opportunity only after its evidence, scope, priority, capacity, owner, dependency, and acceptance check are explicit.
- End every cycle with a next-cycle backlog, a review date or trigger, and an appended dated decision/change log.
- Preserve original source URLs and attribute any borrowed strategy.
- Do not present Markethink's roadmap or any illustrative example as proof for this business.
- Do not schedule the next review, create a monitor, use a paid tool, publish, or begin outreach unless I separately authorize that action.

LIMITATIONS
- Search and AI-answer systems change. A plan can improve clarity, crawlability, usefulness, and evidence without guaranteeing selection, ranking, citation, traffic, or leads.
- Low-volume businesses may need review windows longer than 30 days for comparable outcome observations.
- Tool estimates use different datasets and definitions. Record the provider and do not merge unlike metrics.
- The first 30 days are an initial implementation cycle, not the lifespan of the strategy or a claim that search engines will recrawl, index, rank, or cite a page on that schedule.
- A current baseline is evidence for prioritization, not a permanent cap on future actions. New work enters the maintained backlog only when it is justified and scoped.
- Markethink's public roadmap is an implementation example from Markethink.ai. It is not independent proof and its statuses must not be copied into another business's plan.

ORIGINAL SOURCES
- Google Search Central, Optimizing your website for generative AI features on Google Search: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Google Search Central, AI features and your website: https://developers.google.com/search/docs/appearance/ai-features
- Google Search Central, Creating helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Google Search Central, Google Search's guidance on using generative AI content on your website: https://developers.google.com/search/docs/fundamentals/using-gen-ai-content
- Google Search Central, Link best practices for Google: https://developers.google.com/search/docs/crawling-indexing/links-crawlable

START
First summarize the context already available. Then show the tool and data-availability register. Ask only for material missing inputs. If this is a new program, produce the initial foundation cycle. If this is an established program, resume from existing records and produce the current or next capacity-aware cycle without restarting day 1. Review delivery and results separately, preserve original work-item IDs and status history, distinguish proposed new IDs, and finish with an honest next-cycle backlog and review checkpoint.

## Reusable output templates

# Reusable output templates

## Tool and data-availability register

| Source | Status | Scope | Date range | Filters or denominator | Can support | Unavailable |
| --- | --- | --- | --- | --- | --- | --- |

## Query-to-existing-URL intent map

| Query or question family | Intent | Audience or location | Existing primary URL | Page job | Evidence | Gap | Recommended action |
| --- | --- | --- | --- | --- | --- | --- | --- |

## Prioritized foundation or current/next capacity-aware cycle

| Existing work-item ID or proposed new ID | Current status | Status history or evidence-transition reference | Window or cycle | Action | Owner | Reviewer | Dependency | Effort | Target | Delivery acceptance evidence | Outcome observation and timing |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

## Page-improvement brief

- Target URL:
- Current page job:
- Observed issue and evidence:
- Recommended change:
- Facts or sources required:
- Contextual links:
- Approval required:
- Delivery acceptance check:
- Outcome observation and timing:

## Measurement baseline

| Measurement lane | Value or Not available | Source | Collection date | Scope | Denominator or filters | Limitation | Next comparable review |
| --- | --- | --- | --- | --- | --- | --- | --- |

## Delivery review

| Planned item | Delivery state | Verification evidence | Unfinished dependency | Carry forward |
| --- | --- | --- | --- | --- |

## Results review

| Measurement lane | Observation or Not available | Source | Collection date | Scope | Limitation |
| --- | --- | --- | --- | --- | --- |

## Next-cycle backlog and review checkpoint

| Existing work-item ID or proposed new ID | Current status | Status history or evidence-transition reference | Carried-forward task | Newly justified opportunity | Scope evidence | Priority | Capacity | Owner | Dependency | Acceptance check | Review date or trigger |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

## Dated decision and change log

| Date | Decision | Owner | Evidence reviewed | Delivery review | Results review | Lesson | Next action |
| --- | --- | --- | --- | --- | --- | --- | --- |

## Source notes

# Original sources and evidence limits

Reviewed 2026-09-13. Read the live source before relying on a detail that may have changed.

## Optimizing your website for generative AI features on Google Search

- Publisher: Google Search Central
- URL: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Used for: Foundational SEO, valuable non-commodity content, technical clarity, supported measurement, and limits on AI-search shortcuts.

## AI features and your website

- Publisher: Google Search Central
- URL: https://developers.google.com/search/docs/appearance/ai-features
- Used for: Eligibility, crawlability, indexability, internal links, visible text, structured-data consistency, and reporting limits.

## Creating helpful, reliable, people-first content

- Publisher: Google Search Central
- URL: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Used for: Originality, completeness, sourcing, authorship, audience value, and avoiding search-engine-first production.

## Google Search's guidance on using generative AI content on your website

- Publisher: Google Search Central
- URL: https://developers.google.com/search/docs/fundamentals/using-gen-ai-content
- Used for: Accuracy, quality, relevance, transparency, and scaled-content limits when AI supports production.

## Link best practices for Google

- Publisher: Google Search Central
- URL: https://developers.google.com/search/docs/crawling-indexing/links-crawlable
- Used for: Crawlable anchors, descriptive link text, contextual internal links, and useful external citations.

## Working-example boundary

Markethink's public implementation log is available at https://markethink.ai/seo-aio-strategy/. It is a working example, not independent proof. Do not copy its statuses or observations into another business's plan.