#pokemon m15 | Explore Tumblr Posts and Blogs

eiirisworkshop · 3 years

Text

The Fanfic Author's Guide to Metatext

(As Used on Ao3) by Eiiri

Also available as a PDF here. This thing is 13,000 words. The PDF is recommended.

Intro: What is Metatext?

Metatext is everything we fanfic authors post along with our story that is not the story itself: title, tags, summary, author's notes, even the rating.

It is how we communicate to potential readers what they're signing themselves up for if they choose to read our story, how we let them make informed decisions regarding which fics they want to read, how we get their interest and, frequently, how they find our story in the first place. A lot of metatext acts as a consent mechanism for readers, it's the informed part of informed consent.

Since most of us who write fanfic also read it, we understand how important this is! But, for the most part, no one ever teaches us how to use metatext; we have to pick it up by osmosis. That makes it hard to learn how to use it well, we all suck at it when we first start out, and some of us may go years without learning particular conventions that seem obvious to others in our community. This creates frustration for everybody.

Enter this guide!

This is meant to be a sort of handbook for fic writers, particularly those of us who post on Archive of Our Own, laying out and explaining the established metatext conventions already in use in our community so we (and our readers!) are all on the same page. It will also provide some best-practices tips.

The point is to give all of us the tools to communicate with our audience as clearly and effectively as possible, so the people who want to read a story like ours can find it and recognize it as what they're looking for, those who don't want to read a story like ours can easily tell it's not their cup of tea and avoid it, nobody gets hurt, and everybody has fun—including us!

Now that we know what we're talking about, let's get on with the guide! The following content sections appear in the order one is expected to provide each kind of metatext when posting a fic on Ao3, but first….

Warning!

This is a guide for all authors on Ao3. As such, it mentions subject matter and kinds of fic that you personally might hate or find disgusting, but which are allowed under the Archive's terms of use. There are no graphic descriptions or harsh language in the guide itself, but it does acknowledge the existence of fic you may find distasteful and explains how to approach metatext for such fics.

Some sexual terminology is used in an academic context.

A note from the author:

This guide reflects the conventions of the English-language fanfiction community circa 2021. Conventions may differ in other language communities, and although many of our conventions have been in place for decades (praise be to our Star Trek loving foremothers) fanfiction now exists primarily in the realm of internet fandom where things tend to change rather quickly, so some conventions in this guide may die out while other new conventions, not covered in this guide, arise.

This is not official or in any way produced by the Archive of Our Own (Ao3), and though some actual site rules are mentioned, it is not a rulebook. Primarily, it is a descriptivist take on how the userbase uses metatext to communicate amongst ourselves, provided in the interest of making that communication easier and more transparent for everyone, especially newer users.

Contents

How To Use This Guide Ratings Archive Warnings Fandom Tags Category Relationship Tags Character Tags Additional Tags Titles Summaries Author's Notes Series and Chapters Parting Thoughts

How To Use This Guide

Well, read it. Or have it read to you.

This isn't a glossary, it's a handbook, and it's structured more like an academic paper or report, but there's lots and lots of examples in it!

Many of these examples are titles of real media and the names of characters from published media, or tags quoted directly from Ao3 complete with punctuation and formatting.

Some examples are more generic and use the names Alex, Max, Sam, Chris, Jamie, and Tori for demonstration purposes. In other generic examples, part of an example tag or phrase may be sectioned off with square brackets to show where in that tag or phrase you would put the appropriate information to complete it. This will look something like “Top [Character A]” where you would fill in a character's name.

This guide presumes that you know the basics of how to use Ao3, at least from the perspective of reading fic. If you don't, much of this guide may be difficult to understand and will be much less helpful to you, though not entirely useless.

Ratings

Most fanfic hosting sites provide ratings systems that work a lot like the ratings on movies and videogames.

Ao3's system has four ratings:

General

Teen

Mature

Explicit

These seem like they should be pretty self-explanatory, and the site's own official info pop-up (accessible by clicking the question mark next to the section prompt) gives brief, straightforward descriptions for each of them.

Even so, many writers have found ourselves staring at that dropdown list, thinking about what we've written, and wondering what's the right freaking rating for this? How do I know if it's appropriate for “general audiences” or if it needs to be teen and up? What's the difference between Mature and Explicit?

The best way to figure it out is often to think about your fic in comparison to mainstream media.

General is your average Disney or Dreamworks movie, Cartoon Network or Nickelodeon shows, video games like Mario, Kirby, and Pokemon.

There may be romance, but no sexual content or discussion. Scary things might happen and people might get hurt, but violence is non-graphic and usually mild. Adults may be shown drinking alcohol or smoking tobacco, and some degree of intoxication may be shown (usually played for laughs and not focused on), but hard drug use is generally not shown or discussed. There is little to no foul language written out and what language there may be is mild, though harsher swears may be implied by narration. There are no explicit F-bombs or slurs.

Teen is more like a Marvel movie, most network television shows (things like The Office, Supernatural, or Grey's Anatomy), video games like Final Fantasy, Five Nights at Freddie's, and The Sims.

There might be some sex and sexual discussion, but nothing explicit is shown—things usually fade to black or are leftimplied. More intense danger, more severe injuries described in greater detail, and a higher level of violence may be present. Substance use may be discussed and intoxication shown, but main characters are unlikely to be shown doing hard drugs. Some swearing and other harsh language may be present, possibly including an F-bomb or two. In longer works, that might mean an F-bomb every few chapters.

Mature is, in American terms, an R-rated movie* like Deadpool, Fifty Shades of Grey, The Exorcist, and Schindler's List; certain shows from premium cable networks or streaming services like Game of Thrones, Shameless, Breaking Bad, and Black Sails; videogames like Bioshock, Assassin's Creed, Grand Theft Auto, and The Witcher.

Sex may be shown and it might be fairly explicit, but it's not as detailed or graphic or as much the focus of the work as it would be if it were porn. Violence, danger, and bodily harm may be significant and fairly graphic. Most drug use is fair game. Swearing and harsh language may be extensive.

Explicit is, well, extremely explicit. This is full on porn, the hardcore horror movies, and snuff films.

Sex is highly detailed and graphic. Violence and injury is highly detailed and graphic. Drug use and its effects may be highly detailed and graphic. Swearing and harsh language may be extreme, including extensive use of violent slurs.

Please note that both Mature and Explicit fics are intended for adult audiences only, but that does not mean a teenaged writer isn't going to produce fics that should be rated M or E. Ratings should reflect the content of the fic, not the age of the author.

Strictly speaking, you don't have to choose any of these ratings; Ao3 has a “Not Rated” option, but for purposes of search results and some other functions, Not Rated fics are treated by the site as Explicit, just in case, which means they end up hidden from a significant portion of potential readers. It really is in your best interest as a writer who presumably wants people to see their stories, to select a rating. It helps readers judge if yours is the kind of story they want right now, too.

Rating a fic is a subjective decision, there is some grey area in between each level. If you're not quite sure where your fic falls, best practice is to go with the more restrictive rating.

*(Equivalent to an Australian M15+ or R18+, Canadian 14A, 18A or 18+, UK 15 or 18, German FSK 16 or FSK 18.)

Warnings

Ao3 uses a set of standard site-wide Archive Warnings to indicate that a work contains subject matter that falls into one or more of a few categories that some readers are likely to want to avoid. Even when posting elsewhere, it's courteous to include warnings of this sort.

These warnings are:

Graphic Depictions Of Violence

Major Character Death

Rape/Non-Con

Underage

Just like with the ratings, the site provides an info-pop up that explains what each warning is for. They're really exactly what it says on the tin: detailed descriptions of violence, injury, and gore; the death of a character central to canon or tothe story being told; non-consensual sex i.e. rape; and depictions of underage sex, which the site defines as under the age of 18 for humans—Ao3 doesn't care if your local age of consent or majority is lower than that.

In addition to the four standard warnings above, the warnings section has two other choices:

No Archive Warnings Apply

Choose Not To Use Archive Warnings

These do not mean the same thing and cannot be used interchangeably. “No Archive Warnings Apply” means that absolutely nothing in your fic falls into any of the four standard warning categories. “Choose Not To Use Archive Warnings” means that you the author are opting out of the warning system; your fic could potentially contain things that fall into any and all of the four standard warning categories.

There's nothing wrong with selecting Choose Not To Use Archive Warnings! It may mean that some readers will avoid your fic because they're not sure it's safe for them, and you might need to use more courtesy tags than you otherwise would (we'll talk about courtesy tags later), but that's okay! Opting out of the warning system can be a way to avoid spoilers,* and is also good for when you're just not sure if what you've written deserves one of the Archive warnings. In that case, the best practice is to select either the warning it might deserve or Choose Not To Use Archive Warnings, then provide additional information in other tags, the summary, or an initial author's note.

