#using the que feature for my sanity

[captain-astors]

Don't actually have the game, but who am I to pass up the chance to draw a dragon fellow.

[independentartistbuzz]

7 FROM THE WOMEN: MARLA LEWIS

We are delighted to welcome Marla Lewis, New Jersey born singer, songwriter and educator currently taking the World Indie Charts by storm with her brand new single "Te Quiero A Ti"!

A dynamic and versatile musician, her journey began in 1953 with piano lessons and a memorable TV performance.

After writing her first song in 1961 and dedicating herself to music in 1963, Marla spent a decade performing solo before transitioning to teaching English as a Second Language. There, she created award-winning children's music that captured hearts and minds.

Post-retirement in 2010, Marla returned to her musical roots, collaborating with producer Bob Stander and earning a GRAMMY for her contribution to "All About Bullies…Big and Small." In recent years, she has embraced smooth jazz, releasing "Songbook" in 2021 and "Songbook Vol. 2" in 2023, with her single "Enchantee" topping the World Indie charts.

Her latest single "Te Quiero A Ti" has reached both #13 and #22 on the World Indie Charts!

We connected with Marla for an exclusive 7 From the Women Interview:

What Have You Been Working To Promote Lately?

On May 23, I released a new single, both in English and in Spanish, called “Te Quiero a Ti,” which means simply, I Love You.

It’s a bossa nova tune that features lush piano, flute, electric guitar, drums, and background vocals a la the Manhattan Transfer.  I wrote the music, Dave Kinnoin wrote the lyrics, and Melissa Sanley wrote the Spanish translation.  I always wanted to sing that song in Spanish, so this is my dream come true! 

There’s a backstory here: I met Melissa when I signed up for a Peer Networking program for voting members of the GRAMMYS (I am one), and they paired me up with her. Talk about being touched by an angel! I played this song for her, which I had previously recorded as “Quiero Que Si” (on my first smooth jazz album, SONGBOOK). Melissa informed me that the title was NOT correct Spanish! She then revised the title, wrote the Spanish translation, did the cover art, AND created a Spanish lyric video! Plus, she coached me on every line of the lyric. I feel like I have been blessed! At this writing, Te Quiero a Ti is #13 on the World Indie Charts and # 15 on the Euro Indie Charts!

Here is the link to my tune on Spotify:

 And here is the link to the Spanish lyric video:

Please tell us about your favorite song written, recorded or produced by another woman and why it’s meaningful to you.

My answer depends upon the day! I think of “Strange Fruit” by Billie Holiday.  How courageous she was to sing it during her brief time on earth. The metaphor of that song is so powerful. I shake my head at the way humans have treated each other, and thank her for recording that song. I also thank heaven for microphones, without which Billie would not have been able to record, since her natural voice was not very strong.

I also think of Joni Mitchell – how can I name one song? For now, I’ll choose “Troubled Child” from COURT AND SPARK. This is one of the tunes I played over and over and over! The melody, harmonies and arrangement are like chocolate to my ears, particularly the use of the major second, the muted trumpet, and Joni’s smooth vocals.

As with all of her lyrics, you can easily visualize the scene, as in this case, of a kid fighting for his sanity in a mental hospital.

And Laura Nyro – “Save the Country.” Another tune I put on endless repeat. Had me jumping for joy!

What does it mean to you to be a woman making music/in the music business today and do you feel a responsibility to other women to create messages and themes in your music? 

I want to create the best songs I possibly can. Period. I’m not “out there” touring and performing, so I’m not in the fray.  I write songs at home, sometimes I collaborate, and I go to songwriter workshops to improve my craft.  I love the process of creating a song; that is one of my greatest pleasures in life! I’m not “in the business” per se, and I think if I were a man, I would have the same goals and desires for my music as I do now. I feel responsible to my audience – male and female -- to do my best and continue to improve; that sums it up.

I am a retired teacher, thrilled to have more time than ever to create! I wish for only one thing: to have at least one of my songs recorded by a great (female) vocalist, say, Bette Midler? Or Gloria Estefan!  Oh, wait, here’s another: I would like at least onbe of my songs to be added to the Great American Songbook.

As for messages and themes, there is one I’d like to explore in my next song: my older self, traveling back in time to guide my anxious, confused younger self!

What female artists have inspired you and influenced you? 

Joni Mitchell, Laura Nyro, Ella Fitzgerald, Billie Holiday, Phoebe Snow, Bonnie Raitt

Who was the first female artist that made want to create music / be in the business? 

Joan Baez, as soon as I learned to play guitar at age 13, then Joni Mitchell. I wanted to be just like them! They “made it” in a man’s world. Ella did, too. To think shows like “Queen for a Day” aired back then

Do you consider yourself a feminist? If so, why or why not?

