Wikipedia:Deletion review
From Wikipedia, the free encyclopedia
Deletion review (DRV) is for reviewing speedy deletions and outcomes of deletion discussions. This includes appeals to delete pages kept after a prior discussion.
If you are considering a request for a deletion review, please read the "Purpose" section below to make sure that is what you wish to do. Then, follow the instructions below.
Purpose
Deletion review may be used:
- if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
- if a speedy deletion was done outside of the criteria or is otherwise disputed;
- if there were substantial procedural errors in the deletion discussion or speedy deletion (including information of socks participating in the discussion);
- if significant new information has come to light since a deletion that would justify undeleting the page, and previously deleted content may be helpful for writing a new version of the page – provided that an administrator declined undeleting the page and their decision is being challenged;
- if a page has been wrongly deleted with no way to tell what exactly was deleted;
- if the deleted page cannot be recreated because of preemptive restrictions on creation that cannot be removed without a consensus after removal was requested and declined. Such restrictions include creation protection and title blacklisting.
Deletion review should not be used:
- to request undeletion of a page deleted on grounds which permits summary undeletion. Place such requests at Wikipedia:Requests for undeletion. Deletion review can be used if such a request is declined. (Undeletion may also be requested there for pages which are not explicitly eligible for summary undeletion, but such a request is usually declined; it is worth trying when substantial new sources have arisen after an article was deleted.)
- to ask for permission to write a new version of a page which was deleted, unless a preemptive restriction on creation is in place for which removal was requested and declined. In the case of:
- creation protection – request removal of the protection from the protecting administrator or, if the administrator is unavailable or non-responsive, request at Wikipedia:Requests for page unprotection.
- title blacklisting – file a delisting request at MediaWiki talk:Titleblacklist.
- because of a disagreement with the deletion discussion's outcome that does not involve the closer's judgment (a page may be renominated after a reasonable timeframe);
- to repeat arguments already made in the deletion discussion;
- to argue technicalities (such as a deletion discussion being closed ten minutes early);
- to point out other pages that have or have not been deleted (as each page is different and stands or falls on its own merits);
- to challenge an article's deletion via the proposed deletion process, or to have the history of a deleted page restored behind a new, improved version of the page, called a history-only undeletion (please go to Wikipedia:Requests for undeletion for these);
- to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
- to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed).
Copyright violating, libelous, or otherwise prohibited content will not be restored.
Instructions
Steps to list a new deletion review
Before listing a review request, please:
- Consider attempting to discuss the matter with the closer as this could resolve the matter more quickly. There could have been a mistake, miscommunication, or misunderstanding, and a full review may not be needed. Such discussion also gives the closer the opportunity to clarify the reasoning behind a decision.
- Check that it is not on the list of perennial Deletion review requests. Repeated requests every time some new, tiny snippet appears on the web have a tendency to be counter-productive. It is almost always best to play the waiting game unless you can decisively overcome the issues identified at deletion.
- If your request is completely non-controversial (e.g., restoring an article deleted with a PROD, restoring an image deleted for lack of adequate licensing information, asking that the history be emailed to you, etc.), use Wikipedia:Requests for undeletion instead.
- Be aware that requests which appear to be written by large-language models will normally be summarily denied. Write in your own words.
| 1. |
and paste the template immediately below the "Add a new entry BELOW THIS LINE ..." comment. Before publishing your changes, replace {{subst:drv2
|page=File:Foo.png
|xfd_page=Wikipedia:Files for deletion/2009 February 19#Foo.png
|reason=
}} ~~~~
|
| 2. |
Inform the editor who closed the deletion discussion by adding the following at the bottom of their user talk page:
|
| 3. |
For nominations to delete, merge, or redirect an article previously kept or slated for merging, place |
| 4. |
Leave notice of the deletion review at the very top of the original AfD discussion, above all other content:
|
Commenting in a deletion review
Any editor may express their opinion about an article or file being considered for deletion review. In the deletion review discussion, please type one of the following opinions preceded by an asterisk (*) and surrounded by three apostrophes (''') on either side. If you have additional thoughts to share, you may type this after the opinion. Place four tildes (~~~~) at the end of your entry, which should be placed below the entries of any previous editors:
- Endorse the original closing decision; or
- Relist on the relevant deletion forum (usually Articles for deletion); or
- List, if the page was speedy deleted outside of the established criteria and you believe it needs a full discussion at the appropriate forum to decide if it should be deleted; or
- Overturn the original decision and optionally an (action) per the Guide to deletion. For a keep decision, the default action associated with overturning is delete and vice versa. If an editor desires some action other than the default, they should make this clear; or
- Allow recreation of the page if new information is presented and deemed sufficient to permit recreation.
Examples of opinions for an article that had been deleted:
- *'''Endorse''' The original closing decision looks like it was sound, no reason shown here to overturn it. ~~~~
- *'''Relist''' A new discussion at AfD should bring a more thorough discussion, given the new information shown here. ~~~~
- *'''Allow recreation''' The new information provided looks like it justifies recreation of the article from scratch if there is anyone willing to do the work. ~~~~
- *'''List''' Article was speedied without discussion, criteria given did not match the problem, full discussion at AfD looks warranted. ~~~~
- *'''Overturn and merge''' The article is a content fork, should have been merged into existing article on this topic rather than deleted. ~~~~
- *'''Overturn and userfy''' Needs more development in userspace before being published again, but the subject meets our notability criteria. ~~~~
- *'''Overturn''' Original deletion decision was not consistent with current policies. ~~~~
Remember that deletion review is not an opportunity to (re-)express your opinion on the content in question. It is an opportunity to correct errors in process (in the absence of significant new information), and thus the action specified should be the editor's feeling of the correct interpretation of the debate. Deletion review is facilitated by succinct discussions of policies and guidelines; long or repeated arguments are not generally helpful. Rather, editors should set out the key policies and guidelines supporting their preferred outcome.
The presentation of new information about the content should be prefaced by Relist, rather than Overturn and (action). This information can then be more fully evaluated in its proper deletion discussion forum. Allow recreation is an alternative in such cases.
The usage of large language models such as ChatGPT to create deletion review nominations or comments is strongly discouraged and such contributions are liable to be removed or collapsed by an uninvolved administrator.
Temporary undeletion
Admins participating in deletion reviews are routinely requested to restore deleted pages under review and replace the content with the {{temporarily undeleted}} template, leaving the history for review by everyone. However, copyright violations and violations of the policy on biographies of living persons should not be restored.
Closing reviews
A nominated page should remain on deletion review for at least seven days, unless the nomination was a proposed deletion. After seven days, an administrator will determine whether a consensus exists. If that consensus is to undelete, the admin should follow the instructions at Wikipedia:Deletion review/Administrator instructions. If the consensus was to relist, the page should be relisted at the appropriate forum. If the consensus was that the deletion was endorsed, the discussion should be closed with the consensus documented.
If the administrator closes the deletion review as no consensus, the outcome should generally be the same as if the decision was endorsed. However:
- If the decision under appeal was a speedy deletion, the page(s) in question should be restored, as it indicates the deletion was not uncontroversial. The closer, or any editor, may then proceed to nominate the page at the appropriate deletion discussion forum, if they so choose.
- If the decision under appeal was an XfD close, the closer may, at their discretion, relist the page(s) at the relevant XfD.
Ideally, all closes should be made by an administrator to ensure that what is effectively the final appeal is applied consistently and fairly. But, in cases where the outcome is patently obvious or where a discussion has not been closed in good time, it is permissible for a non-admin (ideally a DRV regular) to close discussions. Non-consensus closes should be avoided by non-admins unless they are absolutely unavoidable and the closer is sufficiently experienced at DRV to make that call. (Hint: if you are not sure that you have enough DRV experience then you don't.)
Speedy closes
- An objection to a proposed deletion can be processed immediately as though it were a request at Wikipedia:Requests for undeletion.
- Where the closer of a deletion discussion realizes their close was wrong, and nobody has endorsed, the closer may speedily close as overturn. They should fully reverse their close, restoring any deleted pages if appropriate.
- Where the nominator of a DRV wishes to withdraw their nomination, and nobody else has recommended any outcome other than endorse, the nominator may speedily close as "endorse" (or ask someone else to do so on their behalf).
- Certain discussions may be closed without result if there is no prospect of success (e.g. disruptive or sockpuppet nominations, if the nominator is repeatedly nominating the same page, a large language model is used to construct the request, or the page is listed at WP:DEEPER). These will usually be marked as "procedural close".
Active discussions
3 July 2026
2 July 2026
John Paczkowski
This page should really be restored and updated: I've been a journalist for well over two decades. Stories I've edited have won the Livingston, Polk, Pulitzer, Mirror, SABEW and NYFWA Impact awards, and journalists I've mentored have gone on to columnist roles at The New York Times, The Wall Street Journal and The Atlantic. I currently oversee tech, innovation, sustainability and VC coverage at Forbes. I previously ran BuzzFeed News' award winning tech desk. With Kara Swisher and Walt Mossberg, I helped found AllthingsD.com, where I was the first editorial hire. I accompanied them to Recode, where I oversaw our edit partnership with NBC. I got my start at The Mercury News where I wrote one of the first daily tech newsletters, Good Morning Silicon Valley. https://x.com/JohnPaczkowski https://www.forbes.com/sites/johnpaczkowski/ https://www.linkedin.com/in/pczki/ https://bsky.app/profile/pczki.bsky.social https://www.forbes.com/sites/forbespr/2022/05/26/forbes-names-john-paczkowski-executive-editor-of-innovation-and-technology/ Polk Award: https://www.buzzfeed.com/buzzfeedpress/buzzfeed-news-wins-george-polk-award Livington Award: https://news.umich.edu/livingston-awards-for-young-journalists-announce-2019-winners/ Mirror award: Ryan Mac, who reported to John and was edited by him, also won The Mirror: https://www.nytco.com/press/ryan-mac-joining-technology-team/ 2023 SABEW award: Kenrick Cai and Iain Martin worked for Paczkowski:Winner – Forbes Magazine; The AI Founder Taking Credit for Stable Diffusion’s Success Has a History of Exaggeration Kenrick Cai, Iain Martin John hired, mentored and edited Emily Baker White's award winning TikTok coverage: https://libraryfoundationsd.org/events/baker-white
https://fortune.com/2015/03/20/paczkowski-rocks-buzzfeeds-star-apple-reporter-is-earning-his-keep/
https://talkingbiznews.com/media-news/forbes-hires-four-buzzfeed-tech-news-staffers/ ~2026-38015-07 (talk) 17:51, 2 July 2026 (UTC)
- https://www.vox.com/2014/4/28/11626138/john-paczkowskis-back-with-daily-codered-column-on-recode
- https://www.buzzfeednews.com/author/johnpaczkowski
- https://www.buzzfeednews.com/article/johnpaczkowski/inside-iphone-7-why-apple-killed-the-headphone-jack
- https://daringfireball.net/linked/2014/05/02/recode-wwdc ~2026-38015-07 (talk) 17:54, 2 July 2026 (UTC)
- Are you, by any chance, referring to the article discussed here? If so, I'll be happy to fix the header for you. As it stands, you copied the example without following the instructions to replace "Foo" with the actual page you are discussing. Owen× ☎ 18:08, 2 July 2026 (UTC)
- Comment - If OwenX has correctly inferred what the appellant is asking about, then this is another version of Wikipedia:Deletion review/Log/2024 March 25, a malformed request by a new editor or temporary editor. Robert McClenon (talk) 18:27, 2 July 2026 (UTC)
- Procedural Close as malformed. We don't need to waste our time assembling and considering a Deletion Review when the filing editor can't even provide a title or formatting and gives us nothing but a URL dump. I am aware that some editors think that we should be helpful. So do I, but there is a limit to how much help we should give to users who pop up and don't even try to use Wikipedia correctly. Robert McClenon (talk) 18:27, 2 July 2026 (UTC)
- Endorse if we are reviewing Wikipedia:Articles for deletion/John Paczkowski. This closure was already reviewed Wikipedia:Deletion review/Log/2024 March 25. Robert McClenon (talk) 00:36, 3 July 2026 (UTC)
- Allow submission of draft to AFD. That will be a waste of time if the draft is prepared with the same lack of skill as this filing, but that is their problem. Robert McClenon (talk) 00:36, 3 July 2026 (UTC)
- Endorse. This is the wrong place to seek approval for recreation. Use WP:AfC. Read advice at WP:THREE. —SmokeyJoe (talk) 13:47, 3 July 2026 (UTC)
1 July 2026
Dabrowski-Stefani tennis partnership
I am requesting review because there have been significant developments since the AfD closed. Several participants based their !votes on the assumption that the partnership had ended permanently and was unlikely to reunite. However, Dabrowski and Stefani reunited for the 2026 season and have continued to compete together, adding further notable achievements after the discussion concluded. In addition to their previous records, they also reached multiple Grand Slam and WTA Tour semifinals and won various WTA titles across every tournament category (250, 500, 1000) on all major court surfaces and they have continued to add to their résumé since reuniting, becoming one of the three most successful pairs of 2026. These post-AfD developments were not available to participants in the original discussion and may materially affect the assessment of the partnership's standalone notability. Haddad Maia fan (talk) 19:12, 1 July 2026 (UTC)
- what sources are there that discuss the partnership to GNG level? Spartaz Humbug! 22:44, 1 July 2026 (UTC)
- Endorse the close if this is an appeal of the close. Robert McClenon (talk) 22:54, 1 July 2026 (UTC)
- Allow Submission of Draft for AFC review. DRV approval is not required to allow the submission of a draft. The draft will need to answer Spartaz's question of what sources satisfy GNG, Robert McClenon (talk) 22:54, 1 July 2026 (UTC)
- Endorse the 13 month old AfD, deny permission to recreate because no new sources are offered, but Draftify to allow new sources to be added at leisure. Read advice at WP:THREE. Use AfC processes if you think the draft overcomes the reasons for deletion in the 2025 AfD. SmokeyJoe (talk) 14:41, 2 July 2026 (UTC)
- Endorse as delete was clearly the only plausible close. However, new information has come to light which may affect the notability of the subject, as per WP:DRVPURPOSE #4. Restore to draft to allow Haddad Maia fan or any other interested user to improve with newer references. A Google News search of the topic shows several articles which post-date the AFD. I did not review these references against GNG as deletion review is not a content forum. Frank Anchor 14:49, 2 July 2026 (UTC)
- In response to @Spartaz's question regarding sources satisfying WP:GNG: since the AfD closed, there has been additional independent coverage discussing the partnership itself, beyond routine match merely reporting individual match results.
- @Frank Anchor also noted above that a Google News search identifies several articles published after the AfD.
- The examples below are some of those newer sources that I believe demonstrate the changed evidentiary landscape:
- Ge (21 November 2025) covered the reunion of Dabrowski and Stefani for the 2026 season in a dedicated article. It discusses the history of the partnership, why they reunited, their previous achievements together, the interruption caused by Stefani's injury, and expectations for the renewed partnership.
- UOL (28 January 2026) published a feature on the pair returning to a Grand Slam semifinal four years later. The article reviews the partnership from 2021 onward, discusses Stefani's injury, their brief reunion in 2023, the split, and the decision to reform the team for 2026, rather than simply reporting the Australian Open result.
- The Canadian Press (21 February 2026) covered their Dubai WTA 1000 title with a focus on the reunion of the partnership, its history, quotes from both players about the partnership, and the significance of their renewed success. This is independent coverage centred on the partnership itself rather than a routine match report.
- WTA (21 February 2026) In addition, the WTA published a retrospective on the partnership that recounts its history, "Dabrowski and Stefani win first title together since 2022 in Dubai".explains the reunion, and includes comments from both players. While this is not an independent source for GNG purposes, it provides additional context regarding the partnership itself.
- One of the premises underlying the AfD discussion was that the partnership had effectively ended and was unlikely to resume. Since then, Dabrowski and Stefani have reunited for the 2026 season and have continued to add to their record, including two further Grand Slam semifinals, another WTA 1000 title and additional tour titles and continued deep runs on tour.
- I appreciate that DRV is not intended to determine notability itself. My point is simply that the evidentiary record has changed materially since the 2025 AfD. If the consensus is that these newer sources should instead be assessed through Articles for Creation, I am happy to proceed through that process. Haddad Maia fan (talk) 22:48, 2 July 2026 (UTC)
- Those sources hardly seem to be very significant coverage. Is there any reason this can't be covered briefly on the biographies of each respective player?
- In any case, Restore to draft. I would personally not !vote to keep this standalone article at an AfD based on the sourcing provided here, nor would I accept any AfC draft that had these sources, but that doesn't impinge on the relevant argument here (as made by Frank Anchor). Katzrockso (talk) 00:57, 3 July 2026 (UTC)
- The issues that existed at the time of the AFD still exist. There are many doubles teams which achieved far far better results (winning even career grand slams together) which don’t have their own articles. The bar for doubles teams in tennis to be independenly notable is far far higher than you think. Two masters 1000 titles and no grand slam finals just doesn’t cut it. Tvx1 13:18, 3 July 2026 (UTC)
Hot Girl Walk (closed)
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
In my opinion the discussion has been closed too quickly, I think it's odd to claim no consensus after so many comments in one week. The closure also doesn't seem to have been done correctly as the notice is still on the article and was closed by a non admin without any note along those lines. Apologies if this is the wrong place for this, I'm not so familiar with deletion admin. orangesclub 🍊 16:51, 1 July 2026 (UTC) |
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
29 June 2026
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
I was told that my deletion review proposal could not be accepted because I had received help from an LLM. Fine. Since I still believe I manage very well with English, I will proceed, and this time I will not even use a translator. So, I believe that the deletion of the page carried out by administrator Owen was unfair, because he distorted the score—which had been 3-2 in favor of Delete over Keep—into a 4-1 with two errors. The first error attributed a Delete vote to Lijil, who had opened the AfD, but the AfD had actually been wanted by me. In fact, there is proof, which you can find in the history, that I had requested a third opinion and had discussed it on the talk page. However, not having found any participants, I decided, perhaps on the advice of an admin, to open or to request the opening of the deletion page. Therefore, Lijil's "non vote", for this reason, cannot be considered delete. For the same reason, the vote of TortugaP cannot be considered invalid—meaning it must be considered valid, whereas Owen had instead canceled it, claiming that the user had registered just for this purpose. On the contrary, we have seen in the global contributions that Tortuga P had already been present on the Catalan Wikipedia for quite some time. But beyond this, I generally oppose the deletion of the Palamara article because I have demonstrated updating the artiche also with the new that IHI in May sayd that is ready to start the construction of the Messina Bridge such as had do with Akashi Bridge and in 13 June the Italian and Japanese Prime Ministers had a summit and told the the Messina Bridge is very very important for the cooperation of two natios, both on the talk pages and in the deletion discussion, that 9 out of 16 sources are national. Therefore, his notoriety regarding the Strait of Messina Bridge project is high enough to be considered sufficient to have a Wikipedia page as an engineer. Moreover, there are no specific notability guidelines for engineers, but there are those for WP:CREATIVE professionals and the General Notability Guidelines (GNG), which Palamara absolutely satisfied. Therefore, I hope I have been brief enough. I request a deletion review. --Kasper2006 (talk) 10:47, 29 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
27 June 2026
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
I am formally requesting a Deletion Review of the AfD for the article "Giuseppe Palamara", which was closed by administrator Owen (talk · contribs) as "delete" based on an alleged consensus. The closure and the subsequent explanations provided by the closing administrator on his talk page rely on demonstrably false factual claims regarding user registration, an arbitrary invention of non-existent participant counts, and a severe misrepresentation of community consensus. 1. Factual Error and Misrepresentation of User Status (The "TortugaP" Keep Vote)
In his talk page response, administrator Owen justified discarding the Keep vote of user TortugaP (talk · contribs) by stating it was "a brand new account created for the purpose of voting on this AfD" and implying meatpuppetry. This is factually incorrect. Global account analysis (GUC) proves that TortugaP (talk · contribs) is an established contributor active on other language projects, such as the Catalan Wikipedia (ca.wikipedia), with a clear edit history dating back to at least April 2026—months before this AfD was opened. Furthermore, the user contributes from Catalonia, focused independently on regional infrastructure and historical bridges, demonstrating zero correlation or "call to arms" with the article creator in Italy. Disqualifying a legitimate cross-wiki editor's input based on a false premise is a severe administrative oversight that violates WP:BITE and WP:AGF. 2. Direct Invention of Participant Counts and Consensus Distortion
The actual breakdown of community members who took an explicit stance and voted in the AfD discussion was a tight 3-2 split:
On his talk page, Owen claimed there were "four participants arguing for deletion" to assert an artificial "4-to-1" split against retention. This fourth distinct voting participant does not exist. While user Lijil (talk · contribs) technically opened the debate as the nominator providing structural background, they did not cast a separate, independent vote, meaning the total count of delete proponents is strictly three. Even if the administrator had valid grounds to discount TortugaP (talk · contribs), the real count would be 3-1, not 4-1. More importantly, if we look at the independent community feedback by subtracting the two primary opposing parties—the active nominator who led the deletion push (Adri08 (talk · contribs)) and the main contributor of the article (Kasper2006 (talk · contribs))—the outside community was split at a minimal 2 to 1. A 2-1 margin (or 3-2 overall) represents a glaring lack of consensus under WP:CON. Fabricating an additional participant to claim a 4-1 "consensus" to delete is an unacceptable distortion of the process. Per WP:DELGROUP, when no clear consensus is formed, the default outcome should be to keep or extend the discussion. 3. Ad Hominem Deflection on Sourcing
Instead of evaluating the 16 secondary media sources provided—9 of which are major Italian national networks and outlets (such as RAI, Mediaset, and La7) providing independent expert coverage—the closing administrator dismissed the arguments by claiming the text "reads like it was generated by an LLM". Utilizing structural or language assistance to present a well-documented table of national media coverage is entirely within policy. An administrator cannot bypass a rigorous source assessment under WP:GNG and WP:SIGCOV simply by attacking the drafting style of a non-native English speaker. Conclusion
Because the closing administrator relied on a false claim to invalidate a valid Keep vote, invented a non-existent fourth Delete participant to inflate the numbers, and declared a "consensus" where independent editors were split 2-1, the closure violates standard consensus-building guidelines. I respectfully request that the deletion be overturned, the page restored, or moved back to a neutral, third-party discussion. Kasper2006 (talk) 23:58, 27 June 2026 (UTC)
The most unfair accusation that can be leveled against me is that my text was written by an LLM. I have already explained that, not being a native English speaker, sometimes I use a translator for assistance, but the arguments and thoughts are entirely my own. What is true, however, is that I am an expert wiki user. Therefore, before drawing the conclusion that Lijil automatically voted 'delete' by default simply because they opened the AfD, I would strongly advise Robert McCleon to review the entire history starting from April, when the article was first created, he can look at my contributions to see the steps I have taken. This was well before Adri08 brought their cross-wiki not-notability campaign over to en.wiki, in fact before his intervention the page had remained quiet in the namespace for almost a month. Doing so would reveal that it was actually myself who wanted the AfD process, after multiple attempts to obtain third-party opinions over several months had failed. It is a pity he did not check, because if he had, he would have noticed at least a few other editors there who had explicitly expressed their support for Palamara's notability. --Kasper2006 (talk) 06:53, 28 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
The merge discussion was not tagged at the merge target. It had the deletion tag on the page but no one responded to the deletion discussion. It was therefore closed after one relist as consensus to merge to the proposed target. The proposed target is the wrong target. The correct target would be Christ Embassy. I only noticed this when consensus to merge was tagged on a page I watch (Chris Oyakhilome). It is not clear that there's anything to merge though, and straight deletion might be better. Either way, discussion should be relisted for another week, with a tag at the proposed merge target, so that editors watching that page can be involved in the discussion. Attempted to request this be done informally yesterday at closer's talk page but the closer has not responded, despite continuing to edit (and close discussions). Requested action is to Relist for one week, properly tagged. Sirfurboy🏄 (talk) 08:30, 27 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
26 June 2026
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
This discussion was closed 8 days after it was opened, by which point it only had a few comments, which I thought had only indicated mixed consensus so far. I talked to the closing administrator, who provided this rationale:
Although I consider these points to be fair, I still think this discussion was closed too soon for the consensus to be considered quite clear just yet. – MrPersonHumanGuy (talk) 22:32, 26 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Recent discussions
25 June 2026
LoopMe
I'm contesting the deletion of the LoopMe article under G11 (unambiguous advertising). I believe this deletion was in error and the article meets Wikipedia's notability standards.
LoopMe is a significant UK-based adtech company with extensive coverage in independent, tier-one trade publications. The article is sourced primarily in AdExchanger, TechCrunch, Broadcasting+Cable, MediaPost, Digiday, and ExchangeWire (all highly renowned publications!). LoopMe has also been used as a data source for articles in non-trade publications including the BBC, CNBC and Forbes.
A G11 deletion assumes the article's purpose is to promote the company. But the article describes what LoopMe does (i.e. its business model, history, products, and industry standing) in neutral, factual language. It doesn't use marketing claims; it reports on third-party coverage. Describing a company's achievements, awards, and products is encyclopedic, not promotional. Wikipedia has similar articles on Criteo, Databricks, and other adtech/martech companies.
The product descriptions are grounded in trade publication reporting, not company marketing copy.
I'm more than happy for neutral editors to review the article and toning down any language that reads as promotional.
The article was deleted without discussion an opportunity for improvement before removal. I'm requesting restoration so the article can be reviewed and improved by the community. Hannahloopme (talk) 09:01, 25 June 2026 (UTC)
- Even this request reads like a promotional piece. If the article is written even close to the same tone and manner as this then you are better off to walk away and let someone else create it from scratch, if the company is indeed notable. McMatter (talk)/(contrib) 09:45, 25 June 2026 (UTC)
- I appreciate what you're saying but I'm just trying to make my case! Hannahloopme (talk) 09:49, 25 June 2026 (UTC)
- Its written in promotional language and is a paid for article that was restored to mainspace 3 times on successive days by the nominator after 3 different admins deleted it as a g11 I suggest that we endorse and salt. Multiple creations in these circumstances is disruptive and I question whether we should allow the nominator to continue editing. Spartaz Humbug! 10:23, 25 June 2026 (UTC)
- Please can you define promotional language? I wholeheartedly believe that I have been neutral in tone and I've given tons and tons of citations - both industry-specific press and in the general press (e.g. BBC). Hannahloopme (talk) 10:34, 25 June 2026 (UTC)
- its ref bombed and far from neutral. Spartaz Humbug! 16:13, 25 June 2026 (UTC)
- Please do not ask the volunteer editors at DRV to assist you (a paid editor) in writing or rewriting your article. Robert McClenon (talk) 00:02, 26 June 2026 (UTC)
- its ref bombed and far from neutral. Spartaz Humbug! 16:13, 25 June 2026 (UTC)
- To add - I complied with Wikipedia's policies in disclosing my affiliation to the subject too! Hannahloopme (talk) 10:35, 25 June 2026 (UTC)
- Please can you define promotional language? I wholeheartedly believe that I have been neutral in tone and I've given tons and tons of citations - both industry-specific press and in the general press (e.g. BBC). Hannahloopme (talk) 10:34, 25 June 2026 (UTC)
- Endorse and SALT per Spartaz. I appreciate the appellant declaring her paid editing status--eventually, after being prodded to do so by an admin. But in recreating the article in mainspace a day after it was deleted, she was not only violating WP:PAID/WP:COI, but also engaging in an edit war. The 8 June 2026 revision removed a lengthy product listing section, but was otherwise essentially identical to the one deleted the previous day, promotional tone and all. While I'm not yet ready to swing the ban hammer, if there's any attempt to circumvent the SALT with title-gaming, a p-block from mainspace is in order. Owen× ☎ 11:25, 25 June 2026 (UTC)
- Please can you try to appreciate that I've been trying my very best to stick to Wikipedia's rules. I added a paid disclosure note as soon as I found out that was required. I can infer the meaning of edit war but that wasn't my intention. I'm trying my best to understand and adhere to a complex system of rules. I'm also confused because so many similar companies have pages with far fewer citations: Quantcast, Criteo, OpenX etc - so I don't understand how those pages are live when LoopMe was taken down? Hannahloopme (talk) 12:11, 25 June 2026 (UTC)
- I understand how daunting it can be for a new user on Wikipedia to learn our elaborate and often complex policies and guidelines. But let me boil things down to this: on 5 June, you were notified that the article was tagged for speedy deletion, along with a clear explanation of the reason for tagging, and links to relevant policy and steps to contest such a deletion. You did not engage with the editor placing the notice on your Talk page, nor follow the guidelines to contest it. The article was deleted on Sunday, 7 June, at 4pm UK time. The next morning, Monday at 08:46 UK time, you simply recreated the article, minus one section. This does not come across as the action of someone who is engaging with Wikipedia in good faith. Arguments pointing to other companies with articles here are typically rejected; see WP:OTHERSTUFFEXISTS for details. As for earned vs. paid, how long would it take us to find examples of LoopMe buying ad space in one of MediaPost's 20+ publications? I don't think you want to go down that path. In general, trade journals are considered non-independent sources in almost all cases. Owen× ☎ 15:10, 25 June 2026 (UTC)
- Please can you try to appreciate that I've been trying my very best to stick to Wikipedia's rules. I added a paid disclosure note as soon as I found out that was required. I can infer the meaning of edit war but that wasn't my intention. I'm trying my best to understand and adhere to a complex system of rules. I'm also confused because so many similar companies have pages with far fewer citations: Quantcast, Criteo, OpenX etc - so I don't understand how those pages are live when LoopMe was taken down? Hannahloopme (talk) 12:11, 25 June 2026 (UTC)
- I have restored to Draft:LoopMe so non-admins can comment. Personally I'm not seeing the "unambiguous advertising or promotion" but no comment on notability. I also note it was accepted via AfC in April, so this probably deserves discussion at AfD rather than speed deletion — Martin (MSGJ · talk) 11:30, 25 June 2026 (UTC)
- To take one of many examples, the paragraph starting with,
LoopMe has contributed to broader industry discussion on AI through publications and podcasts
doesn't strike you as corporate marketing brochure penmanship? The repeated reliance on paid trade rag MediaPost for many of the claims is itself a red flag. Owen× ☎ 11:49, 25 June 2026 (UTC)- MediaPost articles are earned not paid! Hannahloopme (talk) 12:04, 25 June 2026 (UTC)
- What does that mean ? Spartaz Humbug! 16:14, 25 June 2026 (UTC)
- Earned media, I suspect. Left guide (talk) 19:03, 25 June 2026 (UTC)
- well that's a new concept to me. The problem with marketeers is an inability to communicate in a way that people who live outside their world can readily understand.
- I'm kind of blown away that the distinction appears something necessary to say. Spartaz Humbug! 20:39, 25 June 2026 (UTC)
- Yes exactly I was countering the claim that I was relying on articles in a 'paid trad rag'. Yes it's a trade publication. But we're talking about earned media rather than articles which you pay for. Hannahloopme (talk) 12:08, 29 June 2026 (UTC)
- Earned media, I suspect. Left guide (talk) 19:03, 25 June 2026 (UTC)
- What does that mean ? Spartaz Humbug! 16:14, 25 June 2026 (UTC)
- MediaPost articles are earned not paid! Hannahloopme (talk) 12:04, 25 June 2026 (UTC)
- To take one of many examples, the paragraph starting with,
- Technically overturn G11 but keep in draftspace. The article is not
exclusively promotional
and would not need to befundamentally rewritten to serve as [an] encyclopedia [article]
, as required by the policy. That said, this article as written would stand zero chance at AFD. Keeping it in draftspace allows for improvement to encyclopedic standards (both for notability and POV) to eventually be restored as a better article, or to be abandoned and G13ed. No opinion on whether or not the mainspace title should be salted. Frank Anchor 12:20, 25 June 2026 (UTC) - Endorse G11 If I had come across this in the AFC process I would have flagged it there for G11 as well. This is not an encyclopedic article written about a subject. It's a promotional fluff piece discussing how much affect they have had on the industry and boasting about the "coverage" they have recieved. It needs to be rewritten from the ground up by someone else. McMatter (talk)/(contrib) 12:57, 25 June 2026 (UTC)
- Endorse. I can find all of four sentences that could survive unchanged in a neutrally-written article, two of them dubiously so. —Cryptic 13:36, 25 June 2026 (UTC)
- Really? I would be curious for a sentence-by-sentence breakdown. Here are six that are factual and neutral and I'm not even halfway down the article....
- LoopMe is an advertising technology (AdTech) company headquartered in London, United Kingdom.
- In January 2022, LoopMe received a $120 million investment from private equity firm Mayfair Equity Partners, valuing the company at approximately $200 million
- LoopMe was founded in 2012 by Stephen Upstone and Marco van de Bergh, two executives who had previously worked together in mobile advertising at Ad Infuse (later acquired by Velti)
- In 2022, former OMD (part of Omnicom) CEO Mainardo de Nardis was appointed as Chair of LoopMe's board of directors.
- In December 2024, LoopMe acquired Chartboost from Zynga, a wholly-owned subsidiary of Take-Two Interactive (Nasdaq: TTWO), for an undisclosed sum. Zynga had originally acquired Chartboost in 2022 for $250 million
- Chartboost is a mobile programmatic advertising and monetization platform that connects app developers with marketers through immersive in-app advertising experiences, and operates a mediation business for gaming publishers Hannahloopme (talk) 14:00, 25 June 2026 (UTC)
- Please do not ask the volunteer editors at DRV for assistance in writing or rewriting an article. Robert McClenon (talk) 00:02, 26 June 2026 (UTC)
- Noted! Hannahloopme (talk) 12:11, 29 June 2026 (UTC)
- Please do not ask the volunteer editors at DRV for assistance in writing or rewriting an article. Robert McClenon (talk) 00:02, 26 June 2026 (UTC)
- are you able to explain that last paragraph in plain English and not marketing gobbledegook? Spartaz Humbug! 16:11, 25 June 2026 (UTC)
- Chartboost is a mobile programmatic advertising and monetization platform that connects app developers with marketers through advertising in app environments, and operates a mediation business for gaming publishers Hannahloopme (talk) 12:16, 29 June 2026 (UTC)
- One half out of seven, and the only reason that the first sentence might (dubiously) survive is because nobody thought to excise the gratuitous buzzword. —Cryptic 16:19, 25 June 2026 (UTC)
- Endorse and I'll note that the appeal sounds suspiciously like AI that has been told to minimize the chance of it being detected as AI. I realize this is a drown-the-witch sort of approach, but... We don't need this article, or any other article made on this company, which I believe fails NCORP in any event, nearly so much as they need a Wikipedia article to seem legitimate. Thank you, appellant, for disclosing your COI, but we just don't want your company's article here. Jclemens (talk) 14:23, 25 June 2026 (UTC)
- For the record, I refute the AI accusation. I was trying to explain my case clearly and in accordance with Wikipedia's rules/terminology. Hannahloopme (talk) 14:46, 25 June 2026 (UTC)
- Endorse and block Hannahloopme as they're clearly here only to promote LoopMe. Frank Anchor if you or any other non conflicted editor want to work on this, I'm happy to provide it for you as I'm sure you'd produce an acceptable draft if sourcing is available. Star Mississippi 18:07, 25 June 2026 (UTC)
- Endorse the speedy deletion from article space. The page is not so promotional that it should be speedily deleted from draft space. Robert McClenon (talk) 00:02, 26 June 2026 (UTC)
- ECP salt in article space, to allow a neutral reviewer to accept a submission from draft space to article space if/after it has been rewritten by a volunteer editor. Robert McClenon (talk) 00:02, 26 June 2026 (UTC)
- Endorse, salt, ECP, and block the nominator. Then they might begin to get the message. Stifle (talk) 08:10, 26 June 2026 (UTC)
- Keep deleted from mainspace and salt, retain in draftspace (where it is now). Wikipedia fundamentally does not want articles written by COI editors. Those editors tend to have an objective of "get X listed in Wikipedia", therefore edit with a bias, and community time is wasted policing for this bias. Such COI editors have a clear interest in pushing the boundaries of promotional content and tone. That is why COI editors have to disclose, and cannot write/place a COI article directly into mainspace. They need to draft it in Draft space, where the AfC process should decide whether to promote it to a mainspace article, with particular rigour to make sure the sourcing is good, the entity is notable, and the tone is nonpromotional. In this case, the current draft has indeed been written by a COI editor, and a quick look at the sourcing shows a tell-tale pattern of many sources, but not sufficiently in-depth and independent to support an article on this company. They're "Company had this (pretty routine) corporate/financial event", or "X from Company was interviewed and said ...". What will make the difference are sources that discuss, with an independent editorial voice, why this company is interesting and what makes it more notable than a run-of-the-mill company in the space. So at best more work is needed on the draft; at worst, there is just not enough independent in-depth coverage to warrant an article. Draftspace is the right place to figure it out, without trying to short circuit the process. Salting is appropriate, since there have been multiple attempts to do so. Technically, I'm not sure CSD G11 was appropriate (not unambiguous enough as advertising for my taste, per Martin above) but I also note the concerning history noted by Owen; an AFD discussion would not have been a good use of time. Martinp (talk) 09:57, 26 June 2026 (UTC)
- Just to note that it already went through the AfC process and it was accepted. — Martin (MSGJ · talk) 12:18, 26 June 2026 (UTC)
- and it was deleted then too prior to the deletion @Hannahloopme is contesting. I think the community consensus is fairly clear and if she remains unblocked and moves the extant draft it will probably be deleted again. That said, not opposed to an AFD if folks think that would be helpful for a final enough. Star Mississippi 13:29, 26 June 2026 (UTC)
- Just to note that it already went through the AfC process and it was accepted. — Martin (MSGJ · talk) 12:18, 26 June 2026 (UTC)
- Endorse utterly unambiguous. Regards, --Goldsztajn (talk) 12:00, 26 June 2026 (UTC)
- Just a note that the promotional content is blatantly a product of a LLM (probably ChatGPT) being asked to write an article about the company. Helpful Raccoon (talk) 21:33, 26 June 2026 (UTC)
- Where is the evidence this was LLM-generated? @Helpful Raccoon Katzrockso (talk) 18:56, 27 June 2026 (UTC)
- Numerous instances of WP:OVERATTRIBUTION and WP:AITREND/WP:SUPERFICIAL, such as "Industry publications including Cynopsis and Street Fight have reported on this trend in the context of LoopMe's position in the mobile app ecosystem". Helpful Raccoon (talk) 19:02, 27 June 2026 (UTC)
- I appreciate your point of view here but please note that I did not use any kind of LLM to write this. I was actually working with a spreadsheet of LoopMe related press coverage and weaving in citations that way. I was under the impression that I needed lots of attributions/citations in order to meet Wikipedia's standards. Hannahloopme (talk) 12:04, 29 June 2026 (UTC)
- Numerous instances of WP:OVERATTRIBUTION and WP:AITREND/WP:SUPERFICIAL, such as "Industry publications including Cynopsis and Street Fight have reported on this trend in the context of LoopMe's position in the mobile app ecosystem". Helpful Raccoon (talk) 19:02, 27 June 2026 (UTC)
- Where is the evidence this was LLM-generated? @Helpful Raccoon Katzrockso (talk) 18:56, 27 June 2026 (UTC)
- Retain as draft, review at AfC: The draft is promotional. If @MSGJ says it was accepted at AfC, but was deleted per G11, then retaining in draftspace (or even userspace) is acceptable. The editor has declared they're being paid, and clearly appear to be engaging here, so a block would be punitive (and correct me if I'm wrong, but DRV isn't a conduct noticeboard). Improve the draft, send to AfC. 11WB (talk) 15:34, 1 July 2026 (UTC)
23 June 2026
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
ArbCom has found that most of the editors who voted to delete this article were involved in meatpuppetry and off-wiki canvassing across this and other Michael Jackson-related discussions, producing a skewed consensus. Another editor who voted to delete, 2BOARNOT2B, was not included in the ArbCom case but
) and am concerned that it may constitute inappropriate canvassing in support of Popcornfud. According to that comment, an article with substantially the same content, albeit under a slightly different title, was deleted only two or three months ago following a repeat AfD (https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Overview_of_Michael_Jackson_sexual_abuse_allegations ).TroVes6 (talk) 16:34, 24 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
21 June 2026
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
Reliable sources seem to exist for this person and she seems to meet notability requirements to have her own article. Article in Slovenian already exists and is a good start. StructuredFlorescence (talk) 01:19, 21 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
20 June 2026
|
|---|
| The following is an archived debate of the deletion review of the page above. Please do not modify it. |
|
Spartaz closed the AfD with the summary
Spartaz then expanded on their close summary:
As I had stated in the AfD discussion,
The !votes to delete the article, a number of which appear to be drive-by !votes, do not provide any convincing argument against this. إيان (talk) 17:41, 20 June 2026 (UTC)
|
| The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |