#the server is still under construction so the things to do there are basically chatting
Explore tagged Tumblr posts
kenniko · 2 years ago
Text
so ik I'm new to the betasquadblr but I'm helping out a friend here🙈
There's a beta squad discord server and I (and a few others alr in it)will be very happy for more to join!
The server is new, and there's only very few people, not even two digits yet (the members are two digits but that's w bots) so if you guys want to introduce yourself and get comfortable, now is the perfect time because of the small amount! So,
thank you in advance, and welcome!
9 notes · View notes
princessofprocrastination · 4 years ago
Text
Just A Bet (GeorgeNotFound)
MASTERLIST
pairing : georgenotfound / george x reader - dreamwastaken/dream / clay x reader
summary : you’re just a bet to him. that is, until he realizes that you’re someone with a title. he scrambles to pick up your broken pieces, but he doesn’t realise that he’s too late. (angst) (trigger warning) (happy ending)
a/n : here’s sorta a little AU for you guys, don’t take any of this seriously, some things in this are clearly made up. side note ; holy shit i have more than a 100 followers right now. thank you so so much. 
everyone has probably dreamt of being a princess, a real one. for example, when the movie ‘the princess diaries’ came out, people wanted to be mia thermopolis and rule genovia. 
sounds like a dream, that is, to be going to high school and have plenty of paparazzi’s chasing you, or to be able to be recognized everywhere. 
in reality, it is the complete opposite of living the dream. you could barely walk out without being recognized if you didn’t cover up your face in some way. you were restricted to do many things, even to just hang out with your friends to grab lunch. 
to other people, they might just tell you to suck it up, that in the end of the day, you’re royalty, and that these are only tiny problems. 
you agreed, sure. but you did want to smell the fresh flowers outside. you wanted to be able to get food from wherever, with whoever without people’s prying eyes. 
you just wanted freedom. 
to whom might be reading this might be confused. you’re a princess. just like the movie, yes. princess of saudi arabia, you are. 
you are fairly young, still in your twenties. most people your age are out having fun going on a girls night, or still studying for their degrees, or even working right now. 
but you were prohibited to leave the castle. you were told to leave on the queen’s orders, only during meal times.
some days, you really liked it, being a princess. if you weren’t being egoistical, you would say that your face really did suit the royal title. 
you didn’t have to leave your room to make stacks of money. but the problem with that was, what would you do with the money if you couldn’t leave the house?
so you went on the internet. you settled on the internet. with the queen’s permission, of course. 
sure, she can be strict like all the time, but she tried her best to give you your freedom. so she let you have social media accounts. you being you, the public immediately found your accounts. 
you couldn’t find new friends, they were too scared to come across you. so you just entertained yourself. 
this isn’t bragging, but a lot of people knew who you were, but that doesn’t mean everyone does.
since you barely had a childhood, with being born and raised royal, you entertained yourself watching minecraft youtubers. for some reason, it calmed you. 
dream team, as you called the group, caught your eye. you watched all of their videos, caught up with every single live streams of theirs, even followed their instagrams and twitters. 
one morning, when you woke up, you found your instagram notifications fuller than other days. you were fairly confused. that is, until you realised that the whole of dream team had followed you back. 
they definitely know who you are and what you do now, right? they have a large fanbase, surely, they would’ve told the boys. 
your followers, since seeing the boys follow you, have told you to start playing games. you didn’t disappoint them. you asked your parents if you could and they granted you permission to do whatever you wanted. 
they told you “this would entertain the public and love you even more.” and smiled at you. you thought maybe they hit themselves in the head today with the leniency they gave you. but you pushed that thought. maybe they thought you have grown old enough. 
valkyrae, a streamer on twitch had reached out to you after knowing about your gaming desires. she asked if you wanted to join her and her group to play among us together. 
you almost immediately agreed and the rest of her friends welcomed you in with opened arms. 
your mum gave you one condition, that you had to follow in order to film yourself playing games. that is, if you kept yourself poised and respectable. you agreed to her shenanigans and started to play with rae. 
playing with her meant that you met countless different content creators, such as corpse husband and pokimane. they all were super nice to you, even when you had told them that they didn’t have to be nice to you because of your title. 
soon you had found yourself in an amazing group of friends and you felt great about yourself. 
you and rae had sustained such amazing friendship that she had came over to your house multiple times for meals. 
you’d text her “come over to my house, let’s eat lunch.” 
and she’d reply with “your castle you mean?” she jokes around. 
your friendship was loved by many people out there. 
one thing you didn’t say was that not everyone was obligated to know who you are, which then happens to be funny to see when they did end up finding out who you are. 
just the fact that they show such shock to their faces, and the tone in their voice changes. 
“holy fuck, she’s royal.” toast says as he came back from googling your name to know more about how you came about in a game of among us. 
“i’m so sorry for the past rounds.” he apologizes for the time he accuses you for no reason.
“please treat me the same way you used to, i’m just y/n when i’m playing games, definitely not a princess.” you told him. 
you didn’t have a big ego, although your parents did. “they need to know that you’re important.” they told you, but it never stuck to you. you wanted to be respected as a person, for your personalities, not because of a stupid title you were born in. 
sykkuno, rae and you had decided to make an smp, where you three would start building things for fun and stream it. 
you three had enough fun until it got boring, for you to start asking your other friends to join. the first person you offered to tour your little world was corpse since you and him had clicked so well. 
because you started playing minecraft and streaming it, it got the attention of minecraft youtubers. and for some reason, the seventeen year old, tommyinnit had found you interesting enough to talk to you. 
with tommy being that close to you, you attracted tubbo and wilbur soot, as well.
“i am in a vc with a princess.” tommy had said on stream when you two decided to play minecraft along with tubbo and wilbur. 
sure, the teenage boy got a little annoying at times, but you found it entertaining and funny. of course, tommy being tommy, he’d ask slightly personal questions about how royalty works in saudi arabia. 
not that he knew how royalty works in general, anyways. 
“the queen is still my favourite woman, but you come in close second.” he told you once. you laughed at that. 
no big title could stop you from fangirling the moment the man, dream itself had sent you a donation, and then later sending you a direct message. 
“let’s play minecraft together soon, seen me your discord.” he dmed you one day. of course you complied. 
for some reason, you never had the chance to play with george, and you played minecraft with sapnap and dream separately, never together. not that you were complaining. 
you decided on a more chill and laid back stream on that specific day, not really feeling like going on a minecraft server or play among us with your bestfriends when you got a text from an unknown number. 
hey. they sent
who’s this? you sent a text back.
my bad, this is george. they sent a text back to you.
holy shit. why would george text you. sure, you have played minecraft and among us with him sometimes but he isn’t one to give out his number so this was weird to you. 
although you consider to be close to the entirety to the dream team, you often tried to avoid texting them, especially outside of streaming. you didn’t want it to be awkward or tense. 
surprisingly, as your conversation with george lengthened, it became less and less awkward. the more you two texted, the more you felt like you and him had been friends for the longest time. 
being the princess, raised in a castle meant that you didn’t really have a social life. other than being put together with some prince of another country in hopes you’ll fall in love with them or marry them, you haven’t really had a legitimate boyfriend. not even a crush. 
to you, the princes in the world can be arrogant, snobby. they act like they are the most important thing in the world, that if they walk in a restaurant, everyone was to drop all their work for other people to entertain them. 
sure, this could just be the way that they were raised, but you didn’t want that in a man, a husband. it wouldn’t kill to be a little humble. 
princes are also a bore. they live practically the same lifestyle as you. conversations were never interesting, always the usual. 
to summarise this, since you and george have been talking and texting, you had fallen for him. hard. and it seems like he’s feeling the same way, just that the both of you hadn’t really said anything. 
-
DREAM’S POV
being really close friends with someone, more than one person, bestfriends, that is, meant that we had a group chat together. 
nothing constructive was ever said, only boys being boys. 
nick was the one to bring it up. and since he is the youngest, he sure does say some stupid things. 
dude, you should try to get in y/n’s pants. nick asked george in the groupchat.
there was a running joke between the nick and i. george lives under a rock, basically. when everyone was walking on eggshells around you, trying not to offend a princess, he never really cared. 
and that was when nick and i found out that george had no clue you held such a title on your pretty little head. 
you are a beautiful girl, no doubting that. i was sure that many people, even before you started streaming had a major crush on you. george definitely fits right in. he was practically vomiting hearts when he first saw you. 
it was meant to be funny. it was never meant to go this far. nick didn’t mean for his little bet to break a heart, let alone a princess. 
but he did. well, technically george did. he was so brutal with it. he toyed with your feelings, like he had no care in this world. 
no one would’ve guessed that the little cute, short george would do something as bad as he did. 
and now, no one can find you. no one. 
you were there, smiling in front of your camera one day and you were gone the other. just gone. no one knew where you went. 
granted, you are royal. it must not be hard to get people to hide you. but at the same time, you had major reporters trying to find you. and they couldn’t. what does that leave us? 
where did you go? 
come back. 
and although i know you want to hear this from george instead of his friends, you won’t. because he probably doesn’t.
we miss you. 
please just text us, we need to know you’re safe. 
-
YOUR POV
you left. you had to. it had been extremely humiliating. 
you didn’t think someone as sweet as george would do that, it all happened so quick. 
you had flown to england to meet him. he encouraged you to. it felt amazing to leave your hometown, you’ve lived there all your life. you definitely needed to fresh air. 
it took a lot of convincing your parents to let you fly to england. without a doubt, you knew that the only way you’ll get to leave is if you had a guard with you. 
this isn’t that kind of cliche story, your guard could literally be your dad, get your head out of the gutter, you are utterly in love with george, and you were sure george knew that and that’s why he encouraged you to fly to him. 
the first couple of days were fun. he brought you to all over brighton for you to experience what it’s like in england. he told you he wanted you to get your first real experience as a tourist, and that was what he did. 
winding down for the night, you brought him to relax in your hotel suite. frankly, george was surprised that you could afford such a place. but he didn’t want to ask where you got the money from, he didn’t really care. 
all he wanted to do was to complete his dare. his ego was too big to lose this time. 
that night was when you decided to tell him about your feelings about him. you were pretty confident that it was going to go smooth sailing. just the way he treated you showed so much about his feelings. 
so you did, you told him. while you told him that you love him, more than friends love each other, he looked you in the eyes. you weren’t sure what that meant. 
but he smiled. or smirked, you weren’t sure. 
and he kissed you. and the night didn’t end with you just kissing. 
so you thought the night was amazing, that it couldn’t get any better than that. 
that was, until you woke up the next morning. 
-
you woke up, sun shining straight into your suite, curtains wide open. 
although you didn’t really feel the presence of another person in the room with you, you brushed it off. you felt like something was off, that something was missing. 
you rolled over in your hotel bed, to see if the british man was laying next to you. 
he wasn’t. in fact, he was not in the hotel room at all. you checked the bathroom, the small little living room in your suite. he was found nowhere. 
you tried to see if he had left traces of himself in your hotel room, a sign that he was indeed there and that you hadn’t been dreaming it all. 
but the pain between your legs caused by the brit told you that it was all not a dream. 
so you did what a logical person would, text him. maybe he left to get food. 
but you knew that wasn’t the case the moment you had unlocked your phone. 
texts flood in, your social media notifications seemed to not be stopping anytime soon. 
you opened your texts messages. a couple from your parents, a lot from rae, multiple from some minecraft youtubers who you called friends. 
besides your parents, they were asking if you were okay. they were telling you to stay safe and to lay off social media for a while. 
your parents were practically screaming at you through texts. they called you a disgrace, not an honour to the family. you didn’t understand where this was coming from. 
you opened twitter, knowing that it was going to be the easiest way for you to find out what had happened, and why were you involved in it. 
you were trending. number one worldwide. you clicked on your name. your phone left your hand, falling hard to your hotel floor with a loud thud as you covered your mouth with both your hands, crying. 
two pictures. two photos that said it all. 
first photo was of you in bed, obviously naked under the hotel duvet. you were still sleeping. there was light coming from the windows, that showed that it had barely been sunrise when it was taken. 
second photo was what hit you the hardest. you wanted the earth to swallow you from below. it was a photo of your back, very naked back. it was clear that it was a photo that had been taken during sex. 
and it was obvious who you had it with, because he was the one who posted it all over twitter. 
george. 
that was why he left, with no traces of him ever being in the hotel room. 
you weren’t sure what was his motive. but you sure did know that he had completely broke you. 
crying, you picked up your phone from the floor, calling rae. 
“oh my god, tell me you’re okay.” she was panicking on the phone.
“i need to leave.” you told her. you knew that she would immediately understand the severity of the four words you told her. 
since then, you never came back. to the eyes of public, it was as if you never even existed. you were gone. 
-
you moved with rae. 
she had to leave her roommates to settle in with you. her roommates weren’t mad at her for leaving them. they completely understood, you needed the help.
although her roommates wanted to help you, they couldn’t. you needed to have the least amount of people to be with you. 
it didn’t help that they were all content creators, too. 
rae told people that she moved because she wanted her own space, so that she can make better videos. when she announced she was moving, not one person speculated that you had been the reason of her move. 
you paid for the house, you needed to. you owed her. no matter the amount of times she told you that you owed her nothing, that she was just doing it because she loves you, you couldn’t let her pay for a single thing. 
you needed to up your security, too. so you two had decided to get a house that was pretty big, somewhere in the mountains, with top security, away from other people. 
your parents soon calmed down after that day. they told you to come back, the begged you to come back. but you told them that you needed the time alone at that moment, and assured them that you would be okay. 
so they did what parents would. they made sure you were well taken care of. they sent you massive amounts of money, sent your their trusted guards to stay around the house. 
they did this all for you without the knowledge of the public. 
your parents told reporters that you were well safe, and would not be in the public eye, not until you were ready. 
you helped rae film certain videos. well, not like there was anything good to do in the massive mansion, anyways. 
all your social media pages were still up, just not updated. you left everything. you had created a more private one, for your close and trusted friends to follow. 
and you thought that nothing could really top that eventful day in england. 
but it did. 
you’re sat on toilet in on of the bathrooms, rae rubbing your back.
pregnant. it was clearly written on the test.
no fucking way. 
-
in no ways were you ready to be a mother. 
as a little kid, you had dreamt of being a mum, alongside a successful man who took responsibility. 
you never would have seen yourself to be a mother alone, with the help of your bestfriend. 
you never thought that you would be a mother, whose dad is someone who clearly doesn’t want anything to do with you. 
rae stayed with you all the time. even through the gross vomit sessions in the morning, or all the time, in your case. 
but you were in no way shape or form ready for a child. you had to raise a child on your own. even the thought of that had emotionally drained you. 
weeks after you found out you were pregnant, you were significantly getting more moody, and rae knew that. 
she made sure you ate well, slept well and kept up with eating vitamins each day. that was until, you couldn’t take it all anymore. 
maybe it was the stress. well, it was the stress. 
you blamed it all on the emotional toll the pregnancy took on you. your body was practically screaming for help. help that you need, but you weren’t in the right head space to offer the help to yourself. 
it was a typically normal day for rae and you. besides rae screaming in her gaming room while streaming, it had been pretty quiet. 
you felt queasy, but you pushed it off. it was normal for you nowadays. everything almost made you throw up. the look of something, the smell. 
but on that day, it was a different type of feeling in your stomach.
one second, you were walking into the kitchen, trying to get some water, and the other, you were on the floor, in pain. 
you screamed. this was the worst type of pain you’ve felt in your life. you screamed for anyone who could hear you. you were sure that even rae’s stream could hear you, but you didn’t care. 
soon you heard multiple footsteps. one of your guards came to your aid before rae did. he supported your head on his lap, him sitting on the floor. 
he told the other guard who came soon after he did to call the ambulance. 
that was when you finally found out what was happening. 
“holy shit, she’s bleeding.” rae repeated to herself. 
you were bleeding? that wasn’t good, right? that meant bad things, doesn’t it?
you felt like you were floating, like your limbs were as light as a feather. that was because you were losing consciousness. 
you lost it. you lost it and found out it was a boy. 
now the two boys you love more than your life aren’t here with you, forever. 
you cried for weeks, rae next to you, making sure you were still alive and eating. she was the only one that stayed by your side in real life. sure, your online friends did care about you, but they just couldn’t be there with you. 
clay and nick had always been texting you, sometimes calling to try their luck, clay mostly. you knew they cared about you, and they wanted to make sure that you’re okay. but you felt embarrassed. you didn’t want to face anyone, even if people kept saying that you did nothing wrong. 
apparently rae’s stream heard your scream, and that was how rae found out that you were in danger. she couldn’t hear through her headphones, but her chat kept spamming her about it, and that raised alarms. 
they kept asking about the ‘mysterious girl screaming’ in rae’s stream. it was short lived, though. rae told them that she had a friend over and that they were injured, and that rested the chaos for a little. 
you were sure that some people knew you were living with her. most of them were almost like detectives, after all. 
you didn’t blame the stans. it wouldn’t take a genius to figure out that you would live with her, anyways. 
since the awful day at the hospital, you have texted clay and nick. you wanted to tell them that you were okay, that you aren’t hurt, at least not physically anymore. 
it didn’t take you long to start calling clay daily again. other than rae, you didn’t really have anyone. so you told clay. 
it felt weird talking about a baby that used to be in you to someone whose bestfriend was the dad of. but he completely understood you. sure, he couldn’t say for experience, seeing as he clearly can’t get pregnant, but he supported you, made sure you let it all out to him. 
you and clay grew close, almost bestfriends. although you and nick were close, he’s still in college, and that meant that he usually didn’t have time to talk to you as much as clay did, and you didn’t blame him. school can be a pain in the ass.
but you still made sure to never keep nick in the dark. as much as clay is one of your bestfriends, so is nick. 
clay made sure never to talk about george to you, which deemed to be difficult since they had been friends for years. he had accidentally slipped his name out to you a couple times, but you were sure he didn’t meant to do that. 
other than the usual “george has been sleeping like a log” and “he slept through the smp war.” you hadn’t heard anything else about him, but it seemed like he was doing well. 
clay had told you about the bet. 
“nick brought it up, but we didn’t think he was actually going to go through with it.” the floridian said. 
you aren’t the type to hold grudges, not even if they did you really dirty, so you told clay that you were on the path of being fully healthy and that he didn’t need to apologise for his friend’s behaviour. 
“are you ever going to come back?” he asks you in a facetime call. you knew exactly what he was talking about. he wanted to know if you’d ever come back on the internet. 
you didn’t even know the answer yourself. you weren’t sure. so you told him that. 
“maybe, maybe not. who knows.” and that was months ago. 
you had plenty of time to heal, to get back on track. but nothing could top your pain of losing your child, that you never got to hold, to kiss, to spoil. 
telling your mother about the loss of your baby was the hardest. she is a traditional woman, always telling you to get married before bearing children, but that didn’t mean she didn’t love the baby you were carrying in you. 
she cried on the phone, sobbing, hiccupping. you wanted to hug her so bad, she even asked you when you’d come back, but you told her you needed time, but you’d be there soon. 
for some reason, although you got maximum hours of sleep each day, you still felt exhausted. you consulted a doctor, but he told you that it was normal since your body is still fragile, but the exhaustion never really went away as months go by. 
being bored at home, and hearing rae having fun made you feel lonely, it made you feel like you were left out. so you made the decision to come back. not to stream, but to appear in rae’s videos.
rae and the rest of the group welcomed you with open arms. they were caring and made sure you felt comfortable again, not stepping any boundaries. not that you cared, the public was bound to know everything soon enough. 
so you did that. 
you were playing proximity chat among us, with the usual people. at that point, you and the other nine people were still in the lobby, chatting, until corpse sounded out. 
“what have you been doing nowadays?” harmless question, in your opinion. 
you didn’t want to hide anything anymore, and rae knew what was about to happen.
“been having a lot of rest. doctor said that i’m still fragile.” you told corpse. 
“are you sick?” toast asks. some people would’ve been offended at that question, or take it the wrong way, but you didn’t. 
“actually, i suffered a miscarriage recently.” you told them honestly. 
there was no awkward silence. immediately, everyone started apologising, saying “sorry for your loss.” 
you brushed them off, telling them that it’s okay, that they didn’t offend you at all for asking that question. 
“feels good to get it out my chest.” you told them, laughing at the end of that sentence. 
“she hasn’t slept well at all, she really wanted to tell you guys.” rae told her
one by one, they all spoke to you, asked you if it was even okay that you all talked about it on streams. you told them that it had been your choice to tell people this way, and they had nothing to worry about. 
on the other hand, it was tough for george. not at first, though. he thought it was going to be easy, having sex with a pretty, virgin girl and ditch her alone in a country she she hasn’t personally been to.
but that changed the moment she disappeared. the guilt never really hit george until people started bashing him on the internet. 
at first, people were too focused on the girl. people discriminated you, called you a slut. they didn’t think that george was wrong at all, although he was the one who took the explicit photos and posted it. 
but then, people, mostly woman had started to realise indeed how messed up it was. 
george really couldn’t care that you “left.” but then people kept on commenting on his posts. specifically, they often left a comment saying “really bold of you to do that to a princess.”
at the start, he thought the comments meant that they couldn’t believe he did such terrible things to their princess, someone wholesome they cherished. he didn’t realise that his comments literally meant that you are a princess. 
so he googled it. he wanted to know why people kept calling you ‘princess’ or ‘next on the throne’. he was curious, and he wasn’t expecting it all to be real. 
when he googled your name, a huge google tab came out. 
princess of saudi arabia. 
this must be a typo, right? he couldn’t deny that you are indeed a pretty girl, he just couldn’t believe that he had done such things to someone so royal. 
he never even thought that one day, he would score to talk to celebrities, let alone be able to be in bed with an actual princess. 
so he doubted it. 
but then he kept looking. 
he looked at images of you. photos of you with a small tiara, next to what seemed to be the queen of saudi arabia, wearing a long, modest emerald gown. the photo was taken when the king had a birthday. 
picture after picture, he started to doubt his thoughts even more. 
he couldn’t lie, your face really fit the title. if he really thought about it, your existence screamed royalty. the way you spoke, your poise, the way you strut in a hallway and was able to wow a crowd without trying. 
george always assumed that people only stared at you in public because of how beautiful you are. he never really realised it all until now. 
usually, guys can be insecure when they hear rude comments about how a lanky man is able to get a beautiful, confident woman. but to george, he felt even more egoistical. he used you, truly like a trophy wife. 
that was until he really realised. 
now, he thinks that everything he did was just a plain asshole move, not saying it isn’t if he did it to any other normal girl.
“i fucking messed up” he thought to himself, reading press conferences about your princess title.
if he thought he messed up then, wait till he found out you were pregnant, and then later losing it. 
he felt like he was in a fever dream. it felt like a written book, not real life. 
he kept slapping himself, pinching himself to make sure he wasn’t dreaming. it all felt unreal. so many things were happening. 
now, he’s more concerned than guilty. he wanted to know if you’re okay. even he felt like he can’t cope with the information he was given, how would you feel?
furthermore, he kept reading theories that the scream in the background of valkyrae’s stream was yours. had you lost the baby there? had you lost his baby there?
-
he called clay and nick. he wanted to double check. it was all a lot to handle, knowing you’re a princess and a mother in the same week. 
nick screamed at him on discord for hours, literally. george knew clay was just as mad, just as disappointed. he just didn’t have the energy to say it all, even though all he wanted to do was fly to england and beat george up. 
although it took george a while to realise everything he did was messed up, he came to. and he really did want to contact you. but really, anyone in your position wouldn’t even glance at his name twice after what he did. 
he was happy that you were looking healthy on rae’s stream. although you weren’t really ready to stream on your own again and many people understood that, and never pushed you. 
but whenever he saw you sometimes on rae’s facecam, he could see that pain, deeply hidden in your eyes. you were trying to cover up the fact that you were still trying to heal. 
-
CLAY’S POV
it was infuriating to see george not really giving a shit at first, and then changing to a new man. it took you to tell the world about your lost child for him to own up to his mistakes.
nick and i had been friends with him for years, it takes a lot to just dump a friend, a close one at that. so we did what we could, help him wake up from this “dream” he’s in. 
that didn’t mean we weren’t mad at him still. 
if he didn’t want to own up, i will. 
-
the subsequent years came by and went really quickly. people were starting to forget the drama that you and george were in. people soon became uninterested about it, but still stayed with you, encouraging you to heal slowly and take your time. 
that was what you liked about the internet. granted, some people can be mean, but the people who supported you were the ones that helped you keep going, helped you find a reason to wake up in the morning. 
no, you’d never forget that you lost a child, and you were reminded by the people on the internet who made it a pact to make sure george never forgot that too. 
george did end up talking to you a couple years ago. you accepted his apology, but not him. you were sure he only wanted to apologise after knowing that you were the next in the throne. 
speaking of throne, you were back in the castle. not permanently, but you visited often. you still lived with rae, and you had actually started streaming on your own again a few months before george reached out to you. 
clay and nick had been supportive of you since the start, still clearly apologetic even though you told him that you had forgotten about it and that it hadn’t even been their fault in the first place. 
but they were persistent, clay more than nick since nick was still very busy with college. you loved the two of them and considered them to be one of your best friends, aside from rae. 
-
GEORGE’S POV 
it was difficult. i felt like i had no shame to just text her one day after being gone for so long. but i actually felt bad. i know it was a rocky start. 
i had been so focused on winning the bet and not wanting to be called a pussy from my friends that i disregarded you, your feelings.
i knew from the start that you had been a great girl. you were just so sweet to everyone you meet, even strangers. it warmed my heart, it made me feel safe to be around you all the time. 
not that i can say that right now anyways, i didn’t have the right at all, after what i did to you. 
i don’t know what love is, given the fact that multiple girls had left me before this. i asked myself often if what i felt for my exes were actually love, or had i just been desperate. 
but i felt like when i was with you, it had been love, or close enough. 
but i couldn’t just burst it out one day that i love you, we weren’t really even dating. 
given that you had been pure, prior to me, it was shocking to see you so open, so welcoming to me. it was like you had known me forever, that you trusted me. 
and i took advantage of that, and later i got the consequences. 
i suffered the consequences. i see him with you. and i see that you’re happier with him. if it was any other guy, i think it would hurt less. 
but it was my own best friend. it was clay. 
all the instagram photos you post, his face blurred or covered, or when he posts a photo of you, it all hurt. 
i started the fall for you, for your genuine heart, and when i finally decide to do something about it, someone else had done it before me. 
deep down, i knew that clay would’ve been the better choice for you anyway. but it still hurt me. hearing his voice coming from behind you when you stream without your facecam. 
everyone was so supportive of you and clay, they’re obviously happy that you found someone who treats you better, even i knew that.
i wished i hadn’t taken you for granted, i wish i hadn’t listened to the stupid voice in my head reminding that you were all just a bet, that i wouldn’t love you like you think i would. 
i felt left out. 
a while ago, you were in florida with nick and your boyfriend, clay. it stung to see nick and you streaming so happily, not remembering me. 
but i deserved it. and i knew you deserve to be happy, after everything i did to you.
but that didn’t compare to the pain i felt now, a year later, seeing photos of clay and you, his face turned from the camera, facing you. he was down on one knee, proposing. 
and although you were crying and your hands covered the bottom half of your face, i could see how happy you are, i could see the amount of love you held for clay. 
how i wish i had done things a little more differently. 
304 notes · View notes
avatarhanami · 3 years ago
Text
Writers Applications Open!
Our development team at "Avatar: New Beginnings" is looking for an additional role as a writer to help with document editing, but also provide new perspectives on Hanami's story and the development of our plotline!
Disclaimer: This is a volunteer-based project, and we are not affiliated with Viacom, Nickelodeon, Avatar Studios, or the creators of both series. Hanami's project is to help grow our personal skills while also promoting your work to a widespread audience! We don't provide any compensation or payment in return for your services outside of promoting in on our different media platforms.
If you're still interested, below the cut is additional info about the role, as well as requirements!
Important: A good portion of Hanami's story and key plot points are solidified. While we are always interested in constructive criticism, we are needing help with individual chapters for future books and elements of the story.
Positions open: 1
Responsibilities as Writing Support:
Being able to work with others in a collaborative environment over Discord, Zoom, etc.
Help edit documents located in a shared Google Drive, help create documents, notes, etc. during writing meetings
Being consistently present during chats, Zoom meetings, and any team held occasions.
Making sure you are up to date with the story, character, and plot development (we will hold a meeting after the decision is made to bring someone on to introduce you to the characters, story, and the project overall so please don't feel to worried about this element too much)
If any assigned work is given, be sure to keep consistent updates with the Project Lead or any other writing support.
Keep all things related to the story, plot, characters, etc. strictly between the team and yourself. We'd like our work to remain secret and confidential to ensure spoilers aren't given out.
Keep our project a positive environment for creativity, support, and memes. Any discourse or rude behavior will not be tolerated.
Requirements:
Fluency/advanced speaking and writing in English
We will not be bringing on anyone under the age of 18, specifically because of our whole team being consisted of adults. I'd like to maintain our comfort and the comfort of those outside of our project.
Being able to edit, organize, and manage documents related to writing or notes made during development
Access to Google or a Google account to access our shared Google Drive to create, edit, and move documents.
Open to video chats, text chats, and other means of communication via Discord, Zoom, or other online chatting platforms.
A history with creative writing (can be previous fan-fiction work, short stories, whatever you may have!)
Commitment to the project and active within the server. Also consistent with interacting with other team members and consistent to participating in writing meetings over Zoom.
Flexible scheduling to doing meetings with other writers or one on one meetings with the Project Lead
Up to date on the Avatar lore, canon, and series. (You must have watched both "Avatar: The Last Airbender" and "The Legend of Korra")
Self-motivated and open to collaborating
Open-mindset into growth and constructive criticism as well as giving constructive criticism.
Open to researching different topics related to cultural backgrounds, historical writing, and diverse topics that will relate to Hanami's story.
Brownie Points:
Have a background in scriptwriting
Organizational skills
Knowledge of one or more languages (Spanish, Chinese, Portuguese, etc.)
Flexible schedule and openness to meet
How do I apply? Great question!
First, fill out the written portion of the application here (it's a short questionnaire for basic information). Next, we require you to email us writing samples or any portfolio work you may have, so we can get an idea of how you write and get familiar with your work! Be sure to clarify who you are so we can link your first application with your samples! Email your work to [email protected].
What Happens After I Apply?
We will keep applications open for a month to ensure everyone who wants to apply can! Once we narrow down who we feel would be a good fit for our project, we will email you back from the email you sent your portfolio with.
We will hold interviews over video chat via Zoom, and will ask any follow up questions we may have, but also just hang out and get familiar with one another!
After that, we will meet and decide who we feel is the best fit for our team! It's not a quick process, but we want to ensure we make the best decision for us and for the project!
The interview will be held with the Project Lead, Kee, and one of the other writers.
Application deadline is February 17th, 2022 at 11:59 CST. We will not look at any late submissions.
Other Notes:
The development team of "Avatar: New Beginnings" is a diverse and nerdy group of friends who love to explore the world of Avatar and make memes. We are open to all identities and promote inclusive representation through our project. We hope everyone who applies feels comfortable and we look forward to seeing your applications!
12 notes · View notes
luminous-shifting-vibes · 4 years ago
Text
*sequel* to actual fucking quotes from the shiftblr coffeehouse discord server
once again, it's out of context because x1000 funnier
also x1000 longer than previous post
"ur satan is gnc af"
"Bestie I’m already having gender envy over a fucking demon please"
"O_O ODEPIJHFbavevisdpvfhzdcnjawedsidjksjdkoeirjfmkdsoeirujdksodifjndmksoidfjdksidfj ITS" NOT IN MY FRAFTS IS SPEDNT 1 hour PN THAT SHIT"
"AUGHHHHHHHHHHHHHHHHHHH"
"ohoho sexy"
"I am very proud of myself"
"himbo x edgy fuck"
"YOU COULD SQUISH HES CHEECKS"
"he has teefs"
"SQUASH"
"good for biting 📷"
"he's a himbo basically"
"B͂̒̄iͫ̍̈tͧ̓ͯè̄̇"
"bifth"
"i havent watched blue exorcist in years but mr okumura my beloved </3"
"MY LIFE QUESTIONS HAVE BEEN ANSWERED"
"is it important information to mention that the person i put up for my turn is the son of satan" "I know like 1 thing about everyone who isnt ranboo lmfao"
"crimes"
"tumblr sexyman"
"idk why but my first thought was cowboy onceler"
"I vibe with him but he is very long and twisty"
"steampunk e-girl"
"steampunk tumblr sexyman"
"Canonically bi crimelord I agree!!"
"OOO FRIEND SHAPED"
"ARTIST SIGHTED"
"they look like someone i would want to be friends with but is way cooler than me so i'd never actually talk to them"
"babby..... would die for him"
"honestly i probably kin him"
"i'm sure he's lovely but he looks way too much like my ex i'm sorry-"
"i'd be down for another rotation! i have another twink to show y'all"
"Also :00 blonde friend"
"Let us all infodhmo"
"Hsjagdvbs shhh im on phone"
"Nix woukd you like to joon?
"skitters away"
"I have two braincells and they both drink dumb bitch juice"
"oof wait whats the order again i have 0 memory"
"i want to bond with him over cosplay-"
"Awkwardly watches in band kid"
"One day I'm gonna a broadway star"
"which isnt to say they were bad. they were just fortnite dancing during rehersals"
"I threw it so hard my glasses flew off and slid under the stage right divider"
"anyway heres my boi"
"emo"
"haha emo"
"virgil sanders kinnie"
"he looks like he listens to my chemical panic at the fallout boy"
"Bro I bet he'd kick my ass with his deck"
"bird man my beloved"
"fuck i had so much to say and then i forgot it all"
"Birds!!"
"guiguhuh"
"crabrave"
"She sounds like someone I would end up stealing her personality"
"yess name collector gang"
"alias glass aiden haven absinthe fish brick rice"
"But I have Cypress, Remure, Genesis, Lemres, and Comet"
"And she's named after a mars candy bar bc alien"
"Hey, if plato went by plato, you can be king thief"
"im not dissing my gramma like that shfojd"
"My dad has seven legal names" "bitches be like *looks at fictional character* *steals their name* it's us we're bithces"
"coraline lowkey traumatized me but i adore it regardless"
"mmmmmm magic man :]"
"°0° green man"
"criminal (affectionate)"
"he would shoplift a candy bar from walmart and then brag to all of his friends about the sick stealing he did"
"despite the fact he's canonically been capable of overpowering a minor deity"
"i would commit so many crimes for him"
"Very babey"
"Yes please tell green man he is very pog"
"he also keeps a lot of dumb secrets"
"but I will sorely miss the chaos and energy of this here chat until I wake again" (by request XD)
"i just say words and if they're funny then they're funny"
"* or extremly chaotic either works"
"at this point we are just taking turns rambling"
"oH--"
"bc my brain has a schedule"
"Hopefully they have gyoza there or I will lose my mind"
"hehe yes spooky man"
"my ghost glucose guardian"
"the head of the undead group that lives there, and we end up dating. (yes I date a ghost, no I will not be taking constructive criticism /lh)"
"ghosts r just inherently sexy"
"i mean im becoming a squid thing so"
"Raven quirk raven quirk!!"
"ł â m p"
"łæmp"
"mothman: ooh lamp you look very nice today! do you come here often? mothman: wait shit no"
"I'd date a ghost"
"mine is still accurate, i am still sobbing (/j)"
"p e e p e e"
""@nick wilde is a tumblr sexyman" is the best thing i have ever seen"
"im sorry im cackling like a dying hyena"
"you're all 12 year olds"
"PEENIE"
"He once caused global warming on accident so he could get a tan"
"god, what a himbo. i love him"
"that reminds me of my friends kin assigned me jesus"
"Man outside of battle be like: princely crying but then in battle hes like: "CATACLYSM! DISASTER! DEVASTATION!" Chill out man"
"Every time I talk about satan it never fails to shock people it's my favorite thing to do"
"im kin assigning him roman sanders" ""Oh yeah he caused global warming because he wanted to get girls" "he what""
"oh damn i forgot satan was straight"
"twink appreciation club"
"give us the twinks"
"my first thought was bottom-"
"so many people to try and get his dad to love him"
"daddy issued"
"OH MY GOD ITS WILBUR"
"Big boy but"
"anyways janus is swagggg"
"........................."
"gib twink"
"give twink then i will share"
"holds him gentle like hamburger"
"This dumb bitch opened a book that said "do not open" and got possessed by a little bastard"
"he is. fragile creachur"
"klug is beauty klug is grace i would let him step on my face"
"If I'm playing swap and I have to hear one more "Pwanet Powew" Im gonna lose it"
"Who is to blame? Pandora or the box?"
"Bakugo isnt my type but I respect the drip"
"i say like my type isnt long-haired pretty boys and girls that look so gnc that people have a history of confusing them for men"
"hes a gremlin and i can appreciate a pretty gremlin"
"that is to say i am attracted to VFlower vocaloid. This is a confession."
"note i am a lesbian"
"You may like Schezo wegey"
"why does he have one single expression"
"soul soul eater passes the vibe check"
"magic wand"
"I Want To Hold His Hand"
"i would commit a war crime for him any war crime idc which one"
"my favorite one is when he sounded rlly gay because he said "Muscular bodies keep me satisfied""
"p e a n u t"
"Klug is a homophobic homosexual its just facts"
"grug from the croods is peak male performance"
"jaw drops to floor, eyes pop out of sockets accompanied by trumpets, heart beats out of chest, awooga awooga sound effect, pulls chain on train whistle that has appeared next to head as steam blows out, slams fists on table, rattling any plates, bowls or silverware, whistles loudly, fireworks shoot from top of head, pants loudly as tongue hangs out of mouth, wipes comically large bead of sweat from forehead, clears throat, straightens tie, combs hair Ahem, you look very lovely."
"tag yourself im the fireworks shooting from the top of the head"
"i like essays"
"central time gang"
"11:11 pog-" (wait... is that a suprise angel number?? yes it is lovelies just for you <3)
"Then again im also a dumbass bitch who wonders what the souls in soul eater taste like. SERIOUSLY THOUGH. THEY LOOK TASTY AS HELL!!!! LIKE GODDAMN BRO YOU'RE MAKING ME FUCKING HUNGRY. Like. that shit- it's Bone Apple motherfucking Teeth. hell yea my guy. Im hongy now.... shlorp I'm seriously considering this. Like. They seem kinda like a liquid? But a solid? Are they like jello? The fuck they taste like my guy???? I keep imagining they're like sour, like sour candy maybe? Or do they taste salty? Sweet? Maybe some combo of two? Do they even have a taste or is it about the texture? The sensation? God my mouth is watering what the hell. I am starving. I think I need to go get a cookie. I'm gonna go get a cookie. Brb. I'm better. I'm still craving souls though. Which is a weird-ass cringey thing to say but I'm being dead-ass rn. They just.... look tasty???? And I wanna eat one. Thus. I am shifting to Soul Eater for the express purpose of satisfying my fucking cravings. enjoy"
"points were made"
"jello? more like helloooo schloooAHFJDSDAIDWNALDHSJKDAIDANDM"
"WAIT I THINK I HAVE AN ANIME GIRL BITING VIDEO TOO"
"anime girl voice: mmm! mm... ahhhhmp!! mmm, mmm... aaahmp!"
"i think it sounds great i'm going to start eating like that"
"several people are typing"
"do these look edible to you"
"forbidden gummies"
"when I was on lsd I couldn't eat my fruit gummies because I thought they were alive because they had little faces on them"
"oh shit yeah don't do drugs"
"anyways general consensus is puyos are edible, ty for your input everyone"
"everypony is a word so powerful it can bring nations to its knees"
"pls the self control it's taking me not to say "hewwo everypony" in gen chat when someone new joins-"
"hewwo evewrypony uwu deaw cewestia i hopwe it doewsnt wain owo"
"ive cooked up a sowution wiwth the knowwege ive acwued. they say a kitcwen time saves niwne, but im just savwing two. Ive gathewwed the inwedients to make a time sowbet. Thewe's hawdly woom fow seconds when the seconds mewt away."
"I had a ten year old sister... you know what happened to her??? very sad, very tragic... she turned eleven....."
"NIIICE"
"Guts dont say the secks word :( /j"
"watch your fucking language in front of the president"
"im so sorry lumi"
"i think you're like ehhhh 8/10 funny"
"now me???? 10/10. Hilarious"
"sometimes i have to take a step back and remember that this is the same guts i follow on tumblr /lh"
""ok every here's some good shifting advice!!! uwu have a good day" "yeah i did lsd and ate fruit gummies""
"i have one setting and it's whatever this is"
"my bitch ass cat just pushed the door open with his fuzzy face and now my sleeping dad is being lulled into dreams by Cosmo Sheldrake's 'Pliocine'."
"me on discord: nick wilde"
"me on tumblr: shifting water! haha funne! me on here: my hermit crabs are cannibals also i want to eat souls."
"im sorry yOUR VIBESA RE JUST SO DIFFERNT"
"u give off older cousin ive never spoken to but always admire at the family gatherings vibes"
"what the fuck"
"BC I HAVE LIBERTU"
"If you adopt me then yes"
"am I qualified for dad jokes???"
"we're all a lot smarter on tumblr"
"I'm like "awww... sweet... sweet little shiftlings... posting such sweet shiftling content... so pure, so wholesome... does not even know abcs....""
"can't think before you speak if you never think B)"
"I'm not responsible enough to be a mom"
"cat pet"
"show us pictures of the cat or i will do Crime"
"maybe thats me being a coward tho"
"MOTH!!!! MOTH MY BELOVED"
if y'all want I can make this a series bc shiftblr keeps giving me more content
34 notes · View notes
fijiangecko · 4 years ago
Text
Maintaining a New Life
Chapter 8 - In Motion
Read it on AO3 here
previous | next
~~~~~~
The sun had risen and set 3 times since each group began their hunts. Each day providing no new information and the hope of keeping each other safe felt as if it was getting farther and farther away. Kuroo, Oikawa and Iwazumi split off into two groups most of the time, Oikawa and Kuroo walking around town while Iwaizumi kept an eye out for any Port Mafia patrols and your car.
Iwaizumi refused to be alone with Kuroo, stating multiple times that he would “rather gauge his own eyes out then look at the fuckwad who drove out one of his best friends”. A tad bit harsh for Oikawa's taste, but he maintained the peace between the two whenever they brought tension to the table. Kuroo doesn’t mean to be irritating but there’s still so much he doesn’t understand, and these two don’t help in answering his questions since they don’t know much about your past and why you left.
On your end of things, you decided to lay low during the day and do some rounds on the streets at dusk and dawn. Largely things remained the same for the Port Mafia: they operated on the schedule you created and stuck to the same routine based on what vehicles and hangouts you’d seen so far. 
Guess they really haven’t progressed all that much since I left, you think while watching the endless stream of cars. Washijo’s health wasn’t too good, and I can’t imagine it’s gotten any better with all the stress of transferring power and dealing with the mess that I left.
After little to no new information and more questions than answers, the weekend rolled around and the sun has started to hang lower in the sky. You lean against the counter in your kitchen, sipping on a cup of tea and listen to the birds sing from tree to tree. Looking to the clock, you sigh and set the mug down, heading towards the bedroom.
If everything goes according to plan, this whole operation should be relatively quick and you can just leave the club within an hour of getting in. You sift through what little clothes you have and get ready to blend in with tonight’s crowd; standard makeup, nothing too flashy, and a relatively short dress to match. None of your shoes really fit, so the black sneakers would have to do for now. 
With a deep breath, you take a final glance in the mirror and mentally prepare for whatever the night has in store. You double check that your car is stacked with any you could possibly need and rev the engine, taking the dirt road down onto the streets.
The sun starts to set over the horizon, leaving the bright orange orb blaring down on the asphalt as the tires roll down the highway. You don’t bother to turn on the radio, deciding to run through the plan and all of the backups you have prepared. Through public records you were able to find the new layout plans for “The Neon Nights”, so you knew relatively where everything should be and how to get to it. That didn’t always translate into action, though. 
Instead of chewing on your lip you moved onto the inside of your cheek, ripping it to shreds over the course of the past couple of days. You haven’t been this nervous in quite a while and it was really starting to fuck with your head. 
Confidence and assurance were two very different things but often got confused for one another. Back at the ADA everyone just believed you to be confident, and that’s not to say that you weren’t. You know you are one hell of a detective, doing the work that needs to be done and doing it effectively, but it was more so that you knew you were safe and around people that were relatively safe as well. Standard protocol in the Port Mafia was not to fuck with others that had gifts. Washijo always stated that it was to keep the peace on the streets, but that was total bullshit. At the very least, you knew that while the ADA was on their radar, there wasn’t anything that they would be able to do in order to harm your friends.
Now everything was uncertain, there was no more assurance. You didn’t know if they were going to be safe. Tendou always did what he wanted and Washijo just turned a blind eye to it. Now he knows that you’re alive and in Yokohama.
On top of that, he saw you with the two of your right hand men that left shortly after you and a new man from the ADA. Tooru and Hajime were found out because you got careless.
The Port Mafia is also aware now of who Kuroo is and that he has connections to you. There’s always going to be a crosshair aimed at the back of his head if you don’t get into that club tonight and do everything you possibly can to erase those damn records of not only your existence, but everyone you care about too.
You blink hard, letting the colors settle behind your eyelids before reopening your eyes and focusing on the road. The stream of thoughts that just crossed your mind had left your heart and head pounding.
Nothing will happen to them as long as everything goes as planned. I’ll find the data servers and wipe whatever I can then skip town. Again, you go through the plan as the last bit of sun disappears around the edge of the world.
 Coming to a slow halt, you park a few blocks away and walk the area in order to secure a teleportation spot and secure an escape route. The checklist in your mind finally had everything marked and every movement from now on was going to be almost robotic as you try to act like the crowd around you. Countless couples and parties line the edge of the building you once knew as a headquarters, the stink of alcohol present already from those who were leaving the venue for whatever reason.
By your lonesome you wait to meet the bouncer at the door, minutes passing as the line dwindles down until you can hear the muffled electronic music. The ground felt like it was shaking from the hundreds of people all dancing just a few feet past this wall. You peer around a few people ahead of you and make note of a pin on the bouncer's suit jacket, confirming that this club is still under mafia control.
You take another deep breath and just hope that news of your reappearance was just kept to the inner circle and henchmen like him weren’t informed quite yet of what was happening. The person in front of you walks inside the club, leaving you face to face with the man with shades. He looks you up and down, your heart picking up as you smile sweetly. Charm wasn’t your specialty but you know the basics. Without another moment to spare, he nods towards the mass of people and you quickly take your place inside the dark and dense room.
The music increases tenfold from when you were outside, feeling the bass changing the rhythm of your heartbeat. Hundreds of people crowd the center of the room, dancing to their hearts out while others line the bars stretched out on the walls.
You walk to the furthest side of the bar, mapping out where you are in your head and making note of little landmarks on the map you practically memorized. Figuring it would look more natural, you squeeze yourself in and order something. Partially to calm your nerves. 
“And the devil herself appears.” Chills run up and down your spine, the voice of whomever just spoke stopping you dead in your tracks. They lean in real close,from behind, lips grazing your ear, their breath warm against your skin as they whisper to you. “Nice to see you Y/N.”
Cautiously you turn your head and face the voice, only to be met with a head of bleached hair and a sultry smile. “Miss me?” He says while placing his hands on his hips.
“Terushima.” The tension in your body hadn’t quite left, unsure of where his loyalties are makes your mind run a thousand miles per second. You prepare to portal out of the club, but his hand on your wrist interrupts everything.
“Let’s have a chat in the back, yeah?” Before you even know what’s going on, you're being dragged to one of the side hallways and up a set of stairs. You take in the surroundings the best you can while being pulled along and realize that he’s taking you back to what used to be the main office area.
Terushima pushes open a set of doors into a lounge area. A large sectional couch faces glass panes that showcase the entirety of the club and a small personal bar and desk line the other two walls in the room. He lets go of the hold on your wrist and beelines it to the alcohol and starts to construct his own drink.
You’re stiff as a board in the center of the room, still taking in everything that just happened in the last two minutes. He watches as you try and create a plan, and laughs out loud at your distraught. “I’m not gonna tell anyone you know.”
It’s like your body snaps when you move to look at him. “Excuse me?”
“I said, ‘I’m not going to tell anyone’.” He strains his cocktail into a glass and saunters over to the couch, sitting himself down. “I really don’t do any work with the Port Mafia since I manage the club. There’s no real benefit to me telling them.”
“Wait,” you blink and scrunch your face together as you follow him down onto the couch, “you manage the club now?”
“Bingo.” The amber drink in his hands disappears slowly as it glides down his throat. “After you left and Tendou took over your position they redistributed everything and wanted to change our little jazz club into a full blow nightclub for the younger people to come and party. I was pretty much the only person around that knew how to keep everything relatively in order, so here we are.” The one free hand Terushima has open lifts up off of his thigh and plops back down in a sort of defeat. His chocolatey spheres hold your gaze.
“And you gave up on singing?” It’s an honest question. The last time you both had a serious conversation was when Terushima was the main singer for your aforementioned jazz club.
“No, more like I took a break. I couldn’t really say no to the Port Mafia so I put my career on hold.” A pained expression flashes across his face before returning to his previous position.
“I’m really sorry Teru.” You scoot closer to him on the cushion, setting your drink down on the table at the center and resting a hand on his shoulder. It was the best consoling you got considering this is basically your fault.
“Don’t be.” He can see the guilt in your eyes and quickly dismisses them. “You did what was better for yourself. Anyone who couldn’t see that you were unhappy was stupid and it wasn’t a suprise when they told me you were gone.” He rests that free hand on top of yours and rubs circles onto the back of your hand while reaching down to place his drink on the same table. “I just thought that I would never see you again, so spotting you by the bar tonight really shook me to the core, y’know?”
The smile that finishes his sentence is wicked, lips curling up at the end. There was always something left unsaid between you both; light touches here and there, lingering glances from across the dimly lit club room and the handful of “dates” (according to him) shared between you two. It never went anywhere; he being the flirt he was made you very nonchalant about his advances. Plus there was the matter of his gift that made things complicated, so it was just better for you to stay out of trouble the best you could.
Things are different now, though. Terushima didn’t cause your chest to tighten or make the blood in your system rush to your cheeks when you thought of what it would be like to be with him late into the night, curled into one another and just simply being. No, that spot now belonged to a tall, lean and dark haired man that weaseled his way into your heart and mind by using his shitty science puns and awkward dancing when he was almost blackout drunk. Those nights of wondering what life would be like with someone else no longer contained bleach blonde hair or a tongue piercing, but the easy comfort that came from Kuroo Tetsuro.
“Yeah, about that.” Your grasp on his shoulder tightens, other fist clenching “Tendou saw me a couple days ago and I’m pretty sure he’s on the hunt. I need to find the P.M. servers-”
“So you came here to find them.” He cuts you off, but doesn’t finish the sentence with a question. He might be a playboy but he’s been through the ringer once or twice and knows that you just didn’t show up tonight to see him. “Unfortunately they moved them a couple of years ago to create an arms deal station in the basement. To my knowledge they took all that stuff to Club Impac-”
Suddenly a young lady busts through the doors, drunkenly falling onto the floor with her eyes completely unfocused on the area around her. A man in a suit comes rushing down the corridor, targeting the woman on the ground.
With many apologies the guard pulls the woman rather harshly off of the ground and looks up to once again ask for forgiveness from Terushima, but meets your cold eyes instead. The spur of the moment interruption caused you to turn around in your seat and watch the events unfold.
Unknown to you, this man had worked under Ushijima for years and had met your eyes years ago. He recognized the dead stare you were giving him currently, but continued pulling the woman out of the room. A bitter taste fills his mouth as he shuts the doors, immediately ditching the woman by the restrooms and walking to the head of security to inform him of the guest that just happened to be sitting up in the lounge.
“Anyways…” Terushima continues filling you in on what has happened logistically within the mafia since your leaving.
Roughly 30 minutes prior to that conversation, miles out into the outskirts of the city the three men who have been trying to catch you at the right time huddled around a coffee table and went over their plan of attack one last time.
“You both got it?” Iwaizumi flicked the last piece of paper in a file down onto the hardwood, looking between the two taller men. Wordlessly they both nodded and turned to grab their respective bags with the appropriate clothes for the night. Oikawa’s outfit was a little more classy then the others to match his personality, Kuroo and Iwaizumi going for something pretty simple just in case anything goes haywire, but with their final touches done up they were ready to set out for the night.
“Do you really think that she’s going to be here tonight?” Kuroo asked Oikawa while Iwaizumi called a taxi. They were a little behind schedule and missed the train, so they had to opt for something quick.
“Out of everything we’ve done so far, I think this is our best chance at catching her. This club used to be a faux headquarters for her. I’m almost positive that she’s either looking for a certain someone,” Iwaizumi catches the tone in Oikawa’s voice as he spoke, making eyes at him while he finished his sentence, “or that she left something behind.”
They both knew that you were fond of Terushima, but they also knew that you had moved on from all of that. You had your eyes set on someone else. That still didn’t mean that you weren’t there for him, but the idea that it was anything but business was a little far fetched.
“So you guys used to be there all the time?” The taxi pulled up to the curb, waiting for Kuroo and the others to hop in. 
“Yeah. Every weekend she would have us come have drinks with her since we were her ‘groupies’, essentially .” Iwaizumi answered, using quotations with his fingers to get the point across. “It was more like a weekly check in but sometimes all we did was catch up with one another.”
The memories warmed his heart. He never once felt like he was working for you, but alongside you. You truly cared about their goals and ambitions, oftentimes ignoring the actual work that the Port Mafia wanted to get done and helping the citizens most in need. Coincidentally, that was how you made the most money and controlled the most area - the people liked you. Being in your squad was a different experience from every other job he had within the Mafia, and as soon as you disappeared he knew that he was going to have to get out sooner rather than later.
Oikawa felt the exact same way, and couldn’t imagine a life where he and Iwaizumi didn’t work together, so they devised a plan and faked their deaths in order to obtain what little freedom that would allow. Both knew that you weren’t dead, no matter how solid the evidence looked, and stuck their foot in the ground in Yokohama in an effort to find you. Two years later they accepted jobs as detectives with the ADA and walked in to see you, sitting at a desk, smiling and laughing with your fellow detectives.
The car ride was silent for the most part, the taxi driver asked a handful of questions before letting the radio fill the dead air. Iwaizumi kept track of how close they were and directed the driver to a few blocks off so they could walk up to the club (he really didn’t want to get this poor guy involved, so better to keep him out of it).
With a small wave from Oikawa, the boys head down the streets but their moods quickly shift as streams of people flood out of the building. The screams of hundreds fills the night air and the heavy footsteps of the three carry as closely as possible to the front entrance. Crowds topple over one another in an attempt to make it out safely as the sound of a single gunshot ricochets off of every surface, furthering the panic in the chests of innocents. Eyes flicking to every possible entrance, Kuroo feels deep down in his soul that you’re inside - you’re either the one firing or being fired at and either causes his chest to tighten, the neverending pit of anxiety at the bottom of his stomach somehow growing deeper. The three stand like a rock against a current of bodies, everyone just running past them and filling the space behind the group as they run.
Only a few moments before their arrival, Terushima and yourself were finishing your drinks and sharing a laugh when splinters flick off the set of doors, and single shot entering the room and shattering the large glass windows that look down on the dance floor. The initial panic takes a second to kick in before the patrons below start their scramble. Terushima’s instincts kicked in and he grabbed you rather harshly and shoved you down onto the ground, covering your body with his own.
“We know you’re in there Y/N!” The voice that spoke was unfamiliar to you, probably just some higher level goon that happened to know what was going on. While tucked under Terushima’s body, you open a small portal to the dashboard of your car and grab the handgun you left waiting. It always pays off to have a backup plan, you think while taking in the surrounding area. The men had yet to breach the room itself, leaving an opportunity for both of you to escape, whether that be jumping down onto the dance floor or using a portal.
“Teru,” his eyes focus on the door but you know he’s listening to your harsh whispers, “we can jump down and blend in the crowd-”
“No.” His jaw clenches, the lines on his face becoming harsher. “They deliberately shot at the window to lure us out there. The one talking is the head of this district so I’m sure every mobster in the area is here keeping an eye out for you.”
“Fuck…” your heart beats just as fast as your brain fires off thousands of different ideas. The crowd of people down below scream for help as they run out into the night and then another shot comes, this time it sounds like it’s from down below. In the crowd.
“Are they firing at civilians?!” Your mind spirals down. What the fuck are they thinking?
“One of those idiots might’ve thought that they saw you.” Terushima detaches himself from you and reaches under one of the tables, grabbing a hidden handgun and making sure it’s loaded.
As he checks the magazine, you muster up a portal big enough for a person to fit through, the other end looking out onto the streets. “Get in Teru. They’re after me.” You plead him with both your eyes and your voice, hands twitching around the cold metal of your pistol.
“Not happening sweetheart.” His smile is sly and coy, teasing you almost. “This is my club that they’re ruining and these people are my guests.” He gestures to the window and then to you, slowing the fall of his hand to emphasize his next words. “It’s my duty to protect them.”
Your lips tugs into a smile and you shut the portal. “Alright then.”
Down on the streets below the three men try to push up river through the endless streams of people running away from yet another shot. Women fall over, others trampling them in the fearful haze that covers the downtown. Iwaizumi rushes over and picks them up, shielding them from the hoards of shoes and getting them back on their feet.
SUV’s among other black vehicles speed around various street corners and men in suits start to surround the area, each fitted with different weapons of different calibers. Pressure grows in the small atmosphere of the downtown area, ears yearning to pop and get ahold of the situation but Kuroo doesn’t know if he would rather feel the throbbing in his head or the despair of hundreds.
Oikawa spins in circles, taking in every detail he can of the mayhem. Each of his senses feels like they’re on fire, enhanced from the sudden change in pace. It would be suicide to use his gift now, so the best he can do in trust his brain to intake whatever information is available.
The three converge after each attains their bearings and stand back to back. “What now?” Iwaizumi is forced to yell over the collage of sounds.
“We go in? I mean she’s gotta be in there, right?!” Oikawa shouts equally as loud, still turning his head around to look at the distressed faces. His voice comes out exasperated and rushed, his breathing picking up.
“Go in?! We can barely move five feet forward, how the fuck are we supposed to get in?” Kuroo takes the more logical stance, trying his best to find a solution to the problem at hand: what to do next.
Luckily, Oikawa, in his twisty turn around scavenger hunt, had spotted a fire escape on the side of the closest apartment building. If they wanted to get a height advantage and take a moment to clear their heads, that would be the spot. He shakes both of his companions shoulders and gestures his head to the ladder. Lightbulbs light up in their heads and slowly but surely they take small steps towards the iron bars, giving the people enough time to adjust to the change in current.
It only takes a minute or two to finally reach the ladder, Iwa hoisting Tooru with weaved fingers and will to lift with his legs, not his back. One handed, Oikawa pulls down the ladder and the three make their way to the landing.
The chaos seen from above is only less claustrophobic as it doesn't let their hearts take a moment to rest. Rather, showcasing the complete lack of control from anyone down below. Every person down below looks like a rat on the loose, caught at the wrong time as they scatter in all directions. Kuroo leans over the edge of the railing, trying to get a better view of the inside of the club.
“There’s a bunch of guys with guns pointed at the top room, part of the window was either smashed or shot at since it’s all over the floor.” Iwa observes to the left of Kuroo, also leaning over the delicate iron bars.
“Can you see in that top room?” Kuroo squints, but it doesn’t enhance his vision.
“Not really,” Iwaizumi starts to tilt his head in various directions, finding the best angle to peer inside that room. “Looks like there’s two people up there but I can’t make out any faces.”
“We should’ve brought Akaashi…” Kuroo mumbles to himself, at this point wondering everything that could’ve been different in this moment. “Well one of them has to be Y/N. I think that’s a given at this point.”
“That or she’s the woman one of the guys has hostage on the lower level.” Oikawa notes, gesturing to each of them to come to where he stands and uses his hand to try and guide their view to a better position.
You also take note of the hostage, peeking down from the remains of the windows. The thought that the Port Mafia is now so low that they would take hostages in order to obtain an ex-member leaves a bad taste on the tip of your tongue. Cold metal brushes your chest as you keep your gun close to your chest. Being as silent as possible, you carefully crouch around the room and get eyes on everything you can.
Terushima had taken off his blazer just a few seconds ago, throwing it over the edge of the couch and creeping closer to the double doors. He listens to whatever words he can make out through the veil of screams and footsteps, retaining only the name “Tendou”.
His head turns to yours from across the room, mouthing the words “Tendou is coming”.
With a clenched jaw, you turn back to the dance floor and see that two more girls were being kicked onto the ground, making a total of three hostages. Hands cover their ears as they plead for their lives.
“Alright Y/N! You’ve got one choice: you either turn yourself over right now or you sit and wait until Satori gets here and we kill those girls and Terushima!” Whoever spoke before loudy shouts again, the words bouncing off of every glossy surface of the club.
GODDAMMIT! Sweat builds in the palm of your hands, the bass from the speakers making the miniscule shards of glass on the ground shake; bits and pieces falling off the ledge and into various crevices in the tile. There’s really only one thing left to do, you think to yourself and Terushima watches as the familiar cerulean hue starts to color the very lines of your body. 
A portal opens to your left, the circle opening up to a view of the entryway of the building. From this vantage point you can see a group of men, all in suits and with their weapons either pointed at the hostages or the balcony. Without hesitation you aim the barrel of the gun at the closest guy and fire at his leg. The bullet enters his calf muscle, leaving through the shin and he immediately keels over. Other men are alerted by the sound and turn quickly to find the source. Like a trained soldier you close and open various portals, one at a time and in dissimilar spots to try and confuse them, and fire potshots at whoever catches your eye first. 
Arguing continues between Kuroo and Iwaizumi as they battle on what to do next; one trying to approach the situation like it’s made of delicate porcelain and the other ready to give blood, sweat and tears. Oikawa refuses to let his eyes leave the club, and it proves to be useful as rifts start to open and close within the confined space. His eyes dilate and once again he slaps Iwa on the shoulder mid sentence.
“What the hell Shittykawa?!” Iwa gnashes, foam practically running down the side of his mouth.
“She’s making her move.” Dominos start to fall, but for once in a very long time the two don’t know what lies at the end of the line. Kuroo can’t believe what he’s seeing - he’s only ever seen you use your gift sparingly and in desperate situations, never to an extent such as this. The last piece of the puzzle finally goes into place as it dawns on Tetsuro that this is life or death. There is no playing around and there are no wrong moves. 
“Alright Iwaizumi: I’m in.”
The aforementioned turns to him with a blank expression, a little unsure of what to do now. Oikawa watches as Kuroo claps his hands together and squats down and it hits him all at once; this is the first time he’s ever seen Kuroo’s gift in any capacity. Satisfied with the warm feeling on his skin, Tetsuro releases his hands and places them on the iron below, the space surrounding them glowing like they do.
In an instance, the vibrancy dies down and on the landing lies two items in a similar shape to hand grenades. A smirk tugs at his features and he states, “We’ll get in with these.”
Their jaws drop and Tooru starts to huff in disbelief, “I can appreciate your tenacity Kuroo-san but that seems like overkill.”
“Seriously…” Iwa adds sarcastically, slightly sticking out his arm to act as a shield between the two.
The smile disappears quickly and Kuroo brings a hand up to rub his brows. “They’re smoke grenades…”
Forming an ‘o’ with his mouth, Tooru starts to nod his head and Hajime drops the raised arm. “I knew that.”
Licking his lips, Kuroo passes one of the grenades to Iwaizumi and mouths “of course you did” to silently mock them. At least they share a brain cell.
Another few minutes pass, the gang of men make their way back down the ladder and into the frey. During that time you remain using the same tactic, effectively avoiding any unwanted attention from the growing crowd of henchmen. More had been called in after your initial shot, the head honcho making plays over the various walkie talkies. 
You close a portal and let your chest heave, taking long deep breaths and settling down. The spacing of your shots has been growing larger to keep the suspense up, but in this timeframe you create a mini portal to grab a new magazine and reload. You close your eyes and let the noise wrap you like a blanket, surrounding you and taking precedence over every other sense in your body. Right as you whip to the right and start to open a rift, the small tinks of metal on concrete are drowned out.
Slowly, smoke swirls around the dance floor, rising and expanding out in all directions. Another can sputter to life and causes the room to turn opaque. Light bounces around in rays that color the white sheet that now fills the room.
Right outside the doors of the club Iwaizumi charges up his ability, letting a firm feeling prick every inch of his skin before ramming himself through the doors. Tooru sticks to his back and fires at every shape he can make out through the fog, Kuroo acting as the kaboose and covering any stragglers that those two seem to miss.
From your end of things, the room starts to fill with white and immediately you shut the gateway, watching from your perch as the fog dissipates right as it reaches your feet. Terushima also evaluates the situation, deciding to take the chance and barge out of the doors and tackle whoever is closest. Unfortunately he didn’t think super far ahead and that leaves you in a compromising position.
Gunfire fills the hallways of the building, but the light that flashes up on the second level lets Kuroo know that shit’s going down. Without hesitation he leaves formation and hauls ass down the hall and up some stairs. Four men in total block his path to you, two being on the floor and the other two shooting in your general direction.  
It’s as if red seeps into his eyelids, rage pumps through his veins at a level he thought himself incapable. The barrel of his gun points down at the thigh of one of the standing men. As soon as the bullet hits its mark he rushes the other one and knocks him upside the head with the butt of the gun. In less than three minutes Kuroo had entered the building and knocked out two guys in order to rush to your side.
A wedge was pushed in the cogs in your brain, halting all functions and making your eye twitch. Kuroo squats down to meet your eye level and stares at you with piercing golden eyes. His pupils dilate when they meet yours which are full of confusion, then disbelief and finally annoyance.
“You fuckin’ asshole.” The words should be lost to the mirage of the night, but they’re the only things Kuroo can hear.
Almost scared, he reaches forward and curls his fingers around the flesh of your forearm and responds. “Let’s get out of here.”
Whatever shock that stopped your brain had washed over and now it felt like everything was moving too quickly in order to catch up. The fog was starting to clear and you can make out the figures of both Oikawa and Iwaizumi down on the dance floor below, watching each other's backs. Terushima stands near the edge of the balcony and joins them in taking down what seems to be an endless stream of goons.
He turns to you and winks, a silent goodbye as Kuroo grabs a tight hold of your arm and pulls you off of the ground. It’s a blur as you leap over several unconscious men and down the stairs. Whatever crowd was left was thin at best, no civilians in sight and many mafia members toppled over. Iwaizumi steps backwards towards you two, Oikawa shifting himself so the three act as armor around you.
Just as swift as the entrance, the boys shove you along and out into the streets. The screeching of tires alerts the four of you, yet another SUV speeds down the narrow streets of the downtown.
“Fuck” you whisper and get your bearings. Your legs are quicker than your brain and you shout, “follow me!” Your two fellow ex-members are already by your sides and Kuroo lags behind. Quickly you throw the keys to Iwaizumi. “When we get to the car, just drive. Doesn’t matter what streets you go down.”
Yet again Kuroo watches as the three of you work together like a well oiled machine, Hajime practically ripping the door off of its hinges and shaking the car as he sits. Tooru follows suit on the passenger side and deja vu strikes hard once Kuroo gets his but down into the seat.
Iwaizumi revs the engine and rapidly turns the wheel from side to side as the car skids and jolts into the center of a major road.
“Whatever happens, just keep her in the center of the road!” You whirl around and face the rear windshield, spotting the vehicles that now tail you all. Luckily the night means less traffic and Hajime can keep to the center of the road. Whoever was driving this late at night veers out of the way as the street turns crowded with several cars turning corners rather fast and joining in with those that already follow you.
You roll down the window next to you and start to shoot blindly out of the side, not daring to stick your whole body out of the car like last time due to the sheer amount of firepower that would be sure to hit you. Kuroo and Oikawa do the same as you, Kuroo ducking his head while doing so just in case any bullets come flying in through the back window and Oikawa tries to use the side mirror to aim his shots. 
Not even two minutes since this drive began and cop cars light up the road ahead, about three quarters of a mile in front.
“Uhh Y/N! We got a problem!” Iwaizumi white knuckles the steering wheel and starts to turn it, planning on going down one of the side streets to put all threats behind your car. You whip your head around and evaluate the situation, quickly realizing that this is an opportune moment for something you’ve been keeping up your sleeve.
“You better keep this car in the center of the road Hajime or so help me God I will kill you before anyone else has the chance!” You scream and place yourself in the center of the back bench which gives you a relatively clear view of the road. Breathing in through your nose and out with your mouth, you clap your hands together much like Kuroo did earlier in the night. Continuing your breathing pattern, Hajime returns the car to the center of the road.
“Step on the gas.” You command, your eyes closed in concentration.
“Y/N are you sure?!” There wasn’t a hint of doubt in Iwaizumi’s questioning, but more of a confirmation of action.
“Just fucking do it!”
The clock ticks down as both forces start to close in. Five seconds before impact: the cops are unsure what to do. Some stopped their vehicles and were preparing road spikes while the others continue charging forward and speak through the sound system, warning you all of what’s going to happen. The Port Mafia also starts to slow down as they are just as confused as the police. No one really knows what you have in plan, but those in charge of each group are determined to get to the bottom of things.
Four seconds to go and the pit at everyone’s stomach grows a size larger; a faint sapphire glow emanates just from your hands and Kuroo watches curiously. The phrase trusting someone with your life had never meant much to him, but in this moment he really understood the complete lack of control he has.
Three; Oikawa sits up right in his seat and straps himself in, also closing his eyes to alleviate the stress of the scene before him.
Two; the glow around your fingertips has grown exponentially into something almost blinding. Iwaizumi steadies the wheel and fights the urge to jerk the car.
Right before impact with the front runner the view of a country road lined with trees fills Hajime and Kuroo’s eyes. The car barely fits into the rift and bounces up and down. You weren’t able to align the two roads perfectly off of memory, so you opted to have it a little high up. Kuroo checks behind them and the road is empty. No sight of any buildings or vehicles - just a clear sky and the wilderness that surrounds them.
Tooru didn’t realize he was clutching onto his chest strap until he opens his eyes and lets out a breath he was holding. Hajime adjusts quickly to the new territory and slows the car down some, leaning back into his seat. Kuroo, amazed that you were in the clear, turns to you, but your head is lolled to the side. 
“Y/N?” Ever so gently, he shakes your shoulder and your eyes crack open. You turn to face him and blood is streaming from one nostril, down your face and dripping onto your shirt. He freezes up, just now realizing how much this whole ordeal must’ve taken out of you.
A tissue appears in front of both of your faces, Tooru’s hand attached to it. “You always pull that stuff off last second even though you could’ve just done it as soon as we got in the car.”
“Fuck off,” you sound drained and totally devoid of any emotion. “If we can get out of it without having to port out then we’ll do it that way, but the cops got in the way.” You take the tissue and start to wipe up whatever you can, your movements slow.
“Are you alright?” Kuroo is unsure of his place, a total contrast from inside the club when he was the most assertive you had ever seen him.
“Loaded question.” You want so badly to drop them off on the side of the road and hope that they just leave you alone, but your eyes blur every few seconds and you know that you are in no position to drive. Several emotions bubble up at the thought that they kept looking for you, put their lives on the line to find you and actually ended up saving you.
Effectively dodging the question, you slide back over to your side of the car and place your head on the window, giving Hajime directions to your home. They’re smart enough to know that now isn’t the time to talk, nor is it the time to ask questions like “what’s next?” and so on.
The high beams of your car light up the large house at the end of the gravel road, your headache nearing its end and the boys all ogle at your property. A flick of his hands and Iwaizumi turns the car off, then steps out into the cold air. He takes a few steps back and precariously opens the door you’re leaning on. With careful consideration, he crouches down and tries to let you use him as a crutch, but in all the time you had to think on the ride here, you shove him off and stumble a bit.
Gaining some balance, you speak with an unwavering tone. “What you did tonight was stupid. All of you.” You turn and meet each of their eyes, Kuroo and Oikawa still on the other side of the car. “I explicitly told you all not to get involved and still you fucking showed up.”
They all freeze at the accusatory finger you’re pointing and watch as you start to back yourself up to the entryway. Iwaizumi, who normally decides to let Tooru charm his way out of things, is the first to speak. “You’re right.” His eyes bore into your own, but he continues. “But that doesn’t change the fact that if we weren’t there you would’ve been fucked.”
“As if.” You spit back, not thinking clearly as you’re more focused on getting your own point across. Hajime only started fights when he thought it was absolutely necessary. This didn’t cross your mind, but Tooru’s as he realizes the upcoming screaming match. 
“As if?!” His voice booms over the forest, possibly shaking the leaves on the trees. “You were backed into a fucking corner Y/N! For god's sake, did you think Terushima was gonna be able to help you out of that shitshow?” He stops his assault for a moment, seeing if you would answer but you grind your teeth instead. “You needed our help. We’re the ones that got you out of that situation-”
“Hajime-”
“No Tooru! She doesn’t get to disappear behind everyone’s backs and tell us NOT to find her! Especially not us.” Tooru purses his lips, knowing that he’s right. Tooru would’ve thought that maybe after the first day or two you would contact them, allowing them to help, all things considered. He knows where Hajime is coming from and ultimately decides to let him continue. “She sure as fuck doesn’t get to tell us that we didn’t help either. I know damn well that once we all cool off you’re gonna have to apologize and admit to me that I was right.”
“That still doesn’t change the fact that you still decided to follow me.”  You're quick with your rebuttal. “I’m trying my best to protect you all-” A cackle catches you mid sentence, and you watch as Iwaizumi rests a hand over his face and laughs, shoulders shaking. “What? What’s so hilarious Hajime?”
“Do you really think that we need protecting?” His eyes peek through the cracks in his fingers, a sly smirk curling his lips.
“Maybe you don’t but the Port Mafia knows now that I’m involved with the agency. For the safety and protection of everyone I need to erase myself from their records and go away.” This is your retreat. You can feel your own arms wrap around your form and start rubbing slow circles into your sides. The more you think about it, the more you realize that you’re just pleading for them to live. Or pleading with them to leave you with the idea that they’ll be living a peaceful life without you.
“You do know who you’re talking about, right?” Iwaizumi takes his hand off of his face and glares at you. “You got Bokuto, who is an accidental genius; Sugawara and myself who act like human shields; Tanaka and Nishinoya who are the wildcards; Kenma and Asahi who can heal practically any injury and Kuroo, who can literally create a bomb if he has the right materials within his vicinity.” As he lists off the various members he sticks fingers up and counts. “I don’t think they need as much protection as you seem to think. I bet everyone’s losing their shit right now since you just walked out and now the three of us have been M.I.A. for almost a week.”
While he presents a pretty good argument, it feels like it just goes in one ear and out the other. Your only goal right now is to get them to understand that you don’t want them here. Anything you can do to save them is the top priority, and having them here with you is a fucking nuisance. “I don’t give a rat's ass about any of that! You and Torru have seen what the Port Mafia is capable of and there’s is nothing that is going to stop them from finding me! If that means blowing up the agency building, they will! You know Tendou will do anything and Washijo will just let him!”
“Y/N.” The desperation in your voice is becoming more apparent with each word as your sentences speed up and your tone gets higher and higher. Oikawa walks around the car and stands next to Hajime, taking your beat of silence as a cue to speak. “You know you can’t say that anymore. We haven’t been with them for years. Washijo might be too sick to even speak.”
“Plus everyone at the agency knows what this job entails.”
“You don’t get to talk Tetsuro.” He stands behind the two, and honestly your rage was so hyper focused on Oikawa and Iwaizumi that you forgot he was there. You snap at spit back. “It’s not a matter of knowing what they signed up for more than a problem of the Port Mafia doing whatever they want.”
“That’s why we’re here to help you.” Tooru still stands between you and the others, the mediator. “You know that we’ll do everything we can, everything you say, in order to protect them. Tendou didn’t just see you that night. Obviously he doesn’t care all that much about us but we’re on their records too so it’s not just your problem.”
“I can’t fucking do this right now.” It feels like no one is listening to you, just throwing water in the tank you’re already drowning in. With a sigh and balled fists, you come to a hasty decision. “You can all stay here tonight. I expect you to be gone by midday.” Without a chance to speak, you storm into the house and start preparing mats for them to sleep on.
Tooru runs his tongue over his teeth, lips shut and starts tapping his foot. There were a thousand different possibilities for how tonight could’ve gone - this being one that wasn’t on his radar. Hajime feels the frustration bubble over, but he knows there’s not much else he can say that will get to you. Focusing his attention on Tooru, he pats his shoulder and says, “She’s not gonna budge. C’mon.” The two walk into the house, following the lights and let you finish preparing their room.
Swiftly you finish fluffing the pillows and brushing past them, avoiding any contact, any chance for them to stop you. You slide open the door for the next room over and raid the closet, setting the room up for Kuroo.
“Y/N wait.” For one reason or another, you stop your actions and look to the aforementioned, him standing in the doorway. With a final push of your muscles, you throw the mat down on the floor and wait for what’s next. “I just wanted to say that- that I want to do everything I can to help you. I know it’s not much but Iwaizumi and Oikawa have been doing so much and I really think that-”
“Go to bed Kuroo. You guys are gonna have a long day making your way back into the city tomorrow, so you’re gonna need all the sleep you can get.” You shoulder check him, leaving the room and the yet to be unfurled bed mat on the floor.
In the late hours of the night you find yourself tossing and turning. The entirety of the past few hours replayed in your mind, every situation rewinds and restarts as you analyze the points that the guys made. You wouldn’t have lived through last night if it wasn’t for them. There’s no way in hell Tendou wouldn’t have gotten his hands on you if it wasn't for them.
You sit up, sweat dripping off of your brow bone and everything starts to feel like it’s closing in. The four walls around you feel like hands around your throat and your chest heaves. Throwing off the duvet you stand up and stretch, the small pops and clicks from your back. After a few moments you slide open the door and step into the hallway, heading to the kitchen to start a kettle.
Maybe you were being a little harsh on them earlier. Tendou was a real threat and only sought you out, but that doesn’t take away from the fact that whoever that boy was with him a few nights ago seemed to recognize you, Oikawa and Iwaizumi. They were there with you through thick and thin when you had to organize almost half of the mafia’s patrol cars, pickup sites and so much more. You went above and beyond to prove to that old fucking geezer that you deserved to be in your seat as an executive. Tooru and Hajime did nothing but support you, even after they discovered that you did in fact fake your death and worked as a detective in the same city they thought you abandoned. Even after that they still treated you like nothing happened.
The kettle whistles and you take it off the heat, trying your best to stay as quiet as possible in the early morning hours. Preparing a tea strainer and some leaves, you grab a mug and start to assemble everything. As the tea steeps, you open the back door and let the cool breeze engulf your body. 
The wood that covers the porch is cool to the touch, the soles of your feet uncomfortable, wanting to go back inside but you continue forward. The only things warming you under the cascade of stars is the mug between your hands and a blanket you placed around your shoulders. You venture off of the porch onto the soft moss that tickles your toes. Further into the trees is a small creek, in which you placed a few hardwood chairs.
No distractions, you allowed yourself to continue your train of thought from earlier. Once it fully settles in your consciousness that they are in their own right to want to be a part of this battle. Just as much was on the line for them as it was for you, and it never really hit until now. 
So what would happen if I let them stay?
This was the real kicker. And before you knew it, you were going through every possible scenario you could think of, listing the pros and cons of having a team to work with rather than only relying on yourself. 
The moon shifts throughout the night sky as you get up a few times to refill your cup, and before you know it rays of sunshine start to peer through the fog that settles under the canopy of leaves. With a new piping cup in your hands you resume the various tracks of different decisions. Inside, Kuroo slowly cracks open his eyes, the sunshine peeking through the blinds and the birds chirping. In the other room Iwaizumi sighs heavily and looks over Tooru. Shadows define his jaw and cheekbones, even accentuating the curve of his lips and the flutter of his lashes when he finally opens his eyes.
“G’morning.” Hajime’s voice is scratchy, his eyes red from the haziness that comes in the morning.
“Morning.” With a smile, they both take their time getting up and ready for the day. 
Kuroo straightens out his clothes (which he slept in) and walks out into the living room. He notes the kettle and jars of loose tea leaves on the counter, also noting that you’re nowhere to be seen. The door to your room is open as well, arousing his suspicion.
A glance passes between the two men as they each put back into their clothes. First it was Hajime trying to catch a glance at Tooru, and then vice versa just a few seconds later. They stumble around one another, pick dusting their cheeks but neither speaks.
A knock at the door interrupts their game of cat and mouse along with a voice. “Have you guys seen Y/N?”
Hajime finishes the buttons of his shirt and slides the door open. “No? She’s not here?” It’s like last night all over again, the panic bubbling in his chest.
“I haven’t seen her at all, and her room’s empty. I think she’s around since the car is still here and there’s stuff on the counter, I was just wondering if you guys heard or saw her?” Kuroo fidgets with his fingers, picking at the cuticles with his nail.
“You checked all the rooms?” Hajime takes command of the situation, stepping out of his room and into the living space.
“Yeah, all empty.” Kuroo follows him and Oikawa behind Kuroo.
“Well the back door is open, so…” Tooru nods towards the door although no one sees it.
Without another word the trio walk into the forest, taking in the scenery before them. Calm was the one word that came to mind. Branches crunch under their heels, alarming you to their presence. 
They can see your figure up just ahead and slow their roll. Kuroo stops in his tracks and just looks at you bathing in the golden sunlight, hair disheveled and eyes baggy once you finally turn and face them.
“Morning boys.” You sound and look tired, each of them knowing that you probably didn’t get any sleep at all but continue down the path to meet you. With a single gesture you get them to sit in the chairs beside you. You say nothing as you drink the cold tea - or what’s left of it at this point.
“What’s going on up there Y/N?” Oikawa pokes his temple and looks at you with the most sincere eyes. It’s not like the question wasn’t just on his mind, but the silence was starting to kill him.
“I did a lot of reflecting last night,” you start, setting the small cup onto the moss and straightening up. “For starters, I hope you all can forgive me for the way I treated you last night. It was unfair and I finally get that we’re all fighting for the same thing. You all have just as much reason to fight the Port Mafia as I do.” You make eye contact with each of them individually as you try to convey remorse. 
They each take it the same, knowing that adrenaline was high and that you meant the best for all of them. If anything, Hajime knows that the both of you will need to have a one on one conversation later to clear the air. 
“As for what I said last night,” you turn your eyes downward, knowing that you can’t bear to stare at their eager eyes, “I thought about it, and I want to take it all back. If you want, I could use the extra hands.”
Silence settles again, but Tooru doesn’t let it last long. He stands up from his chair and rushes over to give you a big hug. His arms encase you and he puts his head close to your shoulder. “Thank you.”
It catches you off guard, but tears build in your eyes. What did you ever do to deserve them? “Of course. I knew you guys weren’t gonna leave me alone once you knew where I've been hiding.”
“Damn straight.” Hajime joins the hug, placing his head on your other shoulder.
Kuroo stays in his seat and watches the scene unfold, not wanting to ruin a second reunion. He goes back to fiddling with his fingers and looking at the ground until the three of you break off from one another. You walk over to him and place a hand over his, preventing him from doing any more damage to his hands. Maneuvering them in a way to grasp one of his hands, he looks up at you, the rays of sunshine behind you, filling the forest.
Holding onto his rough hand and smiling down on him, you say “Let’s get to work.”
16 notes · View notes
jaxsteamblog · 5 years ago
Text
Betrayal
Click here to read the full fic on AO3
They worked together every night of the week. Zuko always brought food and the three of them chatted together as they worked. At a certain point, they had to stop and seriously discuss transportation. This resulted in Zuko and Sokka taking measurements inside of the van but arguing about what the dimensions meant.
Katara laughed and sat back, watching them.
When it was all done and staged, the backroom looked like a construction zone. Foam blocks and partially built wooden structures covered almost every available surface. The refrigerators were stuffed with flowers. Leaves were stuck to everything.
“Tomorrow we’ll be closed, by the way.” Sokka said as he came out of the workroom with three bottles of iced tea. They sat in the alley, still damp from their cold and waterlogged activity. Zuko had pilfered the milk crates from a restaurant a few doors down and Katara didn’t even care about the hard plastic digging into her backside.
“Do we get to stay for the party?” Katara asked.
“I usually hang around and snag something from the catering.” Sokka said and drank his tea.
“As long as you guys have a nice outfit to change into, I think you could even manage to be with the other guests.” Zuko said.
“I don’t think it’s a good idea.” Sokka said.
“Why not?” Katara asked.
“Don’t worry, he’s not coming anymore. Something came up.” Zuko replied.
“Who’s not going to be there?” Katara questioned.
“My father.” Zuko said and chugged most of his tea. After letting out a small gasp, he smiled at her. “He usually does that. He’ll say he’ll be somewhere to stress people out and then cancel last minute.”
“Full offense, your dad sounds like a jerk.” Katara said. Zuko gave a short laugh and Sokka snorted.
“They’re all jerks. Jerkbenders, every single one of ��em.” He said.
“So how nice of an outfit are we talking here?” Katara asked.
The next day Zuko didn’t show up to help. While she understood, Katara still felt a little disappointed; she had wanted his opinion on her dress before they left. Still, Sokka’s girlfriend Suki showed up to assist and gave her seal of approval. Because Katara was driving separately, she took everyone’s garment bags, laying them out on her back seat as gently as Sokka did his flowers.
When they got to the Jasmine Dragon, Zuko was still nowhere to be found.The party planner - a very severe woman in a well-tailored tux - showed them where to put the flowers. And while she herself didn’t help, she certainly allocated enough hired hands to do so. Again, Katara was tasked with filling the vases and making sure water didn’t spill. It created a little cognitive dissonance in her, knowing that in a few short weeks she’d be learning how to use her bending to save people’s lives. But for now, she was cleaning up spills.
Once everything was set up, they all stood for a moment in quiet awe. The tablecloths were a deep blue and with the predominance of white in the flower arrangements, the snowfall effect played out over individual seas. Crystal glasses glinted under the light and the pristine dishes  were smooth tundras. Katara shivered in spite of herself.
“Awesome. Now let’s get changed.” Sokka said.
Katara gathered the bags from her car and went with Suki to the restroom. She had expected tight quarters, even with the teahouse’s obviously elite interior. But the restroom was nothing like the front of the business. There were only a few stalls, yes, but it was portioned off into two rooms; the first had a couch on one side and a vanity on the other.
“For all the fixtures, this is actually an old school style.” Suki said as she saw Katara take it all in. “This is why they were called restrooms afterall.”
The stalls were spacious and each one equipped for a number of mobility needs. But it was still a toilet stall, so Katara stood on her shoes as she changed out of her clothes.
The dress was from her Gran-Gran’s wedding; it had been a stroke of luck that Zuko’s party was basically Water Tribe themed. The skirt of her dress was almost the same shade of blue as the tablecloths and the bodice was white lace. It had been impossible to zip up at the wedding and Katara flailed about just as uselessly this time.
“Need a hand?” Suki asked from the next stall.
“Yeah, let me just get my shoes on.” Katara said.
The restroom door opened and Katara heard two women enter, talking.
“So what?” One woman, sounding bored, asked.
“So,” The other said, sounding irritated. “I just don’t know why he always does that.”
“They’re friends.” The first woman said.
“And we’re always so happy to see you.” Suki called out. Katara gathered up her things and opened the stall door.
“Oh great, he invited more commoners.” The first woman remarked.
Suki came out of her stall and went to the sinks, placing her clothes down.
“Nice to see you too Azula. Mai.” Suki said and went back to Katara. “Hey, hold your hair up.”
Katara held her clothes in one arm and lifted up her hair. She briefly examined the two new women, put off by the hostility. One of them looked a little like Zuko, mostly in the eyes, and she assumed this was his sister Azula. The other was a tall woman with long straight hair. Maybe Mai.
“I’m Katara.” Katara interjected as Suki zipped up her dress.
“I don’t think I care.” Probably Azula said.
“That’s prissy princess Azula and the other one is Mai.” Suki said. “Now do me.”
Katara turned around and zipped up Suki’s gown. It was an evergreen color, simply cut but it looked very stylish.
“That’s a great dress.” Katara said.
“Thanks. Zuko and Sokka go out a lot when he’s in town, so I had to get some adequate attire.” Suki said with faux-bitterness. She turned and flashed Katara a quick smile.
“Great, can you get out now? Your bargain bin dresses are giving me a headache.” Azula said and pushed between the two of them. Suki rolled her eyes but started walking out.
“I can’t believe they’re related.” Katara said as they exited. Guests had started to show up and now a few people eyed them awkwardly.
“Come on.” Suki whispered and headed to the side exit where Katara’s car was parked. They walked out and found Sokka standing next to the open passenger door, talking to Zuko. Both of them were in tuxes and looked pretty comfortable in them.
Katara tried to remember when Sokka had gotten used to wearing a suit. Clearly it had only happened after he met Zuko.
“Well don’t you boys clean up nice.” Suki said, her Kyoshi accent slipping out purposefully. Sokka kissed her cheek and took her clothes, tossing them unceremoniously into the backseat.
“I’d compliment you but you always look radiant.” Sokka told her. Zuko smiled and looked at Katara.
“That dress is beautiful.” He said. Katara glanced down and put her hands on the bottom half of her bodice.
“Thanks. I got it for my grandmother’s wedding.” She replied.
“Hey, so people have shown up and your sister is here.” Suki said, linking her arm through Sokka’s and leaning on him.
“Well we certainly don’t need her holding court right now.” Zuko grumbled. “Alright, I guess it’s time for me to go in.”
Sokka shut the door of the car and they all walked back in.
It only took a few moments for people to notice but once they did, they swarmed around Zuko. Clearly he was well known, and it obviously wasn’t for his uncle’s teashop. But whatever was going on back in the Fire Nation, he didn’t talk about it and Katara always felt weird when she was about to search him up online. Anything she found she knew wouldn’t be congruent with the man she had spent every night this week working on flower displays. It was bad enough to see him like this, dressed so formally and chatting up equally lavish looking people when just last night he had been covered in tiny statice flowers.
“So what’s supposed to happen?” Katara asked.
“Well, there will probably be a tea demonstration. I wouldn’t be surprised if Azula did it. And then lunch, where a ton of people will drink too much and make speeches. Then someone will push the tables out of the way and dancing will start, regardless of what time it is.” Sokka answered.
“That seems like a lot.” Katara replied.
“Is it really any different than what the rest of us do?” Suki asked.
“But everything is so nice.” Katara countered.
“That doesn’t mean anything to these people. Just wait till you see how much they rack up in damages.” Sokka said.
After about thirty minutes of greeting, an older man stepped onto a raised stage. He tapped the microphone to get everyone’s attention and Zuko took the opportunity to weave through the crowd back to them.
“Hey.” He whispered and squeezed Katara’s shoulder as he stepped behind her. Blushing, she became acutely aware of his presence behind her right shoulder as he stood next to Sokka.
“Thank you everyone for coming out to celebrate my nephew’s birthday. It is an honor to be surrounded by so many friends, and by such delicious tea!” The man said and the audience laughed politely. “Because the two greatest joys in my old age are tea and my niece and nephew, I am delighted to invite out my niece Azula to perform a traditional tea ceremony.”
The audience applauded and Zuko scoffed. Everyone started to shuffle around, taking a seat as Azula and a few others brought cases and equipment to the stage. Azula had changed into a traditional kimono and she looked serene. It was a shocking change from their interaction in the restroom.
The ceremony was artfully done and Zuko went forward to receive the cup his sister had prepared. More tea was made and people started to socialize. Other performers came to the stage to play instruments and servers brought out small dishes, all which became background noise.
Zuko kept having to get up and circulate amongst the guests, but ultimately returned to their table to eat a few appetizers and drink some tea. By the time lunch was served, Katara was already full. But this time, the alcohol was poured and the room started to grow warmer and louder.
Stopping back at their table, Katara handed him a cold glass of water, which he took gratefully.
“All the old guys are eyeing the microphone.” Suki said, leaning across the table toward Zuko.
“Probably trying to figure out how to suck up to my father while telling me off.” He replied, glancing over at the stage.
“Well that just means someone has to get up there first to set the tone.” Sokka said and stood.
“Sokka, do not tell them-” Zuko started but Sokka cut him off.
“I will confess my love to you as many times as it takes Zuko.” He said. Zuko put his face in his hands and groaned while Katara patted his back.
The microphone whined as Sokka twisted it and most of the audience watched him.
“Good afternoon everyone. My name is Sokka and some of you know me as That Native Boy Who Sells Flowers. Anyway, I just wanted to be the first to say, Zuko, you are the most handsome Fire Nation guy I’ve ever met and I hope you never change. Happy birthday you magnificent sunbeam you.” Sokka said and raised his beer glass. A few voices, most likely belonging to the younger members of the crowd, cheered as Sokka took a drink.
As Sokka made it to the table, Zuko was rubbing his chin and shaking his head. Sokka just slapped his back and sat down.
“Do you like getting me in trouble?” Zuko asked, gesturing with his hand in the empty air.
“What’s the worst that can happen? You get another scar?” Sokka said and then made a dismissive sound. “You’ll be fine champ.”
There was a tapping on the microphone and they looked over again. Mai stood there, holding her champagne glass and leaning over the microphone gracefully.
“Thank you Sokka, I’m always glad to know my boyfriend is in such safe hands when he’s away from home.” Mai began. Katara felt her stomach sink and she sat up in her chair. Boyfriend?
“Zuko, you know I’m not one for grand speeches. But I’m here, which is saying something. Happy birthday.” Mai continued and raised her glass. “To the Fire Lord.”
The entire audience and Zuko raised their glasses and replied, in near perfect unison, “To the Fire Lord.”
Zuko looked uneasy and didn’t turn as he took a drink. Good thing, as Katara’s hands had turned to lead and she hadn’t been able to move them.
1 2 3 4 5 6
55 notes · View notes
campweehawken · 6 years ago
Text
Hello Campers! This is the official signup post for Weehawken 2019!
We are just going to cut right to the chase and open the doors up for another exciting year of camp Weehawken!
As with other year there are a handful of new additions to the AU which I will briefly describe in this post.
Returning features-
DISCORD SERVER: Like the year before, the Discord server will now be hosting the campfire groupchats which used to take place on Tinychat. Tinychat unfortunately stopped working for a lot of people who tried to access it so it will no longer be used.
The Discord Server is going to be in use again this year for Campfire group RP and general discussion of the AU.
This server was set up to help participants get in touch with each other, discuss the events of weehawken in a group chat and share art and fics.
Discord is available to computer and mobile users and it’s free to sign up if you don’t already have an account. Requesting a link to the discord will be part of the weehawken signup process which I will be detailing below.
Links will be given out for the entirety of the event and won’t close until Camp Weehawken’s conclusion.
Important note: You do not need to join the Discord server to take part in Weehawken. The main posts and character interactions take place on tumblr between RP/ask blogs. However it is highly recommended that you do so if you don’t want to miss out on a single thing.
CONTINUING: If you would like you can request the exact same cabin and roles that you had the year before and continue where you left off with the same characters and the same plot threads. Some people have expressed an interest in doing this but the option to start from scratch with new or existing characters is still available.
Please contact the blog as soon as possible to re-secure your spot in the cabin!
If you have any questions about these new features, send an ask to this blog. Without further ado, here is everything you need to know about signing up.
New Features-
CALENDAR:
This year, Camp Weehawken has a calendar! It will be available to everyone, linked on this blog and updated by the moderators as new events arise. It will be used to keep track of events and streams and aid participants in organizing their own events with the help of the mods. Speaking of which, EVENT IDEAS AND SUGGESTIONS: Camp weehawken has always been constructed by the participants and this year is no different! This time around the moderators of the AU want to bring to the attention of the participants that anybody can host their own little events in camp such as movie streams and RP events and other things you can think of! We will also also be taking suggestions for bigger weeklong events that all participants will vote upon wanting to do. Things like summerween and camp dances! If your suggestion is approved it will be added to the calendar and announced and possibly polled for.
HOW TO SIGN UP:
Message this blog and give us these three details:
Desired Role: options are camper,     counselor or staff. If you would rather have some other role     like camp mascot, send a request! Campers are under the age of 18. They     tend to range from 12 - 17 years of age but you can have somewhat younger     characters. Only characters 18 years old and up can be staff or     counselors. Because this is an AU you can make your character any age     you’d like!
Blog Name: You will need to have an RP     blog to participate in Weehawken and when it’s all set up, tell us the     blog name. Tumblr might not let the message through if you type a URL.     Just give us the name of the blog, like so: ex. “campweehawken”
Preferred Cabin: (doesn’t apply to staff)     Campers and counselors reside in cabins that fit one counselor and a     maximum of 8 campers.  If you have any preference for what cabin you     want to be sorted into, let us know in your registration. If you supply no     preference you will be sorted into a random cabin.
Discord (Optional): If you would like a link to     the discord, please ask for it in your signup ask.
Take a look at the 2019 Cabin List to see where you and other campers have been sorted as well at who the staff are! Links to all participant blogs will be available there. The list is constantly updating as more submissions come in.      
If your blog has more than one character, you will be filling up more than one vacancy spot unless your characters happen to be family: cousins, twins, siblings. Then, the characters can share a bed in the cabin and fill up just one vacancy spot.
INFORMATION LINKS:
Since it’s hard for me to cover all of the topics in one little post, I’m going to give you all some resources to help you figure this event out.
-FAQ: Answers to general questions we receive. Also a     well of basic information about this event.    
-Camp Weehawken Staff Brochure:     Information about camp activities and various roles to be played at Camp.
-Camp Tags: The tags that are used on this blog and     participant’s blogs for the event.
If you can’t find an answer to your question in any of these places, just drop us an ask and we’ll respond as soon as we can.
All in all, Camp Weehawken is an open ended event! You can be as creative as you’d like. The moderators of the event are always open to suggestions for RP events, streams and more. But keep in mind that this is a public event! Please be respectful.
If you have any issues with other participants, how things are being run or any other problems, the moderators are here to help. You can send messages to this blog to request help with any topic.
Applications are officially open!!
-Camp Weehawken Directors
15 notes · View notes
minrcrafter · 7 years ago
Photo
Tumblr media
UltraCraft [SMP]{1.12.2}{Survival}{Active Staff}{Jobs}{Community Focus}{Economy}{McMMO}{Skyblock}{No Whitelist}{GriefPrevention}{Marriage}{Anti-Grief}
🔹⬥🔶⬥🔹 ──── What Makes Us, Us ────🔹⬥🔶⬥🔹
For the past 2 years, we've had ups and downs but through those ups and downs, we've still stayed true to ourselves and continued to push through to make your Minecraft experience something worth wild. We believe in doing the right thing and doing what we can to take care of our players.
🔹⬥🔶⬥🔹 ──── Basic Server Info ────🔹⬥🔶⬥🔹 Name: Ultracraft
Server Address: ultracrafttowny.mcph.co
Version: 1.12.2 (1.13 coming ASAP)
Website: Ultracraft
Store: Donation Store
Discord: Discord
Twitter: Twitter
🔹⬥🔶⬥🔹 ────Features────🔹⬥🔶⬥🔹
Servers:
Hub: A simple hub server. Not much to it but a good place to start when you join the server!
Survival: Ultracraft Survival is your basic survival server with McMMO, Jobs, the golden shovel claiming system, marriage and more! We have a separate mining, end and nether worlds which reset every 2 months and our wild world that is only used for making claims. We offer in-game ranks that can be purchased with in-game money. Our economy is player based and driven by the community.
Skyblock: It's your simple Skyblock set up. It's the Skyblock you know and love. We offer donation ranks for Skyblock and /ah to buy/sell items.
Ultrawarts: UNDER CONSTRUCTION!
Games/Events: Our Events server has just been released! July 2018 brought on a project that was a long time in the making. Our Events server works like a theme park with almost every game being fully automated. We have plans to bring in Mob Arena, Skywars, bedwars & more smaller games!
Other features:
Active Staff
In-game ranks that provide a challenge with our highest rank being 15 million. This has NOT been accomplished yet so will you take on the challenge?
Warm, family-friendly community
Dynmap on our website
Silk spawners
Spawner crate
Seasonal Events
Seasonal crates
Newly created admin shop + player shops at /warp shop.
Marriage on Survival
Resource worlds that reset every 2 months on Survival
Economy
Start a town! Meet new people! Chat with friends! Join in on a community project!
We want everyone to enjoy their time on Ultracraft. We try to promote a friendly environment free from toxic energies. Players are encouraged to voice any suggestions or concerns they may have for the community.
🔹⬥🔶⬥🔹 ────General Server Rules────🔹⬥🔶⬥🔹
Some of these rules will carry over to the website or vice versa.
+Advertising:
You may not advertise or discuss other servers, server IPs or mention other servers to players. This applies to any chat type in-game or on the website. If an IP is mentioned or discussed you risk your account being banned from the server/site.
+Cheating:
You are not allowed to use any sort of cheat or exploit to gain an advantage over other players. AFK machines are the exception. Rule of Thumb: if you're not sure if something is allowed, ASK before using. This does not include the community. Ask a staff member. Punishment on those cheating will depend on the severity of the cheating.
+Griefing (and stealing):
Destroying other players blocks without their permission is against the rules. Giving a player permissions to your plot or town is indirectly giving that player permission to break your plots (this includes setting towns and plots to public). If you have given a player permission to your plot and something is broken that is on you as you put trust in this player.
+Hacking:
Modifications to your client that give you a substantial advantage over players are not allowed, for example X-Ray modifications. The only modifications that are allowed are those of like Optifine where it helps with performance but doesn't give any advantage in-game. Minimaps are allowed as long as it's just that, a minimap. Minimaps that include mob trackers and cave finders are not allowed. Again, if you have to question whether a mod is allowed, ask a staff member before installing or using.
+Swearing:
As of February 2018, we do allow for swearing. While we were a family-friendly server before our revamp, as an owner, at 27, I've grown away from that family friendly aspect. Therefore, we do allow for swearing as long as it's not over the top or becomes inappropriate.
+Trolling:
Trolling and annoying players is not allowed. Deliberately provoking players for fun or for example, "tricking" a player into breaking the rules is not allowed. Respect will fall into this category. Treat those with respect as you would like that respect to be reciprocated.
+Spamming:
This applies to both in-game and on the website. No excessive messages should be sent within a short amount of time. Spam can include song lyrics, random formations of letters, repetition of letters or words and so forth. TPA requests will fall into this category as well.
+Respect:
Each player will show respect to other players and staff members. There will be absolutely NO toleration on bullying or disrespect to any player on the server. If you are being bullied on the server or on the site, please report (along with screenshots) the bullying to a staff member.
🔸⬥🔷⬥🔸────Current Staff────🔸⬥🔷⬥🔸
Staff work tirelessly to give you the best Minecraft experience possible! We are always willing to take on new staff members of upon joining the server, spending time getting to know the community, don't hesitate to apply!
Owner Head Admin Admins Moderators Helpers gamergirlxo Redbear47 Meepdoodles adude1134 Cosmopilot Kayepur Prisilalee IEatCrayons03 ScorpianGirl13 (Mod+) HaiColin (Skyblock) Tucker_Games98
1 note · View note
heroes-hq-blog1 · 6 years ago
Photo
Tumblr media
THE BINARY IS OFFICIALLY READY TO JOIN THE ACADEMY!
› HAN YEOL › 20 YEARS OLD › DATE MANIPULATION › 7 YEARS IN THE ACADEMY
POWER
data manipulation - yeol can create, shape and manipulate data/digital information from systems and networks, convert himself or objects into data and vice versa.
STRENGTHS
data embodiment: yeol’s physical body can become data, allowing his consciousness to enter and move through the digital world.
data modification: yeol can change or delete information stored on digital networks (hard and software).
numerical precision: yeol can always accurately calculate things without using mathematical techniques, but with pure intuition. he has an intuitive understanding of all forms of math, and perceives reality as a numerical construct.
data transfer: yeol can make physical objects become data, and make physical objects out of data.
WEAKNESSES
must be physically touching a digital device in order to enter its system.
ability to move around the digital world depends on the device’s status (if he’s in a phone and the phone loses battery, he’ll be stuck there).
any injuries sustained in the digital world carry over to the physical world - if he dies in the digital world, he’s dead in the real world.
cannot recover information or alter encrypted information without first utilizing traditional hacking methods or entering the digital world and doing it by hand.
must be physically touching the device or a device connected to the network whose data he is altering. 
has an extremely hard time understanding and using traditional mathematical concepts - he cannot explain or prove how he solved the calculation.
since he basically views the world on a binary level, it can take him a long time to understand things that have no mathematical bearing, like philosophy or why fake news is fake news. (his understanding could be improved with considerable effort, but they have not yet reached the level you might expect for a 20 year old.)
the objects he puts in or takes out of the digital world depend on the place he’s putting it/taking it from - a device with insufficient storage cannot hold a large item, and extracting a large digital object requires a proportional amount of electricity.
he must accompany the object he is putting into the digital world/have a pre-existing program to contain it, or it will likely act as an error in the code of wherever he’s putting it.
ORIGINS
0. the world moves fast in 8704, but life in the han household moves so quickly you’d think they had superpowers. just five years ago they welcomed their first child, yeol, into the world and already he’s growing into a child that can walk and smile and - he’s a little late on talking, that’s okay, but he’s the most punctual five year old they’ve ever seen! it’s seven pm on a tuesday night, and both of yeol’s parents are still at work, tied to desk jobs that never leave them off-call. but this is normal. the sitter’s taking a juul break and she’s left yeol in front of the widescreen, one of his favorite shows playing. (it’s in effort to get him to speak, to say more than ‘umma’, 'appa’, or the number of bananas left on the kitchen table.) yeol reaches forward, his child mind just aching to reach out and touch his favorite character.
so he does. 1. it starts off as a missing child case, then it turns in to accusations of abduction, until a year later with no sign of yeol and no evidence against the sitter, han yeol’s mysterious disappearance goes cold. no one knows where he is, or where he could have gone. it’s an international favorite for conspiracy theorists in the late 00’s.
but the thing is - even though yeol’s been missing for seven years, he’s not dead. he’s very much alive, as alive as the networks that have been powering the world for centuries. it’s a messy, ugly, lonely place for a child to grow up, but it happens anyway, yeol stuck in the confusing, twisted-up tubes of the internet. he runs into everything, from self-care posts to obscure fetish porn to wikipedia articles to well-hidden chat servers. it’s a jungle, really, and yeol is mowgli in the year 8711. it’s then that he sees the biggest window ever. he’s seen the windows before - that’s what he calls them, anyway, these rectangles of bright white light. sometimes they’re dirty, fuzzy, with particles floating across them. he has the vaguest memory of looking behind himself, when he first floated into the jungle, and seeing a white square just like this one. but the window in front of him - it’s massive, and shines with such a clarity he can’t help but feel drawn to it. he steps back into the physical world for the first time in seven years out of stark tower’s newest monitor. 2. immediately, the academy takes him under their wing. it’s not the strangest case they’ve ever seen - a pale, wide-eyed twelve year old stumbling right through the newest iteration of plasma screening - but it’s somewhere up there. there’s a lot of things he’s missing. in fact, he’s missing just about everything, except for a full name and the apparent ability to move in and out of the digital world. “yeol,” he says, pointing to himself. “how old are you?” they ask him. he holds up 12 fingers, then pauses. “four months…” he trails off, shy. “seventeen days, two hours, thiry-eight minutes and- four, five, six! seven!” they cut him off after that. they don’t tell his parents he’s alive immediately, but they do get him started in the academy. basic things, like how to use a pair of chopsticks and what normal, physical life is like. it takes a lot longer than anyone expects. 3. it makes sense for him to continue to attend the academy. he starts off going home and back again, but his parents are as busy as ever, so yeol finds himself boarding and attending as a regular student at sixteen. (years, seven months, and-!) controlling his power takes work, especially since his presence in the network is virtually undetectable. it’s near-impossible to explain what the jungle looks like - how it’s white and dark and clean and messy all at once, sharp and soft and square and round, how it terrifies and excites him simultaneously. but they’re working on it. they work on it. it gets better. somehow, the physical world doesn’t quite feel like home the same way the jungle does (not yet, anyway) but it’s going to get better. yeol is sure of it. really, the only thing holding him back now is passing literature - he’s on retake number four and things still aren’t looking so hot.
0 notes
mdesemiconductor-blog · 6 years ago
Text
Metal Oxide Varistors  - TVs Diodes
TVs Diodes are available in many shapes and dimensions. High-current TVs diodes are usually mounted onto a heat-sink apparatus to decrease their temperature. It's likely to put diodes in parallel to boost the current-carrying capability, however, the VI characteristics of the diodes have to be carefully matched to make sure that present divides evenly (even though a little resistor can be put in series with each diode to help equalize the currents). All diodes have any leakage current (present that gets when a diode is reverse-biased).
This leakage current-better referred to as the reverse present (IR)-is quite small, typically within the nano ampere selection. In case the PIV is surpassed, the diode can get zapped and might become permanently damaged. The PIV to get diodes changes from several volts to up to several thousand volts. One method for attaining an effectively high PIV would be to put diodes in series. Again, it's necessary that diodes are paired to make sure that the reverse voltage divides both (even though a little resistor placed in parallel with each diode may be used to equalize the opposite voltages).
The 2 ends of a diode are often distinguished from one another with a mark. To get glass-encapsulated diodes, the cathode is designated using a black ring, whereas black-plastic encapsulated diodes utilize a white ring if no symbols exist (as viewed with many electricity diodes), the cathode could be a bolt such as slice. This bit is inserted via a heat-sink apparatus (bit of metal with a hole) and can be fastened down with a nut. A fiber or mica washer can be used to isolate the cathode electrically in the metallic heat sink, and also particular silicone grease is put between the washer and heat sink to increase thermal conductivity.
A zener diode is a device that serves as a normal pn-junction diode in regards to forward biasing, but additionally, it has the capacity to run from the reverse-biased management every time a particular breakdown voltage (VB) is attained. Zener diodes generally have breakdown voltages in the assortment of a few volts to a couple hundred volts (although bigger effective breakdown voltages could be attained by putting zener diodes in series).
There's a significant instrument for protecting your personal computer that's frequently overlooked. You have probably figured by now that I am discussing the Surge Suppressor. The name of the darn article loathed my surprise. Before we talk about surge suppressors however, we must chat about surges.
What's a spike, and must we suppress it? I am greatly oversimplifying, but power runs through the power lines into the outlets in your house similar to water in a nozzle. The water in a nozzle goes from a place of high pressure to a region of reduced pressure. That is why it flows down the nozzle. Voltage is similar to the dimension of the amount of strain in the electrical lines. Regular electricity in North America flows in 120 volts. A surge is similar to forcing an excessive amount of water down the hose simultaneously.
Matters can happen that influence the voltage. The one which the majority of men and women consider first is that a lightning attack on or close to a power line. This may give rise to a surge of millions of people. In case of a lightning storm, then your very best option is just to unplug your computer from the power socket.
You can find several other, more ordinary things that result in power surges. Big parts of electric equipment like springs, air conditioners, and refrigerators can draw considerable amounts of electricity because they turn motors off and on. This results in the power level to spike. It may occur Again and Again during the course of this day.
The system of electric supplies, from generators via power-lines and switch-boxes and transformers and finally to the wall sockets in your house, is quite complicated, and there are many opportunities across the way for electricity surges to happen.
In case the voltage growth continues for 3 nanoseconds or longer, it's referred to as a surge. Spikes and surges can be quite harmful to your computer gear. In extreme situations, they could fry your energy cord and also begin a fire. Smaller surges can damage or ruin the fragile electronics and microprocessors on your PC. If a surge does not ruin the equipment, it may still significantly lower the life-span of their pc.
Thus far, we have discovered what a surge is and why we'd like to not have it anywhere close to our computers. That is where surge suppressors arrive in. They're also commonly referred to as surge protectors. I am not likely to enter a technical justification of just how they function. You will find an assortment of different methods utilized, but they boil down to the exact same thing: curb the excess voltage and keep it from damaging your PC. Many suppressors divert the excess power to earth; some decrease it by massaging it and allow it to out in a more controlled pace. Many have fuses or circuit breakers constructed in that reduce the link altogether if the voltage becomes too large. Most devices will utilize a blend of techniques.
There's a bewildering selection of surge protectors, with various features and costs, and degrees of reliability and efficacy. I will provide you an summary of your options, tell you exactly what to look for in a surge suppressor, and ultimately, provide you with a step-by-step checklist that will assist you speed a specific model you are thinking about.
Listed below are the main Kinds of surge protectors:
Basic Power Strip - is available for under ten bucks, has no or minimal protection against power surges.
Better Power Strip exactly the like the fundamental, but has slightly superior evaluations and possibly a couple more attributes can normally be obtained in the 15 - 30 price range. These are not just surge protectors, but frequently do exactly the identical function as surge protectors. They can also smooth out the flow of electricity, eliminating miniature spikes and sags from the flow.
An Uninterruptible Power Supply includes an integrated battery, and shields against three items:
The UPS comes in 2 flavors - the Standby UPS perceptions when there's been a power fluctuation, and immediately switches to the battery electricity. This will not occur instantly, and for the little time period prior to the switchover happens, your computer is exposed. Another type is known as a Constant UPS. The battery is continually recharged in the wall, along with your gear is continually fed with a steady stream of power in the battery. This is the easiest, most secure supply of electricity, and is often favored for servers or very important parts of gear as you may guess, a Constant UPS costs about twice as far as the Standby UPS.
A surge protector is similar to an insurance plan. You must ask yourself exactly what it is you are insuring, and just how significant it is. You then select how much insurance you require, and just how much you are prepared to spend for this. There's nobody answer, but if you understand the issue, you have got a much better chance at answering it properly.
What do you need to look for when buying a surge suppressor metal oxide varistors?
A UL listing does not guarantee quality, however when the surge suppressor does not have one, you are likely considering a piece of crap.
Indicator Light: The components in a surge suppressor may burn out or quit working and there is no way to inform. Having a sign light, so long as it's lit, you understand that the unit is in great working order.
RATINGS: Great versions will have specifications recorded on the bundle. Knowing these is the trick to choosing a fantastic surge suppressor.
Energy absorption/dissipation: just how much electricity can the apparatus absorb or dissipate prior to failing?
Warranty: Typically, the longer it's, the better. Superior qualities to search for are a life warranty or a gear replacement warranty.
0 notes
we-johnnygonzalez-blog · 7 years ago
Text
Rewriting the Beginner's Guide to SEO, Chapter 5: Technical Optimization
Posted by BritneyMuller
After a short break, we're back to share our working draft of Chapter 5 of the Beginner's Guide to SEO with you! This one was a whopper, and we're really looking forward to your input. Giving beginner SEOs a solid grasp of just what technical optimization for SEO is and why it matters — without overwhelming them or scaring them off the subject — is a tall order indeed. We'd love to hear what you think: did we miss anything you think is important for beginners to know? Leave us your feedback in the comments!
And in case you're curious, check back on our outline, Chapter One, Chapter Two, Chapter Three, and Chapter Four to see what we've covered so far.
Chapter 5: Technical Optimization
Basic technical knowledge will help you optimize your site for search engines and establish credibility with developers.
Now that you’ve crafted valuable content on the foundation of solid keyword research, it’s important to make sure it’s not only readable by humans, but by search engines too!
You don’t need to have a deep technical understanding of these concepts, but it is important to grasp what these technical assets do so that you can speak intelligently about them with developers. Speaking your developers’ language is important because you will likely need them to carry out some of your optimizations. They're unlikely to prioritize your asks if they can’t understand your request or see its importance. When you establish credibility and trust with your devs, you can begin to tear away the red tape that often blocks crucial work from getting done.
Pro tip: SEOs need cross-team support to be effective
It’s vital to have a healthy relationship with your developers so that you can successfully tackle SEO challenges from both sides. Don’t wait until a technical issue causes negative SEO ramifications to involve a developer. Instead, join forces for the planning stage with the goal of avoiding the issues altogether. If you don’t, it can cost you in time and money later.
Beyond cross-team support, understanding technical optimization for SEO is essential if you want to ensure that your web pages are structured for both humans and crawlers. To that end, we’ve divided this chapter into three sections:
How websites work
How search engines understand websites
How users interact with websites
Since the technical structure of a site can have a massive impact on its performance, it’s crucial for everyone to understand these principles. It might also be a good idea to share this part of the guide with your programmers, content writers, and designers so that all parties involved in a site's construction are on the same page.
1. How websites work
If search engine optimization is the process of optimizing a website for search, SEOs need at least a basic understanding of the thing they're optimizing!
Below, we outline the website’s journey from domain name purchase all the way to its fully rendered state in a browser. An important component of the website’s journey is the critical rendering path, which is the process of a browser turning a website’s code into a viewable page.
Knowing this about websites is important for SEOs to understand for a few reasons:
The steps in this webpage assembly process can affect page load times, and speed is not only important for keeping users on your site, but it’s also one of Google’s ranking factors.
Google renders certain resources, like JavaScript, on a “second pass.” Google will look at the page without JavaScript first, then a few days to a few weeks later, it will render JavaScript, meaning SEO-critical elements that are added to the page using JavaScript might not get indexed.
Imagine that the website loading process is your commute to work. You get ready at home, gather your things to bring to the office, and then take the fastest route from your home to your work. It would be silly to put on just one of your shoes, take a longer route to work, drop your things off at the office, then immediately return home to get your other shoe, right? That’s sort of what inefficient websites do. This chapter will teach you how to diagnose where your website might be inefficient, what you can do to streamline, and the positive ramifications on your rankings and user experience that can result from that streamlining.
Before a website can be accessed, it needs to be set up!
Domain name is purchased. Domain names like moz.com are purchased from a domain name registrar such as GoDaddy or HostGator. These registrars are just organizations that manage the reservations of domain names.
Domain name is linked to IP address. The Internet doesn’t understand names like “moz.com” as website addresses without the help of domain name servers (DNS). The Internet uses a series of numbers called an Internet protocol (IP) address (ex: 127.0.0.1), but we want to use names like moz.com because they’re easier for humans to remember. We need to use a DNS to link those human-readable names with machine-readable numbers.
How a website gets from server to browser
User requests domain. Now that the name is linked to an IP address via DNS, people can request a website by typing the domain name directly into their browser or by clicking on a link to the website.
Browser makes requests. That request for a web page prompts the browser to make a DNS lookup request to convert the domain name to its IP address. The browser then makes a request to the server for the code your web page is constructed with, such as HTML, CSS, and JavaScript.
Server sends resources. Once the server receives the request for the website, it sends the website files to be assembled in the searcher’s browser.
Browser assembles the web page. The browser has now received the resources from the server, but it still needs to put it all together and render the web page so that the user can see it in their browser. As the browser parses and organizes all the web page’s resources, it’s creating a Document Object Model (DOM). The DOM is what you can see when you right click + “inspect element” on a web page in your Chrome browser (learn how to inspect elements in other browsers).
Browser makes final requests. The browser will only show a web page after all the page’s necessary code is downloaded, parsed, and executed, so at this point, if the browser needs any additional code in order to show your website, it will make an additional request from your server.
Website appears in browser. Whew! After all that, your website has now been transformed (rendered) from code to what you see in your browser.
Pro tip: Talk to your developers about async!
Something you can bring up with your developers is shortening the critical rendering path by setting scripts to "async" when they’re not needed to render content above the fold, which can make your web pages load faster. Async tells the DOM that it can continue to be assembled while the browser is fetching the scripts needed to display your web page. If the DOM has to pause assembly every time the browser fetches a script (called “render-blocking scripts”), it can substantially slow down your page load.
It would be like going out to eat with your friends and having to pause the conversation every time one of you went up to the counter to order, only resuming once they got back. With async, you and your friends can continue to chat even when one of you is ordering. You might also want to bring up other optimizations that devs can implement to shorten the critical rendering path, such as removing unnecessary scripts entirely, like old tracking scripts.
Now that you know how a website appears in a browser, we’re going to focus on what a website is made of — in other words, the code (programming languages) used to construct those web pages.
The three most common are:
HTML – What a website says (titles, body content, etc.)
CSS – How a website looks (color, fonts, etc.)
JavaScript – How it behaves (interactive, dynamic, etc.)
HTML: What a website says
HTML stands for hypertext markup language, and it serves as the backbone of a website. Elements like headings, paragraphs, lists, and content are all defined in the HTML.
Here’s an example of a webpage, and what its corresponding HTML looks like:
HTML is important for SEOs to know because it’s what lives “under the hood” of any page they create or work on. While your CMS likely doesn’t require you to write your pages in HTML (ex: selecting “hyperlink” will allow you to create a link without you having to type in “a href=”), it is what you’re modifying every time you do something to a web page such as adding content, changing the anchor text of internal links, and so on. Google crawls these HTML elements to determine how relevant your document is to a particular query. In other words, what’s in your HTML plays a huge role in how your web page ranks in Google organic search!
CSS: How a website looks
CSS stands for cascading style sheets, and this is what causes your web pages to take on certain fonts, colors, and layouts. HTML was created to describe content, rather than to style it, so when CSS entered the scene, it was a game-changer. With CSS, web pages could be “beautified” without requiring manual coding of styles into the HTML of every page — a cumbersome process, especially for large sites.
It wasn’t until 2014 that Google’s indexing system began to render web pages more like an actual browser, as opposed to a text-only browser. A black-hat SEO practice that tried to capitalize on Google’s older indexing system was hiding text and links via CSS for the purpose of manipulating search engine rankings. This “hidden text and links” practice is a violation of Google’s quality guidelines.
Components of CSS that SEOs, in particular, should care about:
Since style directives can live in external stylesheet files (CSS files) instead of your page’s HTML, it makes your page less code-heavy, reducing file transfer size and making load times faster.
Browsers still have to download resources like your CSS file, so compressing them can make your web pages load faster, and page speed is a ranking factor.
Having your pages be more content-heavy than code-heavy can lead to better indexing of your site’s content.
Using CSS to hide links and content can get your website manually penalized and removed from Google’s index.
JavaScript: How a website behaves
In the earlier days of the Internet, web pages were built with HTML. When CSS came along, webpage content had the ability to take on some style. When the programming language JavaScript entered the scene, websites could now not only have structure and style, but they could be dynamic.
JavaScript has opened up a lot of opportunities for non-static web page creation. When someone attempts to access a page that is enhanced with this programming language, that user’s browser will execute the JavaScript against the static HTML that the server returned, resulting in a web page that comes to life with some sort of interactivity.
You’ve definitely seen JavaScript in action — you just may not have known it! That’s because JavaScript can do almost anything to a page. It could create a pop up, for example, or it could request third-party resources like ads to display on your page.
JavaScript can pose some problems for SEO, though, since search engines don’t view JavaScript the same way human visitors do. That’s because of client-side versus server-side rendering. Most JavaScript is executed in a client’s browser. With server-side rendering, on the other hand, the files are executed at the server and the server sends them to the browser in their fully rendered state.
SEO-critical page elements such as text, links, and tags that are loaded on the client’s side with JavaScript, rather than represented in your HTML, are invisible from your page’s code until they are rendered. This means that search engine crawlers won’t see what’s in your JavaScript — at least not initially.
Google says that, as long as you’re not blocking Googlebot from crawling your JavaScript files, they’re generally able to render and understand your web pages just like a browser can, which means that Googlebot should see the same things as a user viewing a site in their browser. However, due to this “second wave of indexing” for client-side JavaScript, Google can miss certain elements that are only available once JavaScript is executed.
There are also some other things that could go wrong during Googlebot’s process of rendering your web pages, which can prevent Google from understanding what’s contained in your JavaScript:
You’ve blocked Googlebot from JavaScript resources (ex: with robots.txt, like we learned about in Chapter 2)
Your server can’t handle all the requests to crawl your content
The JavaScript is too complex or outdated for Googlebot to understand
JavaScript doesn’t "lazy load" content into the page until after the crawler has finished with the page and moved on.
Needless to say, while JavaScript does open a lot of possibilities for web page creation, it can also have some serious ramifications for your SEO if you’re not careful. Thankfully, there is a way to check whether Google sees the same thing as your visitors. To see a page how Googlebot views your page, use Google Search Console's "Fetch and Render" tool. From your site’s Google Search Console dashboard, select “Crawl” from the left navigation, then “Fetch as Google.”
From this page, enter the URL you want to check (or leave blank if you want to check your homepage) and click the “Fetch and Render” button. You also have the option to test either the desktop or mobile version.
In return, you’ll get a side-by-side view of how Googlebot saw your page versus how a visitor to your website would have seen the page. Below, Google will also show you a list of any resources they may not have been able to get for the URL you entered.
Understanding the way websites work lays a great foundation for what we’ll talk about next, which is technical optimizations to help Google understand the pages on your website better.
2. How search engines understand websites
Search engines have gotten incredibly sophisticated, but they can’t (yet) find and interpret web pages quite like a human can. The following sections outline ways you can better deliver content to search engines.
Help search engines understand your content by structuring it with Schema
Imagine being a search engine crawler scanning down a 10,000-word article about how to bake a cake. How do you identify the author, recipe, ingredients, or steps required to bake a cake? This is where schema (Schema.org) markup comes in. It allows you to spoon-feed search engines more specific classifications for what type of information is on your page.
Schema is a way to label or organize your content so that search engines have a better understanding of what certain elements on your web pages are. This code provides structure to your data, which is why schema is often referred to as “structured data.” The process of structuring your data is often referred to as “markup” because you are marking up your content with organizational code.
JSON-LD is Google’s preferred schema markup (announced in May ‘16), which Bing also supports. To view a full list of the thousands of available schema markups, visit Schema.org or view the Google Developers Introduction to Structured Data for additional information on how to implement structured data. After you implement the structured data that best suits your web pages, you can test your markup with Google’s Structured Data Testing Tool.
In addition to helping bots like Google understand what a particular piece of content is about, schema markup can also enable special features to accompany your pages in the SERPs. These special features are referred to as "rich snippets," and you’ve probably seen them in action. They’re things like:
Top Stories carousel
Review stars
Sitelinks search boxes
Recipes
Remember, using structured data can help enable a rich snippet to be present, but does not guarantee it. Other types of rich snippets will likely be added in the future as the use of schema markup increases.
Some last words of advice for schema success:
You can use multiple types of schema markup on a page. However, if you mark up one element, like a product for example, and there are other products listed on the page, you must also mark up those products.
Don’t mark up content that is not visible to visitors and follow Google’s Quality Guidelines. For example, if you add review structured markup to a page, make sure those reviews are actually visible on that page.
If you have duplicate pages, Google asks that you mark up each duplicate page with your structured markup, not just the canonical version.
Provide original and updated (if applicable) content on your structured data pages.
Structured markup should be an accurate reflection of your page.
Try to use the most specific type of schema markup for your content.
Marked-up reviews should not be written by the business. They should be genuine unpaid business reviews from actual customers.
Tell search engines about your preferred pages with canonicalization
When Google crawls the same content on different web pages, it sometimes doesn’t know which page to index in search results. This is why the tag was invented: to help search engines better index the preferred version of content and not all its duplicates.
The rel="canonical" tag allows you to tell search engines where the original, master version of a piece of content is located. You’re essentially saying, "Hey search engine! Don’t index this; index this source page instead." So, if you want to republish a piece of content, whether exactly or slightly modified, but don’t want to risk creating duplicate content, the canonical tag is here to save the day.
Proper canonicalization ensures that every unique piece of content on your website has only one URL. To prevent search engines from indexing multiple versions of a single page, Google recommends having a self-referencing canonical tag on every page on your site. Without a canonical tag telling Google which version of your web page is the preferred one, http://www.example.com could get indexed separately from http://example.com, creating duplicates.
"Avoid duplicate content" is an Internet truism, and for good reason! Google wants to reward sites with unique, valuable content — not content that’s taken from other sources and repeated across multiple pages. Because engines want to provide the best searcher experience, they will rarely show multiple versions of the same content, opting instead to show only the canonicalized version, or if a canonical tag does not exist, whichever version they deem most likely to be the original.
Pro tip: Distinguishing between content filtering & content penalties There is no such thing as a duplicate content penalty. However, you should try to keep duplicate content from causing indexing issues by using the rel="canonical" tag when possible. When duplicates of a page exist, Google will choose a canonical and filter the others out of search results. That doesn’t mean you’ve been penalized. It just means that Google only wants to show one version of your content.
It’s also very common for websites to have multiple duplicate pages due to sort and filter options. For example, on an e-commerce site, you might have what’s called a faceted navigation that allows visitors to narrow down products to find exactly what they’re looking for, such as a “sort by” feature that reorders results on the product category page from lowest to highest price. This could create a URL that looks something like this: example.com/mens-shirts?sort=price_ascending. Add in more sort/filter options like color, size, material, brand, etc. and just think about all the variations of your main product category page this would create!
To learn more about different types of duplicate content, this post by Dr. Pete helps distill the different nuances.
3. How users interact with websites
In Chapter 1, we said that despite SEO standing for search engine optimization, SEO is as much about people as it is about search engines themselves. That’s because search engines exist to serve searchers. This goal helps explain why Google’s algorithm rewards websites that provide the best possible experiences for searchers, and why some websites, despite having qualities like robust backlink profiles, might not perform well in search.
When we understand what makes their web browsing experience optimal, we can create those experiences for maximum search performance.
Ensuring a positive experience for your mobile visitors
Being that well over half of all web traffic today comes from mobile, it’s safe to say that your website should be accessible and easy to navigate for mobile visitors. In April 2015, Google rolled out an update to its algorithm that would promote mobile-friendly pages over non-mobile-friendly pages. So how can you ensure that your website is mobile friendly? Although there are three main ways to configure your website for mobile, Google recommends responsive web design.
Responsive design
Responsive websites are designed to fit the screen of whatever type of device your visitors are using. You can use CSS to make the web page "respond" to the device size. This is ideal because it prevents visitors from having to double-tap or pinch-and-zoom in order to view the content on your pages. Not sure if your web pages are mobile friendly? You can use Google’s mobile-friendly test to check!
AMP
AMP stands for Accelerated Mobile Pages, and it is used to deliver content to mobile visitors at speeds much greater than with non-AMP delivery. AMP is able to deliver content so fast because it delivers content from its cache servers (not the original site) and uses a special AMP version of HTML and JavaScript. Learn more about AMP.
Mobile-first indexing
As of 2018, Google started switching websites over to mobile-first indexing. That change sparked some confusion between mobile-friendliness and mobile-first, so it’s helpful to disambiguate. With mobile-first indexing, Google crawls and indexes the mobile version of your web pages. Making your website compatible to mobile screens is good for users and your performance in search, but mobile-first indexing happens independently of mobile-friendliness.
This has raised some concerns for websites that lack parity between mobile and desktop versions, such as showing different content, navigation, links, etc. on their mobile view. A mobile site with different links, for example, will alter the way in which Googlebot (mobile) crawls your site and sends link equity to your other pages.
Breaking up long content for easier digestion
When sites have very long pages, they have the option of breaking them up into multiple parts of a whole. This is called pagination and it’s similar to pages in a book. In order to avoid giving the visitor too much all at once, you can break up your single page into multiple parts. This can be great for visitors, especially on e-commerce sites where there are a lot of product results in a category, but there are some steps you should take to help Google understand the relationship between your paginated pages. It’s called rel="next" and rel="prev."
You can read more about pagination in Google’s official documentation, but the main takeaways are that:
The first page in a sequence should only have rel="next" markup
The last page in a sequence should only have rel="prev" markup
Pages that have both a preceding and following page should have both rel="next" and rel="prev"
Since each page in the sequence is unique, don’t canonicalize them to the first page in the sequence. Only use a canonical tag to point to a “view all” version of your content, if you have one.
When Google sees a paginated sequence, it will typically consolidate the pages’ linking properties and send searchers to the first page
Pro tip: rel="next/prev" should still have anchor text and live within an <a> link This helps Google ensure that they pick up the rel="next/prev".
Improving page speed to mitigate visitor frustration
Google wants to serve content that loads lightning-fast for searchers. We’ve come to expect fast-loading results, and when we don’t get them, we’ll quickly bounce back to the SERP in search of a better, faster page. This is why page speed is a crucial aspect of on-site SEO. We can improve the speed of our web pages by taking advantage of tools like the ones we’ve mentioned below. Click on the links to learn more about each.
Google's PageSpeed Insights tool & best practices documentation
GTMetrix
Google's Mobile Website Speed & Performance Tester
Google Lighthouse
Images are one of the main culprits of slow pages!
As discussed in Chapter 4, images are one of the number-one reasons for slow-loading web pages! In addition to image compression, optimizing image alt text, choosing the right image format, and submitting image sitemaps, there are other technical ways to optimize the speed and way in which images are shown to your users. Some primary ways to improve image delivery are as follows:
SRCSET: How to deliver the best image size for each device
The SRCSET attribute allows you to have multiple versions of your image and then specify which version should be used in different situations. This piece of code is added to the <img> tag (where your image is located in the HTML) to provide unique images for specific-sized devices.
This is like the concept of responsive design that we discussed earlier, except for images!
This doesn’t just speed up your image load time, it’s also a unique way to enhance your on-page user experience by providing different and optimal images to different device types.
Pro tip: There are more than just three image size versions! It’s a common misconception that you just need a desktop, tablet, and mobile-sized version of your image. There are a huge variety of screen sizes and resolutions. Learn more about SRCSET.
Show visitors image loading is in progress with lazy loading
Lazy loading occurs when you go to a webpage and, instead of seeing a blank white space for where an image will be, a blurry lightweight version of the image or a colored box in its place appears while the surrounding text loads. After a few seconds, the image clearly loads in full resolution. The popular blogging platform Medium does this really well.
The low resolution version is initially loaded, and then the full high resolution version. This also helps to optimize your critical rendering path! So while all of your other page resources are being downloaded, you’re showing a low-resolution teaser image that helps tell users that things are happening/being loaded. For more information on how you should lazy load your images, check out Google’s Lazy Loading Guidance.
Improve speed by condensing and bundling your files
Page speed audits will often make recommendations such as “minify resource,” but what does that actually mean? Minification condenses a code file by removing things like line breaks and spaces, as well as abbreviating code variable names wherever possible.
“Bundling” is another common term you’ll hear in reference to improving page speed. The process of bundling combines a bunch of the same coding language files into one single file. For example, a bunch of JavaScript files could be put into one larger file to reduce the amount of JavaScript files for a browser.
By both minifying and bundling the files needed to construct your web page, you’ll speed up your website and reduce the number of your HTTP (file) requests.
Improving the experience for international audiences
Websites that target audiences from multiple countries should familiarize themselves with international SEO best practices in order to serve up the most relevant experiences. Without these optimizations, international visitors might have difficulty finding the version of your site that caters to them.
There are two main ways a website can be internationalized:
Language Sites that target speakers of multiple languages are considered multilingual websites. These sites should add something called an hreflang tag to show Google that your page has copy for another language. Learn more about hreflang.
Country Sites that target audiences in multiple countries are called multi-regional websites and they should choose a URL structure that makes it easy to target their domain or pages to specific countries. This can include the use of a country code top level domain (ccTLD) such as “.ca” for Canada, or a generic top-level domain (gTLD) with a country-specific subfolder such as “example.com/ca” for Canada. Learn more about locale-specific URLs.
You’ve researched, you’ve written, and you’ve optimized your website for search engines and user experience. The next piece of the SEO puzzle is a big one: establishing authority so that your pages will rank highly in search results.
Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don't have time to hunt down but want to read!
0 notes
mariasolemarionqi · 7 years ago
Text
Rewriting the Beginner's Guide to SEO, Chapter 5: Technical Optimization
Posted by BritneyMuller
After a short break, we're back to share our working draft of Chapter 5 of the Beginner's Guide to SEO with you! This one was a whopper, and we're really looking forward to your input. Giving beginner SEOs a solid grasp of just what technical optimization for SEO is and why it matters — without overwhelming them or scaring them off the subject — is a tall order indeed. We'd love to hear what you think: did we miss anything you think is important for beginners to know? Leave us your feedback in the comments!
And in case you're curious, check back on our outline, Chapter One, Chapter Two, Chapter Three, and Chapter Four to see what we've covered so far.
Chapter 5: Technical Optimization Basic technical knowledge will help you optimize your site for search engines and establish credibility with developers.
Now that you’ve crafted valuable content on the foundation of solid keyword research, it’s important to make sure it’s not only readable by humans, but by search engines too!
You don’t need to have a deep technical understanding of these concepts, but it is important to grasp what these technical assets do so that you can speak intelligently about them with developers. Speaking your developers’ language is important because you will likely need them to carry out some of your optimizations. They're unlikely to prioritize your asks if they can’t understand your request or see its importance. When you establish credibility and trust with your devs, you can begin to tear away the red tape that often blocks crucial work from getting done.
Pro tip: SEOs need cross-team support to be effective
It’s vital to have a healthy relationship with your developers so that you can successfully tackle SEO challenges from both sides. Don’t wait until a technical issue causes negative SEO ramifications to involve a developer. Instead, join forces for the planning stage with the goal of avoiding the issues altogether. If you don’t, it can cost you in time and money later.
Beyond cross-team support, understanding technical optimization for SEO is essential if you want to ensure that your web pages are structured for both humans and crawlers. To that end, we’ve divided this chapter into three sections:
How websites work
How search engines understand websites
How users interact with websites
Since the technical structure of a site can have a massive impact on its performance, it’s crucial for everyone to understand these principles. It might also be a good idea to share this part of the guide with your programmers, content writers, and designers so that all parties involved in a site's construction are on the same page.
1. How websites work
If search engine optimization is the process of optimizing a website for search, SEOs need at least a basic understanding of the thing they're optimizing!
Below, we outline the website’s journey from domain name purchase all the way to its fully rendered state in a browser. An important component of the website’s journey is the critical rendering path, which is the process of a browser turning a website’s code into a viewable page.
Knowing this about websites is important for SEOs to understand for a few reasons:
The steps in this webpage assembly process can affect page load times, and speed is not only important for keeping users on your site, but it’s also one of Google’s ranking factors.
Google renders certain resources, like JavaScript, on a “second pass.” Google will look at the page without JavaScript first, then a few days to a few weeks later, it will render JavaScript, meaning SEO-critical elements that are added to the page using JavaScript might not get indexed.
Imagine that the website loading process is your commute to work. You get ready at home, gather your things to bring to the office, and then take the fastest route from your home to your work. It would be silly to put on just one of your shoes, take a longer route to work, drop your things off at the office, then immediately return home to get your other shoe, right? That’s sort of what inefficient websites do. This chapter will teach you how to diagnose where your website might be inefficient, what you can do to streamline, and the positive ramifications on your rankings and user experience that can result from that streamlining.
Before a website can be accessed, it needs to be set up!
Domain name is purchased. Domain names like moz.com are purchased from a domain name registrar such as GoDaddy or HostGator. These registrars are just organizations that manage the reservations of domain names.
Domain name is linked to IP address. The Internet doesn’t understand names like “moz.com” as website addresses without the help of domain name servers (DNS). The Internet uses a series of numbers called an Internet protocol (IP) address (ex: 127.0.0.1), but we want to use names like moz.com because they’re easier for humans to remember. We need to use a DNS to link those human-readable names with machine-readable numbers.
How a website gets from server to browser
User requests domain. Now that the name is linked to an IP address via DNS, people can request a website by typing the domain name directly into their browser or by clicking on a link to the website.
Browser makes requests. That request for a web page prompts the browser to make a DNS lookup request to convert the domain name to its IP address. The browser then makes a request to the server for the code your web page is constructed with, such as HTML, CSS, and JavaScript.
Server sends resources. Once the server receives the request for the website, it sends the website files to be assembled in the searcher’s browser.
Browser assembles the web page. The browser has now received the resources from the server, but it still needs to put it all together and render the web page so that the user can see it in their browser. As the browser parses and organizes all the web page’s resources, it’s creating a Document Object Model (DOM). The DOM is what you can see when you right click + “inspect element” on a web page in your Chrome browser (learn how to inspect elements in other browsers).
Browser makes final requests. The browser will only show a web page after all the page’s necessary code is downloaded, parsed, and executed, so at this point, if the browser needs any additional code in order to show your website, it will make an additional request from your server.
Website appears in browser. Whew! After all that, your website has now been transformed (rendered) from code to what you see in your browser.
Pro tip: Talk to your developers about async!
Something you can bring up with your developers is shortening the critical rendering path by setting scripts to "async" when they’re not needed to render content above the fold, which can make your web pages load faster. Async tells the DOM that it can continue to be assembled while the browser is fetching the scripts needed to display your web page. If the DOM has to pause assembly every time the browser fetches a script (called “render-blocking scripts”), it can substantially slow down your page load.
It would be like going out to eat with your friends and having to pause the conversation every time one of you went up to the counter to order, only resuming once they got back. With async, you and your friends can continue to chat even when one of you is ordering. You might also want to bring up other optimizations that devs can implement to shorten the critical rendering path, such as removing unnecessary scripts entirely, like old tracking scripts.
Now that you know how a website appears in a browser, we’re going to focus on what a website is made of — in other words, the code (programming languages) used to construct those web pages.
The three most common are:
HTML – What a website says (titles, body content, etc.)
CSS – How a website looks (color, fonts, etc.)
JavaScript – How it behaves (interactive, dynamic, etc.)
HTML: What a website says
HTML stands for hypertext markup language, and it serves as the backbone of a website. Elements like headings, paragraphs, lists, and content are all defined in the HTML.
Here’s an example of a webpage, and what its corresponding HTML looks like:
HTML is important for SEOs to know because it’s what lives “under the hood” of any page they create or work on. While your CMS likely doesn’t require you to write your pages in HTML (ex: selecting “hyperlink” will allow you to create a link without you having to type in “a href=”), it is what you’re modifying every time you do something to a web page such as adding content, changing the anchor text of internal links, and so on. Google crawls these HTML elements to determine how relevant your document is to a particular query. In other words, what’s in your HTML plays a huge role in how your web page ranks in Google organic search!
CSS: How a website looks
CSS stands for cascading style sheets, and this is what causes your web pages to take on certain fonts, colors, and layouts. HTML was created to describe content, rather than to style it, so when CSS entered the scene, it was a game-changer. With CSS, web pages could be “beautified” without requiring manual coding of styles into the HTML of every page — a cumbersome process, especially for large sites.
It wasn’t until 2014 that Google’s indexing system began to render web pages more like an actual browser, as opposed to a text-only browser. A black-hat SEO practice that tried to capitalize on Google’s older indexing system was hiding text and links via CSS for the purpose of manipulating search engine rankings. This “hidden text and links” practice is a violation of Google’s quality guidelines.
Components of CSS that SEOs, in particular, should care about:
Since style directives can live in external stylesheet files (CSS files) instead of your page’s HTML, it makes your page less code-heavy, reducing file transfer size and making load times faster.
Browsers still have to download resources like your CSS file, so compressing them can make your web pages load faster, and page speed is a ranking factor.
Having your pages be more content-heavy than code-heavy can lead to better indexing of your site’s content.
Using CSS to hide links and content can get your website manually penalized and removed from Google’s index.
JavaScript: How a website behaves
In the earlier days of the Internet, web pages were built with HTML. When CSS came along, webpage content had the ability to take on some style. When the programming language JavaScript entered the scene, websites could now not only have structure and style, but they could be dynamic.
JavaScript has opened up a lot of opportunities for non-static web page creation. When someone attempts to access a page that is enhanced with this programming language, that user’s browser will execute the JavaScript against the static HTML that the server returned, resulting in a web page that comes to life with some sort of interactivity.
You’ve definitely seen JavaScript in action — you just may not have known it! That’s because JavaScript can do almost anything to a page. It could create a pop up, for example, or it could request third-party resources like ads to display on your page.
JavaScript can pose some problems for SEO, though, since search engines don’t view JavaScript the same way human visitors do. That’s because of client-side versus server-side rendering. Most JavaScript is executed in a client’s browser. With server-side rendering, on the other hand, the files are executed at the server and the server sends them to the browser in their fully rendered state.
SEO-critical page elements such as text, links, and tags that are loaded on the client’s side with JavaScript, rather than represented in your HTML, are invisible from your page’s code until they are rendered. This means that search engine crawlers won’t see what’s in your JavaScript — at least not initially.
Google says that, as long as you’re not blocking Googlebot from crawling your JavaScript files, they’re generally able to render and understand your web pages just like a browser can, which means that Googlebot should see the same things as a user viewing a site in their browser. However, due to this “second wave of indexing” for client-side JavaScript, Google can miss certain elements that are only available once JavaScript is executed.
There are also some other things that could go wrong during Googlebot’s process of rendering your web pages, which can prevent Google from understanding what’s contained in your JavaScript:
You’ve blocked Googlebot from JavaScript resources (ex: with robots.txt, like we learned about in Chapter 2)
Your server can’t handle all the requests to crawl your content
The JavaScript is too complex or outdated for Googlebot to understand
JavaScript doesn’t "lazy load" content into the page until after the crawler has finished with the page and moved on.
Needless to say, while JavaScript does open a lot of possibilities for web page creation, it can also have some serious ramifications for your SEO if you’re not careful. Thankfully, there is a way to check whether Google sees the same thing as your visitors. To see a page how Googlebot views your page, use Google Search Console's "Fetch and Render" tool. From your site’s Google Search Console dashboard, select “Crawl” from the left navigation, then “Fetch as Google.”
From this page, enter the URL you want to check (or leave blank if you want to check your homepage) and click the “Fetch and Render” button. You also have the option to test either the desktop or mobile version.
In return, you’ll get a side-by-side view of how Googlebot saw your page versus how a visitor to your website would have seen the page. Below, Google will also show you a list of any resources they may not have been able to get for the URL you entered.
Understanding the way websites work lays a great foundation for what we’ll talk about next, which is technical optimizations to help Google understand the pages on your website better.
2. How search engines understand websites
Search engines have gotten incredibly sophisticated, but they can’t (yet) find and interpret web pages quite like a human can. The following sections outline ways you can better deliver content to search engines.
Help search engines understand your content by structuring it with Schema
Imagine being a search engine crawler scanning down a 10,000-word article about how to bake a cake. How do you identify the author, recipe, ingredients, or steps required to bake a cake? This is where schema (Schema.org) markup comes in. It allows you to spoon-feed search engines more specific classifications for what type of information is on your page.
Schema is a way to label or organize your content so that search engines have a better understanding of what certain elements on your web pages are. This code provides structure to your data, which is why schema is often referred to as “structured data.” The process of structuring your data is often referred to as “markup” because you are marking up your content with organizational code.
JSON-LD is Google’s preferred schema markup (announced in May ‘16), which Bing also supports. To view a full list of the thousands of available schema markups, visit Schema.org or view the Google Developers Introduction to Structured Data for additional information on how to implement structured data. After you implement the structured data that best suits your web pages, you can test your markup with Google’s Structured Data Testing Tool.
In addition to helping bots like Google understand what a particular piece of content is about, schema markup can also enable special features to accompany your pages in the SERPs. These special features are referred to as "rich snippets," and you’ve probably seen them in action. They’re things like:
Top Stories carousel
Review stars
Sitelinks search boxes
Recipes
Remember, using structured data can help enable a rich snippet to be present, but does not guarantee it. Other types of rich snippets will likely be added in the future as the use of schema markup increases.
Some last words of advice for schema success:
You can use multiple types of schema markup on a page. However, if you mark up one element, like a product for example, and there are other products listed on the page, you must also mark up those products.
Don’t mark up content that is not visible to visitors and follow Google’s Quality Guidelines. For example, if you add review structured markup to a page, make sure those reviews are actually visible on that page.
If you have duplicate pages, Google asks that you mark up each duplicate page with your structured markup, not just the canonical version.
Provide original and updated (if applicable) content on your structured data pages.
Structured markup should be an accurate reflection of your page.
Try to use the most specific type of schema markup for your content.
Marked-up reviews should not be written by the business. They should be genuine unpaid business reviews from actual customers.
Tell search engines about your preferred pages with canonicalization
When Google crawls the same content on different web pages, it sometimes doesn’t know which page to index in search results. This is why the tag was invented: to help search engines better index the preferred version of content and not all its duplicates.
The tag allows you to tell search engines where the original, master version of a piece of content is located. You’re essentially saying, "Hey search engine! Don’t index this; index this source page instead." So, if you want to republish a piece of content, whether exactly or slightly modified, but don’t want to risk creating duplicate content, the canonical tag is here to save the day.
Proper canonicalization ensures that every unique piece of content on your website has only one URL. To prevent search engines from indexing multiple versions of a single page, Google recommends having a self-referencing canonical tag on every page on your site. Without a canonical tag telling Google which version of your web page is the preferred one, http://www.example.com could get indexed separately from http://example.com, creating duplicates.
"Avoid duplicate content" is an Internet truism, and for good reason! Google wants to reward sites with unique, valuable content — not content that’s taken from other sources and repeated across multiple pages. Because engines want to provide the best searcher experience, they will rarely show multiple versions of the same content, opting instead to show only the canonicalized version, or if a canonical tag does not exist, whichever version they deem most likely to be the original.
Pro tip: Distinguishing between content filtering & content penalties There is no such thing as a duplicate content penalty. However, you should try to keep duplicate content from causing indexing issues by using the tag when possible. When duplicates of a page exist, Google will choose a canonical and filter the others out of search results. That doesn’t mean you’ve been penalized. It just means that Google only wants to show one version of your content.
It’s also very common for websites to have multiple duplicate pages due to sort and filter options. For example, on an e-commerce site, you might have what’s called a faceted navigation that allows visitors to narrow down products to find exactly what they’re looking for, such as a “sort by” feature that reorders results on the product category page from lowest to highest price. This could create a URL that looks something like this: example.com/mens-shirts?sort=price_ascending. Add in more sort/filter options like color, size, material, brand, etc. and just think about all the variations of your main product category page this would create!
To learn more about different types of duplicate content, this post by Dr. Pete helps distill the different nuances.
3. How users interact with websites
In Chapter 1, we said that despite SEO standing for search engine optimization, SEO is as much about people as it is about search engines themselves. That’s because search engines exist to serve searchers. This goal helps explain why Google’s algorithm rewards websites that provide the best possible experiences for searchers, and why some websites, despite having qualities like robust backlink profiles, might not perform well in search.
When we understand what makes their web browsing experience optimal, we can create those experiences for maximum search performance.
Ensuring a positive experience for your mobile visitors
Being that well over half of all web traffic today comes from mobile, it’s safe to say that your website should be accessible and easy to navigate for mobile visitors. In April 2015, Google rolled out an update to its algorithm that would promote mobile-friendly pages over non-mobile-friendly pages. So how can you ensure that your..
https://ift.tt/2PoeXug
0 notes
mercedessharonwo1 · 7 years ago
Text
Rewriting the Beginner's Guide to SEO, Chapter 5: Technical Optimization
Posted by BritneyMuller
After a short break, we're back to share our working draft of Chapter 5 of the Beginner's Guide to SEO with you! This one was a whopper, and we're really looking forward to your input. Giving beginner SEOs a solid grasp of just what technical optimization for SEO is and why it matters — without overwhelming them or scaring them off the subject — is a tall order indeed. We'd love to hear what you think: did we miss anything you think is important for beginners to know? Leave us your feedback in the comments!
And in case you're curious, check back on our outline, Chapter One, Chapter Two, Chapter Three, and Chapter Four to see what we've covered so far.
Chapter 5: Technical Optimization Basic technical knowledge will help you optimize your site for search engines and establish credibility with developers.
Now that you’ve crafted valuable content on the foundation of solid keyword research, it’s important to make sure it’s not only readable by humans, but by search engines too!
You don’t need to have a deep technical understanding of these concepts, but it is important to grasp what these technical assets do so that you can speak intelligently about them with developers. Speaking your developers’ language is important because you will likely need them to carry out some of your optimizations. They're unlikely to prioritize your asks if they can’t understand your request or see its importance. When you establish credibility and trust with your devs, you can begin to tear away the red tape that often blocks crucial work from getting done.
Pro tip: SEOs need cross-team support to be effective
It’s vital to have a healthy relationship with your developers so that you can successfully tackle SEO challenges from both sides. Don’t wait until a technical issue causes negative SEO ramifications to involve a developer. Instead, join forces for the planning stage with the goal of avoiding the issues altogether. If you don’t, it can cost you in time and money later.
Beyond cross-team support, understanding technical optimization for SEO is essential if you want to ensure that your web pages are structured for both humans and crawlers. To that end, we’ve divided this chapter into three sections:
How websites work
How search engines understand websites
How users interact with websites
Since the technical structure of a site can have a massive impact on its performance, it’s crucial for everyone to understand these principles. It might also be a good idea to share this part of the guide with your programmers, content writers, and designers so that all parties involved in a site's construction are on the same page.
1. How websites work
If search engine optimization is the process of optimizing a website for search, SEOs need at least a basic understanding of the thing they're optimizing!
Below, we outline the website’s journey from domain name purchase all the way to its fully rendered state in a browser. An important component of the website’s journey is the critical rendering path, which is the process of a browser turning a website’s code into a viewable page.
Knowing this about websites is important for SEOs to understand for a few reasons:
The steps in this webpage assembly process can affect page load times, and speed is not only important for keeping users on your site, but it’s also one of Google’s ranking factors.
Google renders certain resources, like JavaScript, on a “second pass.” Google will look at the page without JavaScript first, then a few days to a few weeks later, it will render JavaScript, meaning SEO-critical elements that are added to the page using JavaScript might not get indexed.
Imagine that the website loading process is your commute to work. You get ready at home, gather your things to bring to the office, and then take the fastest route from your home to your work. It would be silly to put on just one of your shoes, take a longer route to work, drop your things off at the office, then immediately return home to get your other shoe, right? That’s sort of what inefficient websites do. This chapter will teach you how to diagnose where your website might be inefficient, what you can do to streamline, and the positive ramifications on your rankings and user experience that can result from that streamlining.
Before a website can be accessed, it needs to be set up!
Domain name is purchased. Domain names like moz.com are purchased from a domain name registrar such as GoDaddy or HostGator. These registrars are just organizations that manage the reservations of domain names.
Domain name is linked to IP address. The Internet doesn’t understand names like “moz.com” as website addresses without the help of domain name servers (DNS). The Internet uses a series of numbers called an Internet protocol (IP) address (ex: 127.0.0.1), but we want to use names like moz.com because they’re easier for humans to remember. We need to use a DNS to link those human-readable names with machine-readable numbers.
How a website gets from server to browser
User requests domain. Now that the name is linked to an IP address via DNS, people can request a website by typing the domain name directly into their browser or by clicking on a link to the website.
Browser makes requests. That request for a web page prompts the browser to make a DNS lookup request to convert the domain name to its IP address. The browser then makes a request to the server for the code your web page is constructed with, such as HTML, CSS, and JavaScript.
Server sends resources. Once the server receives the request for the website, it sends the website files to be assembled in the searcher’s browser.
Browser assembles the web page. The browser has now received the resources from the server, but it still needs to put it all together and render the web page so that the user can see it in their browser. As the browser parses and organizes all the web page’s resources, it’s creating a Document Object Model (DOM). The DOM is what you can see when you right click + “inspect element” on a web page in your Chrome browser (learn how to inspect elements in other browsers).
Browser makes final requests. The browser will only show a web page after all the page’s necessary code is downloaded, parsed, and executed, so at this point, if the browser needs any additional code in order to show your website, it will make an additional request from your server.
Website appears in browser. Whew! After all that, your website has now been transformed (rendered) from code to what you see in your browser.
Pro tip: Talk to your developers about async!
Something you can bring up with your developers is shortening the critical rendering path by setting scripts to "async" when they’re not needed to render content above the fold, which can make your web pages load faster. Async tells the DOM that it can continue to be assembled while the browser is fetching the scripts needed to display your web page. If the DOM has to pause assembly every time the browser fetches a script (called “render-blocking scripts”), it can substantially slow down your page load.
It would be like going out to eat with your friends and having to pause the conversation every time one of you went up to the counter to order, only resuming once they got back. With async, you and your friends can continue to chat even when one of you is ordering. You might also want to bring up other optimizations that devs can implement to shorten the critical rendering path, such as removing unnecessary scripts entirely, like old tracking scripts.
Now that you know how a website appears in a browser, we’re going to focus on what a website is made of — in other words, the code (programming languages) used to construct those web pages.
The three most common are:
HTML – What a website says (titles, body content, etc.)
CSS – How a website looks (color, fonts, etc.)
JavaScript – How it behaves (interactive, dynamic, etc.)
HTML: What a website says
HTML stands for hypertext markup language, and it serves as the backbone of a website. Elements like headings, paragraphs, lists, and content are all defined in the HTML.
Here’s an example of a webpage, and what its corresponding HTML looks like:
HTML is important for SEOs to know because it’s what lives “under the hood” of any page they create or work on. While your CMS likely doesn’t require you to write your pages in HTML (ex: selecting “hyperlink” will allow you to create a link without you having to type in “a href=”), it is what you’re modifying every time you do something to a web page such as adding content, changing the anchor text of internal links, and so on. Google crawls these HTML elements to determine how relevant your document is to a particular query. In other words, what’s in your HTML plays a huge role in how your web page ranks in Google organic search!
CSS: How a website looks
CSS stands for cascading style sheets, and this is what causes your web pages to take on certain fonts, colors, and layouts. HTML was created to describe content, rather than to style it, so when CSS entered the scene, it was a game-changer. With CSS, web pages could be “beautified” without requiring manual coding of styles into the HTML of every page — a cumbersome process, especially for large sites.
It wasn’t until 2014 that Google’s indexing system began to render web pages more like an actual browser, as opposed to a text-only browser. A black-hat SEO practice that tried to capitalize on Google’s older indexing system was hiding text and links via CSS for the purpose of manipulating search engine rankings. This “hidden text and links” practice is a violation of Google’s quality guidelines.
Components of CSS that SEOs, in particular, should care about:
Since style directives can live in external stylesheet files (CSS files) instead of your page’s HTML, it makes your page less code-heavy, reducing file transfer size and making load times faster.
Browsers still have to download resources like your CSS file, so compressing them can make your web pages load faster, and page speed is a ranking factor.
Having your pages be more content-heavy than code-heavy can lead to better indexing of your site’s content.
Using CSS to hide links and content can get your website manually penalized and removed from Google’s index.
JavaScript: How a website behaves
In the earlier days of the Internet, web pages were built with HTML. When CSS came along, webpage content had the ability to take on some style. When the programming language JavaScript entered the scene, websites could now not only have structure and style, but they could be dynamic.
JavaScript has opened up a lot of opportunities for non-static web page creation. When someone attempts to access a page that is enhanced with this programming language, that user’s browser will execute the JavaScript against the static HTML that the server returned, resulting in a web page that comes to life with some sort of interactivity.
You’ve definitely seen JavaScript in action — you just may not have known it! That’s because JavaScript can do almost anything to a page. It could create a pop up, for example, or it could request third-party resources like ads to display on your page.
JavaScript can pose some problems for SEO, though, since search engines don’t view JavaScript the same way human visitors do. That’s because of client-side versus server-side rendering. Most JavaScript is executed in a client’s browser. With server-side rendering, on the other hand, the files are executed at the server and the server sends them to the browser in their fully rendered state.
SEO-critical page elements such as text, links, and tags that are loaded on the client’s side with JavaScript, rather than represented in your HTML, are invisible from your page’s code until they are rendered. This means that search engine crawlers won’t see what’s in your JavaScript — at least not initially.
Google says that, as long as you’re not blocking Googlebot from crawling your JavaScript files, they’re generally able to render and understand your web pages just like a browser can, which means that Googlebot should see the same things as a user viewing a site in their browser. However, due to this “second wave of indexing” for client-side JavaScript, Google can miss certain elements that are only available once JavaScript is executed.
There are also some other things that could go wrong during Googlebot’s process of rendering your web pages, which can prevent Google from understanding what’s contained in your JavaScript:
You’ve blocked Googlebot from JavaScript resources (ex: with robots.txt, like we learned about in Chapter 2)
Your server can’t handle all the requests to crawl your content
The JavaScript is too complex or outdated for Googlebot to understand
JavaScript doesn’t "lazy load" content into the page until after the crawler has finished with the page and moved on.
Needless to say, while JavaScript does open a lot of possibilities for web page creation, it can also have some serious ramifications for your SEO if you’re not careful. Thankfully, there is a way to check whether Google sees the same thing as your visitors. To see a page how Googlebot views your page, use Google Search Console's "Fetch and Render" tool. From your site’s Google Search Console dashboard, select “Crawl” from the left navigation, then “Fetch as Google.”
From this page, enter the URL you want to check (or leave blank if you want to check your homepage) and click the “Fetch and Render” button. You also have the option to test either the desktop or mobile version.
In return, you’ll get a side-by-side view of how Googlebot saw your page versus how a visitor to your website would have seen the page. Below, Google will also show you a list of any resources they may not have been able to get for the URL you entered.
Understanding the way websites work lays a great foundation for what we’ll talk about next, which is technical optimizations to help Google understand the pages on your website better.
2. How search engines understand websites
Search engines have gotten incredibly sophisticated, but they can’t (yet) find and interpret web pages quite like a human can. The following sections outline ways you can better deliver content to search engines.
Help search engines understand your content by structuring it with Schema
Imagine being a search engine crawler scanning down a 10,000-word article about how to bake a cake. How do you identify the author, recipe, ingredients, or steps required to bake a cake? This is where schema (Schema.org) markup comes in. It allows you to spoon-feed search engines more specific classifications for what type of information is on your page.
Schema is a way to label or organize your content so that search engines have a better understanding of what certain elements on your web pages are. This code provides structure to your data, which is why schema is often referred to as “structured data.” The process of structuring your data is often referred to as “markup” because you are marking up your content with organizational code.
JSON-LD is Google’s preferred schema markup (announced in May ‘16), which Bing also supports. To view a full list of the thousands of available schema markups, visit Schema.org or view the Google Developers Introduction to Structured Data for additional information on how to implement structured data. After you implement the structured data that best suits your web pages, you can test your markup with Google’s Structured Data Testing Tool.
In addition to helping bots like Google understand what a particular piece of content is about, schema markup can also enable special features to accompany your pages in the SERPs. These special features are referred to as "rich snippets," and you’ve probably seen them in action. They’re things like:
Top Stories carousel
Review stars
Sitelinks search boxes
Recipes
Remember, using structured data can help enable a rich snippet to be present, but does not guarantee it. Other types of rich snippets will likely be added in the future as the use of schema markup increases.
Some last words of advice for schema success:
You can use multiple types of schema markup on a page. However, if you mark up one element, like a product for example, and there are other products listed on the page, you must also mark up those products.
Don’t mark up content that is not visible to visitors and follow Google’s Quality Guidelines. For example, if you add review structured markup to a page, make sure those reviews are actually visible on that page.
If you have duplicate pages, Google asks that you mark up each duplicate page with your structured markup, not just the canonical version.
Provide original and updated (if applicable) content on your structured data pages.
Structured markup should be an accurate reflection of your page.
Try to use the most specific type of schema markup for your content.
Marked-up reviews should not be written by the business. They should be genuine unpaid business reviews from actual customers.
Tell search engines about your preferred pages with canonicalization
When Google crawls the same content on different web pages, it sometimes doesn’t know which page to index in search results. This is why the tag was invented: to help search engines better index the preferred version of content and not all its duplicates.
The tag allows you to tell search engines where the original, master version of a piece of content is located. You’re essentially saying, "Hey search engine! Don’t index this; index this source page instead." So, if you want to republish a piece of content, whether exactly or slightly modified, but don’t want to risk creating duplicate content, the canonical tag is here to save the day.
Proper canonicalization ensures that every unique piece of content on your website has only one URL. To prevent search engines from indexing multiple versions of a single page, Google recommends having a self-referencing canonical tag on every page on your site. Without a canonical tag telling Google which version of your web page is the preferred one, http://www.example.com could get indexed separately from http://example.com, creating duplicates.
"Avoid duplicate content" is an Internet truism, and for good reason! Google wants to reward sites with unique, valuable content — not content that’s taken from other sources and repeated across multiple pages. Because engines want to provide the best searcher experience, they will rarely show multiple versions of the same content, opting instead to show only the canonicalized version, or if a canonical tag does not exist, whichever version they deem most likely to be the original.
Pro tip: Distinguishing between content filtering & content penalties There is no such thing as a duplicate content penalty. However, you should try to keep duplicate content from causing indexing issues by using the tag when possible. When duplicates of a page exist, Google will choose a canonical and filter the others out of search results. That doesn’t mean you’ve been penalized. It just means that Google only wants to show one version of your content.
It’s also very common for websites to have multiple duplicate pages due to sort and filter options. For example, on an e-commerce site, you might have what’s called a faceted navigation that allows visitors to narrow down products to find exactly what they’re looking for, such as a “sort by” feature that reorders results on the product category page from lowest to highest price. This could create a URL that looks something like this: example.com/mens-shirts?sort=price_ascending. Add in more sort/filter options like color, size, material, brand, etc. and just think about all the variations of your main product category page this would create!
To learn more about different types of duplicate content, this post by Dr. Pete helps distill the different nuances.
3. How users interact with websites
In Chapter 1, we said that despite SEO standing for search engine optimization, SEO is as much about people as it is about search engines themselves. That’s because search engines exist to serve searchers. This goal helps explain why Google’s algorithm rewards websites that provide the best possible experiences for searchers, and why some websites, despite having qualities like robust backlink profiles, might not perform well in search.
When we understand what makes their web browsing experience optimal, we can create those experiences for maximum search performance.
Ensuring a positive experience for your mobile visitors
Being that well over half of all web traffic today comes from mobile, it’s safe to say that your website should be accessible and easy to navigate for mobile visitors. In April 2015, Google rolled out an update to its algorithm that would promote mobile-friendly pages over non-mobile-friendly pages. So how can you ensure that your..
https://ift.tt/2PoeXug
0 notes
rodneyevesuarywk · 7 years ago
Text
Rewriting the Beginner's Guide to SEO, Chapter 5: Technical Optimization
Posted by BritneyMuller
After a short break, we're back to share our working draft of Chapter 5 of the Beginner's Guide to SEO with you! This one was a whopper, and we're really looking forward to your input. Giving beginner SEOs a solid grasp of just what technical optimization for SEO is and why it matters — without overwhelming them or scaring them off the subject — is a tall order indeed. We'd love to hear what you think: did we miss anything you think is important for beginners to know? Leave us your feedback in the comments!
And in case you're curious, check back on our outline, Chapter One, Chapter Two, Chapter Three, and Chapter Four to see what we've covered so far.
Chapter 5: Technical Optimization Basic technical knowledge will help you optimize your site for search engines and establish credibility with developers.
Now that you’ve crafted valuable content on the foundation of solid keyword research, it’s important to make sure it’s not only readable by humans, but by search engines too!
You don’t need to have a deep technical understanding of these concepts, but it is important to grasp what these technical assets do so that you can speak intelligently about them with developers. Speaking your developers’ language is important because you will likely need them to carry out some of your optimizations. They're unlikely to prioritize your asks if they can’t understand your request or see its importance. When you establish credibility and trust with your devs, you can begin to tear away the red tape that often blocks crucial work from getting done.
Pro tip: SEOs need cross-team support to be effective
It’s vital to have a healthy relationship with your developers so that you can successfully tackle SEO challenges from both sides. Don’t wait until a technical issue causes negative SEO ramifications to involve a developer. Instead, join forces for the planning stage with the goal of avoiding the issues altogether. If you don’t, it can cost you in time and money later.
Beyond cross-team support, understanding technical optimization for SEO is essential if you want to ensure that your web pages are structured for both humans and crawlers. To that end, we’ve divided this chapter into three sections:
How websites work
How search engines understand websites
How users interact with websites
Since the technical structure of a site can have a massive impact on its performance, it’s crucial for everyone to understand these principles. It might also be a good idea to share this part of the guide with your programmers, content writers, and designers so that all parties involved in a site's construction are on the same page.
1. How websites work
If search engine optimization is the process of optimizing a website for search, SEOs need at least a basic understanding of the thing they're optimizing!
Below, we outline the website’s journey from domain name purchase all the way to its fully rendered state in a browser. An important component of the website’s journey is the critical rendering path, which is the process of a browser turning a website’s code into a viewable page.
Knowing this about websites is important for SEOs to understand for a few reasons:
The steps in this webpage assembly process can affect page load times, and speed is not only important for keeping users on your site, but it’s also one of Google’s ranking factors.
Google renders certain resources, like JavaScript, on a “second pass.” Google will look at the page without JavaScript first, then a few days to a few weeks later, it will render JavaScript, meaning SEO-critical elements that are added to the page using JavaScript might not get indexed.
Imagine that the website loading process is your commute to work. You get ready at home, gather your things to bring to the office, and then take the fastest route from your home to your work. It would be silly to put on just one of your shoes, take a longer route to work, drop your things off at the office, then immediately return home to get your other shoe, right? That’s sort of what inefficient websites do. This chapter will teach you how to diagnose where your website might be inefficient, what you can do to streamline, and the positive ramifications on your rankings and user experience that can result from that streamlining.
Before a website can be accessed, it needs to be set up!
Domain name is purchased. Domain names like moz.com are purchased from a domain name registrar such as GoDaddy or HostGator. These registrars are just organizations that manage the reservations of domain names.
Domain name is linked to IP address. The Internet doesn’t understand names like “moz.com” as website addresses without the help of domain name servers (DNS). The Internet uses a series of numbers called an Internet protocol (IP) address (ex: 127.0.0.1), but we want to use names like moz.com because they’re easier for humans to remember. We need to use a DNS to link those human-readable names with machine-readable numbers.
How a website gets from server to browser
User requests domain. Now that the name is linked to an IP address via DNS, people can request a website by typing the domain name directly into their browser or by clicking on a link to the website.
Browser makes requests. That request for a web page prompts the browser to make a DNS lookup request to convert the domain name to its IP address. The browser then makes a request to the server for the code your web page is constructed with, such as HTML, CSS, and JavaScript.
Server sends resources. Once the server receives the request for the website, it sends the website files to be assembled in the searcher’s browser.
Browser assembles the web page. The browser has now received the resources from the server, but it still needs to put it all together and render the web page so that the user can see it in their browser. As the browser parses and organizes all the web page’s resources, it’s creating a Document Object Model (DOM). The DOM is what you can see when you right click + “inspect element” on a web page in your Chrome browser (learn how to inspect elements in other browsers).
Browser makes final requests. The browser will only show a web page after all the page’s necessary code is downloaded, parsed, and executed, so at this point, if the browser needs any additional code in order to show your website, it will make an additional request from your server.
Website appears in browser. Whew! After all that, your website has now been transformed (rendered) from code to what you see in your browser.
Pro tip: Talk to your developers about async!
Something you can bring up with your developers is shortening the critical rendering path by setting scripts to "async" when they’re not needed to render content above the fold, which can make your web pages load faster. Async tells the DOM that it can continue to be assembled while the browser is fetching the scripts needed to display your web page. If the DOM has to pause assembly every time the browser fetches a script (called “render-blocking scripts”), it can substantially slow down your page load.
It would be like going out to eat with your friends and having to pause the conversation every time one of you went up to the counter to order, only resuming once they got back. With async, you and your friends can continue to chat even when one of you is ordering. You might also want to bring up other optimizations that devs can implement to shorten the critical rendering path, such as removing unnecessary scripts entirely, like old tracking scripts.
Now that you know how a website appears in a browser, we’re going to focus on what a website is made of — in other words, the code (programming languages) used to construct those web pages.
The three most common are:
HTML – What a website says (titles, body content, etc.)
CSS – How a website looks (color, fonts, etc.)
JavaScript – How it behaves (interactive, dynamic, etc.)
HTML: What a website says
HTML stands for hypertext markup language, and it serves as the backbone of a website. Elements like headings, paragraphs, lists, and content are all defined in the HTML.
Here’s an example of a webpage, and what its corresponding HTML looks like:
HTML is important for SEOs to know because it’s what lives “under the hood” of any page they create or work on. While your CMS likely doesn’t require you to write your pages in HTML (ex: selecting “hyperlink” will allow you to create a link without you having to type in “a href=”), it is what you’re modifying every time you do something to a web page such as adding content, changing the anchor text of internal links, and so on. Google crawls these HTML elements to determine how relevant your document is to a particular query. In other words, what’s in your HTML plays a huge role in how your web page ranks in Google organic search!
CSS: How a website looks
CSS stands for cascading style sheets, and this is what causes your web pages to take on certain fonts, colors, and layouts. HTML was created to describe content, rather than to style it, so when CSS entered the scene, it was a game-changer. With CSS, web pages could be “beautified” without requiring manual coding of styles into the HTML of every page — a cumbersome process, especially for large sites.
It wasn’t until 2014 that Google’s indexing system began to render web pages more like an actual browser, as opposed to a text-only browser. A black-hat SEO practice that tried to capitalize on Google’s older indexing system was hiding text and links via CSS for the purpose of manipulating search engine rankings. This “hidden text and links” practice is a violation of Google’s quality guidelines.
Components of CSS that SEOs, in particular, should care about:
Since style directives can live in external stylesheet files (CSS files) instead of your page’s HTML, it makes your page less code-heavy, reducing file transfer size and making load times faster.
Browsers still have to download resources like your CSS file, so compressing them can make your web pages load faster, and page speed is a ranking factor.
Having your pages be more content-heavy than code-heavy can lead to better indexing of your site’s content.
Using CSS to hide links and content can get your website manually penalized and removed from Google’s index.
JavaScript: How a website behaves
In the earlier days of the Internet, web pages were built with HTML. When CSS came along, webpage content had the ability to take on some style. When the programming language JavaScript entered the scene, websites could now not only have structure and style, but they could be dynamic.
JavaScript has opened up a lot of opportunities for non-static web page creation. When someone attempts to access a page that is enhanced with this programming language, that user’s browser will execute the JavaScript against the static HTML that the server returned, resulting in a web page that comes to life with some sort of interactivity.
You’ve definitely seen JavaScript in action — you just may not have known it! That’s because JavaScript can do almost anything to a page. It could create a pop up, for example, or it could request third-party resources like ads to display on your page.
JavaScript can pose some problems for SEO, though, since search engines don’t view JavaScript the same way human visitors do. That’s because of client-side versus server-side rendering. Most JavaScript is executed in a client’s browser. With server-side rendering, on the other hand, the files are executed at the server and the server sends them to the browser in their fully rendered state.
SEO-critical page elements such as text, links, and tags that are loaded on the client’s side with JavaScript, rather than represented in your HTML, are invisible from your page’s code until they are rendered. This means that search engine crawlers won’t see what’s in your JavaScript — at least not initially.
Google says that, as long as you’re not blocking Googlebot from crawling your JavaScript files, they’re generally able to render and understand your web pages just like a browser can, which means that Googlebot should see the same things as a user viewing a site in their browser. However, due to this “second wave of indexing” for client-side JavaScript, Google can miss certain elements that are only available once JavaScript is executed.
There are also some other things that could go wrong during Googlebot’s process of rendering your web pages, which can prevent Google from understanding what’s contained in your JavaScript:
You’ve blocked Googlebot from JavaScript resources (ex: with robots.txt, like we learned about in Chapter 2)
Your server can’t handle all the requests to crawl your content
The JavaScript is too complex or outdated for Googlebot to understand
JavaScript doesn’t "lazy load" content into the page until after the crawler has finished with the page and moved on.
Needless to say, while JavaScript does open a lot of possibilities for web page creation, it can also have some serious ramifications for your SEO if you’re not careful. Thankfully, there is a way to check whether Google sees the same thing as your visitors. To see a page how Googlebot views your page, use Google Search Console's "Fetch and Render" tool. From your site’s Google Search Console dashboard, select “Crawl” from the left navigation, then “Fetch as Google.”
From this page, enter the URL you want to check (or leave blank if you want to check your homepage) and click the “Fetch and Render” button. You also have the option to test either the desktop or mobile version.
In return, you’ll get a side-by-side view of how Googlebot saw your page versus how a visitor to your website would have seen the page. Below, Google will also show you a list of any resources they may not have been able to get for the URL you entered.
Understanding the way websites work lays a great foundation for what we’ll talk about next, which is technical optimizations to help Google understand the pages on your website better.
2. How search engines understand websites
Search engines have gotten incredibly sophisticated, but they can’t (yet) find and interpret web pages quite like a human can. The following sections outline ways you can better deliver content to search engines.
Help search engines understand your content by structuring it with Schema
Imagine being a search engine crawler scanning down a 10,000-word article about how to bake a cake. How do you identify the author, recipe, ingredients, or steps required to bake a cake? This is where schema (Schema.org) markup comes in. It allows you to spoon-feed search engines more specific classifications for what type of information is on your page.
Schema is a way to label or organize your content so that search engines have a better understanding of what certain elements on your web pages are. This code provides structure to your data, which is why schema is often referred to as “structured data.” The process of structuring your data is often referred to as “markup” because you are marking up your content with organizational code.
JSON-LD is Google’s preferred schema markup (announced in May ‘16), which Bing also supports. To view a full list of the thousands of available schema markups, visit Schema.org or view the Google Developers Introduction to Structured Data for additional information on how to implement structured data. After you implement the structured data that best suits your web pages, you can test your markup with Google’s Structured Data Testing Tool.
In addition to helping bots like Google understand what a particular piece of content is about, schema markup can also enable special features to accompany your pages in the SERPs. These special features are referred to as "rich snippets," and you’ve probably seen them in action. They’re things like:
Top Stories carousel
Review stars
Sitelinks search boxes
Recipes
Remember, using structured data can help enable a rich snippet to be present, but does not guarantee it. Other types of rich snippets will likely be added in the future as the use of schema markup increases.
Some last words of advice for schema success:
You can use multiple types of schema markup on a page. However, if you mark up one element, like a product for example, and there are other products listed on the page, you must also mark up those products.
Don’t mark up content that is not visible to visitors and follow Google’s Quality Guidelines. For example, if you add review structured markup to a page, make sure those reviews are actually visible on that page.
If you have duplicate pages, Google asks that you mark up each duplicate page with your structured markup, not just the canonical version.
Provide original and updated (if applicable) content on your structured data pages.
Structured markup should be an accurate reflection of your page.
Try to use the most specific type of schema markup for your content.
Marked-up reviews should not be written by the business. They should be genuine unpaid business reviews from actual customers.
Tell search engines about your preferred pages with canonicalization
When Google crawls the same content on different web pages, it sometimes doesn’t know which page to index in search results. This is why the tag was invented: to help search engines better index the preferred version of content and not all its duplicates.
The tag allows you to tell search engines where the original, master version of a piece of content is located. You’re essentially saying, "Hey search engine! Don’t index this; index this source page instead." So, if you want to republish a piece of content, whether exactly or slightly modified, but don’t want to risk creating duplicate content, the canonical tag is here to save the day.
Proper canonicalization ensures that every unique piece of content on your website has only one URL. To prevent search engines from indexing multiple versions of a single page, Google recommends having a self-referencing canonical tag on every page on your site. Without a canonical tag telling Google which version of your web page is the preferred one, http://www.example.com could get indexed separately from http://example.com, creating duplicates.
"Avoid duplicate content" is an Internet truism, and for good reason! Google wants to reward sites with unique, valuable content — not content that’s taken from other sources and repeated across multiple pages. Because engines want to provide the best searcher experience, they will rarely show multiple versions of the same content, opting instead to show only the canonicalized version, or if a canonical tag does not exist, whichever version they deem most likely to be the original.
Pro tip: Distinguishing between content filtering & content penalties There is no such thing as a duplicate content penalty. However, you should try to keep duplicate content from causing indexing issues by using the tag when possible. When duplicates of a page exist, Google will choose a canonical and filter the others out of search results. That doesn’t mean you’ve been penalized. It just means that Google only wants to show one version of your content.
It’s also very common for websites to have multiple duplicate pages due to sort and filter options. For example, on an e-commerce site, you might have what’s called a faceted navigation that allows visitors to narrow down products to find exactly what they’re looking for, such as a “sort by” feature that reorders results on the product category page from lowest to highest price. This could create a URL that looks something like this: example.com/mens-shirts?sort=price_ascending. Add in more sort/filter options like color, size, material, brand, etc. and just think about all the variations of your main product category page this would create!
To learn more about different types of duplicate content, this post by Dr. Pete helps distill the different nuances.
3. How users interact with websites
In Chapter 1, we said that despite SEO standing for search engine optimization, SEO is as much about people as it is about search engines themselves. That’s because search engines exist to serve searchers. This goal helps explain why Google’s algorithm rewards websites that provide the best possible experiences for searchers, and why some websites, despite having qualities like robust backlink profiles, might not perform well in search.
When we understand what makes their web browsing experience optimal, we can create those experiences for maximum search performance.
Ensuring a positive experience for your mobile visitors
Being that well over half of all web traffic today comes from mobile, it’s safe to say that your website should be accessible and easy to navigate for mobile visitors. In April 2015, Google rolled out an update to its algorithm that would promote mobile-friendly pages over non-mobile-friendly pages. So how can you ensure that your..
https://ift.tt/2PoeXug
0 notes
maryhare96 · 7 years ago
Text
Rewriting the Beginner's Guide to SEO, Chapter 5: Technical Optimization
Posted by BritneyMuller
After a short break, we're back to share our working draft of Chapter 5 of the Beginner's Guide to SEO with you! This one was a whopper, and we're really looking forward to your input. Giving beginner SEOs a solid grasp of just what technical optimization for SEO is and why it matters — without overwhelming them or scaring them off the subject — is a tall order indeed. We'd love to hear what you think: did we miss anything you think is important for beginners to know? Leave us your feedback in the comments!
And in case you're curious, check back on our outline, Chapter One, Chapter Two, Chapter Three, and Chapter Four to see what we've covered so far.
Chapter 5: Technical Optimization Basic technical knowledge will help you optimize your site for search engines and establish credibility with developers.
Now that you’ve crafted valuable content on the foundation of solid keyword research, it’s important to make sure it’s not only readable by humans, but by search engines too!
You don’t need to have a deep technical understanding of these concepts, but it is important to grasp what these technical assets do so that you can speak intelligently about them with developers. Speaking your developers’ language is important because you will likely need them to carry out some of your optimizations. They're unlikely to prioritize your asks if they can’t understand your request or see its importance. When you establish credibility and trust with your devs, you can begin to tear away the red tape that often blocks crucial work from getting done.
Pro tip: SEOs need cross-team support to be effective
It’s vital to have a healthy relationship with your developers so that you can successfully tackle SEO challenges from both sides. Don’t wait until a technical issue causes negative SEO ramifications to involve a developer. Instead, join forces for the planning stage with the goal of avoiding the issues altogether. If you don’t, it can cost you in time and money later.
Beyond cross-team support, understanding technical optimization for SEO is essential if you want to ensure that your web pages are structured for both humans and crawlers. To that end, we’ve divided this chapter into three sections:
How websites work
How search engines understand websites
How users interact with websites
Since the technical structure of a site can have a massive impact on its performance, it’s crucial for everyone to understand these principles. It might also be a good idea to share this part of the guide with your programmers, content writers, and designers so that all parties involved in a site's construction are on the same page.
1. How websites work
If search engine optimization is the process of optimizing a website for search, SEOs need at least a basic understanding of the thing they're optimizing!
Below, we outline the website’s journey from domain name purchase all the way to its fully rendered state in a browser. An important component of the website’s journey is the critical rendering path, which is the process of a browser turning a website’s code into a viewable page.
Knowing this about websites is important for SEOs to understand for a few reasons:
The steps in this webpage assembly process can affect page load times, and speed is not only important for keeping users on your site, but it’s also one of Google’s ranking factors.
Google renders certain resources, like JavaScript, on a “second pass.” Google will look at the page without JavaScript first, then a few days to a few weeks later, it will render JavaScript, meaning SEO-critical elements that are added to the page using JavaScript might not get indexed.
Imagine that the website loading process is your commute to work. You get ready at home, gather your things to bring to the office, and then take the fastest route from your home to your work. It would be silly to put on just one of your shoes, take a longer route to work, drop your things off at the office, then immediately return home to get your other shoe, right? That’s sort of what inefficient websites do. This chapter will teach you how to diagnose where your website might be inefficient, what you can do to streamline, and the positive ramifications on your rankings and user experience that can result from that streamlining.
Before a website can be accessed, it needs to be set up!
Domain name is purchased. Domain names like moz.com are purchased from a domain name registrar such as GoDaddy or HostGator. These registrars are just organizations that manage the reservations of domain names.
Domain name is linked to IP address. The Internet doesn’t understand names like “moz.com” as website addresses without the help of domain name servers (DNS). The Internet uses a series of numbers called an Internet protocol (IP) address (ex: 127.0.0.1), but we want to use names like moz.com because they’re easier for humans to remember. We need to use a DNS to link those human-readable names with machine-readable numbers.
How a website gets from server to browser
User requests domain. Now that the name is linked to an IP address via DNS, people can request a website by typing the domain name directly into their browser or by clicking on a link to the website.
Browser makes requests. That request for a web page prompts the browser to make a DNS lookup request to convert the domain name to its IP address. The browser then makes a request to the server for the code your web page is constructed with, such as HTML, CSS, and JavaScript.
Server sends resources. Once the server receives the request for the website, it sends the website files to be assembled in the searcher’s browser.
Browser assembles the web page. The browser has now received the resources from the server, but it still needs to put it all together and render the web page so that the user can see it in their browser. As the browser parses and organizes all the web page’s resources, it’s creating a Document Object Model (DOM). The DOM is what you can see when you right click + “inspect element” on a web page in your Chrome browser (learn how to inspect elements in other browsers).
Browser makes final requests. The browser will only show a web page after all the page’s necessary code is downloaded, parsed, and executed, so at this point, if the browser needs any additional code in order to show your website, it will make an additional request from your server.
Website appears in browser. Whew! After all that, your website has now been transformed (rendered) from code to what you see in your browser.
Pro tip: Talk to your developers about async!
Something you can bring up with your developers is shortening the critical rendering path by setting scripts to "async" when they’re not needed to render content above the fold, which can make your web pages load faster. Async tells the DOM that it can continue to be assembled while the browser is fetching the scripts needed to display your web page. If the DOM has to pause assembly every time the browser fetches a script (called “render-blocking scripts”), it can substantially slow down your page load.
It would be like going out to eat with your friends and having to pause the conversation every time one of you went up to the counter to order, only resuming once they got back. With async, you and your friends can continue to chat even when one of you is ordering. You might also want to bring up other optimizations that devs can implement to shorten the critical rendering path, such as removing unnecessary scripts entirely, like old tracking scripts.
Now that you know how a website appears in a browser, we’re going to focus on what a website is made of — in other words, the code (programming languages) used to construct those web pages.
The three most common are:
HTML – What a website says (titles, body content, etc.)
CSS – How a website looks (color, fonts, etc.)
JavaScript – How it behaves (interactive, dynamic, etc.)
HTML: What a website says
HTML stands for hypertext markup language, and it serves as the backbone of a website. Elements like headings, paragraphs, lists, and content are all defined in the HTML.
Here’s an example of a webpage, and what its corresponding HTML looks like:
HTML is important for SEOs to know because it’s what lives “under the hood” of any page they create or work on. While your CMS likely doesn’t require you to write your pages in HTML (ex: selecting “hyperlink” will allow you to create a link without you having to type in “a href=”), it is what you’re modifying every time you do something to a web page such as adding content, changing the anchor text of internal links, and so on. Google crawls these HTML elements to determine how relevant your document is to a particular query. In other words, what’s in your HTML plays a huge role in how your web page ranks in Google organic search!
CSS: How a website looks
CSS stands for cascading style sheets, and this is what causes your web pages to take on certain fonts, colors, and layouts. HTML was created to describe content, rather than to style it, so when CSS entered the scene, it was a game-changer. With CSS, web pages could be “beautified” without requiring manual coding of styles into the HTML of every page — a cumbersome process, especially for large sites.
It wasn’t until 2014 that Google’s indexing system began to render web pages more like an actual browser, as opposed to a text-only browser. A black-hat SEO practice that tried to capitalize on Google’s older indexing system was hiding text and links via CSS for the purpose of manipulating search engine rankings. This “hidden text and links” practice is a violation of Google’s quality guidelines.
Components of CSS that SEOs, in particular, should care about:
Since style directives can live in external stylesheet files (CSS files) instead of your page’s HTML, it makes your page less code-heavy, reducing file transfer size and making load times faster.
Browsers still have to download resources like your CSS file, so compressing them can make your web pages load faster, and page speed is a ranking factor.
Having your pages be more content-heavy than code-heavy can lead to better indexing of your site’s content.
Using CSS to hide links and content can get your website manually penalized and removed from Google’s index.
JavaScript: How a website behaves
In the earlier days of the Internet, web pages were built with HTML. When CSS came along, webpage content had the ability to take on some style. When the programming language JavaScript entered the scene, websites could now not only have structure and style, but they could be dynamic.
JavaScript has opened up a lot of opportunities for non-static web page creation. When someone attempts to access a page that is enhanced with this programming language, that user’s browser will execute the JavaScript against the static HTML that the server returned, resulting in a web page that comes to life with some sort of interactivity.
You’ve definitely seen JavaScript in action — you just may not have known it! That’s because JavaScript can do almost anything to a page. It could create a pop up, for example, or it could request third-party resources like ads to display on your page.
JavaScript can pose some problems for SEO, though, since search engines don’t view JavaScript the same way human visitors do. That’s because of client-side versus server-side rendering. Most JavaScript is executed in a client’s browser. With server-side rendering, on the other hand, the files are executed at the server and the server sends them to the browser in their fully rendered state.
SEO-critical page elements such as text, links, and tags that are loaded on the client’s side with JavaScript, rather than represented in your HTML, are invisible from your page’s code until they are rendered. This means that search engine crawlers won’t see what’s in your JavaScript — at least not initially.
Google says that, as long as you’re not blocking Googlebot from crawling your JavaScript files, they’re generally able to render and understand your web pages just like a browser can, which means that Googlebot should see the same things as a user viewing a site in their browser. However, due to this “second wave of indexing” for client-side JavaScript, Google can miss certain elements that are only available once JavaScript is executed.
There are also some other things that could go wrong during Googlebot’s process of rendering your web pages, which can prevent Google from understanding what’s contained in your JavaScript:
You’ve blocked Googlebot from JavaScript resources (ex: with robots.txt, like we learned about in Chapter 2)
Your server can’t handle all the requests to crawl your content
The JavaScript is too complex or outdated for Googlebot to understand
JavaScript doesn’t "lazy load" content into the page until after the crawler has finished with the page and moved on.
Needless to say, while JavaScript does open a lot of possibilities for web page creation, it can also have some serious ramifications for your SEO if you’re not careful. Thankfully, there is a way to check whether Google sees the same thing as your visitors. To see a page how Googlebot views your page, use Google Search Console's "Fetch and Render" tool. From your site’s Google Search Console dashboard, select “Crawl” from the left navigation, then “Fetch as Google.”
From this page, enter the URL you want to check (or leave blank if you want to check your homepage) and click the “Fetch and Render” button. You also have the option to test either the desktop or mobile version.
In return, you’ll get a side-by-side view of how Googlebot saw your page versus how a visitor to your website would have seen the page. Below, Google will also show you a list of any resources they may not have been able to get for the URL you entered.
Understanding the way websites work lays a great foundation for what we’ll talk about next, which is technical optimizations to help Google understand the pages on your website better.
2. How search engines understand websites
Search engines have gotten incredibly sophisticated, but they can’t (yet) find and interpret web pages quite like a human can. The following sections outline ways you can better deliver content to search engines.
Help search engines understand your content by structuring it with Schema
Imagine being a search engine crawler scanning down a 10,000-word article about how to bake a cake. How do you identify the author, recipe, ingredients, or steps required to bake a cake? This is where schema (Schema.org) markup comes in. It allows you to spoon-feed search engines more specific classifications for what type of information is on your page.
Schema is a way to label or organize your content so that search engines have a better understanding of what certain elements on your web pages are. This code provides structure to your data, which is why schema is often referred to as “structured data.” The process of structuring your data is often referred to as “markup” because you are marking up your content with organizational code.
JSON-LD is Google’s preferred schema markup (announced in May ‘16), which Bing also supports. To view a full list of the thousands of available schema markups, visit Schema.org or view the Google Developers Introduction to Structured Data for additional information on how to implement structured data. After you implement the structured data that best suits your web pages, you can test your markup with Google’s Structured Data Testing Tool.
In addition to helping bots like Google understand what a particular piece of content is about, schema markup can also enable special features to accompany your pages in the SERPs. These special features are referred to as "rich snippets," and you’ve probably seen them in action. They’re things like:
Top Stories carousel
Review stars
Sitelinks search boxes
Recipes
Remember, using structured data can help enable a rich snippet to be present, but does not guarantee it. Other types of rich snippets will likely be added in the future as the use of schema markup increases.
Some last words of advice for schema success:
You can use multiple types of schema markup on a page. However, if you mark up one element, like a product for example, and there are other products listed on the page, you must also mark up those products.
Don’t mark up content that is not visible to visitors and follow Google’s Quality Guidelines. For example, if you add review structured markup to a page, make sure those reviews are actually visible on that page.
If you have duplicate pages, Google asks that you mark up each duplicate page with your structured markup, not just the canonical version.
Provide original and updated (if applicable) content on your structured data pages.
Structured markup should be an accurate reflection of your page.
Try to use the most specific type of schema markup for your content.
Marked-up reviews should not be written by the business. They should be genuine unpaid business reviews from actual customers.
Tell search engines about your preferred pages with canonicalization
When Google crawls the same content on different web pages, it sometimes doesn’t know which page to index in search results. This is why the tag was invented: to help search engines better index the preferred version of content and not all its duplicates.
The tag allows you to tell search engines where the original, master version of a piece of content is located. You’re essentially saying, "Hey search engine! Don’t index this; index this source page instead." So, if you want to republish a piece of content, whether exactly or slightly modified, but don’t want to risk creating duplicate content, the canonical tag is here to save the day.
Proper canonicalization ensures that every unique piece of content on your website has only one URL. To prevent search engines from indexing multiple versions of a single page, Google recommends having a self-referencing canonical tag on every page on your site. Without a canonical tag telling Google which version of your web page is the preferred one, http://www.example.com could get indexed separately from http://example.com, creating duplicates.
"Avoid duplicate content" is an Internet truism, and for good reason! Google wants to reward sites with unique, valuable content — not content that’s taken from other sources and repeated across multiple pages. Because engines want to provide the best searcher experience, they will rarely show multiple versions of the same content, opting instead to show only the canonicalized version, or if a canonical tag does not exist, whichever version they deem most likely to be the original.
Pro tip: Distinguishing between content filtering & content penalties There is no such thing as a duplicate content penalty. However, you should try to keep duplicate content from causing indexing issues by using the tag when possible. When duplicates of a page exist, Google will choose a canonical and filter the others out of search results. That doesn’t mean you’ve been penalized. It just means that Google only wants to show one version of your content.
It’s also very common for websites to have multiple duplicate pages due to sort and filter options. For example, on an e-commerce site, you might have what’s called a faceted navigation that allows visitors to narrow down products to find exactly what they’re looking for, such as a “sort by” feature that reorders results on the product category page from lowest to highest price. This could create a URL that looks something like this: example.com/mens-shirts?sort=price_ascending. Add in more sort/filter options like color, size, material, brand, etc. and just think about all the variations of your main product category page this would create!
To learn more about different types of duplicate content, this post by Dr. Pete helps distill the different nuances.
3. How users interact with websites
In Chapter 1, we said that despite SEO standing for search engine optimization, SEO is as much about people as it is about search engines themselves. That’s because search engines exist to serve searchers. This goal helps explain why Google’s algorithm rewards websites that provide the best possible experiences for searchers, and why some websites, despite having qualities like robust backlink profiles, might not perform well in search.
When we understand what makes their web browsing experience optimal, we can create those experiences for maximum search performance.
Ensuring a positive experience for your mobile visitors
Being that well over half of all web traffic today comes from mobile, it’s safe to say that your website should be accessible and easy to navigate for mobile visitors. In April 2015, Google rolled out an update to its algorithm that would promote mobile-friendly pages over non-mobile-friendly pages. So how can you ensure that your..
https://ift.tt/2PoeXug
0 notes
byronheeutgm · 7 years ago
Text
Rewriting the Beginner's Guide to SEO, Chapter 5: Technical Optimization
Posted by BritneyMuller
After a short break, we're back to share our working draft of Chapter 5 of the Beginner's Guide to SEO with you! This one was a whopper, and we're really looking forward to your input. Giving beginner SEOs a solid grasp of just what technical optimization for SEO is and why it matters — without overwhelming them or scaring them off the subject — is a tall order indeed. We'd love to hear what you think: did we miss anything you think is important for beginners to know? Leave us your feedback in the comments!
And in case you're curious, check back on our outline, Chapter One, Chapter Two, Chapter Three, and Chapter Four to see what we've covered so far.
Chapter 5: Technical Optimization Basic technical knowledge will help you optimize your site for search engines and establish credibility with developers.
Now that you’ve crafted valuable content on the foundation of solid keyword research, it’s important to make sure it’s not only readable by humans, but by search engines too!
You don’t need to have a deep technical understanding of these concepts, but it is important to grasp what these technical assets do so that you can speak intelligently about them with developers. Speaking your developers’ language is important because you will likely need them to carry out some of your optimizations. They're unlikely to prioritize your asks if they can’t understand your request or see its importance. When you establish credibility and trust with your devs, you can begin to tear away the red tape that often blocks crucial work from getting done.
Pro tip: SEOs need cross-team support to be effective
It’s vital to have a healthy relationship with your developers so that you can successfully tackle SEO challenges from both sides. Don’t wait until a technical issue causes negative SEO ramifications to involve a developer. Instead, join forces for the planning stage with the goal of avoiding the issues altogether. If you don’t, it can cost you in time and money later.
Beyond cross-team support, understanding technical optimization for SEO is essential if you want to ensure that your web pages are structured for both humans and crawlers. To that end, we’ve divided this chapter into three sections:
How websites work
How search engines understand websites
How users interact with websites
Since the technical structure of a site can have a massive impact on its performance, it’s crucial for everyone to understand these principles. It might also be a good idea to share this part of the guide with your programmers, content writers, and designers so that all parties involved in a site's construction are on the same page.
1. How websites work
If search engine optimization is the process of optimizing a website for search, SEOs need at least a basic understanding of the thing they're optimizing!
Below, we outline the website’s journey from domain name purchase all the way to its fully rendered state in a browser. An important component of the website’s journey is the critical rendering path, which is the process of a browser turning a website’s code into a viewable page.
Knowing this about websites is important for SEOs to understand for a few reasons:
The steps in this webpage assembly process can affect page load times, and speed is not only important for keeping users on your site, but it’s also one of Google’s ranking factors.
Google renders certain resources, like JavaScript, on a “second pass.” Google will look at the page without JavaScript first, then a few days to a few weeks later, it will render JavaScript, meaning SEO-critical elements that are added to the page using JavaScript might not get indexed.
Imagine that the website loading process is your commute to work. You get ready at home, gather your things to bring to the office, and then take the fastest route from your home to your work. It would be silly to put on just one of your shoes, take a longer route to work, drop your things off at the office, then immediately return home to get your other shoe, right? That’s sort of what inefficient websites do. This chapter will teach you how to diagnose where your website might be inefficient, what you can do to streamline, and the positive ramifications on your rankings and user experience that can result from that streamlining.
Before a website can be accessed, it needs to be set up!
Domain name is purchased. Domain names like moz.com are purchased from a domain name registrar such as GoDaddy or HostGator. These registrars are just organizations that manage the reservations of domain names.
Domain name is linked to IP address. The Internet doesn’t understand names like “moz.com” as website addresses without the help of domain name servers (DNS). The Internet uses a series of numbers called an Internet protocol (IP) address (ex: 127.0.0.1), but we want to use names like moz.com because they’re easier for humans to remember. We need to use a DNS to link those human-readable names with machine-readable numbers.
How a website gets from server to browser
User requests domain. Now that the name is linked to an IP address via DNS, people can request a website by typing the domain name directly into their browser or by clicking on a link to the website.
Browser makes requests. That request for a web page prompts the browser to make a DNS lookup request to convert the domain name to its IP address. The browser then makes a request to the server for the code your web page is constructed with, such as HTML, CSS, and JavaScript.
Server sends resources. Once the server receives the request for the website, it sends the website files to be assembled in the searcher’s browser.
Browser assembles the web page. The browser has now received the resources from the server, but it still needs to put it all together and render the web page so that the user can see it in their browser. As the browser parses and organizes all the web page’s resources, it’s creating a Document Object Model (DOM). The DOM is what you can see when you right click + “inspect element” on a web page in your Chrome browser (learn how to inspect elements in other browsers).
Browser makes final requests. The browser will only show a web page after all the page’s necessary code is downloaded, parsed, and executed, so at this point, if the browser needs any additional code in order to show your website, it will make an additional request from your server.
Website appears in browser. Whew! After all that, your website has now been transformed (rendered) from code to what you see in your browser.
Pro tip: Talk to your developers about async!
Something you can bring up with your developers is shortening the critical rendering path by setting scripts to "async" when they’re not needed to render content above the fold, which can make your web pages load faster. Async tells the DOM that it can continue to be assembled while the browser is fetching the scripts needed to display your web page. If the DOM has to pause assembly every time the browser fetches a script (called “render-blocking scripts”), it can substantially slow down your page load.
It would be like going out to eat with your friends and having to pause the conversation every time one of you went up to the counter to order, only resuming once they got back. With async, you and your friends can continue to chat even when one of you is ordering. You might also want to bring up other optimizations that devs can implement to shorten the critical rendering path, such as removing unnecessary scripts entirely, like old tracking scripts.
Now that you know how a website appears in a browser, we’re going to focus on what a website is made of — in other words, the code (programming languages) used to construct those web pages.
The three most common are:
HTML – What a website says (titles, body content, etc.)
CSS – How a website looks (color, fonts, etc.)
JavaScript – How it behaves (interactive, dynamic, etc.)
HTML: What a website says
HTML stands for hypertext markup language, and it serves as the backbone of a website. Elements like headings, paragraphs, lists, and content are all defined in the HTML.
Here’s an example of a webpage, and what its corresponding HTML looks like:
HTML is important for SEOs to know because it’s what lives “under the hood” of any page they create or work on. While your CMS likely doesn’t require you to write your pages in HTML (ex: selecting “hyperlink” will allow you to create a link without you having to type in “a href=”), it is what you’re modifying every time you do something to a web page such as adding content, changing the anchor text of internal links, and so on. Google crawls these HTML elements to determine how relevant your document is to a particular query. In other words, what’s in your HTML plays a huge role in how your web page ranks in Google organic search!
CSS: How a website looks
CSS stands for cascading style sheets, and this is what causes your web pages to take on certain fonts, colors, and layouts. HTML was created to describe content, rather than to style it, so when CSS entered the scene, it was a game-changer. With CSS, web pages could be “beautified” without requiring manual coding of styles into the HTML of every page — a cumbersome process, especially for large sites.
It wasn’t until 2014 that Google’s indexing system began to render web pages more like an actual browser, as opposed to a text-only browser. A black-hat SEO practice that tried to capitalize on Google’s older indexing system was hiding text and links via CSS for the purpose of manipulating search engine rankings. This “hidden text and links” practice is a violation of Google’s quality guidelines.
Components of CSS that SEOs, in particular, should care about:
Since style directives can live in external stylesheet files (CSS files) instead of your page’s HTML, it makes your page less code-heavy, reducing file transfer size and making load times faster.
Browsers still have to download resources like your CSS file, so compressing them can make your web pages load faster, and page speed is a ranking factor.
Having your pages be more content-heavy than code-heavy can lead to better indexing of your site’s content.
Using CSS to hide links and content can get your website manually penalized and removed from Google’s index.
JavaScript: How a website behaves
In the earlier days of the Internet, web pages were built with HTML. When CSS came along, webpage content had the ability to take on some style. When the programming language JavaScript entered the scene, websites could now not only have structure and style, but they could be dynamic.
JavaScript has opened up a lot of opportunities for non-static web page creation. When someone attempts to access a page that is enhanced with this programming language, that user’s browser will execute the JavaScript against the static HTML that the server returned, resulting in a web page that comes to life with some sort of interactivity.
You’ve definitely seen JavaScript in action — you just may not have known it! That’s because JavaScript can do almost anything to a page. It could create a pop up, for example, or it could request third-party resources like ads to display on your page.
JavaScript can pose some problems for SEO, though, since search engines don’t view JavaScript the same way human visitors do. That’s because of client-side versus server-side rendering. Most JavaScript is executed in a client’s browser. With server-side rendering, on the other hand, the files are executed at the server and the server sends them to the browser in their fully rendered state.
SEO-critical page elements such as text, links, and tags that are loaded on the client’s side with JavaScript, rather than represented in your HTML, are invisible from your page’s code until they are rendered. This means that search engine crawlers won’t see what’s in your JavaScript — at least not initially.
Google says that, as long as you’re not blocking Googlebot from crawling your JavaScript files, they’re generally able to render and understand your web pages just like a browser can, which means that Googlebot should see the same things as a user viewing a site in their browser. However, due to this “second wave of indexing” for client-side JavaScript, Google can miss certain elements that are only available once JavaScript is executed.
There are also some other things that could go wrong during Googlebot’s process of rendering your web pages, which can prevent Google from understanding what’s contained in your JavaScript:
You’ve blocked Googlebot from JavaScript resources (ex: with robots.txt, like we learned about in Chapter 2)
Your server can’t handle all the requests to crawl your content
The JavaScript is too complex or outdated for Googlebot to understand
JavaScript doesn’t "lazy load" content into the page until after the crawler has finished with the page and moved on.
Needless to say, while JavaScript does open a lot of possibilities for web page creation, it can also have some serious ramifications for your SEO if you’re not careful. Thankfully, there is a way to check whether Google sees the same thing as your visitors. To see a page how Googlebot views your page, use Google Search Console's "Fetch and Render" tool. From your site’s Google Search Console dashboard, select “Crawl” from the left navigation, then “Fetch as Google.”
From this page, enter the URL you want to check (or leave blank if you want to check your homepage) and click the “Fetch and Render” button. You also have the option to test either the desktop or mobile version.
In return, you’ll get a side-by-side view of how Googlebot saw your page versus how a visitor to your website would have seen the page. Below, Google will also show you a list of any resources they may not have been able to get for the URL you entered.
Understanding the way websites work lays a great foundation for what we’ll talk about next, which is technical optimizations to help Google understand the pages on your website better.
2. How search engines understand websites
Search engines have gotten incredibly sophisticated, but they can’t (yet) find and interpret web pages quite like a human can. The following sections outline ways you can better deliver content to search engines.
Help search engines understand your content by structuring it with Schema
Imagine being a search engine crawler scanning down a 10,000-word article about how to bake a cake. How do you identify the author, recipe, ingredients, or steps required to bake a cake? This is where schema (Schema.org) markup comes in. It allows you to spoon-feed search engines more specific classifications for what type of information is on your page.
Schema is a way to label or organize your content so that search engines have a better understanding of what certain elements on your web pages are. This code provides structure to your data, which is why schema is often referred to as “structured data.” The process of structuring your data is often referred to as “markup” because you are marking up your content with organizational code.
JSON-LD is Google’s preferred schema markup (announced in May ‘16), which Bing also supports. To view a full list of the thousands of available schema markups, visit Schema.org or view the Google Developers Introduction to Structured Data for additional information on how to implement structured data. After you implement the structured data that best suits your web pages, you can test your markup with Google’s Structured Data Testing Tool.
In addition to helping bots like Google understand what a particular piece of content is about, schema markup can also enable special features to accompany your pages in the SERPs. These special features are referred to as "rich snippets," and you’ve probably seen them in action. They’re things like:
Top Stories carousel
Review stars
Sitelinks search boxes
Recipes
Remember, using structured data can help enable a rich snippet to be present, but does not guarantee it. Other types of rich snippets will likely be added in the future as the use of schema markup increases.
Some last words of advice for schema success:
You can use multiple types of schema markup on a page. However, if you mark up one element, like a product for example, and there are other products listed on the page, you must also mark up those products.
Don’t mark up content that is not visible to visitors and follow Google’s Quality Guidelines. For example, if you add review structured markup to a page, make sure those reviews are actually visible on that page.
If you have duplicate pages, Google asks that you mark up each duplicate page with your structured markup, not just the canonical version.
Provide original and updated (if applicable) content on your structured data pages.
Structured markup should be an accurate reflection of your page.
Try to use the most specific type of schema markup for your content.
Marked-up reviews should not be written by the business. They should be genuine unpaid business reviews from actual customers.
Tell search engines about your preferred pages with canonicalization
When Google crawls the same content on different web pages, it sometimes doesn’t know which page to index in search results. This is why the tag was invented: to help search engines better index the preferred version of content and not all its duplicates.
The tag allows you to tell search engines where the original, master version of a piece of content is located. You’re essentially saying, "Hey search engine! Don’t index this; index this source page instead." So, if you want to republish a piece of content, whether exactly or slightly modified, but don’t want to risk creating duplicate content, the canonical tag is here to save the day.
Proper canonicalization ensures that every unique piece of content on your website has only one URL. To prevent search engines from indexing multiple versions of a single page, Google recommends having a self-referencing canonical tag on every page on your site. Without a canonical tag telling Google which version of your web page is the preferred one, http://www.example.com could get indexed separately from http://example.com, creating duplicates.
"Avoid duplicate content" is an Internet truism, and for good reason! Google wants to reward sites with unique, valuable content — not content that’s taken from other sources and repeated across multiple pages. Because engines want to provide the best searcher experience, they will rarely show multiple versions of the same content, opting instead to show only the canonicalized version, or if a canonical tag does not exist, whichever version they deem most likely to be the original.
Pro tip: Distinguishing between content filtering & content penalties There is no such thing as a duplicate content penalty. However, you should try to keep duplicate content from causing indexing issues by using the tag when possible. When duplicates of a page exist, Google will choose a canonical and filter the others out of search results. That doesn’t mean you’ve been penalized. It just means that Google only wants to show one version of your content.
It’s also very common for websites to have multiple duplicate pages due to sort and filter options. For example, on an e-commerce site, you might have what’s called a faceted navigation that allows visitors to narrow down products to find exactly what they’re looking for, such as a “sort by” feature that reorders results on the product category page from lowest to highest price. This could create a URL that looks something like this: example.com/mens-shirts?sort=price_ascending. Add in more sort/filter options like color, size, material, brand, etc. and just think about all the variations of your main product category page this would create!
To learn more about different types of duplicate content, this post by Dr. Pete helps distill the different nuances.
3. How users interact with websites
In Chapter 1, we said that despite SEO standing for search engine optimization, SEO is as much about people as it is about search engines themselves. That’s because search engines exist to serve searchers. This goal helps explain why Google’s algorithm rewards websites that provide the best possible experiences for searchers, and why some websites, despite having qualities like robust backlink profiles, might not perform well in search.
When we understand what makes their web browsing experience optimal, we can create those experiences for maximum search performance.
Ensuring a positive experience for your mobile visitors
Being that well over half of all web traffic today comes from mobile, it’s safe to say that your website should be accessible and easy to navigate for mobile visitors. In April 2015, Google rolled out an update to its algorithm that would promote mobile-friendly pages over non-mobile-friendly pages. So how can you ensure that your..
https://ift.tt/2PoeXug
0 notes