Unless you're opting out of using the warning system, select all the warnings that apply to your fic, if any of them do. So if a sixteen year old main character has consensual sex then gets killed in an accident that you've written out in excruciating detail, that fic gets three out of the four standard warnings: Underage, Major Character Death, and Graphic Depictions Of Violence.

*(Fandom etiquette generally favors thorough tagging and warning over avoiding spoilers. It doesn't ruin the experience of a story to have a general sense of what's going to happen. If it did, we wouldn't all keep reading so many “there was only one bed” fics.)

Fandom Tags

What fandom or fandoms is your fic for? You definitely know what you wrote it for, but that doesn't mean it's obvious what to tag it as.

Sometimes, it is obvious! You watched a movie that isn't based on anything, isn't part of a series, and doesn't have any spinoffs, tie-ins or anything else based on it. You wrote a fic set entirely within the world of this movie. You put this movie as the fandom for your fic. Or maybe you read a book and wrote a fic for it, and there is a movie based on the book, but the movie is really different and you definitely didn't use anything that's only in the movie. You put the book as the fandom for your fic.

All too often, though, it's not that clear.

What if you wrote a fic for something where there's a movie based on a book, but the movie's really different, and you've used both things that are only in the movie and things that are only in the book? In that case you either tag your fic as both the movie and the book, or see if the fandom has an “all media types” tag and use that instead of the separate tags. If the fandom doesn't have an “all media types” tag yet, you can make one! Just type it in.

“All media types�� fandom tags are also useful for cases where there are lots of inter-related series, like Star Wars; there are several tellings of the story in different media but they're interchangeable or overlap significantly, like The Witcher; or the fandom has about a zillion different versions so it's very hard, even impossible, to say which ones your fic does and doesn't fit, like Batman. Use your best judgement as to whether you need to include a more specific fandom tag such as “Batman (Movies 1989-1997)” alongside the “all media types” fandom tag, but try to avoid including very many. The point of the “all media types” tag is to let you leave off the specific tags for every version.

In a situation where one piece of media has a spinoff, maybe several spinoffs, and you wrote a fic that includes things from more than one of them, you might want use the central work's “& related fandoms” tag. For example, the “Doctor Who & Related Fandoms” tag gets used for fics that include things from a combination of any era of Doctor Who, Torchwood, and The Sarah Jane Adventures.

And don't worry, from the reader-side of the site the broadest fandom tags are prioritized. The results page for an “all media types” or “& related fandoms” search includes works tagged with the more specific sub-tags for that fandom, the browse-by-fandom pages show the broadest tag for each fandom included, and putting a fandom into the search bar presumes the broadest tag for that fandom. A search for “Star Wars - All Media Types” will pull up work that only has a subtag for that fandom, like “The Mandalorian (TV).” You don't have to put every specific fandom subtag for people to find your fic.

If you wrote a fic for something that's an adaptation of an older work—especially an older work that's been adapted a lot, like Sherlock Holmes or The Three Musketeers—it can be hard to know how you should tag it. The best choice is to put the adaptation as the fandom, for instance “Sherlock (TV),” then, if you're also using aspects of the older source work that aren't in the adaptation, also put a broad fandom tag such as “Sherlock Holmes & Related Fandoms.” Do not tag it as being fic for the source work—in our Sherlock example that would be tagging it “Sherlock Holmes - Arthur Conan Doyle”—unless you are crossing over the source work and the adaptation. Otherwise, the specific fandom subtag for the source work ends up clogged with fic for the adaptation, which really is a different thing.

By the same token, fic for the source work shouldn't be tagged as being for the adaptation, or the adaptation's subtag will get clogged.

The same principle applies to fandoms that have been rebooted. Don't tag fic for the reboot as being for the original, or fic for the original as being for the reboot. Don't tag a fic as being for both unless the reboot and original are actually interacting. Use an “& related fandoms” tag for the original if your fic for the reboot includes some aspects of the original that weren't carried over but you haven't quite written a crossover between the two. Good examples of these situations can be seen with “Star Trek: Alternate Original Series (Movies)” vs. “Star Trek: The Original Series,” and “She-Ra and the Princesses of Power (2018)” vs. “She-Ra: Princess Of Power (1985).”

Usually, this kind of mistagging as a related fandom happens when someone writes a fic for something that is or has a reboot, spinoff, or adaptation, but they're only familiar with one of the related pieces of media, and they mistakenly presume the fandoms are the same or interchangeable because they just don't know the difference. It's an honest mistake and it doesn't make you a bad or fake fan to not know, but it can be frustrating for readers who want fic for one thing and find the fandom tag full of fic for something else.

In order to avoid those kinds of issues, best practice is to assume fandoms are not interchangeable no matter how closely related they are, and to default to using a tag pair of the most-specific-possible sub-fandom tag + the broadest possible fandom tag when posting a fic you're not entirely sure about, for instance “Star Trek” and “Star Trek: Enterprise.”

The Marvel megafandom has its own particular tagging hell going on. Really digging into and trying to make sense of that entire situation would require its own guide, but we can go through some general tips.

There is a general “Marvel” fandom tag and tags for both “The Avengers - Ambiguous Fandom” and “The Avengers (Marvel) - All Media Types.” Most of us who write Marvel fic are working with a cherry picked combination of canons from the MCU, various comics runs, both timelines of X-Men movies, and possibly several decades worth of cartoons. That's what these tags are for.

If your cherry picked Marvel fic is more X-Men than Avengers, go for the “X-Men - All Media Types” tag.

If you are primarily working with MCU canon, use the MCU specific tags rather than “all media types” and add specific tags for individual comics runs—like Earth 616 or the Fraction Hawkeye comics—if you know you're lifting particular details from the comics. If you're just filling in gaps in MCU canon with things that are nebulously “from the comics” don't worry about tagging for that, it's accepted standard practice in the fandom at this point, use a broader tag along with your MCU-specific tag if you want to.

Same general idea for primarily movie-verse X-Men fics. Use the movie-specific tags.

If your fic mostly draws from the comics, use the comics tags. If you're focusing on an individual run, show, or movie series rather than an ensemble or large swath of the megafranchise, tag for that and leave off the broader fandom tags.

Try your best to minimize the number of fandom tags on your Marvel work. Ideally, you can get it down to two or three. Even paring it down as much as you can you might still end up with about five. If you're in the double digits, take another look to see if all the fandom tags you've included are really necessary, or if some of them are redundant or only there to represent characters who are in the fic but that the fic doesn't focus on. Many readers tend to search Marvel fics by character or pairing tags, it's more important that you're thorough there. For the fandom tags it's more important that you're clear.

If you write real person fiction, you need to tag it as an RPF fandom. Fic about actors who are in a show together does not belong on the fandom tag for that show. There are separate RPF fandom tags for most shows and film franchises. Much like the adaptation/source and reboot/original situations discussed earlier, a fic should really only be tagged with both a franchise's RPF tag and its main tag if something happens like the actors—or director or writer!—falling into the fictional world or meeting their characters.

Of course, not all RPF is about actors. Most sports have RPF tags, there are RPF tags for politics from around the world and for various historical settings, the fandom tags for bands are generally presumed to be RPF tags, and there is a general Real Person Fiction tag.

In order to simplify things for readers, it's best practice to use the general Real Person Fiction tag in addition to your fandom-specific tag. You may even want to put “RPF” as a courtesy tag in the Additional Tags section, too. This is because Ao3 isn't currently set up to recognize RPF as the special flavor of fic that it is in the same way that the site recognizes crossovers as special, so it can be very difficult to either seek out or avoid RPF since it's scattered across hundreds of different fandom tags.

On the subject of crossovers—they can make fandom tagging even more daunting. Even for a crossover with lots of fandoms involved, though, you just have to follow the same guidelines as to tag a single-fandom work for each fandom in the crossover. The tricky part is figuring out if what you wrote is really a crossover, or just an AU informed by another fandom—we'll talk about that later.

There are some cases where it's really hard to figure out what fandom something belongs to, like if you wrote a fanfic of someone else's fanfic, theirs is an AU and yours is about their OC, not any of the characters from canon. What do you do?! Well, you do not tag it as being a fanfic for the same thing theirs was. Put the title of their fic (or name of their series) as the fandom for your fic, attributed to their Ao3 handle just like any other fandom is attributed to its author. Explain the situation in either the summary or the initial author's note. Also, ask the author's permission before posting something like this.

What if you wrote a story about your totally original D&D character? The fandom is still D&D, you want the “Dungeons & Dragons (Roleplaying Game)” tag.

What if there's not a fandom tag on the Archive yet for what you wrote? Not a problem! You can type in a new one if you're the first person to post something for a particular fandom. Do make sure, though, that the fandom isn't just listed by a different name than you expect. Many works that aren't originally in English—including anime—are listed by their original language title or a direct translation first, and sometimes a franchise or series's official name might not be what you personally call it, for instance many people think of Phillip Pullman's His Dark Materials series as The Golden Compass series, so it's best to double check.

What if you wrote an entirely new original story that's not based on anything? Excellent job, that takes a lot of work, but that probably doesn't belong on Ao3! The Archive is primarily meant as a repository for fannish content, but in a few particular circumstances things we'd consider Original Work may be appropriate content for the Archive as well. Double check the Archive's Terms of Service FAQ and gauge if what you wrote falls under the scope of what is allowed. If what you wrote really doesn't fit here, post it somewhere else or try to get it published if you feel like giving it a shot.

Category

What Ao3 means by category is “does this fic focus on sex or romance, and if so what combination of genders are involved in that sex or romance?”

The category options are:

F/F

F/M

Gen

M/M

Multi

Other

The F/F, F/M, and M/M categories are for stories focused on pairings of two women, a woman and a man, and two men, respectively. These refer to sexual and/or romantic pairings.

The Other category is for stories focused on (sexual and/or romantic) pairings where one or both partners are not strictly male or female, such as nonbinary individuals, people from cultures with gender systems that don't match to the Western man-woman system, and nonhuman characters for whom biological sex works differently or is nonexistent, including aliens, robots, and inanimate objects or abstract concepts. There are some problems with treating nonbinary humans, eldritch tentacle monsters, sexless androids, and wayward container ships as all the same category, but it's the system we currently have to work with. Use Additional Tags to clarify the situation.

Multi is for stories in which several (sexual and/or romantic) relationships are focused on or which focus on relationships with multiple partners, including cases of polyamory, serial monogamy, strings of hookups with different people, and orgies. A fic will also show as “Multi” if you, the author, have selected more than one category for the fic, even if none of those are the Multi category. Realistically, the Archive needs separate “Multiple Categories” and “Poly” options, but for now we have to work with this system in which the two are combined. Use Additional Tags to clarify the situation.

Gen is for stories that do not contain or are not focused on sex or romance. Romance may be present in a gen fic but it's going to be in the background. While rare, there is such a thing as a sexually explicit gen fic—solo masturbation which does not feature fantasizing about another character is explicit gen fic; a doctor character seeing a series of patients with sex-related medical needs following an orgy may qualify if the orgy is not shown and the doctor is being strictly professional—but such fic needs to be rated, otherwise tagged, and explained carefully in the summary and/or author's note.

Much like the warnings section, category is a “select all that apply” situation. Use your best judgement. For a fic about a polyamorous relationship among a group of women, it's entirely appropriate to tag it as both F/F and Multi. A poly fic with a combination of men and women in the relationship could be shown as both M/M and F/M, Multi, or all three. A fic that focuses equally on one brother and his husband and the other brother and his wife should be tagged both M/M and F/M, and could be tagged as Multi but you might decided not to just to be clear that there's no polyamory going on. If you wrote a fic about two characters who are both men in canon, but you wrote one of them as nonbinary, you could tag it M/M, Other, or both depending on what you feel is representative and respectful.

When dealing with trans characters, whether they're trans in canon or you're writing them as such, the category selection should match the character's gender. If there's a character who is a cis woman in canon, but who you're writing as a trans man, you categorize the fic based on his being a man. If there's a character who is a cis man in canon, but whom you're writing as a trans man, he is still a man and the fic should be categorized accordingly. When dealing with nonbinary characters the fic should really be classed as Other though, by convention, fics about characters who are not nonbinary in canon may be classed based on the character's canon gender as well or instead. When dealing with gender swapped characters—i.e. a canonically cis male superhero who you're writing as a cis woman—class the fic using the gender you wrote her with, not the gender he is in canon.

Most of the time, gen fics should not be categorized jointly with anything else because a fic should only be categorized based on the ships it focuses on, and a gen fic should not be focusing on a ship in the first place.*

*(One of the few circumstances in which it might make sense to class a fic as both gen and something else is when writing about Queerplatonic Relationships, but that is a judgement call and depends on the fic.)

Relationship Tags

The thing about relationship tagging that people most frequently misunderstand or just don't know is the difference between “Character A/Character B” and “Character A & Character B.”

Use a “/” for romantic or sexual relationships, such as spouses, people who are dating, hookups, and friends with benefits. Use “&” for platonic or familial relationships, such as friends, siblings, parents with their kids, coworkers, and deeply connected mortal enemies who are not tragically in love.

This is where we get the phrase “slash fic.” Originally, that meant any fic focused on a romantic paring, but since so much of the romantic fic being produced was about pairs of men, “slash fic” came to mean same-sex pairings, especially male same-sex pairings. Back in earlier days of fandom, pre-Ao3 and even pre-internet, there was a convention that when writing out a different-sex pairing, you did so in man/woman order, while same-sex pairings were done top/bottom. Some authors, especially those who have been in the fic community a long time, may still do this, but the convention has not been in consistent, active use for many years, so you don't have to worry about putting the names in the “correct” order. Part of why that died out is we, as a community, have gotten less strict and more nuanced in our understandings of sex and relationships, we're writing non-penetrative sex more than we used to, and we're writing multi-partner relationships and sex more than we used to, so strictly delineating “tops” and “bottoms” has gotten less important and less useful.

The convention currently in use on Ao3 is that the names go in alphabetical order for both “/” and “&” relationships. In most cases, the Archive uses the character's full name instead of a nickname or just a given name, like James "Bucky" Barnes instead of just Bucky or James. We'll talk more about conventions for how to input character names in the Characters section. The Archive will give you suggestions as you type—if one of them fits what you mean but is slightly different from how you were typing it, for instance it's in a different order, please use the tag suggested! Consistency in tags across users helps the site work more smoothly for everybody.

This is really not the place for ship nicknames like Puckleberry, Wolfstar, or Ineffable Wives. Use the characters' names.

Now that you know how to format the relationship tag to say what you mean, you have to figure out what relationships in your fic to tag for.

The answer is you tag the relationships that are important to the story you're telling, the ones you spend time and attention following, building up, and maybe even breaking down. Tagging for a ship is not a promise of a happy ending for that pair; you don't have to limit yourself to tagging only the end-game ships if you're telling a story that's more complicated than “they get together and live happily ever after.” That said, you should generally list the main ship—the one you focus on the most—first on the list, and that will usually be the end-game ship. You should also use Additional Tags, the summary, and author's notes to make it clear to readers if your fic does not end happily for a ship you've tagged. Otherwise readers will assume that a fic tagged as being about a ship will end well for that ship, because that's what usually happens, and they'll end up disappointed and hurt, possibly feeling tricked or lied to, when your fic doesn't end well for that ship

You don't have to, and honestly shouldn't, tag for every single relationship that shows up in your fic at all. A character's brief side fling mentioned in passing, or a relationship between two background characters should not be listed under the Relationship tag section. You can list them in the format “minor Character A/Character C” or “Character C/Character D – mentions of” in the Additional Tags section if you want to, or just tag “Minor or Background Relationship(s)” under either the Relationship tag section or in the Additional Tags section.

There are two main reasons to not tag all those minor relationships. The first is to streamline your tags, which makes them clearer and more readable, and therefore more useful. The second reason is because certain ships are far more common as minor or background relationships than as the focus of a work, so tagging all your non-focus focus ships leads to the tags for these less popular ships getting clogged with stories they appear in, but that are not about them. That is, of course, very frustrating for readers who really want to read stories that focus on these ships.

If your fic contains a major relationship between a canon character and an OC, reader-insert, or self-insert, tag it as such. The archive already has /Original Character, /Reader, /You, and /Me tags for most characters in most fandoms. If such a relationship tag isn't already in use, type it in yourself. There are OC/OC tags, too, some of which specify gender, some of which do not. All the relationship tags that include OCs stack the gender-specific versions of the tags under the nongendered ones. Use these tags as appropriate.

For group relationships, both polycules and multi-person friendships, you “/” or “&” all the names involved in alphabetical order, so Alex/Max/Sam are dating while Chris & Jamie & Tori are best friends. For a poly situation where not everyone is dating each other you should tag it something like “Alex/Max, Alex/Sam” because Alex is dating both Max and Sam, but Max and Sam are not romantically or sexually involved with each other. Use your judgement as to whether you still want to include the Alex/Max/Sam trio tag, and whether you should also use a “Sam & Max” friendship tag.

Generally, romantic “/” type relationships are emphasized over “&” type relationships in fic. It is more important that you tag your “/”s thoroughly and accurately than that you tag your “&”s at all. This is because readers are far more likely to either be looking for or be squicked by particular “/” relationships than they are “&” relationships. You can tag the same pair of characters as both / and & if both their romance and their friendship is important to the story, but a lot of people see this as redundant. If you're writing incest fic, use the / tag for the pair not the & tag and put a courtesy tag for “incest” in the Additional Tags section; this is how readers who do not want to see incestuous relationships avoid that material.

Queerplatonic Relationships, Ambiguous Relationships, Pre-Slash, and “Slash If You Squint” are all frequently listed with both the “/” and “&” forms of the pairing; use your best judgement as to whether one or the other or both is most appropriate for what you've written and clarify the nature of the relationship in your Additional Tags.

Overall, list your “/” tags first, then your “&” tags.

Character Tags

Tagging your characters is a lot like tagging your relationships. Who is your fic about? That's who you put in your character tags.

You don't have to and really should not tag every single background character who shows up for just a moment in the story, for pretty much the same reasons you shouldn't tag background relationships. We don't want to clog less commonly focused on characters' tags with stories they don't feature prominently in.

You do need to tag the characters included in your Relationship tags.

A character study type of fic might only have one character you need to tag for. Romantic one shots frequently only have two. Longfics and fics with big ensemble casts can easily end up with a dozen characters or more who really do deserve to be tagged for.

Put them in order of importance. This doesn't have to be strict hierarchal ranking, you can just arrange them into groups of “main characters,” “major supporting characters,” and “minor supporting characters.” Nobody less than a minor supporting character should be tagged. Even minor supporting characters show up for more than one line.

If everyone in the fic is genuinely at the same level of importance (which does happen, especially with small cast fics), then order doesn't really matter. You can arrange them by order of appearance or alphabetically by name if you want to be particularly neat about it.

Do tag your OCs! Some people love reading about OCs and want to be able to find them; some people can't stand OCs and want to avoid them at all costs; most people are fine with OCs sometimes, but might have to be in the mood for an OC-centric story or only be comfortable with OCs in certain contexts. Regardless, though, Character tags are here to tell readers who the story is about, and that includes new faces. Original Characters are characters and if they're important to the story, they deserve to be tagged for just like canon characters do.

There are tags for “Original Character(s),” “Original Male Character(s),” and “Original Female Character(s).” Use these tags! If you have OCs you're going to be using frequently in different stories, type up a character tag in the form “[OC's Name] – Original Character” and use that in addition to the generic OC tags.