I want all people to be treated equal and respect each other, just as Martin Luther King was rooting for everyone, not just Black people. This has been damn near impossible for people to do, since the beginning of time!

If you could collaborate with any other female artists, who would you choose? 

This is the toughest question of all! I’d like to collaborate with a fellow smooth jazz artist, but very few of the female jazz greats of today write songs. 

I feel too shy to approach the incredible Cecile McCloran Salvant. I’d also consider Diana Krall, who wrote songs with her husband, Elvis Costello.  That album wasn’t well received…the only smooth jazz songwriter I can think of today is Michael Franks.  Even male recording artists in the jazz genre stick to the old standards!

Connect with Marla Lewis:

Website // Facebook // Instagram // Twitter // Spotify // YouTube

[writingsofadream]

Masterpiece | Part I

Pairing : Yoongi x Reader

Story : He’s looking for heartbreak and inspiration, and you’re just looking for a new laptop.

Set during the writing and recording period of Love Yourself: Tear. Will involve angst, fluff, and smut. Multiple chapters to follow! 2.3k words in this one :)

♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬ ♬

His hands were a flurry over the keys as he played each note, the individual chords striking through the otherwise silent air. The large dance studio was completely empty, apart from a man dressed in black playing the lonely piano in the corner. Moonlight shone in through the window, illuminating the floor around him and the Big Hit logo plastered to the wall. Another late night. Another song. 

Each key is like another piece of the puzzle to Yoongi. And each fits incorrectly. They bounce back at him disobediently, to the point where frustration builds and he slams down the top. The bang echoes monotonously. 

Yoongi brings his hands to his face, elbows resting on the cool, hard wood of the instrument. It agonises him to no avail, yet he returns every night. Working on songs for their new album was hard, yea, but even harder when he had no fucking inspiration. Breathing in deeply, he runs his hands through his jet-black dyed hair. He needs a drink. Time to head home. 

Pushing open the door to his room, he enters it silently as a mouse. The other members had no doubt been asleep for hours now, and Namjoon’s soft snoring resonates through their shared wall. He finds it soothing, having the same effect as familiar and calming white noise. Plunking down onto the freshly made bed, he sinks into the mattress a little as he sits perched on the edge. With a small grunt he pulls the Puma sneakers from his feet, followed by his socks. Keeping his sweats on, he pulls his shirt over his head as the night is somewhat warm, thanks to Taehyung’s incessant overuse of the heating system. That boy could live in the Sahara Desert and still complain that it was “a bit chilly, hyung”. Yoongi runs his hands through his hair again, swallowing dryly before reaching for the small cupboard compartment of the bedside table. Ah, rum. Exactly what he needed. 

Plodding into the kitchen, he pulls Jungkook’s coke from the fridge. He pours himself a glass, slowly and steadily. The drink looks all too appealing, half rum and half stolen soft drink. Replacing the bottle, the makes his way back to his room to avoid being caught red-handed. Jungkook didn’t take lightly to his snacks and drinks being stolen, Hoseok knew that all too well. What would he be without his friends, he though to himself as he swigged the drink. They were his family, his every moment. Everything he did, said, encountered. It all came back to something about them, and he was grateful for it. They’d made him a better person. But somehow, it wasn’t enough. Not enough to write a love song about anyway. 

Love Yourself. Their new album was the Tear part, that much they had decided. But Yoongi was yet to write his part. He’d only ever broken hearts in his life, and a few bones; though not his either. The fights he’d had he’d won, romantically they were emotionally and through words. In Daegu there’d been a few physical ones. Some kid that doubted his basketball skills then tried to fight him when he’d kicked the kid’s ass. He snorted back a laugh at the memory. He’d gotten in big trouble for that one, but he’d been young and hadn’t cared. Who would’ve? All the kids on his block got into fist fights, his mum should’ve just been proud he’d won. 

Suppressing a yawn, Yoongi set the glass onto his bedside table, mentally bookmarking a reminder to get rid of the evidence in the morning. No matter how many fights he’d won, he didn’t have a chance against Jungkook anymore. That kid? A muscle pig. 

Rolling over into bed, he pulled the covers up over him. Tomorrow he’d write the song, he was sure of it. He’d just ask someone else, get some more ideas flowing about heartbreak and shit. Maybe he could call an ex, he thought for a second, then decided firmly against it. 

___

You pulled the last of the coffee from the machine, seeing there definitely wasn’t enough left to keep you going. Housemates weren’t all they were cracked up to be, that was for sure. Rolling your eyes, you called out to the culprit at hand. 

“Sar? Why the fuck didn’t you refill the coffee after you used it all?” 

On que, your so-called ‘friend’ comes rushing out of her room, hurriedly doing up the buttons to her coffee shop uniform. 

