unavailable_after: schedule a page to drop out of Google
How the unavailable_after meta tag and X-Robots-Tag rule work, which date formats Google accepts, and when a 404, 410 or noindex is the better choice.
By Crawlito · 8 min read
In short
unavailable_after tells Google not to show a page in search results after a set date and time, and it works in a robots meta tag or an X-Robots-Tag header.
Google accepts widely adopted date formats including RFC 822, RFC 850 and ISO 8601, and ignores the rule if the date is not valid.
After the date, Google says Googlebot decreases the crawl rate of the URL considerably, but the page itself keeps returning 200 to visitors.
The rule only works if robots.txt lets Googlebot fetch the page, because a blocked page's indexing rules are never read.
Google documents unavailable_after; check each other search engine's and AI operator's own documentation before relying on it there.
unavailable_after is a robots rule that tells Google not to show a page in search results after a date and time you choose. You set it once, when the page is published, in a robots meta tag or an X-Robots-Tag HTTP header, and Google stops showing the page after that moment without anyone editing it again. It suits events, limited offers, listings and job ads that have a known end date. If the date is not valid, Google ignores the rule without any warning, so the format matters.
This post covers the syntax, the formats Google accepts, what happens after the date, and when a 404, 410 or a later noindex is the better tool. The facts come from Google's robots meta tag documentation, read on 15 November 2026. For how noindex and the snippet rules affect AI Overviews and other AI tools, see noindex, nosnippet and X-Robots-Tag for AI search.
unavailable_after syntax in a meta tag and an X-Robots-Tag header
Google describes the rule in one line: "Do not show this page in search results after the specified date/time." By default there is no expiry date, so without it a page may be shown indefinitely.
In HTML, put it in the <head>. Google's own example uses a date only:
For PDFs, images and other files without a <head>, send the same rule as a header. Google's example pairs it with another rule on a separate line:
http
HTTP/1.1 200 OK
X-Robots-Tag: noimageindex
X-Robots-Tag: unavailable_after: 25 Jun 2010 15:00:00 PST
The header can name a crawler before the rules, for example X-Robots-Tag: googlebot: unavailable_after: 31 Dec 2026 23:59:59 GMT. Rules without a crawler name apply to all crawlers. Header configuration for nginx, Apache, Cloudflare and Vercel is covered in X-Robots-Tag for PDF files.
A few rules from Google's documentation apply to all of these:
Rule names and values are case-insensitive, in both the tag and the header.
Rules can be combined in a comma-separated list or split across separate meta tags.
When rules conflict, the more restrictive one applies. A page with noindex and a future unavailable_after date is already out of results.
Which date formats Google accepts
Google says the date and time "must be specified in a widely adopted format including, but not limited to" RFC 822, RFC 850 and ISO 8601. It also says: "The rule is ignored if no valid date/time is specified." An ignored rule fails silently, and the page stays eligible to be shown.
Format
Example
Notes
ISO 8601 date only
2026-12-31
Used in Google's meta tag example; Google does not document which time or time zone a date alone means
ISO 8601 with offset
2026-12-31T23:59:59+00:00
Unambiguous; also valid under RFC 3339, a profile of ISO 8601
ISO 8601 in UTC
2026-12-31T23:59:59Z
RFC 3339 defines Z as a UTC offset of 00:00
RFC 822 style
31 Dec 2026 23:59:59 GMT
Matches the shape of Google's header example
Three habits keep the date valid:
Include a time and an offset. A date alone leaves the cut-off time to Google's interpretation. An event in Los Angeles that ends at 22:00 local time in winter ends at 06:00 the next day in UTC, so write the offset you mean.
Use one format across the site. Generate it from code, not by hand, so a template change cannot produce 31/12/2026 on some pages.
Never emit the rule with an empty value.unavailable_after: with nothing after it is not a valid date, so Google ignores it. If a listing has no end date, leave the rule out.
What Google does after the date
Once the date passes, Google stops showing the page in search results, and its documentation adds that "Googlebot will decrease the crawl rate of the URL considerably after the specified date and time." Nothing changes on your server: the page still returns 200 OK and anyone with the link can still open it.
That has three practical consequences:
The crawler must be able to read the rule. Google says that if a page is disallowed in robots.txt, its indexing and serving rules "will not be found and will therefore be ignored". Do not block expired listings in robots.txt.
Google has to have crawled the page since you added the rule. A rule added the day before the end date only works if Googlebot fetches the page in time. Add it at publication.
Extending the date may not be picked up quickly. Because crawling slows after the date, an event that is extended after its old end date has passed may take time to come back. Google does not document how long. If dates often move, update the rule before the old date arrives.
Google's AI features documentation says a page must be "indexed and eligible to be shown in Google Search with a snippet" to appear as a supporting link in AI Overviews or AI Mode. A page past its unavailable_after date no longer meets that, so it drops out of those features as well.
unavailable_after vs 404, 410 or a later noindex
The choice depends on whether the page should stay online for people, and whether you know the end date in advance.
Approach
Page for visitors
How Google drops it
Best for
unavailable_after set at publication
Stays online, returns 200
Stops showing it after the date, then crawls it less
Known end dates, pages you keep as an archive
noindex added after the end
Stays online, returns 200
Drops it the next time it crawls the page
End dates not known in advance
404 or 410
Gone
Removes it after crawling the error
Pages with no ongoing value
301 to a replacement
Sent to the new page
Follows the redirect
A real successor, such as next year's event
noindex added later needs a deployment or a scheduled job at the right moment, and Google only sees it on its next crawl, which its block indexing guide says can take months for some pages. unavailable_after is already on the page when the date arrives. The trade-off is that it is only as accurate as the date you publish: a job filled early or an event cancelled still needs a manual change.
If a page will not be kept, a status code is clearer than any meta rule. 410 vs 404 for deleted pages covers which to use. For job ads, Google's job posting documentation lists its own removal methods: a validThrough date in the past, removing the JobPosting markup, or a 404 or 410. unavailable_after is not one of them, so follow that list for jobs, as expired job postings still on Google explains.
How to generate it from a listing's end date
Most listings already store an end date: an event's end time, an offer's expiry, a job's closing date. Build the rule from that field in the server-rendered template, so every page gets it without editorial work.
A small helper in Node.js that returns an ISO 8601 value with a UTC offset, or nothing when the date is missing or invalid:
js
function unavailableAfter(endDate) {
if (!endDate) return null;
const d = new Date(endDate);
if (Number.isNaN(d.getTime())) return null;
// e.g. 2026-12-31T22:59:59Z
return d.toISOString().replace(/\.\d{3}Z$/, "Z");
}
Use it in the page template:
html
<!-- only rendered when unavailableAfter() returned a value -->
<meta name="robots" content="unavailable_after: 2026-12-31T22:59:59Z">
Or send it as a header from an Express route, which also works for PDFs and other files:
Store the end date with its time zone in the database, and decide whether the rule should fire at the end of the event or some time later, for example a week, so people searching for a recent event can still find the recap. Keep the rule in the HTML the server sends rather than adding it with JavaScript after load, since crawlers that do not run JavaScript never see it. If the page also has Event markup, keep its endDate consistent with the same field; the Event schema guide covers those properties.
Check the value by eye. It should be one of the formats above, with the year, month and day in the order you intended and a time zone.
Confirm robots.txt allows the URL for Googlebot, or the rule is never read.
Use URL Inspection in Search Console to view the HTML Googlebot fetched and confirm the tag is there. Google's documentation does not describe a report that shows unavailable_after dates, so the inspection tool is your evidence.
Test a listing with no end date too, to make sure the template leaves the rule out rather than printing an empty value.
Support outside Google
Google's documentation is the one we found that defines unavailable_after. Bing publishes its own help page on the robots meta tags it supports; check that page for the rule before relying on it for Bing and Copilot. We found no documentation of the rule from OpenAI, Anthropic or Perplexity at the time of writing. A crawler that does not support it will simply ignore it, so the page stays indexable there.
If a page must leave every search engine and AI tool, change what the server returns after the date: a 404 or 410, a noindex, or a redirect. For product pages that come and go, out-of-stock products in AI search covers what to keep live instead.
Frequently asked questions
Does unavailable_after delete the page?
No. It only stops Google showing the page in search results after the date. The page keeps returning 200 OK and stays reachable for anyone with the link.
What happens if the date format is wrong?
Google ignores the rule if no valid date or time is given, and the page stays eligible to be shown. Generate the value from code in an ISO 8601 or RFC 822 format with a time zone.
Can I use unavailable_after on PDFs?
Yes. Send it in an X-Robots-Tag HTTP header, which Google supports for any file type, including files that have no HTML <head>.
Can I combine it with other robots rules?
Yes, in a comma-separated list or separate tags. When rules conflict, Google applies the more restrictive one, so a noindex on the same page applies as soon as Google reads it, whatever the date.
Does Bing support unavailable_after?
Check Bing's help page on supported robots meta tags before relying on it. If you need a page out of Bing on a date, a noindex or a 404 or 410 after that date is the safer choice.
Check what your listing pages send
A missing or malformed date fails without any warning. Run the free check on a live event or listing page to see the meta robots tags and X-Robots-Tag header it sends, alongside the robots.txt rule that decides whether crawlers can read them.
How the X-Robots-Tag HTTP header controls indexing and snippets for PDFs and images, with nginx, Apache, Cloudflare and Vercel examples and how to test it.
How nosnippet, max-snippet, data-nosnippet and noindex control AI Overviews and AI Mode, what other AI tools document, and how to set X-Robots-Tag for PDFs.