Also tag “Reader,” “You,” or “Me” as a character if you've written a reader- or self-insert.

You can use the “Minor Characters” tag to wrap up everybody, both OC and canon, who doesn't warrant their own character tag. Remember, though, that this tag is also used to refer to minor canon characters who may not have their own official names.

Just like when tagging for relationships, the convention when tagging for characters is to use their full name. The suggestions the Archive gives you as you type will help you use the established way of referring to a given character.

Characters who go by more than one name usually have their two most used names listed together as one tag with the two names separated by a vertical bar like “Andy | Andromache of Scythia.” This also gets used sometimes for characters who have different names in an adaptation than in the source text, or a different name in the English-language localization of a work than in the original language. For character names from both real-world and fictional languages and cultures that put family or surname before the given name—like the real Japanese name Takeuchi Naoko or the made up Bajoran name Kira Nerys—that order is used when tagging, even if you wrote your fic putting the given name first.

Some characters' tags include the fandom they're from in parentheses after their name like “Connor (Detroit: Become Human).” This is mostly characters with ordinary given names like Connor and no canon surname, characters who have the same full name as a character in another fandom, such as Billy Flynn the lawyer from the musical Chicago and Billy Flynn the serial killer played by Tim Curry in Criminal Minds, and characters based on mythological, religious, or historical figures or named for common concepts such as Lucifer, Loki, Amethyst, Death, and Zero that make appearances in multiple fandoms.