“Shit, Y/N, my bad! I know we had that agreement, but I totallyyyyy forget! Whoopsie!” At this, she chucks you a half-assed smile before dropping it just as quickly as it had appeared. Turning back, he grabs her Gucci bag from the couch. If only she could make rent in time, you thought saltily to yourself. 

“I’ve gotta blast, Y/N. Have a good one, babes.” She throws a little wave your way before disappearing out the door in a rush of overpriced perfume and ugly green. The door bangs shut after her, and you almost let out a sigh of relief. Dealing with her at work on shared shifts was hellish, so you’d swapped it with someone else in a desperate attempt for some time away from her. And, judging by the clock on the kitchen wall, you had approximately eight hours before she made her way back into your life. 

Hopping off the barstool, your footsteps tapped on the cold tiled floor as you made your way into your one place of true solitude - your bedroom. Warm and inviting, your bed called you back to it but you resisted the urge. It simply wouldn’t be right to waste the day sleeping, especially with the big paper you had coming up. Seoul National University was a lot harder then you’d thought it would be, yet you were still infinitely grateful to be attending. It was one of the most prestigious universities in the country, and your parents had cried when you’d announced the news. Hell, you’d cried a fair bit too. Both out of happiness and sadness, you supposed. Melancholic, that was the feeling. Being so far from your family hurt, but it was your dream and you couldn’t exactly turn it down. 

Pulling out your laptop, you flicked the screen up waiting to be met by the glowing Apple logo. Nothing. Pressing the power button, you waited a little longer. Nothing. Impatient, you pressed it harder and repeatedly. Definitely nothing. Your six year old, hand me down MacBook had finally bit the dust. Fuck. How the hell were you going to pay for a new one? 

Slamming it shut, you tried not to burst out into various expletives for the sake of your neighbours and probably your own sanity. A brush against your leg brings your attention down to the carpet, and you’re happy for the distraction as you feel the tears prick at your eyes. 

“Hey, Lil Meow Meow.” 

Your unfortunately-named cat pricks his ears up at the noise of his name, giving you a small meow and another brush to your leg that unmistakably screamed “pat me, human.” Complying, you scratch the black and white cat in the spot just below his chin but before his chest, his absolute favourite spot. He starts purring, and you smile at the little animal that somehow makes every day just a little easier to cope with. 

“Time to go spend all my savings, Lil Meow Meow.” You mumble at the cat, who offers nothing more than a few more insistent purrs. 

__

Yoongi walked into the store, dressed in black from head to toe once again. With the hood of his Kendrick Lamar ‘DAMN’ hoodie pulled up and the black facemask covering his features, he hadn’t been recognised once. Which was fucking good, because he didn’t have any security with him either. The small electronics store was his favourite to go to, mainly because he knew the owner and could order stuff in discreetly and efficiently. A lot of the time you couldn’t trust the bigger brands or outlets; a bad experience had taught him that. He’d been completely ripped off, all because the people knew he had money. Well, his friend knew and didn’t give a shit. Which was why he came here instead. 

The small shop was tucked away down one of Seoul’s alleyways, and apart from the flickering sign that motioned it was ‘open’, people mainly walked straight by it without even noticing. Bad for his friend’s business, but good for Yoongi. 

“Sugaaaaa!” The blonde man behind the counter lit up at the sight of him, rising from his laid-back position on the small chair nestled beside the till. 

“Whatcha here for, my man?” The man raises an eyebrow at the question, waiting for Yoongi’s reply. 

“Hey, Chaen. Just a MacBook, thanks. Mine’s full and honestly, I can’t be fucked to clear it.”

His friend laughs at the answer, throwing his head back and shaking it simultaneously. 

“I can’t believe you, Yoongs. What I’d do with that kind of money, man…” Chaen shakes his head in amusement now, heading out the back to fetch his friend the last of the MacBooks he has in stock. 

__

The rain is heavier than you thought, and you find yourself desperately pulling your raincoat tight around you. 

“Shit!” You exclaim, as the hood flicks back in the wind and your hair is exposed to the wetness for a second. Jerking it back up, you finally reach the alleyway that your phone is displaying through a water droplet-covered screen. Naver had recommended it to you, apparently a pretty good place to find new and refurbished MacBooks. Glancing to your left, you see a small purple neon sign. It flashes the promising word ‘OPEN’ at you, and you make for the door in a hurry to get out of the city’s rain. Pushing the door open, the small bell rings as you do. A man in black is standing at the counter, ominously hiding his hair and body in the dark hoodie. His black jeans are tight on his legs, leading to slightly damp black Puma sneakers. Taking off your raincoat, you turned away from the stranger to hang it on the coat stand by the door. Shaking your head a little, your slightly damp hair fell against your face in what you could only imagine was highly unflattering. When you turned back, the stranger was facing you. 

