Loop/goalContent & SEOlow riskintermediatesafety C · 60Forward Futurepre-dates current gate · under review

Close your search-visibility gaps

Fix the highest-impact crawl, indexation, intent, citation, and answer-readiness gaps first, in priority order.

prompt
→ Claude Code
Run an SEO/GEO audit across crawlability, indexation, page intent, titles, internal links, structured data, source citations, and answer-first content. Rank the gaps by expected impact, fix the highest-leverage issue, then rerun the same crawl and target-query benchmark across search engines and AI answer engines. Repeat until no critical technical issues remain, every priority query maps to a clear answer-ready page, and the benchmark shows no high-impact gap left to fix.
claude-code · codex

Use this when

Use this when a site has a defined set of priority pages and target questions, and you can rerun the same technical crawl and search visibility checks after each change.

How it runs

  1. Record the target queries, answer engines, search engines, locale, date, and benchmark method.
  2. Audit crawlability, indexation, page intent, titles, internal links, structured data, citations, and visible answer quality.
  3. Rank findings by expected impact and fix one high-leverage issue at a time.
  4. Rerun the original crawl and query benchmark until no critical technical issue or high-impact content gap remains.

Done when

✓ Priority pages are indexable, answer-ready, and technically sound. The repeatable crawl and query benchmark finds no remaining high-impact gaps.

Why it works

A fixed benchmark makes visibility work measurable and prevents a long list of low-value SEO tasks from replacing the highest-impact fix. Mapping each priority query to a strong page also gives search and answer systems a clear destination.

Implementation note

AI citations and search results vary by time, location, account state, and model. Record the test conditions and treat sampled visibility as evidence, not a guaranteed ranking.

Source: Forward Future ↗graded C · 60/100 — how grades work →

More content loops

Ship one post a week, learn what works

Loop/scheduleForward FutureB

Six weeks, one variable changed per post; measure replies, saves, and questions, and end with a winner or an honest null.

prompt
→ Claude Code
Find a repeatable weekly post format for [approved account, audience, and topic] through a six-week experiment. If the account, audience, or topic is missing, ask for it before drafting. Obtain approval before publishing anything externally. Each week, draft one short post about a real problem [person, product, or company] solves. Record substantive replies, saves, and questions after the same measurement window. Treat likes as secondary evidence. Keep the audience, topic area, cadence, and measurement window comparable. Change only one meaningful element each week, such as the opening, format, example, or call to action, based on the strongest signal from the previous post. Stop when one format materially outperforms the alternatives, the six-week experiment ends without a winner, approval is withheld, required metrics are unavailable, or the budget is exhausted. Never fabricate engagement data. Finish with every post, its measurements, the variables tested, the winning format or no-winner result, and the next recommendation.

Interview five buyers, fix the copy

Interview recent buyers in batches, track recurring objections, and propose evidence-backed landing-page copy.

prompt
→ Claude Code
Improve [landing page or purchase page] using objections from recent buyers. Before contacting anyone, identify the approved buyer group, outreach channel, privacy rules, and message. Obtain explicit approval for the outreach. Interview buyers in batches of five, up to fifteen people total. Ask each person one question: What almost stopped you from buying? Record their exact words while protecting their identity and honoring any consent or communication requirements. After each batch, group repeated concerns and draft a proposed copy change for the point on the page where each concern is most likely to arise. Do not publish the copy without approval. Use the next batch to check whether the same concern still appears. Stop when the concern no longer repeats, fifteen interviews are complete, the outreach budget ends, or access is blocked. Finish with anonymized quotes, recurring concerns, proposed copy, evidence by batch, and the recommended page change.
Close your search-visibility gaps — /goal for claude-code, codex | looprepo