Google Things to Do and Discoverability

Core takeaway

Search visibility for experiences increasingly depends on structured, machine-readable content rather than only classic SEO patterns. Google Things to Do is one of the clearest examples of this shift.

Why it matters for this repo

This topic sits at the intersection of editorial authority and operator relevance. It is strong material for explainers, course modules, keynote framing, and practical audits.

Practical implications

• Structured product data becomes strategic, not just technical.
• Distribution teams need to think about discoverability across both search interfaces and AI surfaces.
• Content systems that keep product information consistent gain long-term leverage.

Follow-up questions

• Which parts of experience metadata matter most for discoverability?
• How should operators prioritize structured content fixes?
• What should the public library teach versus what should stay inside training resources?