His black facemask was overly uninviting, as was his general demeanour. He stood in a cold, strong way, like an immovable rock. His eyes were glistening in the dull light of the shop, and you felt a shiver run down you that had absolutely nothing to do with the weather. 

“Do you..work here?” Your question incites a chuckle from the stranger, who pulls down his facemask to speak to you. He’s handsome. Really handsome. Then he replies to you, a smile tugging at the corner of his lips. 

“Nah, but the guy who does is about to come back.” He nods his head to the door labeled ‘back room’, and you realise that must be where this dingy, small shop’s owner must be. 

“Oh…thanks.” You swallow, unsure of what to say. He breaks the small silence quickly, motioning with a hand to the spot at the counter by his side. Scurrying up, you stand awkwardly next to him. He smells good, and his hand is resting on the wood of the desk inches away from you. You can’t help but notice his long, slender fingers, veiny and attractive. And on one of those long fingers is a ring, sitting on the index. It’s silver and relatively plain, but you can tell straight away it’s expensive. It has the shine to it that only expensive jewellery has, with not a single scratch or bronzing to be seen. If he was rich, why was he shopping in here? 

You’re jerked from your thoughts and the growing silence by the sound of a swinging door, accompanied by who you can only assume is the owner. He’s blonde and a little chubby, though his face seems friendly and immediately puts you at ease. 

“Here you go, Min. Last one I’ve got, and only 65,000 won.” The stranger next to you smiles, and opens his mouth to speak. You beat him to it. 

‘What? No, I need it!” You exclaim, bringing your hands down on the box with an audible thump. Both men turn to look at you, surprise clear on their faces. 

“I’m sorry?” The stranger’s question is cool and emotionless, and he cocks an eyebrow with his question. The store owner just stands there staring at you, his furrowed brow confused.

Shit. Now you need to rationalise that.

“My laptop’s broken. I have a paper, Seoul university, I can’t fail and it’s hard and I don’t have a lot of money so I can’t buy one brand new and the taxi ride here was expensive enough and that ring looks like it cost a pretty penny and you see, I NEED that laptop!” Out of breath, you stare the stranger down with your eyes, only to see amusement in his. He chuckles, then pushes it your way.

“What’s your name?” His question catches you off guard, having expected an argument to follow your outburst. 

“What?” Realising your surprised answer-question sounds rude, you hurriedly correct yourself. “Y/N. I’m Y/N.” He bites his lip a little, and something deep in your stomach flickers for a second. 

“Tell you what, Y/N, you can have the laptop. In fact, I’ll buy it for you.” His hand pushes it even further towards you, and you look at it questioningly. 

“Wait…what?” 

[humphreycochrane90-blog]

Real Estate Properties For Sale Or Rent In Tallinn, Harjumaa, Area Guide

