Google Lunar X Prize
inducement prize space competition
The Google Lunar X Prize (GLXP) was a 2007–2018 inducement prize space competition organized by the X Prize Foundation, and sponsored by Google. The challenge called for privately funded teams to be the first to land a lunar rover on the Moon, travel 500 meters, and transmit back to Earth high-definition video and images.
The original deadline was the end of 2014, with additional prize money for a landing by 2012. In 2015, XPRIZE announced that the competition deadline would be extended to December 2017 if at least one team could secure a verified launch contract by 31 December 2015. Two teams secured such a launch contract, and the deadline was extended. In August 2017, the deadline was extended again, to 31 March 2018.
Entering 2018, five teams remained in the competition: SpaceIL, Moon Express, Synergy Moon, TeamIndus, and Team Hakuto, having secured verified launch contracts with Spaceflight Industries, Rocket Lab, Interorbital Systems, and ISRO (jointly for the last two teams).
On 23 January 2018, the X Prize Foundation announced that "no team would be able to make a launch attempt to reach the Moon by the [31 March 2018] deadline ... and the US$30 million Google Lunar XPRIZE will go unclaimed." On 5 April 2018, the X Prize Foundation announced that the Lunar XPRIZE would continue as a non-cash competition.
On 11 April 2019, the SpaceIL Beresheet spacecraft crashed while attempting to land on the Moon.
The public source identifies “Google Lunar X Prize” as inducement prize space competition. This brief keeps that definition visible, then builds a research path around Google, Lunar and Prize.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Google Lunar X Prize”, the useful work is to connect “inducement prize space competition” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 26, 2026. The linked authority identifier is Q749700. 1 of 3 selected statements include explicit references; 2 carry qualifiers and 0 use preferred rank. The first chronological checks are 2007, 2018, 2014 and 2012.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Google Lunar X Prize”, its source revision and the description used here.
- Expand the search: follow Google Lunar X Prize primary sources, Google Lunar X Prize archive and Google research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Google Lunar X Prize”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Google Lunar X Prize” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.