Additional Tags

Additional Tags is one of the most complicated, and often the longest, section of metatext we find ourselves providing when we post fic. It's also the one that gives our readers the greatest volume of information.

That, of course, is what makes it so hard for us to do well.

It can help to break down Additional Tags into three main functions of tag: courtesy tags, descriptive tags, and personal tags.

Courtesy tags serve as extensions of the rating and warning systems. They can help clarify the rating, provide more information about the Archive Warnings you've used or chosen not to use, and give additional warnings to tell readers there are things in this fic that may be distasteful, upsetting, or triggering but that the Archive doesn't have a standard warning for.

Descriptive tags give the reader information about who's in this fic, what kind of things happen, what tropes are in play, and what the vibe is, as well as practical information about things like format and tense.

Personal tags tell the readers things about us, the author, our process, our relationship to our fic, and our thoughts at the time of posting.

It doesn't really matter what order you put these tags in, but it is best practice to try to clump them: courtesy tags all together so it's harder for a reader to miss an important one, ship-related info tags together, character-related info tags together, etc.

There are tons and tons of established tags on Ao3, and while it's totally fine, fun, and often necessary to make up your own tags, it's also important to use established tags that fit your fic. For one thing, using established tags makes life easier for the tag wranglers behind the scenes. Using a new tag you just made up that means the same thing as an established tag makes more work for the tag wranglers. We like the tag wranglers, they're all volunteers, and they're largely responsible for the search and sorting features being functional. Be kind to the tag wranglers.