If there is one part of the house that best reflects our personality, it is probably the bedroom. Kuid ärge muretsege, siit leiate tohutul hulgal pakkumisi lähedal asuvates majutusasutustes. J'ai longtemps eu une attitude de repli face à ce traité car il n'est pas enthousiasmant et nombreux sont ceux sur ce site qui peuvent confirmer ma position. For instance, in the example shown under Request Structure ”, we also provide the date-time format. The panic room was 6 feet (1.8 m) by 14 feet (4.3 m). Three versions of the room were built so Fincher could film scenes from multiple angles. Lis l'interview de Rocard dans le journal précédent. La recherche de nourriture ne sera entreprise qu'une fois que les trois précédents problèmes ont été résolus. No data is shared with Facebook unless you engage with this feature. Koepp and Fincher agreed to streamline the film so the opening would introduce the characters as soon as possible. On notera que c'est la seconde fois, cette année, que les pirates s'en prennent un bâtiment de ce genre, le confondant avec un navire civil. In retrospect, Panic Room has been assessed for its portrayal of childhood and feminism , the elements of video surveillance and diabetes , and its thematic approach to mortality. L'émission de TVE Imágenes prohibidas (Miquel Romero, 1994), sur la censure au cinéma pendant le franquisme, qualifie le film de «cas exceptionnel, incompréhensible quel que soit le point de vue adopté, un cas unique dans le contexte de censure répressive auquel le cinéma de cette période devait faire face». A la limite, si j'avais un avis fixe et definitif, je passerais surement moins de temps dans des debats. As an Exotic Club Member you deserve a weekend break in the heart of your city or in a private cottage along the country side. Le TCE définit la règle du jeu européen aussi. What that means in practice is that the Aedra tend to be more mortal-focused and what desires and drives they have are more recognizable and salubrious to mortals. Misleidis and Gustavo, the hosts, are very friendly people, respect the privacy of guests but are always available to help and suggest the best places to visit in the villa and its surroundings. The next day I picked up a "tweet" from a friend on "Letting Go" and I was reminded of my savior, Melody Beattie, and her book, "The Language of Letting Go", the contents of which has helped me keep my sanity during some challenging years. Aun así, son pocos los estudios que existen sobre ella y vienen, más que de los estudios queer, de académicos y críticos interesados en cuestiones de censura. Un comble, et cette guerre n'en manque pas. Spring Cloud Stream provides a common abstraction for implementing partitioned processing use cases in a uniform fashion across different types of middleware. Et guillame Duval, rédacteur en chef d'Alternatives economiques en remet une couche. Application properties that are defined during deployment override the same properties defined during the stream creation. However, they are scattered all over the city which mean that you do not have to be constrained because of location in these hotels. Because this is a "Rooms to let" appartment and not a hotel, if you want something you have contact to the people at the restaurant. You can share the rent costs, allowing you to enjoy the many beneficial features of living in the city, such as museums, galleries, concerts, bars, clubs, restaurants, and much more. Pass over that piece of pie and opt for healthy, nutrient-dense foods this holiday season. Now you are going to be the one receiving PMs (private messages) from landlords, so you have to check your other” folder quite often. C'est incroyable de voir le respect qu'il y avait entre les 2 hommes. Business owners can play the drama in their heads, know the struggles they have had to get to where they are now and wear a medal of valor for having survived all the challenges. A system that is part of the telephone equipment which provides for hotel guests and staff to retrieve a message left by a caller. Lapsed tõid välja enim seda, et tal võib olla kurb, kui ta ei kuule näiteks mida tegevustes ja mängus räägitakse või mida räägib õpetaja. Prétendre que la seule voie possible est celle de la majorité, c'est couper court à toute discution, et c'est fondamentalement une mauvaise chose. Post a free Room Wanted ad and make sure people with rooms can find you. Et Popov fait la même chose pour se protéger d'Uncle Benz. Properties are passed to TaskLauncher as application properties. In the Dependencies text box, type task to select the Cloud Task dependency. Once the space has finished indexing its data it will be marked with a green check. Many of the people I work with, including these three doing the interview, are people who sort through rubbish, people who go to retro bars that resemble the places I used to go to with my parents in a working class area in Madrid in the Seventies. There is a Single bedroom available in Manchester on Longworthy Road Salford near Tram & Bus stop, Tesco, Aldi store, shopping centre and Salford University. Elle s'offre à lui sexuellement, dans une attitude qui renvoie parallèlement à l'excitation de la jeune novice qui débute … et, point encore plus intéressant souligne le sentiment de désir intense que le jeune homosexuel triste suscite chez les femmes» (122). Unless you are signed in to a HubPages account, all personally identifiable information is anonymized. Des chercheurs de l'institut pour l'immunologie de la clinique universitaire d'Hambourg-Eppendorf, en collaboration avec leurs collegues suedois de l'institut Karolinska a Stockholm, ont trouve de quelle maniere les salmonelles rendaient malades et comment agissait le denomme "facteur de virulence". Vu que la déclaration de votre variable n'est pas remontée au scope de la fonction, il existe un moment où votre variable n'existe pas. C'est tout de même 49,99999999% de chances de plus qu'un pilote qui ne s'éjecte pas. Once you let your ego control your life, you will never be happy or relaxed because as soon as you lose one of the things that you identify with, the rest will fall like dominos and you will lose your happiness. All you need to see in Kuressaare city is only walk away from the Kuressaare Family and Garden apartments. Kavand, mille järgi maalimistööd teostati, tuli Nissi Valla Kultuurikeskuse noortelt, keda juhendasid noorsootöötaja Ott Jeeser ja Turba kooli õpetaja Piret Tamm. This entails deploying multiple instances of a message-consuming app and using content-based routing so that messages with a given key (as determined at runtime) are always routed to the same app instance. On the other side of the desk, our customer was building the work flow in K2, creating the new web pages that are now replacing the SSM administration tool and connecting the output directly to our interface tables. Prostitutes have been prime targets since forever and I think it was just by sheer closeness in time of two murders that the press- hungry for stories- made the facade of the Whitechapel Ripper, which then influenced bored, insane people to look for meaning in their life in this Whitechapel Ripper. Marisol en est convaincue et prévient ainsi le garçon : «gare à toi si ma sœur apprend que pour toi ce n'était pas de l'amour mais une question de philatélie…». Les gestes charismatiques de l'actrice la situent aussi dans l'enfance, c'est le cas lorsqu'elle se mord les lèvres, frustrée par une activité manuelle qu'elle n'arrive pas à exécuter et qu'elle refait lorsqu'elle veut voler de la nourriture comme Oliver Twist. The special did so well that it was picked up as a series by CBS, but Thomas considered its assigned time slot to be too quiet and pulled the show. Õppetegevus meie koolis on pikemaajaline astmeline protsess, mis on süsteemselt läbimõeldud ning vastab iga õpilase vanusele, tasemele ja soole. It also shows how to map these applications into Spring Cloud Data Flow and deploy them. As cupboard doors Large cupboards often require bifold doors - sometimes two separate bifold doors - as a space-saving measure. A seamless shot at the beginning of Panic Room took nine days to film on set but took several months to complete in post-production. She offers herself to him in a pose that at once suggests the excitement of the young woman just starting out … and, even more interestingly, the high level of desirability the sad young man arouses in women» ( p. 122). Book your slice of summer sunshine with a prestigious holiday company and you can look forward to an exciting and memorable break in one of these Gran Canaria, Portugal or Tenerife resorts. Neil on seal enne ka üks eestlane töötanud, paar aastat tagasi. However, even if there are already hotels during this time, only few people stay in London hotels because transportation infrastructures were not yet developed. It is one of the busiest parts of London and more people are in Central London at any given time than in any other part of London. Emmaus-france Le site de tous les groupes Emmaüs de France. It's great to know the TYPE of man you want to be with, but stop trying to change the men you meet into your fairytale, and accept nobody, including you is perfect. C'est à dire que le contenu d'un tableau ou d'un objet déclaré avec const bloque la réassignation de la variable, mais ne rend pas la valeur immuable. Tant que des gens comme toi diront que si on a pas le même avis que toi, on rejoint Le Pen. Lisaks osati tegevuste järel välja tuua täiendavalt näiteid, kuidas lapsi igapäevaselt aidata võiks. I know you're adults, but my mother used to say how when three kids were together there was "always a problem". Any problems that you notice should be reported to front desk staff right away. The location of the log file for the log application will be shown in the Data Flow server's log. I can rent the place to you furnished or unfurnished, depending on what you want and also long term lease will be favorable since i won't be coming soon you will definitely be informed 2month before our arrivalAll bills like phone, internet, water and Electricity are included in the rental fee so you have nothing to worry about,i want to let you know that we do not intend making so much money on our home or inconveniencing you we only want our place to be kept nice and clean.I just want to let you know that we wont be staying at the house, you will have the place to yourself as long as it is kept nice and neatFeel free to get back to me after inspecting the place so we can proceed with other move in procedures on time. Donc, il ne faut pas trop s'étonner non plus de se faire insulter par la famille Attac : en ce qui concerne le TCE ils ont posé le cerveau. If over at this website are just starting out with Spring Cloud Data Flow, you should probably read the Getting Started ” guide before diving into this section. As a result, you should see a list of available REST endpoints. In that case, you must configure the Composed Task Runner to use the same datasource that the Spring Cloud Data Flow instance is using. Comme on l'a déjà exposé ci-dessus, il n'est ni possible ni souhaitable d'anticiper d'ores et déjà à cet égard par une révision de la Constitution (voir ci-dessus, nº 7). B & Q than half a year ago into China, the original home in China, the world has only 12 stores in Home Depot's appliance business can only "test the water" to describe, though, Home Depot's appliance market performance in North America extraordinary. No matter how well the shoes are made, our feet won't stay dry in ballet flats with even the lightest of rain. The importance of promoting activity in young people cannot be overstated. I joined Exotic Time Club before 4 Months,and i must say that these guys provide these best services of all.Exotic Time Club such a true value of money. Combination of Victorian elegance and chic style, with contemporary outfit is un-swearing what else but London Boutique hotels. Jack the Ripper was thought to have had both genders but was sewn up to grow up as a man but later developed as a woman and became so angry at women, whom could have children and grow up as respectable women of England, but decided to throw their lives away and spent their time in the beds of sex-hungered men who were more than happy to pay for their services, and started to cut out their uterus's because he was unable to grow up as a normal adult of either gender. If you are just starting out with Spring Cloud Data Flow, you should probably read the Getting Started guide before diving into this section. Even though the exchange is durable, there needs to be a durable queue bound to the exchange for the message to be stored for later consumption. Tantsukooli lõpetajaks on tark tantsija - kehaliselt, vaimselt ja emotsionaalselt intelligentne inimene, kes tuleb edukalt toime iseseisva ja ühtlasi teisi arvestava eluga nii tantsulaval kui mujal. You never know where the perfect lead will come from, but often people are your best source. Most London hotels are equipped with fabulous conference facilities that enable guests to host conferences with alacrity and ease. Spring Cloud Data Flow (SCDF) provides a higher level way to create this group of three Spring Cloud Stream applications by introducing the concept of a stream. Take 5 minutes everyday to think about all the people, experiences, lessons and mistakes you are thankful for. Je me rappelle un reportage sur une entreprise américaine qui avait construit à partir d'une ancienne plate-forme pétrolière une plate-forme de lancement pour un lanceur de satellite privé. The advance in has created a significant trend in the tile sector especially the sizes.

