feat(experiment): rewrite Web/API page titles #10926
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
(MP-1054)
Problem
We identified a drop in search engine impressions in April 2023, which coincides with the Web/API retitle project, and we cannot rule out that there is a causal relationship.
Solution
Run an experiment with 500 randomly sampled Web/API pages (of 2719), partially reverting the change to their
<title>
(but not to the<h1>
) by essentially replacingFoo: bar property
byFoo.bar property
.Note: The change doesn't change the displayed title in the content, but it does affect the displayed title in the browser tab and in search engines.
How did you test this change?
yarn dev
locally and verified that http://localhost:5042/en-US/docs/Web/API/Window/location/index.json (not in the test group) is unmodified, but http://localhost:5042/en-US/docs/Web/API/AudioContext/setSinkId/index.json (in the test group) is modified.