Name the quietest month in destination meta descriptions (CTR) - #38
Merged
Merged
Conversation
Destination meta descriptions named only the busy months and closed with a
generic "find the quietest time to visit", never stating the actual quiet
month. That is exactly the answer "best time to visit {name}" searchers want
in the SERP snippet. The page already computes quietIdx in summarizeBusyness
but generateMetadata ignored it.
Now the description reads "Busiest in {months}, quietest in {quietMonths}. ...
pick the best time to visit." Both lists are capped at three months so the
snippet stays inside the SERP truncation length and the quiet month is never
pushed out of view by a long peak. Copy updated for en/de/es/fr (es/fr are
machine-translated, native review welcome).
Why: several destination pages rank on page 1 (pos 6-10 in Search Console:
new-york-city, montreal, lake-iseo, strasbourg, byron-bay) yet get almost no
clicks. Ranking is fine, the snippet was not answering the query. Meta copy is
the direct CTR lever on the one part of the site that already earns clicks.
Verified: tsc + eslint + next build clean. Local prod server confirmed the
quiet month renders per destination (byron-bay quietest May/June/July =
Southern-Hemisphere winter, strasbourg quietest Jan/Feb/Mar, hainan quietest
Jun/Jul/Aug) and a bad slug still 404s. No em-dashes in copy.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Destination meta descriptions named only the busy months and ended with a generic "find the quietest time to visit", never stating the actual quiet month. That is precisely the answer "best time to visit {name}" searchers want in the SERP snippet. The page already computes quietIdx in summarizeBusyness, but generateMetadata used only peakIdx.
Several destination pages already rank on page 1 in Search Console (28-day window, 2026-07-29 to 2026-08-22): new-york-city pos 10 (90 impr), lake-iseo pos 6 (44 impr), montreal pos 8 (44 impr), strasbourg pos 7 (24 impr), byron-bay pos 9. Ranking is fine but clicks are near zero. The snippet was not answering the query, so this is a pure on-page CTR lever on the one part of the site that already earns clicks.
Change
Description now reads: Is {name} busy? Busiest in {months}, quietest in {quietMonths}. See {name} month-by-month crowd calendar and pick the best time to visit.
Audit reference
Daily website growth audit, Tuesday (Keywords and On-Page focus), 2026-08-25.
Verification
Co-authored-by: Claude Opus 4.8