This tool is optional. No one is required to use it, but it's here if you want to know which of your AO3 fics were scraped. Locked works were not 100% protected from this scrape. Currently, I don't know of any next steps you should be taking, so this is all informational.
Most people should use this link to check if they were included in the March 2025 AO3 scrape. This will show up to 2,000 scraped works for most usernames.
Or you can use this version, which is slower but does a better job if your username is a common word. This version also lets you look up works by work ID number, which is useful if you're looking for an orphaned or anonymous fic.
If you have more than 2,000 published works, first off, I am jealous of your motivation to write that much. But second, that won't display right on the public version of the tools. You can send me an ask (preferred) or DM (if you need to) to have me do a custom search for you if you have more than 2,000 total works under 1 username. If you send an ask off-anon asking me to search a name, I'll assume you want a private answer.
In case this post breaches containment: this is a tool that only has access to the work IDs, titles, author names, chapter counts, and hit counts of the scraped fics for this most recent scrape by nyuuzyou discovered in April 2025. There is no other work data in this tool. This never had the content of your works loaded to it, only info to help you check if your works were scraped. If you need additional metadata, I can search my offline copy for you if you share a work ID number and tell me what data you're looking for. I will never search the full work text for anyone, but I can check things like word counts and tags.
Please come yell if the tool stops working, and I'll fix as fast as I can. It's slow as hell, but it does load eventually. Give it up to 10 minutes, and if it seems down after that, please alert me via ask! Anons are on if you're shy. The link at the top is faster and handles most users well.
On mobile, enable screen rotation and turn your phone sideways. It's a litttttle easier to use like that. It works better if you can use desktop.
Some FAQs below the cut:
Gonna pass this around once more with an addition!
Here is a tool that can be used to poison your current and future AO3 fics if you would like to reduce the chances that your work will be useful to scrapers in the future. You can thank the lovely @all-hail-trash-prince for writing the code and for making it more accessible to those who don't know how to run code.
Here is me doing a very brief runthrough on the current version of the tool (as of this reblog). Here is me yapping about it in video if you prefer that format.
I'm not saying you have to use this tool. I'm just boosting it as one potential path forward for those who want to reduce the quality of their fics for future scrapers without reducing the quality for readers on AO3, including those using screen readers to narrate your fics. You can choose to use it for zero fics, one fic, some of your fics, or all of your fics. Entirely up to you if you want to do this.
Poisoning your fics now does not undo nyuuzyou's scrape. The data, while a little less accessible now, is still out there in a few locations. There's no undoing that, and there will always be a copy of the fics scraped by nyuuzyou. Poisoning your fics is a method to protect you from future scrapes. The protection doesn't reduce the risk that you will be scraped, but it highly increases the chance that the scraper will not be able to use your fic for anything useful, including AI training. There's no surefire way to protect your fics short of not sharing them at all, but this tool provides the best balance I've seen of protecting them from unwanted use and still allowing you to share with real readers.
And once more for anyone who hasn't caught it yet: I am not directly affiliated with AO3. This is a third party tool that you may choose to use or may choose to ignore.
Editing to add: This code should probably be considered in an alpha phase. This is code written by one person, vetted by another who knows coding in general but not this specific language. It may have bugs to iron out. It may have unexpected impacts, particularly to the accessibility of your fics. If you're not okay with that, please send your specific concerns here so I can look into them AND/OR wait for us to get through testing this code in actual use. Any concerns and bugs you report here are appreciated because they help everyone involved make this better over time.
Thank you!