[isearchgoood]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

via Blogger https://ift.tt/2Sl8hzD #blogger #bloggingtips #bloggerlife #bloggersgetsocial #ontheblog #writersofinstagram #writingprompt #instapoetry #writerscommunity #writersofig #writersblock #writerlife #writtenword #instawriters #spilledink #wordgasm #creativewriting #poetsofinstagram #blackoutpoetry #poetsofig

[nutrifami]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[theinjectlikes2]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

from The Moz Blog https://ift.tt/31sLZAr via IFTTT

[kjt-lawyers]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[gamebazu]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[daynamartinez22]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[noithatotoaz]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[drummcarpentry]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[xaydungtruonggia]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

[epackingvietnam]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

#túi_giấy_epacking_việt_nam #túi_giấy_epacking #in_túi_giấy_giá_rẻ #in_túi_giấy #epackingvietnam #tuigiayepacking

[whitelabelseoreseller]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!

from The Moz Blog http://tracking.feedpress.it/link/9375/13224276

[localwebmgmt]

Position Zero Is Dead; Long Live Position Zero

Posted by Dr-Pete

In 2014, Google introduced the featured snippet, a promoted organic ranking that we affectionately (some days were more affectionate than others) referred to as "position zero" or "ranking #0." One of the benefits to being in position zero was that you got to double-dip, with your organic listing appearing in both the featured snippet and page-1 results (usually in the top 3–4). On January 23, Google announced a significant change (which rolled out globally on January 22) ...