For basically the same reasons, using established tags makes it easier for readers to find your fic. If a reader either searches by a tag or uses filters on another search to “Include” that tag, and you didn't use that tag, your fic will not show up for them even if what you wrote is exactly what they're looking for. Established tags can be searched by exactly the same way as you search by fandom or pairing, your off the cuff tags cannot.

Let's talk about some well-known established tags and common tag types, divvied up by main function.

Courtesy

A lot of courtesy tags are specific warnings like “Dubious Consent,” “Incest,” “Drug Use,” “Extremely Underage,” “Toxic Relationship,” and “Abuse.” Many of these have even more specific versions such as “Recreational Drug Use” and “Nonconsensual Drug Use,” or “Mildly Dubious Consent” and “Extremely Dubious Consent.”

Giving details about what, if any, drugs are used or mentioned, specifying what kinds of violence or bodily harm are discussed or depicted, details about age differences or power-imbalanced relationships between characters who date or have sex, discussion or depictions of suicide, severe or terminal illness, or mental health struggles is useful. It helps give readers a clear sense of what they'll encounter in your fic and decide if they're up for it.

One the most useful courtesy warning tags is “Dead Dove: Do Not Eat” which basically means “there are things in this fic which are really screwed up and may be disturbing, read at your own risk, steer clear if you're not sure.” This tag—like all courtesy warnings, really—is a show of good faith, by using it you are being a responsible, and thoughtful member of the fanfic community by giving readers the power and necessary information to make their own informed decisions about what they are and are not comfortable reading.

Saying to “Heed the tags” is quite self-explanatory and, if used, should be the last or second to last tag so it's easy to spot. Remember, though, that “Heed the tags” isn't useful if your tags aren't thorough and clear.

“Additional Warnings In Author's Note” is one of only things that should ever go after “Heed the tags.” If you use this, your additional warnings need to go in the author's note at the very beginning of the fic, not the one at the end of the first chapter. If your additional warnings write up is going to be very long because it's highly detailed, then it can go at the bottom of the chapter with a note at the beginning indicating that the warnings are at the bottom. Some authors give an abbreviated or vague set of warnings in the initial note, then longer, highly detailed, spoilery warnings in the end note. It's best to make it as simple and straightforward as possible for readers to access warnings.

Tagging with “Dead Dove: Do Not Eat,” “Heed the tags,” or “Additional Warnings In Author's Note” is not a substitute for thorough and appropriate courtesy tagging. These are extra reminders to readers to look closely at the other warnings you've given.

While most courtesy tags are warnings, some are assurances like “No Lesbians Die” or “It's Not As Bad As It Sounds.” A fic tagged for rape or dub-con may get a tag assuring that the consent issues are not between the characters in the main ship; or a fic with a premise that sounds likely to involve lack of consent but actually doesn't may get a tag that it's “NOT rape/non-con.” A tag like “Animal Death” may be immediately followed by a freeform tag assuring that the animal that dies is not the protagonist's beloved horse.

Descriptive

There are a few general kinds of descriptive tags including character-related, ship-related, temporal, relation-to-canon, trope-related, smut details, and technical specifications.

Many character- and ship-related tags simply expand on the Character and Relationship tags we've already talked about. This is usually the place to specify details about OCs and inserts, such as how a reader-insert is gendered.

When it comes to character-related tags, one of the most common types in use on Ao3 and in fandom at large is the bang-path. This is things like werewolf!Alex, trans!Max, top!Sam, kid!Jamie, and captain!Tori. Basically, a bang-path is a way of specifying a version of a character. We've been using this format for decades; it comes from the very first email systems used by universities in the earliest days of internet before the World Wide Web existed. It's especially useful for quickly and concisely explaining the roles of characters in an AU. Nowadays this is also one of the primary conventions for indicating who's top and who's bottom in a ship if that's information you feel the need to establish. The other current convention for indicating top/bottom is as non-bang-path character-related tags in the form “Top [Character A], Bottom [Character B].”

Other common sorts of character tags are things like “[Character A] Needs a Hug,” “Emotionally Constipated [Character B],” and “[Character C] is a Good Dad.”

Some character-related tags don't refer to a particular character by name, but tell readers something about what kinds of characters are in the fic. Usually, this indicates the minority status of characters and may indicate whether or not that minority status is canon, as in “Nonbinary Character,” “Canon Muslim Character,” “Deaf Character,” and “Canon Disabled Character.”

Down here in the tags is the place to put ship nicknames! This is also where to say things like “They're idiots your honor” or indicate that they're “Idiots in Love,” maybe both since “Idiots in Love” is an established searchable tag but “They're idiots your honor” isn't yet. If your fandom has catchphrases related to your ship, put that here if you want to.

If relevant, specify some things about the nature of relationships in your fic such as “Ambiguous Relationship,” “Queerplatonic Relationships,” “Polyamory,” “Friends With Benefits,” “Teacher-Student Relationship,” and so on. Not all fics need tags like these. Use your best judgement whether your current fic does.

