Back to GrowthDex
Growth idea action plan

sitemap.md semantic discovery map

Publish a Markdown sitemap with section labels and page descriptions so agents can understand the site structure before they start fetching individual pages.

rare tactic
Best-fit channelSEO · AI Search · Website
Stage + contextseo · site-architecture · ai-discovery
BudgetFreebudget tier
Suggested operator signalQualified search visitors who complete the intended next action

Why this can grow a startup

XML tells crawlers what exists, but Markdown tells assistants what matters. A semantic sitemap reduces wandering, makes internal clusters legible, and gives answer engines a fast orientation layer for the whole corpus. It is one of the simplest ways to turn a pile of pages into a discoverable knowledge surface.

Source-backed example

Vercel's AI-agent documentation checklist explicitly recommends serving `/sitemap.md` as a semantic Markdown sitemap describing docs sections and pages.

Source details

Source: Vercel Knowledge Base · Browse Vercel Knowledge Base tactics

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

Source discovered: May 24, 2026

SEOAI SearchWebsiteseosite-architectureai-discovery
GrowthDex operator note

When to use it

Use this when SEO, AI Search, Website is relevant to seo, site-architecture, ai-discovery and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to SEO and AI Search, using evidence from Vercel Knowledge Base as context—not as a promised result.
  3. Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Turn isolated search tactics into a crawlable visibility system tied to demand and proof.

Work with Ian

SOURCE HUB

More tactics from Vercel Knowledge Base

Explore related GrowthDex examples and evidence connected to Vercel Knowledge Base.

Open Vercel Knowledge Base source hub