"Declutters" sounds innocuous, but the impact to how we think about featured snippets and organic rankings is significant. So, let's dig deep into some examples and the implications for SEO.

What does this mean for Moz?

First, a product announcement. In the past, we treated Featured Snippets as stand-alone SERP features — they were identified in our "SERP Features" report but were not treated as organic due to the second listing. As of Saturday, January 25 (shout-out to many of our team for putting in a long weekend), we began rolling out data that treats the featured snippet as position #1. SERPs with featured snippets will continue to be tagged in SERP Features reporting, and we're working on ways to surface more data.

Here's a partial screenshot of our "SERP Features" report from one of my own experiments ...

At a glance, you can see which keywords displayed a featured snippet (the scissor icon), owned that featured snippet (highlighted in blue), as well as your organic ranking for those keywords. We're working on bringing more of this data into the Rankings report in the near future.

If you're a Moz Pro customer and would like to see this in action, you can jump directly to your SERP Features report using the button below (please let us know what you think about the update):

Check Your SERP Features

This change brings our data in line with Google's view that a featured snippet is a promoted organic result and also better aligns us with Google Search Console data. Hopefully, it also helps provide customers with more context about their featured snippets as organic entities.

How does Google count to 10?

Let's take a deeper look at the before and after of this change. Here are the desktop organic results (left-column only) from a search for "LCD vs LED" on January 21st ...

Pardon some big images, but I promise there's method to my madness. In the "before" screenshot above, we can clearly see that the featured snippet URL is duplicated as the #1 organic result (note: I've added the green box and removed a People Also Ask box). Ranking #1 wasn't always the case prior to January 22nd, but most featured snippet URLs appeared in the #1–#3 organic positions, and all of them came from page-one results.

Here's the same SERP from January 23rd ...

You can see that not only is the featured snippet URL missing from the #1 position, but it doesn't appear on page one at all. There's more to this puzzle, though. Look at the January 21st SERP again, but numbered ...

Notice that, even with the featured snippet, page one displays 10 full organic results. This was part of our rationale for treating the featured snippet as the #0 position and a special case, even though it came from organic results. We also debated whether duplicating data in rankings reports added value for customers or just created confusion.

Now, look at the numbered SERP from January 23rd ...

The duplicate URL hasn't been replaced — it's been removed entirely. So, we're only left with 10 total results, including the featured snippet itself. If we started with #0, we'd be left with a page-one SERP that goes from #0–#9.

What about double snippets?

In rare cases, Google may show two featured snippets in a row. If you haven't seen one of these in action, here's an example for the search "Irish names" from January 21st ...

I've highlighted the organic URLs to show that, prior to the update, both featured snippet URLs appeared on page one. A quick count will also show you that there are 10 traditional organic listings and 12 total listings (counting the two featured snippets).

Here's that same SERP from January 23rd, which I've numbered ...