Temporal tags indicate when your fic takes place. That can be things like “Pre-Canon” and “Post-Canon,” “Pre-War,” “Post-Captain America: The Winter Soldier,” “1996-1997 NHL season,” “Future Fic,” and so on. These tags may be in reference to temporal landmarks in canon, in the real world, or both depending on what's appropriate.

Some temporal tags do double duty by also being tags about the fic's relationship to canon. The Pre- and Post-Canon tags are like that.

Other relation-to-canon type tags are “Canon Compliant” for fics that fit completely inside the framework of canon without changing or contradicting anything, “Alternate Universe - Canon Divergence” for fics that are compliant up to a certain point in canon, then veer off (maybe because you started writing the fic when the show was on season two but now it's at season four and you're not incorporating everything from the newer seasons, maybe a character died and you refuse to acknowledge that, maybe you just want to explore what might have happened if a particular scene had gone differently), and the various other Alternate Universe tags for everything from coffee shop AUs and updates to modern settings, to realities where everyone is a dragon or no one has their canon superpowers.

The established format for these tags is “Alternate Universe – [type],” but a few have irregular names as well, such as “Wingfic” for AUs in which characters who don't ordinarily have wings are written as having wings.

If you have written an AU, please tag clearly what it is! Make things easy on both the readers who are in the mood to read twenty royalty AUs in a row, the readers who are in the middle of finals week and the thought of their favorite characters suffering through exams in a college AU would destroy the last shred of their sanity but would enjoy watching those characters teach high school, and the readers who really just want to stick to the world of canon right now.

Admittedly, it can get a little confusing what AU tag or tags you need to describe what you've written since most of us have never had a fandom elder sit us down and explain what the AU tags mean. One common mix up is tagging things “Alternate Universe - Modern Setting” when what's meant is “Alternate Universe - Canon Divergence.” The misunderstanding here is usually reading “Alternate Universe - Modern Setting” and thinking it means an alternate version of the canon universe that is set at the same time as the canon universe, but is different in some way. That's not how the tag is meant to be used, though.

The Modern Setting AU tag is specifically for fic set now (at approximately the same time period it was written), for media that's canonically set somewhere that is very much not the present of the real world. This can mean things set in the past (like Jane Austen), the future (like Star Trek), or a fantasy world entirely different from our own (like Lord of the Rings or Avatar: the Last Airbender). Fic for a canon that's set more or less “now” doesn't need the Modern Setting AU tag, even if the world of canon is different from our own. If you're removing those differences by putting fantasy or superhero characters in a world without magic or supersoldier serum, you might want the “Alternate Universe - No Powers” tag instead.

Some of the most fun descriptive tags are trope tags. This includes things like “Mutual Pining,” “Bed Sharing” for when your OTP gets to their hotel room to find There Was Only One Bed, “Fake Dating,” “Angst,” Fluff,” “Hurt/Comfort” and all its variants. Readers love tropes at least as much as we love writing them and want to be able to find their favorites. Everyone also has tropes they don't like and would rather avoid. Tagging them allows your fic to be filtered in and out by what major tropes you've used.

Explicit fics, and sometimes fics with less restrictive ratings, that contain sex usually have tags indicating details about the nature of the sexual encounter(s) portrayed and what sex acts are depicted. These are descriptive tags, but they also do double duty as courtesy tags. This is very much a situation in which tags are a consent mechanism; by thoroughly and clearly tagging your smut you are giving readers the chance to knowingly opt in or out of the experience you've written.

Most of the time, it's pretty easy to do basic tagging for sex acts—you know whether what you wrote shows Vaginal Sex, Anal Sex, or Non-penetrative Sex. You probably know the names for different kinds of Oral Sex you may have included. You might not know what to call Frottage or Intercrural Sex, though, even if you understand the concept and included the act in your fic. Sometimes there are tags with rectangle-square type relationships (all Blow Jobs are Oral Sex, but not all Oral Sex is a Blow Job) and you're not sure if you should tag for both—you probably should. Sometimes there are tags for overlapping, closely related, or very similar acts or kinks and you're not sure which to tag—that one's more of judgement call; do your best to use the tags that most closely describe what you wrote.

Tag for the kinks at play, if any, so readers can find what they're into and avoid what they're not. Tag for what genitalia characters have if it's nonobvious, including if there's Non-Human Genitalia involved. Tag your A/B/O, your Pon Farr, and your Tentacles, including whether it's Consentacles or Tentacle Rape.

Technical specification tags give information about aspects of the fic other than its narrative content. Most things on Ao3 are prose fiction so that's assumed to be the default, so anything else needs to be specified in tags. That includes Poetry, Podfics, things in Script Format, and Art. If it is a podfic, you should tag with the approximate length in minutes (or hours). If a fic is Illustrated (it has both words and visual art) tag for that.

Tag if your fic is a crossover or fusion. The difference, if you're not sure, is that in a crossover, two (or more) entire worlds from different media meet, whereas in a fusion, some aspects of one world, like the cast of characters, are combined with aspects of another, like the setting or magic system.

If the team of paranormal investigators from one show get in contact with the cast of aliens from another show, that's a crossover and you need to have all the media you're drawing from up in the Fandom tags. If you've given the cast of Hamlet physical manifestations of their souls in the form of animal companions like the daemons from His Dark Materials but nothing else from His Dark Materials shows up, that's a fusion, the Fandom tag should be “Hamlet - Shakespeare,” and you need the “Alternate Universe - Daemons” tag. If you've given the members of a boy band elemental magic powers like in Avatar: the Last Airbender, that can be more of a judgement call depending how much from Avatar you've incorporated into your story. If absolutely no characters or specific settings from Avatar show up, it's probably a fusion. Either way, if the boyband exists in real life, it needs to be tagged as RPF.

Tag if your fic is a Reader-Insert or Self-Insert.

You might want to tag for whether your fic is written with POV First, Second, or Third Person, and if it's Past Tense or Present Tense (or Future Tense, though that's extremely uncommon). For POV First Person fics that are not self-inserts, or POV Third Person fics that are written in third person limited, you may want to tag which character's POV is being shown. Almost all POV Second Person fics are reader-insert, so if you've written one that isn't, you should tag for who the “you” is.

A fic is “POV Outsider” if the character through whom the story is being conveyed is outside the situation or not familiar with the characters and context a reader would generally know from canon. The waitress who doesn't know the guy who just sat down in her diner is a monster hunter, and the guy stuck in spaceport because some hotshot captain accidentally locked down the entire space station, are both potential narrators for POV Outsider stories.

