{"id":16878,"date":"2017-12-20T17:00:28","date_gmt":"2017-12-20T15:00:28","guid":{"rendered":"https:\/\/cognitiveseo.com\/blog\/?p=16878"},"modified":"2018-08-08T09:52:12","modified_gmt":"2018-08-08T06:52:12","slug":"seo-influence-your-rankings","status":"publish","type":"post","link":"https:\/\/cognitiveseo.com\/blog\/16878\/seo-influence-your-rankings\/","title":{"rendered":"How Did the SEO Landscape Influence Your Rankings in 2017"},"content":{"rendered":"

There\u2019s no better time to draw conclusions and get ready for 2018 than December, a month of celebration and reviews regarding the year that is passing away. Adopt this tactic and avoid getting cold feet in January, having already done your homework and knowing your goals.<\/p>\n

 <\/p>\n

Given that a lot has happened this year and that we also love to analyze and discuss the results, we thought there’s no better way to do that than seeing the gifts Santa Google brought in 2017.\u00a0<\/p>\n

 <\/p>\n

\"How_Did_the_SEO_Landscape_Influence_Your_Rankings_in_2017_v4\"<\/p>\n

 <\/p>\n

So we scooped, searched, and chose the most significant updates and announcements Google has made in the SEO landscape, updates that influenced and will always influence rankings. This is what we’ve found so far:\u00a0<\/p>\n

 <\/p>\n

    \n
  1. The Intrusive Mobile Interstitials Update Is a new Ranking Signal<\/a><\/strong><\/li>\n
  2. Google Introduced the Mobile-Friendly Test API<\/a><\/strong><\/li>\n
  3. Emojis Started to Show up Again in the Search Results Snippets<\/a><\/strong><\/li>\n
  4. Google Has Rolled out the Google Assistant to More Devices<\/a><\/strong><\/li>\n
  5. Officially, the Duplicate Content Penalty Myth Was Broken<\/a><\/strong><\/li>\n
  6. Fred, the New Update, Created Massive Ranking Fluctuations in SERP<\/a><\/strong><\/li>\n
  7. “Upsetting-Offensive” Content Flag Is Rolling out to Offer Qualitative Results<\/a><\/strong><\/li>\n
  8. Google Site Search Is Out. Custom Search Within Site Is the Alternative<\/a><\/strong><\/li>\n
  9. Google Search Console\u2019s Metrics Got Integrated Into Google Analytics<\/a><\/strong><\/li>\n
  10. Google introduced \u201cProject Owl\u201d – The Shield for Fake News<\/a><\/strong><\/li>\n
  11. Fetch as Google for Mobile Apps Is Removed To “Avoid Unnecessary Duplication\u201d<\/a><\/strong><\/li>\n
  12. Baidu, Sogou, and Yahoo Japan Adopted the Mobile Framework (AMP)<\/a><\/strong><\/li>\n
  13. Google Begins Mobile-First Indexing by Moving M-Dot Site to Responsive<\/a><\/strong><\/li>\n
  14. Chatbot Marketing – a Strategy for the Future<\/a><\/strong><\/li>\n
  15. Dwell Time – on Its Way to Become a Ranking Factor<\/a><\/strong><\/li>\n
  16. Conclusion: What to Expect in the Future of SEO<\/a><\/strong><\/li>\n<\/ol>\n
     <\/div>\n

    JANUARY<\/h2>\n
     <\/div>\n

    1. The Intrusive Mobile Interstitials Update Is a new Ranking Signal<\/h2>\n

     <\/p>\n

    At the beginning of this year, people got nervous and concerned with the news of an update meant for\u00a0Intrusive Mobile Interstitials<\/strong><\/a>. On January 10<\/strong><\/a>\u00a0sharp, experts in the SEO industry saw a drop in site traffic, besides some other important changes that Google has made. They were right! A new update happened.<\/p>\n

     <\/p>\n

    At that time, we talked about this update in a blog post<\/a><\/strong>\u00a0since we wanted to see exactly whether a site might be at risk, what the experts say about the interstitials impact on SEO comparing with Google\u2019s statements, and, eventually, how to prevent getting hit by a penalty.<\/p>\n

     <\/p>\n

    The Intrusive Mobile Interstitial Update came in 2015, after Google announced they would downgrade\u00a0sites that show annoying full-page ads prompting users to install mobile apps. Since the Algorithm went live, Google hasn\u2019t made any big changes but kept an eagle eye on the intrusive advertising formats available on the web that offered a negative user experience.<\/p>\n

     <\/p>\n

    Along with this update, penalized websites started to quickly appear.<\/p>\n

     <\/p>\n

    Google stated that this signal is a ranking one:<\/p>\n\n\n\n\n\n
    As we said, this new signal is just one of the hundreds of signals that are used in ranking, and the intent of the search query is still a very strong signal, so a page may still rank highly if it has great, relevant content.<\/td>\n<\/tr>\n
    \"Google<\/td>\nGoogle<\/td>\n<\/tr>\n
     <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The\u00a0Rater Guidelines<\/strong><\/a> were updated. In the Distracting\/ Disruptive\/ Misleading Titles, Ads, and Supplementary Content<\/strong> chapter it was explained which interstitials will be penalized. It includes the ads that actively float over the main content or an interstitial page which redirects the user away. Basically, ads that block the user accessing the main content.<\/p>\n

     <\/div>\n

    2. Google Introduced the Mobile-Friendly Test API<\/h2>\n

     <\/p>\n

    The API launch for Mobile-Friendly Test on January 31<\/strong><\/a>\u00a0was regarded as big news. This year, Google did a lot of changes and improvements for mobile users. We can easily see it, given the fact that they’ve created a\u00a0Mobile-Friendly Test available within an API.<\/p>\n

     <\/p>\n

    The API method allows all mobile device users to check individual pages automatically. Before the API version, the only way was the manual input. Another advantage is the fact that, after running the tests, the method includes a list of all the blocked URLs.<\/p>\n

     <\/p>\n

    Besides that, the Mobile-Friendly Test hasn\u2019t suffered any other big or worthy of mention changes.<\/p>\n

    \"API

    The API key code for the Mobile-Friendly Test
    \nSource: Google Webmaster Central Blog<\/p><\/div>\n

     <\/p>\n

    The documentation used simple steps anybody could follow so to get the API. More information about the API and how to implement it are available on Google Developers<\/strong><\/a>. Or you can search answers and get live help on Webmaster Help Forum<\/strong><\/a>.<\/p>\n

     <\/div>\n

    FEBRUARY<\/h2>\n
     <\/div>\n

    3. Emojis Started to Show up Again in the Search Results Snippets<\/h2>\n

     <\/p>\n

    After Google\u2019s decision to remove characters from the search engine results back in 2015, now it brings back the emojis.<\/p>\n

     <\/p>\n

    Now they can be found everywhere. In other words, for some of us, they became a part of our life, always helpful in our communication. They can be found on mobile phones, social channels, emails, or pictures if you like. They can easily pass the language barriers.<\/p>\n

     <\/p>\n

    Emojis are excellent for captivating attention and for making the text livelier, giving emotions to our words. You know the saying \u201ca picture’s worth 60,000 words\u201d – that goes for emojis too since they are a visual representation. People remember 80% of what they see<\/strong><\/a> and only 20% of what they read.<\/p>\n

     <\/p>\n

    \"emojis<\/p>\n

     <\/p>\n

    Google made a statement regarding this change and said:<\/p>\n\n\n\n\n\n
    We can confirm that we have added a feature to our snippets to feature emojis where relevant, useful, and fun. You’ll see them crop up across various snippets moving forward.<\/td>\n<\/tr>\n
    \"Google<\/td>\nGoogle<\/td>\n<\/tr>\n
     <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The questions that pop out are why they took this decision, whether the emojis will stay for good or not, and how they will improve our search results. An investigation further into this is worth taking. Something we’ll have to look into in 2018.<\/p>\n

     <\/p>\n

    The interesting thing you could easily search on Google using emojis. We tried playing along with this to see the results comparing the standard search.<\/p>\n

     <\/p>\n

    We searched for \u201cKristen Bell\u201d and \u201cKristen ?\u201d and we did that for multiple singers, actors and bands to spot the differences. As you could see in the next screenshot, there are some differences.<\/p>\n

     <\/p>\n

    \"Kristen<\/p>\n

     <\/p>\n

    The results are twisted from a query search to another. As you can see in the first screenshot, for the emoji search, Google offers you some suggestions for other queries. In the standard search, where we use text only, we can see there is also some news displayed, together with more pictures of the actress.<\/p>\n

     <\/p>\n

    There is not an improvement in the emoji search, but there is something to look further into. Google tries to deliver what the user needs, and since this is the time of Millennials, why not offer results for this niche?!<\/p>\n

     <\/div>\n

    4. Google Has Rolled out the Google Assistant to More Devices<\/h2>\n

     <\/p>\n

    Google Assistant, the virtual personal assistant developed by Google was launched in May 2016. At first, it was available only on the Pixel smartphone, Android Wear, Google Home, and its messaging app Allo.<\/p>\n

     <\/p>\n

    In February, Google announced that they will make it available for Android smartphones too, but only for newer smartphones, meaning Android 6.0 and 7.0.<\/p>\n

     <\/p>\n

    \"Google<\/p>\n

     <\/p>\n

    This was a step up because Google Assistant can become in handy for finding what you want online at a faster loading speed and with a more accurate precision. Google is trying to making it easier for users to access the information with shorter actions\/taps.<\/p>\n

     <\/p>\n

    \n

    In the future Google Assistant aspires to be conversational<\/a> and go beyond simple voice query input and text-to-speech playback.<\/p>\n<\/blockquote>\n

     <\/p>\n

    We have to mention that in one Webmaster Central Hangout it was disclosed that PASO might be the future of SEO<\/strong><\/a> due to the fact that it offers personalized information for each user. PASO comes from Personal Assistant Search Optimization.<\/p>\n

     <\/div>\n

    MARCH<\/h2>\n
     <\/div>\n

    5. Officially, the Duplicate Content Penalty Myth Was Broken<\/h2>\n

     <\/p>\n

    Duplicate content: a never-ending topic of discussion.<\/p>\n

     <\/p>\n

    March was a busy month. It started with debunking a myth: the duplicate content penalty<\/a><\/strong>. It was recorded in March 2017, in the Google Search Quality Evaluator Guidelines, that the copied content is penalized, not the duplicate one:<\/p>\n

     <\/p>\n

    \n

    The Lowest rating is appropriate if all or almost all of the MC (main content) on the page is copied with little or no time, effort, expertise, manual curation, or added value for users. Such pages should be rated Lowest, even if the page assigns credit for the content to another source.<\/p>\n<\/blockquote>\n

     <\/p>\n

    We heard it once from Matt Cutts in 2013, and from Andrey Lipattsev again, in 2016, and we can see it written in black and white in the Google Search Quality Evaluator Guidelines. Google has a different approach to dealing with copied content than with duplicate content. Duplicate content doesn’t get you penalized, while copied content does.<\/p>\n

     <\/div>\n

    6. Fred, the New Update, Created Massive Ranking Fluctuations in SERP<\/h2>\n

     <\/p>\n

    Back in March, another big change that shook the SEO landscape was the new update named Fred, still unconfirmed at the moment:<\/p>\n

     <\/p>\n

    \"Gary<\/p>\n

     <\/p>\n

    The first ones to notice some strange activity were WebmasterWorld and Black Hat World. Then the experts took the matter into their own hands and started to debate the possible existence of an update. There was a\u00a0thread<\/strong> <\/a>started on Twitter and SEO forums on this matter.<\/p>\n

     <\/p>\n

    A lot of people experienced some weird search engine ranking position (SERP) fluctuations.<\/p>\n

     <\/p>\n

    After a quick search on cognitiveSEO Signals<\/strong><\/a> we could see that after the unconfirmed update, the volatility was high. In the next screenshot, there is a visual representation of what happened in SERP at that time. The orange line shows a medium volatility and the red one represents a high volatility.<\/p>\n

     <\/p>\n

    \"Google<\/p>\n

     <\/div>\n

    7. ‘Upsetting-Offensive’ Content Flag Is Rolling out to Offer Qualitative Results<\/h2>\n

     <\/p>\n

    Since with the bad effect of the fake news, Google started taking action into offering correct and relevant information to the user, as he tried numerous times before. That\u2019s how the idea of the ‘Upsetting-Offensive’ content flag was born.<\/p>\n

     <\/p>\n

    Even so, Paul Haahr, ranking engineer at Google, said that:<\/p>\n\n\n\n\n\n
    They\u2019re explicitly avoiding the term \u2018fake news,\u2019 because it is too vague.<\/td>\n<\/tr>\n
    \"Paul<\/td>\nPaul Haahr<\/td>\n<\/tr>\n
    Ranking engineer at Google<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Google hired over 10,000 search quality raters worldwide to evaluate the search results and assess the quality of a website based on Google General Guidelines<\/strong><\/a>.<\/p>\n

     <\/p>\n

    Below you can see an example of an article that is flagged for \u201cUpsetting-Offensive\u201d content:<\/p>\n

     <\/p>\n

    \"Upsetting<\/p>\n

     <\/div>\n

    APRIL<\/h2>\n
     <\/div>\n

    8. Google Site Search Is Out. Custom Search Within Site Is the Alternative<\/h2>\n

     <\/p>\n

     <\/p>\n

    A question popped-up during a Google Webmaster Central Hangout about shutting down Site Search and whether it\u2019s going to impact sites.<\/p>\n

     <\/p>\n

    John Mueller said the implementation is different for those two. If you perform a search using those tools you might find different search results. Below you can see a wrap up of the differences between Google Site Search and Free Custom Search:<\/p>\n

     <\/p>\n

    \"Differences<\/p>\n

     <\/p>\n

    \n

    Google Site Search will combine with Custom Search because they almost do similar things. Site Search is used for one website and Custom Search can be both used on different sites, and on one only.<\/p>\n<\/blockquote>\n

     <\/p>\n

    Google announced on Google Enterprise Search<\/strong><\/a>\u00a0that the process of shutting down Google Site Search started in April 2017 and will be finished in April 2018.<\/p>\n

     <\/div>\n

    MAY<\/h2>\n
     <\/div>\n

    9. Google Search Console\u2019s Metrics Got Integrated Into Google Analytics<\/h2>\n

     <\/p>\n

    In May, Google announced another improvement: the integration of Search Console in Analytics<\/strong><\/a> along with support and guideline on the configuration.<\/p>\n

     <\/p>\n

    \"Google<\/p>\n

     <\/p>\n

    Google Search Console helps webmasters manage the way their websites appear in SERP while Google Analytics helps users to integrate services like Webmaster, Adwords, and other tools to see results based on the source (paid search, organic search result).<\/p>\n

     <\/p>\n

    \n

    In the old version, you could only see how users came on the website and not what they did once they got there. Now, with the next improvement, webmasters can see all the metrics in one place and make decisions based on the data combined with those two tools.<\/p>\n<\/blockquote>\n

     <\/div>\n

    10. Google introduced \u201cProject Owl\u201d – The Shield for Fake News<\/h2>\n

     <\/p>\n

    \u201cProject Owl\u201d is an internal name used by Google. It was designed to improve the quality of search after the big fake news on the presidential nomination in the USA last year. The idea of an owl as a symbol of wisdom is appropriate.<\/p>\n

     <\/p>\n

    After that event, the public asked for a solution from search engines and social media giants to tackle \u2018fake news\u2019<\/strong><\/a> and any other misinformation available on the internet. This project encourages white-hat SEO in general and addressed fake news and heavily-biased content in particular.<\/p>\n

     <\/p>\n

    The sites to be spotted by Google for having fake news for the first time will be counted as violating the first amendment. But the second time they\u2019ll be marked as bias to specific news\/media sources.<\/p>\n

     <\/div>\n

    SEPTEMBER<\/h2>\n
     <\/div>\n

    11. Fetch as Google for Mobile Apps Is Removed To “Avoid Unnecessary Duplication\u201d<\/h2>\n

     <\/p>\n

    In September Google announced on Google+<\/strong><\/a> that they’ll begin to remove app indexing features from within Google Search Console.<\/p>\n

     <\/p>\n\n\n\n\n\n
    In May 2016, we announced Firebase App Indexing, together with neat testing tools for apps. To avoid unnecessary duplication, we’ll be turning off the old “Fetch As Google for Apps” feature in Search Console.<\/td>\n<\/tr>\n
    \"profile_googlebot\"<\/td>\nGoogle Webmasters<\/td>\n<\/tr>\n
     <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

     <\/p>\n

    Google\u2019s recommendation for making app content indexable is following the Firebase help documentation<\/strong><\/a>.<\/p>\n

     <\/p>\n

    Last year Google focused their attention more on AMP, responsive design, and other technologies over mobile apps.<\/p>\n

     <\/div>\n

    NOVEMBER<\/h2>\n
     <\/div>\n

    12. Baidu, Sogou, and Yahoo Japan Adopted the Mobile Framework (AMP)<\/h2>\n

     <\/p>\n

    Speaking of AMP<\/strong><\/a>, important SEO news for the ASIA market came in November. Accelerated Mobile Pages will be available to over 1 billion people in Asia. The announcement was made by David Besbris, VP Google Search and AMP Project Lead at Google, on his\u00a0AMP blog<\/strong><\/a>.<\/p>\n

     <\/p>\n

    Baidu, Sogou, and Yahoo Japan joined the team and started supporting the AMP idea. There are a lot of companies that embrace the idea, such as Bing<\/strong><\/a>, Pinterest, Linkedin Tumblr, WordPress, eBay, The Weather Company, Eventbrite, Shopify, Fandango, TripAdvisor, Disney, Food Network, and many more others.<\/p>\n

     <\/p>\n

    According to a study from Google, the average time to fully load a mobile landing page is 22 seconds<\/strong><\/a>. Yet, AMP loads a page faster than 3 seconds.<\/p>\n

     <\/p>\n

    \"AMP

    Source: www.ampproject.org<\/p><\/div>\n

     <\/div>\n

    13. Google Begins Mobile-First Indexing by Moving M-Dot Site to Responsive<\/h2>\n

     <\/p>\n

    Google stated in November that they will start an \u201cexperiment\u201d and look at mobile content first, instead of the\u00a0desktop one, in order to decide the ranking of the results. It began testing mobile-first indexing using mobile content for all search rankings.<\/p>\n

     <\/p>\n

    This change started when Google noticed that searches are more frequent on mobile, yet Google\u2019s index is on desktop pages.<\/p>\n

     <\/p>\n

    They expanded on the idea in their official announcement on Google Webmaster Central Blog<\/strong><\/a>:<\/p>\n\n\n\n\n\n
    Today, most people are searching on Google using a mobile device. However, our ranking systems still typically look at the desktop version of a page\u2019s content to evaluate its relevance to the user. This can cause issues when the mobile page has less content than the desktop page because our algorithms are not evaluating the actual page that is seen by a mobile searcher.<\/td>\n<\/tr>\n
    \"Google<\/td>\nGoogle Webmaster Central Blog<\/td>\n<\/tr>\n
     <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Since there will be a change, even though we don\u2019t know the exact time, it is recommended that we take a look at the documentation<\/strong> <\/a>Google provided for moving your m-dot site to responsive.\u00a0<\/p>\n

     <\/p>\n

    Something extra, that wasn’t necessarily something Google announced but we debated on our blog and we consider important because they regard the future of SEO, is chatbot marketing and dwell time.\u00a0<\/p>\n

     <\/div>\n

    14. Chatbot Marketing – a Strategy for the Future<\/h2>\n

    An interesting idea we debated on our blog this year was the fact that chatbot marketing might be a strategy for the future<\/strong><\/a>. To that end, we wanted to see whether it has any impact on SEO or not.<\/p>\n

     <\/p>\n

    \"Nathan<\/p>\n

     <\/p>\n

    The idea of having a chatbot site is intriguing, but it comes with a cost: the content stored in the database is not indexable.<\/p>\n

     <\/p>\n

    Sujan Patel advises us to stick to conventional SEO. Even so, chatbots attached directly to your website can bring some SEO advantages. Dwell time and bounce rate are linked to rankings. Improving them can also grow your position in Google.<\/p>\n

     <\/p>\n

    Also, chatbots can indirectly help you perform link building, likes,\u00a0and shares. This is a topic that deserves to be taken into consideration for further investigation.<\/p>\n

     <\/div>\n

    15. Dwell Time – on Its Way to Become a Ranking Factor<\/h2>\n

     <\/p>\n

    Speaking of dwell time<\/strong><\/a>, we debated this topic in one of our blog posts. The question was \u201cIs dwell time a ranking factor?\u201d.<\/p>\n

     <\/p>\n

    At the moment we know that content, links, and RankBrain are rankings factors.<\/p>\n

     <\/p>\n

    \n

    But what is the future of SEO, if it is not the links? User engagement is the answer. And how can we measure user experience? By measuring dwell time, of course.<\/p>\n<\/blockquote>\n

     <\/p>\n

    In order to find out more about dwell time, we looked at Google patents and we saw that there is some effort put into using the time on site spent by a\u00a0user as a ranking factor.<\/span> In one way or another, this means that dwell time is able to influence Google rankings.<\/p>\n

     <\/p>\n

    Therefore, in regard to our questions of whether dwell time is a ranking factor, maybe ot is too soon to tell, as there\u2019s a lot of smoke gun, but in the future, it might become one for sure.<\/p>\n

     <\/div>\n

    Conclusion: What to Expect in the Future of SEO<\/h2>\n

     <\/p>\n

    At the end of every year, it is important that we draw a line, see exactly what our goals were, and where we are now. Have we delivered better results for far? Or have we not? Do we need to take any measures whatsoever in order to help us get the results we want? Why did we not outperform the previous year? Hence appear lots of question that need to be answered to.<\/p>\n

     <\/p>\n

    After such a busy year in the SEO world, the same situation can be applied to our site. We need to see what happened after the SEO news and Google changes appeared and set our expectations for the following year.<\/p>\n

     <\/p>\n

    Fred was born, and \u201cUpsetting-Offensive Content flag\u201d became an important guideline, hence quality content is a good ranking signal. Lots of changes happened for mobile, so maybe we should focus more on the mobile next year, and keep an eagle eye on Google\u2019s blog to see what other \u201cgifts\u201d Santa Google has to offer.<\/p>\n

     <\/p>\n

    Pay attention to and beware of the copied content, not duplicate, because that one will bring you a penalty.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"

    There\u2019s no better time to draw conclusions and get ready for 2018 than December, a month of celebration and reviews regarding the year that is passing away. Adopt this tactic and avoid getting cold feet in January, having already done your homework and knowing your goals.   Given that a lot has happened this year […]<\/p>\n","protected":false},"author":12,"featured_media":16904,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-16878","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo"],"_links":{"self":[{"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/posts\/16878","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/comments?post=16878"}],"version-history":[{"count":0,"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/posts\/16878\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/media\/16904"}],"wp:attachment":[{"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/media?parent=16878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/categories?post=16878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cognitiveseo.com\/blog\/wp-json\/wp\/v2\/tags?post=16878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}