# Search visibility follows reader value

This workflow uses SEO for discoverability and GEO for clear, attributable
answers. Neither promises indexing, rankings or citation by an AI assistant.

- Answer a specific business question in the opening. Use the language readers
  use, without keyword density targets or repeated synonyms.
- Choose a unique descriptive title, a useful summary, one H1, and meaningful H2s.
- Make claims understandable in context: name the study, date, metric and limit.
- Use crawlable HTML, stable canonical URLs, internal links and a sitemap.
- Keep structured data consistent with the visible byline, dates and article.
- Prefer a small number of strong original articles to many near-duplicates.
- Do not create a FAQ merely for schema, hidden search text or doorway pages.
- Use real publication dates. Do not refresh dates to simulate new reporting.
- Treat Markdown mirrors and llms.txt as reading aids, not ranking mechanisms.

Primary references, consulted 30 October 2026:

- [Google: helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)
- [Google: AI features and your website](https://developers.google.com/search/docs/appearance/ai-features)
- [Agent Skills specification](https://agentskills.io/specification)

Google's AI feature guidance says ordinary search fundamentals still apply and
that inclusion is not guaranteed. The workflow's evidence ledger and originality
audit are our editorial methods, not official ranking requirements. Check these
sources again before turning their guidance into claims about current search.