Other technical specifications can be tags for things like OCtober and Kinktober or fic bingo games. Tagging something as a Ficlet, One Shot, or Drabble is a technical specification (we're not going to argue right now over what counts as a drabble). Tagging for genre, like Horror or Fantasy, is too.

It's also good to tag accessibility considerations like “Sreenreader Friendly,” but make sure your fic definitely meets the needs of a given kind of accessibility before tagging it.

Personal

Even among personal tags there are established tags! Things like “I'm Sorry,” “The Author Regrets Nothing,” “The Author Regrets Everything,” and “I Wrote This Instead of Sleeping” are common ones. Tags about us and our relationship to the fic, such as “My First Work In This Fandom,” “Author is Not Religious,” and “Trans Porn By A Trans Author,” can help readers gauge what to expect from our fic. Of course, you are not at all obligated to disclose any personal information for any reason when posting your fic.

The “I'm Bad At Tagging” tag is common, but probably overused. Tagging is hard; very few of us have a natural feel for it even with lots of practice. It's not a completely useless tag because it can indicate to readers that you've probably missed some things you should have tagged for, so they should be extra careful; but it can also turn into a crutch, an excuse to not try, and therefore a sign to readers they can't trust your tagging job. Just do your best, and leave off the self depreciation. If you're really concerned about the quality of your tagging, consider putting in an author's note asking readers to let you know if there are any tags you should add.

You might want to let readers know your fic is “Not Beta Read” or, if you're feeling a little cheekier than that, say “No Beta We Die Like Men” or its many fandom-specific variants like the “No Beta We Die Like Robins” frequently found among Batman fics and “No beta we die like Sunset Curve” among Julie and The Phantoms fic. Don't worry, the Archive recognizes all of these as meaning “Not Beta Read.”

The Archive can be inconsistent about whether it stacks specific variants of Additional Tags under the broadest version of the tag like it does with Fandom tags, so best practice is usually to use both. You can double check by trying to search by a variant tag (or clicking on someone else's use of the variant); if the results page says the broader or more common form of the tag, those stack.

There's no such thing as the right number of tags. Some people prefer more tags and more detail, while other people prefer fewer more streamlined tags, and different fics have different things that need to be tagged for. There is, however, such a thing as too many tags. A tagblock that takes up the entire screen, or more, can be unreadable, at which point they are no longer useful. Focus on the main points and don't try to tag for absolutely everything. Use the “Additional Warnings In Author's Note” strategy if your courtesy tags are what's getting out of hand.

Tag for as much as you feel is necessary for readers to find your fic and understand what they're getting into if they decide to open it up.

A little bit of redundancy in tags is not a sin. In fact, slight redundancy is usually preferable to vagueness. Clear communication in tags is a cardinal virtue. Remember that tags serve a purpose, they're primarily a tool for sorting and filtering, and (unlike on some other sites like tumblr) they work, so it's best to keep them informative and try to limit rambling in the tags. Ramble at length in your author's notes instead!

Titles

Picking a title can be one of the most daunting and frustrating parts of posting a fic. Sometimes we just know what to call our fics and it's a beautiful moment. Other times we stare at that little input box for what feels like an eternity.

The good news is there's really no wrong way to select a title. Titles can be long or short, poetic or straight to the point. Song lyrics, idioms, quotes from literature or from the fic itself can be good ways to go.

Single words or phrases with meanings that are representative of the fic can be great. A lot of times these are well known terms or are easy enough to figure out like Midnight or Morning Glow, but if you find yourself using something that not a lot of people know what it means, like Chiaroscuro (an art style that uses heavy shadow and strong contrast between light and dark), Kintsukuroi (the Japanese art of repairing broken pottery with gold), or Clusivity (the grammatical term for differences in who is or isn't included in a group pronoun), you should define the term in either a subtitle, i.e. “Chiaroscuro: A Study In Contrast,” or at the beginning of the summary.

As a courtesy to other writers, especially in small fandoms, you may want to check to make sure there's not already another fic with the same title in the same fandom, but this is not required. In large fandoms, there's no point in even trying. After all, there are only so many puns to be made about the full moon and only so many verses to Hallelujah.

It may be common practice on other platforms to include information such as fandom or ship in the title of a fic, but on Ao3 nothing that is specified by tags belongs in the title unless your title happens to be the same as a tag because, for instance, you've straightforwardly titled your character study of Dean Winchester “Dean Winchester Character Study” and also responsibly tagged it as such.

Summaries

Yes, you really do need to put something down for the summary. It might only need to be a single sentence, but give the readers something to go off of.

The summary is there to serve two purposes: one, to catch the interest of potential readers, give them a taste of what's inside, and make them want to know more; and two, to give you a space to provide information or make comments that don't really fit in the tags but that you want readers to see before they open the fic.

We've already talked some about that second function. When you put an explanation of the title or clarification about tags in the summary, that's the purpose it's serving. You can also put notes to “Heed the tags” or instruct readers that there are additional warnings in the author's note here in the summary, rather than doing so in the tags.

The first function, the actual summarizing, can be very hard for some of us. It's basically the movie trailer for your fic, butwhat are you even supposed to say?

There are two main strategies as to how to approach this: the blurb, and the excerpt. Blurbs are like the synopses you at least used to see on the backs of published books, or the “Storyline” section on an IMDb page. Writing one is a matter of telling your readers who does what, under what circumstances.

Depending on the fic, one sentence can capture the whole thing: “Sam and Alex have sex on a train.” “Tori tries to rob a bank.” “If anybody had mentioned Max's new house was haunted, Jamie wouldn't have agreed to help with the move.”

Sometimes a blurb can be a question! “What happens when you lock a nuclear engineer in a closet with a sewing kit, a tennis ball, and half a bottle of Sprite?”

Of course, plenty of blurbs are more than one sentence. Their length can vary pretty significantly depending on the type and length of fic you're working with and how much detail you're trying to convey, but it shouldn't get to be more than a few short paragraphs. You're not retelling the entire fic here.

An excerpt is a portion of the fic copied out to serve as the summary. This, too, can vary in length from a line or two to several paragraphs, but shouldn't get too long. It should not be an entire scene unless that scene happens to be uncommonly short. It's important to select a portion of the fic that both indicates the who, what, and under what circumstances of the fic and is representative of the overall tone. Excerpts that are nothing but dialogue with no indication of who's talking are almost never a good choice. Portions that are sexually explicit or extremely violent are never ever a good choice—if it deserves content warnings, it belongs inside the fic, not on the results page.

Counterintuitively, some of the best excerpts won't even look like an excerpt to the reader if they don't contain dialogue. They seem like particularly literary blurbs until the reader reaches that part in the fic and realizes they recognize a section of narration.

Some of us have very strong preferences as to whether we write blurbs or use excerpts for our summaries. Some readers have very strong preferences as to which they find useful. Ultimately, there's no accounting for taste, but there are things we can do to limit the frustration for readers who prefer summaries of the opposite kind than we prefer to write, without increasing our own frustration or work load very much. Part of that is understanding what readers dislike about each type so we know what to mitigate.

Blurbs can seem dry, academic, and overly simplified. They don't automatically give the reader a sense of your writing style the way an excerpt does. They can also seem redundant, like they're just rehashing information already given in the tags, so the reader feels like they're being denied any more information without opening the fic.

Excerpts can seem lazy, like you, the author, don't care enough to bother writing a blurb, or pushy like you're telling the reader “just read the fic; I'm not going to give you the information you need to decide if you want to read or not, I'm shoving it in front of you and you just have to read it.” That effect gets worse if your tags aren't very informative or clear about what the plot is, if the excerpt is obviously just the first few lines or paragraphs of the fic, if the except is particularly long, or, worst of all, if all three are true at once.

A lot of the potential problems with blurbs can be minimized by having fun writing them! Make it punchy, give it some character, treat it like part of the story, not just a book report. A fic for a serialized show or podcast, for instance, could have a blurb written in the style of the show's “previously on” or the podcast's intro. Make sure the blurb gives the reader something they can't just get from the tags—like the personality of your writing, important context or characterization, or a sense of the shape of the story—but don't try to skimp on the tags to do it!

Really, the only way to minimize the potential problems with excerpts is to be very mindful in selecting them. Make sure the portion you've chosen conveys the who, what, and under what circumstances and isn't too long. You know the story; what seems clear and obvious from the excerpt to you might not be apparent to someone who doesn't already know what happens, so you might need to ask a friend to double check you.

The absolute best way to provide a summary that works for everybody is to combine both methods. It really isn't that hard to stick a brief excerpt before your blurb, or tack a couple lines of blurb after your excerpt, but it can make a world of difference for how useful and inviting your summary is to a particular reader. The convention for summaries that use both is excerpt first, then blurb.

If you're struggling to figure out a summary, or have been in the habit of not providing one, try not to stress over it. Anything is better than nothing. As long as you've written something for a summary, you've given the reader a little more to help them make their decision. What really isn't helpful, though, is saying “I'm bad at summaries” in your summary. It's a lot like the “I'm Bad At Tagging” tag in that it's unnecessarily self depreciating, frequently comes across as an excuse not to try, and sometimes really is just an excuse. Unlike the “I'm Bad At Tagging” tag, which has the tiny saving grace of warning readers you've probably missed something, saying you're bad at summaries has no utility at all, and may drive away a reader who thought your summary was quite good, but is uncomfortable with the negative attitude reflected by that statement. Summaries are hard. It's okay if you don't like your summary, but it's important for it to be there, and it's important to be kind to yourself about it. You're trying, that's what matters.

Author's Notes

Author's notes are the one place where we, the writers, directly address and initiate contact with our readers. We may also talk to them in the comments section, but that's different because they initiate that interaction while we reply, and comments are mostly one-on-one while in author's notes we're addressing everyone who ever reads our fic.

The very first note on a fic should contain any information, such as warnings or explanations, that a reader needs to see before they get to the body of the story, as well as anything like thanks to your beta, birthday wishes to a character, or general hellos and announcements you want readers to see before they get to the body of the story. On multi-chapter fics, notes at the beginning of chapters serve the same function for that chapter as the initial note on the fic does for the whole story, so you can do things like warn for Self-Harm on the two chapters out of thirty where it comes up, let everyone know your update schedule will be changing, or wish your readers a merry Christmas, if they celebrate it, on the chapter you posted on December 23rd but is set in mid-March.

Notes at the end of a fic or chapter are for things that don't need to be said or are not useful to a reader until after they've read the preceding content, such as translations for that handful of dialogue that's in Vulcan or Portuguese, or any parting greetings or announcements you want to give, like a thanks for reading or a reminder school is starting back so you won't be able to write as much. End notes are the best place to plug your social media to readers if you're inclined to do so, but remember that cannot include payment platforms like Patreon or Ko-fi.

As previously mentioned, warnings can go in end notes but that really should only be done when the warnings are particularly long, such that the length might cause a problem for readers who are already confident in their comfort level and would just want to scroll past the warning description. In that case, the additional warnings need to go in the note at the end of the first chapter, rather than at the end of the fic, if it's a multi-chapter fic; and you need to include an initial note telling readers that warnings/explanations of tags are at the bottom so they know to follow where the Archive tells them to see the end of the chapter/work for “more notes.”

When posting a new work, where the Preface section gives you the option to add notes “at the beginning” or “at the end” or both, if you check both boxes, it means notes at the beginning and end of the entire fic, not the beginning and end of the first chapter. For single-chapter fics this difference doesn't really matter, but for multi-chapter fics it matters a lot. In order to add notes to the beginning or end of the first chapter of a multi-chapter fic you have to first go through the entire process to post the new fic, then go in to Edit, Edit Chapter, and add the notes there.

Series and Chapters

Dealing with Series and Chapters is actually two different issues, but they're closely related and cause some of us mixups, especially when we're new to the site and its systems, so we're going to cover them together.

Series on Ao3 are for collecting up different stories that you've written that are associated with each other in some way. Chapters are for dividing up one story into parts, usually for pacing and to give yourself and your readers a chance to take breaks and breathe, rather than trying to get through the entire thing in a single marathon sitting (not that we won't still do that voluntarily, but it's nice to have rest points built in if we need them).

If your story would be one book if it was officially published, then it should be posted as a single fic—with multiple chapters if it's long or has more than one distinct part, like separate vignettes that all go together. If you later write a sequel to that fic, post it as a new fic and put them together in a series. It's exactly like chapters in a book and books in a series. Another way to think of this structure is like a TV show: different fics in the series are like different seasons of the show, with individual chapters being like episodes.

If you have several fics that all take place in the same AU but really aren't the same story those should go together as a series. If you wrote a story about a superhero team re-cast as school teachers, then wrote another story about different characters in the same school, that's this situation.

Series are also the best way to handle things like prompt games, bingos, or Kinktober, or collect up one shots and drabbles especially if your various fills, entries, and drabbles are for more than one fandom. If you put everything for a prompt game or bingo, or all your drabbles, together as one fic with a different chapter for each story, what ends up happening is that fic gets recognized by the Archive as a crossover when it isn't, so it gets excluded from the results pages for everyone who told the filters to Exclude Crossovers even though one of the stories you wrote is exactly what they're looking for; and that fic ends up with tons and tons of wildly varying and self-contradictory tags because it's actually carrying the tags for several entirely different, possibly unrelated stories, which also means it ends up getting excluded from results pages because, for instance, one out of your thirty-one Kinktober entries is about someone's NoTP.

Dividing these kinds of things up into multiple fic in a series makes it so much easier for readers to find what of your work they actually want to read.

If you've previously posted such things as a single fic, don't worry, it's a really common misunderstanding and there is absolutely nothing stopping you from reposting them separately. You may see traffic on them go up if you do!

Parting Thoughts

Metatext is ultimately all about communication, and in this context effective communication is a matter of responsibility and balance.

Ao3 is our archive. It's designed for us, the writers, to have the freedom to write and share whatever stories we want without having to worry that we'll wake up one day and find our writing has been deleted overnight without warning. That has happened too many times to so many in our community as other fanfic sites have died, been shut down, or caved to threats of legal action. Ao3 is dedicated to defending our legal right to create and share our stories. Part of the deal is that, in exchange for that freedom and protection, we take up the responsibility to communicate to readers what we're writing and who it's appropriate for.

We are each other's readers, and readers who don't write are still part of our community. We have a responsibility as members of this community to be respectful of others in our shared spaces. Ao3 is a shared space. The best way we have to show each other respect is to give one another the information needed to decide if a given fic is something we want to engage with or not, and then, in turn, to not engage with fic that isn't our cup of tea. As long as our fellow writer has been clear about what their fic is, they've done their part of the job. If we decided to look at the fic despite the information given and didn't like what we found, then that's on us.

Because metatext is how we put that vital information about our fics out in the community, it's important that our metatext is clear and easy to parse. The key to that is balance. Striking the balance between putting enough tags to give a complete picture and not putting too many tags that become an unreadable wall; the balance between the urge to be thorough and tag every character and the need to be restrained so those looking for fics actually about a certain character can find them; the balance between using established tags for clarity and ease and making up our own tags for specificity and fun.

Do your best, act in good faith, remember you're communicating with other people behind those usernames and kudos, and, most importantly, have fun with your writing!

#THE GUIDE #metatext #fandom meta #fandom etiquette #Eiiri made this

4K notes · View notes