Separate search request types before increasing new content

The homepage is a reader filter, not a list of possibilities.

Useful for: Growth operators, content teams, AI commercialization teams

Google official visual for search entry points and pre-click page selection
Image source: Google Blog.

Start with search evidence

Large public visibility does not always mean high reader commitment. Request type mixing can create a gap between search appearance and useful action paths.

Build first-screen problem pages around what users want to decide immediately, not around generic AI capability statements.

Visibility is not demand

The useful question is not whether the page appeared somewhere; it is whether the search term, page promise, and next action fit the same reader job.

Check the page path

  • Create one clear task path for each high-intent question and keep generic signals in supporting pages only
  • Keep the test narrow: one priority page with clear topic, source links, internal links, and a conversion action

What still needs proof

Optimizing for every visible signal will blur intent and reduce trust over time. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.

Intent qualityReader readinessTraffic mix