unavailable_after behaves like a timer that turns into noindex once the date passes. If that date is in the past, the page has already been told to drop out, often long after anyone remembered setting it. A past unavailable_after date acts as a timed noindex that has already fired.
Why does unavailable_after date in the past matter for AI search?
The page silently drops from the index after the date.
How do you fix it?
Remove or update the date.
How do you find it on your site?
- Search the robots directives and headers for unavailable_after.
- Parse the date and compare it to today.
- If it is in the past, the page is effectively noindexed.
- Remove the directive or set a future date if expiry is genuinely intended.
Which ranking and citation factors does it touch?
Once the date passes the effect is the same as noindex, so the page cannot rank or be cited until the directive is removed and the page is recrawled.
What is the impact?
High/blocking once elapsed. Direct.
What is the evidence?
unavailable_after removes the page after the specified date. Google Search Central, Robots Meta Tags Specifications
Frequently asked questions about unavailable_after date in the past
What does "unavailable_after date in the past" mean?
A past unavailable_after date acts as a timed noindex that has already fired.
How do you fix unavailable_after date in the past?
Remove or update the date.