# AI Search Action Plan

A Creators Toolbox version with original steps, prompts and an illustrative example, inspired by [Noel Ceta's source workflow](https://x.com/noelcetaSEO/status/2122702185792237736).

Use 24 practical checks and original prompts to improve discoverability without treating citations or rankings as guaranteed.

1. Use this as a backlog, starting with pages that already have demand. Export Search Console queries and pages for a consistent window, gather a small URL list and write five verifiable facts about the offer. Treat Google search performance, AI referral traffic and answer-engine citations as separate measurements. A case study's traffic curve does not prove that a particular tactic caused it.

2. Checks 1 to 4: identify the intended reader and action for each page; pair important queries with the page that actually appears; inspect returned HTML for the answer and links; check whether the canonical and indexing rules agree with the intended URL. Original prompt: "Using these exports and fetched pages, list four mismatches between query intent and page purpose. Cite a row or page section for each. Mark unknowns."

3. Checks 5 to 8: make the title specific to the page; give the visible main heading a clear purpose; remove duplicate descriptions; put a concise answer beside its supporting explanation. Example: a product page should name the tool, its job and a meaningful limit rather than call every tool an all-in-one solution. Prompt: "Rewrite only these four metadata fields using the verified facts. Do not add claims, dates or superlatives."

4. Checks 9 to 12: repair crawlable navigation; add useful contextual links to overlooked pages; explain a hub's selection criteria; consolidate pages that serve the same intent. Before consolidating, inspect links, history and conversion value. Prompt: "Suggest five internal links from this URL inventory. Give the exact source sentence, anchor and destination. Do not invent a destination."

5. Checks 13 to 16: add first-party evidence with a method; make comparisons factual and balanced; update stale instructions against the product's current documentation; show relevant author or organization identity. Useful evidence might be a measured export-size table with input files and dates. Prompt: "Identify claims on this page that need evidence. Propose the smallest reproducible check for each and label any result we do not yet have."

6. Checks 17 to 20: verify sitemap membership; inspect redirects and broken links; ensure structured data matches the visible content; test page delivery and image weight on a representative device. Structured data helps describe a page but does not guarantee inclusion in AI answers. Do not add hidden FAQ answers or ratings the page cannot support.

7. Checks 21 to 24: translate only where audience demand justifies maintenance; validate language targeting and translated facts; record the source and date of each observed AI citation; set a review window with a baseline and change log. Prompt: "Build a four-week measurement sheet with separate columns for clicks, impressions, conversions and verified citations. State what each metric cannot tell us."

8. Choose three actions with direct evidence and a clear owner. Fix defects before mass publishing. Keep an unchanged comparison set when possible and document simultaneous campaigns or releases. Avoid treating an llms.txt file, a particular word count or hundreds of generated pages as a substitute for useful accessible content. Revisit the backlog after observing enough data rather than promising a ranking or citation outcome.

Illustrative sprint: a Creators Toolbox comparison page has impressions but links through a JavaScript-only button and repeats its hub description. Replace the button with a real link, write page-specific metadata and add a tested compatibility table. Success checks: crawler-visible links, unique metadata, current evidence and recorded conversions. Search gains are observed later; they are not assumed.

See [Google's AI search guidance](https://developers.google.com/search/docs/appearance/ai-features) and [Search Console metrics](https://support.google.com/webmasters/answer/7576553) for the underlying measurement limits.

Written by Creators Toolbox. External tool access and costs vary.
