\n for site owners that gave an overview of best practices when it came to building a site. We called
\n this page “Webmaster Guidelines” and it’s been with us ever since. Since then we added a lot of
\n information to these guidelines to help site owners build the site that’s right for their users
\n who visit through Google Search.\n<\/p>\n
\nA lot has changed since 2002, so today we’re launching a refreshed, simplified version of the
\n Webmaster Guidelines, and we’re changing its name as well.\n<\/p>\n
![\"Googlebot](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-68fe69ca5fe7.png\")
<\/p>\n
Introducing the Google Search Essentials <\/h2>\n
\n We moved away from using the term “webmaster” in the name of this site (stop looking: it’s Search \nThe refresh comes with a few changes. Since the whole Search Central site is, by definition, a set \n The technical requirements<\/a> are few and simple: \n The spam policies<\/a> cover common forms of spam \n We asked the Search Quality team<\/a> \n Finally, the key best practices<\/a> are a set \n You might have also noticed that over the past couple of months we’ve been moving pages around on \n We hope you find the new set of Search Essentials<\/a> useful
\n Central) and the only remainder was the “Webmaster Guidelines”. As we mentioned previously<\/a>,
\n “webmaster” is an outdated term and very few people identify with it. For the new name we wanted
\n something generic, something that’s not focusing on just one slice of our visitors, but rather all
\n creators on the internet who wish to see their content in Google Search. We also wanted the new
\n name to highlight the importance of the points covered on these pages. That’s how we landed on
\n the new name: Google Search Essentials<\/a>.<\/b>\n<\/p>\nWhat’s changed<\/h2>\n
\n of guidelines and best practices, we simplified the site by moving many of the former guidelines
\n to specific sections where they belong. Then, we introduced a categorization of the points covered in the former Webmaster Guidelines:\n<\/p>\n\n
A new focused section on the technical requirements<\/h3>\n
\n publish content in a format that Google can index, and allow Google to access that content.
\n This is the bare minimum for getting into Google’s search results; we do realize however that
\n there’s more to getting your site indexed and served, and we encourage creators to also think
\n about the key best practices<\/a>.\n<\/p>\nSpam Policies: more examples and new topics<\/h3>\n
\n and behavior that could lead to a site ranking lower or not appearing at all in Google web search
\n results. Most topics were taken from the former “Quality Guidelines” and other closely related
\n existing guidelines published on Search Central that were originally stand-alone, like malware and
\n hacked content. The new additions and notable modifications are:\n<\/p>\n\n
\n that can lead to demotion and or removal, such as online harassment<\/a>,
\n and scam and fraud<\/a><\/li>\n
\n and thin content<\/a><\/li>\n<\/ul>\n
\n to rewrite the content to address spam that they see on the internet today, and when possible,
\n use more precise language, and add more concrete examples that are relevant in 2022. We believe
\n that they delivered and the new version will help site owners avoid creating content that Search
\n users absolutely hate.\n<\/p>\nKey best practices for success<\/h3>\n
\n of practices that we believe people really should consider when creating sites. While following
\n the requirements can get (and keep!) sites in Search, it’s the best practices that breathe life
\n into sites so they can be more easily found through Search.\n<\/p>\n
\n Search Central. We organized the information into a more logical structure, and consolidated similar
\n pages, but generally we haven’t changed the content.\n<\/p>\n
\n and easier to understand, and that it will help you focus on things that matter for your site.
\n If you have any questions, leave a comment on Twitter<\/a>
\n or in the Search Central Help forums<\/a>.
\n You can also send feedback on the documentation page itself by clicking the Send Feedback<\/b> button.\n<\/p>\n