Files
magnus919_agent-skills/seo/references/discovery-and-freshness.md
T
Magnus HedemarkandGitHub 531ff67537 feat(seo): consolidate answer and generative search optimization
Merging with required validation green. Droid Auto Review was retried twice and failed before producing a review because DeepSeek V4 Flash rejected the action's ApplyPatch tool; the check is non-required per branch protection. The diff was independently inspected and local/repository validation passed.
2026-08-26 19:42:25 -04:00

2.6 KiB

AEO discovery and freshness

Crawl is not citation

A page must be reachable and eligible before many systems can retrieve it, but a successful fetch is not proof of indexing, retrieval, citation, or traffic. Verify each boundary separately.

Robots policy

Robots Exclusion Protocol rules are crawler-specific. Build a policy matrix before changing them:

  • search crawler and search visibility;
  • training crawler and training use;
  • user-triggered fetch;
  • ad, commercial, or partner crawler;
  • private paths and sensitive data.

OpenAI explicitly separates OAI-SearchBot, GPTBot, and ChatGPT-User. Google uses Googlebot for Search controls and Google-Extended for certain other systems. Other providers have their own semantics. Never copy a universal allowlist from a blog post.

Check robots at the origin, CDN, and public URL. Record propagation expectations. A robots file is a policy control, not an AEO optimization switch.

Use crawlable internal links and an accurate XML sitemap. Include canonical URLs and truthful lastmod values. Bing documents sitemaps and IndexNow as discovery/freshness aids; they do not guarantee AI inclusion. Do not set lastmod to sitemap generation time when page content did not change.

Freshness

Freshness means the answer is current for its question. A real update should identify what changed, update visible dates where appropriate, refresh structured data, repair links, and re-run high-risk observations. Date-only edits, “updated” badges without changed content, and stale citations damage trust.

Access verification

GET /robots.txt          → expected policy, status, content type
GET /sitemap.xml         → expected URL and true lastmod
GET /target              → status, canonical, robots meta, visible answer
GET /target as crawler   → only where permitted and provider semantics are known

Inspect edge caching and authentication. A browser page that renders content only after a client-side request needs a separate rendered verification.

Primary references