Guide
Evergreen vs Event-Led Sports Content
Give every recurring event one permanent page that is updated each year, and keep one-off pages for things that happen once. That split keeps links, avoids near-duplicate pages, and makes honest update dates easy.
By FixtureLoom Editorial DeskPublished Updated 3 min read
Key points
- Recurring events (a final, a festival, a Grand Slam) suit one permanent URL updated each year.
- Google's helpful content guidance warns against changing page dates to seem fresh when content has not substantially changed.
- Google uses sitemap lastmod only when it is consistently and verifiably accurate.
- Many near-identical fixture pages can fall under Google's doorway or scaled content abuse policies.
Three page types
| Type | Example | URL | Lifespan |
|---|---|---|---|
| Evergreen reference | How the playoffs work; rules of a race | Permanent, no year | Years; updated when rules change |
| Recurring event hub | A festival, a Slam, a final | Permanent, year in title and text | Updated each edition |
| One-off event page | A single match preview or a special event | Event-specific | Days to weeks; then kept as a record or merged |
Why one URL for a recurring event
A page about a yearly event gathers links and history each time it runs. Moving to a new URL every year starts from zero and splits signals between old and new pages. Keeping one URL and updating it means the page is ready before interest returns. This is our recommendation; Google has published similar advice for recurring retail events, which we could only read quoted in trade press, so we do not quote it here.
Honest dates
- Change the visible "Updated" date and
dateModifiedonly when the content changed in a meaningful way, such as a new date, new runners or a result. - Keep
lastmodin the sitemap equal to the last significant update. Google ignores it when it is not consistently accurate, and it says a copyright year change is not a significant update. - Never set a page date to the event date. Google says page dates describe the publication or update of the page, not the events it covers.
Templated fixture pages
A page for every fixture, generated from a template with only team names changed, is the pattern Google's spam policies describe. Doorway abuse covers pages created to rank for specific, similar queries; scaled content abuse covers many pages generated mainly to manipulate rankings. If a fixture page adds nothing a reader cannot get from the fixture list, fold it into a round or event hub.
Retiring event pages
- If the page will be useful next year, keep it and add the result.
- If it duplicates a hub, redirect it to the hub with a permanent redirect.
- If it has no value and no links, remove it and let it return 404 or 410.
Questions
Should the year be in the URL of an annual event page?
We recommend a permanent URL without the year, with the year in the title and text, so the page keeps its links from edition to edition.
Can I update the date on a page to keep it fresh?
Only when the content changed meaningfully. Google's helpful content guidance warns against changing dates to make pages seem fresh.
Are automated fixture pages against Google's policies?
They can be, if they are near-identical and made mainly to rank. Google's doorway and scaled content abuse policies describe that pattern.
Sources
- Google Search Central, Creating helpful, reliable, people-first content, last updated October 5, 2026.
- Google Search Central, Build and submit a sitemap, last updated July 8, 2026.
- Google Search Central, Influence your byline dates in Google Search, last updated December 10, 2025.
- Google Search Central, Spam policies for Google web search, last updated August 28, 2026.
Found an error? Tell the editors with a link to the source. Corrections are noted on the page they change (corrections policy).