In this case, both featured snippet URLs have been removed from the traditional organic listings, and we're left once again with 10 total page-one results. We see the same pattern with SERP features (such as Top Stories or Video carousels) that occupy an organic position. Whatever the combination in play, the featured snippet appears to count as one of the 10 results on page one after January 22nd.

What about right-hand side panels?

More recently, Google introduced a hybrid desktop result that looks like a Knowledge Panel but pulls information from organic results, like a Featured Snippet. Here's an example from January 21st (just the panel) ...

In the left-hand column, the same Wordstream URL ranked #3 in organic results (I've truncated the image below to save your scrolling finger) ...

After January 22nd, this URL was also treated as a duplicate, which was met with considerable public outcry. Unlike the prominent Featured Snippet placement, many people felt (including myself) that the panel-style UI was confusing and very likely to reduce click-through rate (CTR). In a fairly rare occurrence, Google backtracked on this decision ...

Our data set showed reversal kicking in on January 29th (a week after the initial change). Currently, while some featured snippets are still displayed in right-hand panels (about 30% of all featured snippets across MozCast's 10,000 keywords), those URLs once again appear in the organic listings.

Note that Google has said this is a multi-part project, and they're likely going to be moving these featured snippets back to the left-hand column in the near future. We don't currently know if that means they'll become traditional featured snippets or if they'll evolve into a new entity.

How do I block featured snippets?

Cool your jets, Starscream. Almost the moment Google announced this change, SEOs started talking about how to block featured snippets, including some folks asking publicly about de-optimizing content. "De-optimizing" sounds harmless, but it's really a euphemism for making your own content worse so that it ranks lower. In other words, you're going to take a CTR hit (the organic CTR curve drops off quickly as a power function) to avoid possibly taking a CTR hit. As Ford Prefect wisely said: "There's no point in driving yourself mad trying to stop yourself going mad. You might just as well give in and save your sanity for later."

More importantly, there are better options. The oldest currently available option is the meta-nosnippet directive. I'd generally consider this a last resort — as a recent experiment by Claire Carlile re-affirms, meta-nosnippet blocks all snippets/descriptions, including your organic snippet.

As of 2019, we have two more options to work with. The meta-max-snippet directive limits the character-length of search snippets (both featured snippets and organic snippets). It looks something like this ...

<meta name="robots" content="max-snippet:50">

Setting the max-snippet value to zero should function essentially the same as a nosnippet directive. However, by playing with intermediate values, you might be able to maintain your organic snippet while controlling or removing the featured snippet.

Another relatively new option is the data-nosnippet HTML attribute. This is a tag attribute that you can wrap around content you wish to block from snippets. It looks something like this ...

<span data-nosnippet>I will take this content to the grave!</span>

Ok, that was probably melodramatic, but the data-nosnippet attribute can be wrapped around specific content that you'd like to keep out of snippets (again, this impacts all snippets). This could be very useful if you've got information appearing from the wrong part of a page or even a snippet that just doesn't answer the question very well. Of course, keep in mind that Google could simply select another part of your page for the featured snippet.

One thing to keep in mind: in some cases, Featured snippet content drives voice answers. Danny Sullivan at Google confirmed that, if you block your snippets using one of the methods above, you also block your eligibility for voice answers ...

A featured snippet isn't guaranteed to drive voice answers (there are a few more layers to the Google Assistant algorithms), but if you're interested in ranking for voice, then you may want to proceed with caution. Also keep in mind that there's no position #2 in voice search.

How much should I freak out?

We expect these changes are here to stay, at least for a while, but we know very little about the impact of featured snippets on CTR after January 22nd. In early 2018, Moz did a major, internal CTR study and found the impact of featured snippets almost impossible to interpret, because the available data (whether click-stream or Google Search Console) provided no way to tell if clicks were going to the featured snippet or the duplicated organic URL.

My hunch, informed by that project, is that there are two realities. In one case, featured snippets definitively answer a question and negatively impact CTR. If a concise, self-contained answer is possible, expect some people not to click on the URL. You've given them what they need.

In the other case, though, a featured snippet acts as an incomplete teaser, naturally encouraging clicks (if the information is worthwhile). Consider this featured snippet for "science fair ideas" ...

The "More items..." indicator clearly suggests that this is just part of a much longer list, and I can tell you from my as a parent that I wouldn't stop at the featured snippet. Lists and instructional content are especially well-suited to this kind of teaser experience, as are questions that can't be answered easily in a paragraph.

All of this is to say that I wouldn't take a hatchet to your featured snippets. Answering the questions your visitors ask is a good thing, generally, and drives search visibility. As we learn more about the impact on CTR, it makes sense to be more strategic, but featured snippets are organic opportunities that are here to stay.

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!