{"id":25217,"date":"2021-11-17T00:00:00","date_gmt":"2021-11-17T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/one-year-of-google-search-central\/"},"modified":"2021-11-17T00:00:00","modified_gmt":"2021-11-17T00:00:00","slug":"one-year-of-google-search-central","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/one-year-of-google-search-central\/","title":{"rendered":"One year of Google Search Central"},"content":{"rendered":"

Wednesday, November 17, 2021<\/p>\n

\n A year ago, we launched our new
\n site<\/a> and announced that we were leaving our beloved name, Google Webmasters, behind for a new
\n moniker: Google Search Central. At the beginning of 2020, we were full of hopes and dreams of
\n reuniting all of our content into one easy to find location, which we quickly learned
\n actually
\n came with a ton of work<\/a> to execute (we were absolutely shocked by this, I tell you).\n <\/p>\n

\"Googlebot<\/p>\n

What’ve we been up to since the launch?<\/h2>\n

\n This year, we’ve been working with our internal SEO team to improve our content, writing lots of
\n new documentation, migrating 13 local language blogs, and developing a new checklist for our home page.\n <\/p>\n

Working with our SEOs to improve content<\/h3>\n

\n To help improve Google Search Central’s content, we reached out to our SEOs. They helped monitor
\n our site migration of thousands of URLs, identify broken redirects, and ensure that traffic
\n moved to the new site properly. We also worked with them to
\n improve our title elements<\/a> and
\n descriptions<\/a> across 200+ pages.\n <\/p>\n

\n We started with the priority documents that were viewed most by our readers, or documents we
\n thought should get more traffic. We also had a few cases where we wanted to
\n deoptimize<\/em> traffic (for example, we were getting user feedback from searchers wanting to remove
\n pages, when our page was just about site
\n owner removals only<\/a>).\n <\/p>\n

\n

\n It’s not everyday you get tapped on by John, Lizzi, and the Search Relations team for SEO help.
\n It’s a strange assignment to help SEO the authoritative SEO content based on Google’s own SEO
\n guidelines. It’s even stranger to have John, Lizzi, and the Search Relations team on the other
\n end of a Google Meet to consult on SEO. Nonetheless, we were very excited to take up the
\n challenge and the opportunity.\n <\/p>\n

\n Doing SEO at Google is a real thing—even when it means doing it for Search Central of all
\n sites. We approached this project like any other we do across many of Google’s other marketing,
\n content, and product websites. This approach is generally the same as everyone else working in
\n the industry—backed by guidelines, best practices, and experience. However, we are limited in
\n the tools, data, and information we can use to keep strict separation between Google Search and
\n the people doing SEO at Google. This helps ensure that we don’t have an unfair advantage.\n <\/p>\n<\/p>\n

\n Helping with the Search Central migration went just like any other migrations we’ve assisted with.
\n We completed keyword research and metadata optimizations for key pages, assisted with redirect
\n mapping and QA-ing redirects, and set up a Google Data Studio dashboard to help monitor progress
\n and complete post-migration analysis. You know, the typical SEO migration checklist.\n <\/p>\n

\n It was also really fun to see reactions from the SEO community after the migration. We’re active
\n on Twitter and subscribe to all the SEO publications (we are just regular SEOs after all), so
\n it was awesome to see the feedback, all the articles, and getting a shoutout on the
\n Search Off The Record podcast<\/a>.\n <\/p>\n

\n Thanks to Lizzi, John, and the rest of the Search Relations teams for the opportunity. We’re
\n looking forward to continuing our partnership and helping grow Google Search
\n Central<\/a> (shameless internal link plug).\n <\/p>\n

\n \u2013Jason Stevens, Growth Lab SEO (Google’s Internal SEO Team)\n <\/p>\n<\/blockquote>\n

Adding more documentation<\/h3>\n

\n We restructured our indexing and crawling documentation, which included grouping things by topic,
\n publishing new documentation, and revamping our guidance on the following topics:\n <\/p>\n