The Internet Marketing Driver

  • GSQi Home
  • About Glenn Gabe
  • SEO Services
    • Algorithm Update Recovery
    • Technical SEO Audits
    • Website Redesigns and Site Migrations
    • SEO Training
  • Blog
    • Web Stories
  • Contact GSQi

How To Create A Property Set In Google Search Console (GSC) Before A Domain Name Change or HTTPS Migration

June 8, 2016 By Glenn Gabe Leave a Comment

Share
Tweet
Share
Email
71 Shares

Property Sets in Google Search Console (GSC)

Update: March 2019: Google has released a new type of property in Google Search Console called a domain property. A domain property will include all variations for the domain, including by protocol and subdomain. It’s a great move forward by Google and I highly recommend you set them up as soon as possible.

Domain Property in Google Search Console (GSC)

In order to set up a domain property, you’ll need to verify your site by using DNS verification. You can learn more in the blog post Google published about domain properties.

And as you can guess, property sets have been retired. There’s no reason to have property sets when you can have Google automatically gather data from across your site variations. So, although property sets have gone away, you now have domain properties taking their place. And that’s a good thing. I’ve had many of my clients already set them up and they come packed with historical data from the start. I would set one up today. :)

—————————-

On May 23rd Google rolled out Property Sets in Google Search Console (GSC). Property sets enable you to tie multiple sites together in GSC and view aggregated data. Remember, a “site” in GSC is not necessarily a full website. They are organized by subdomain and protocol in GSC, so the www version of a site is different from the non-www version and the https version is different from the http version. Therefore, a typical website should have at least four sites set up in GSC to cover its bases (http www, http non-www, https www and https non-www).

Before property sets, you had to jump into each version of a site in GSC to view search analytics data (queries, impressions, clicks, average position, pages ranking in Search, etc.) That was a pain in the neck if you were trying to see aggregated data (combined data from across versions of site). For example, if you were analyzing both the http and https versions of a site, you would have to jump into two different sites in GSC. But now with property sets, you can combine those sites and view the combined data in one search analytics report. It was an excellent addition by Google.

Important note: Property set data is not retroactive. Therefore, you will see data from the date you set up the property set and forward. You cannot see data before that date. So time does matter when you are setting up property sets. More about that soon.

Domain name changes and switching to https: Why it’s important to set up property sets before the move.
When you change domain names, it’s always smart to analyze the change via Google Search Console. You can view trending for clicks and impressions, review the queries leading to the site over time, their average position in the search results (ranking), mobile data, and more.

But again, when you change domain names or switch to https, you will have to review a second (and new) site in GSC. That’s based on what I explained earlier about sites being set up by subdomain and protocol. So you can’t get a rolling look at the situation (how clicks and impressions were impacted when the change is made, and as time goes on). But with property sets, you actually can!

For example, here’s what trending typically looks like after a migration to HTTPS (for the http “site” in GSC):
Trending After Domain Name Change in GSC

But here’s what it can look like when you have a property set created that combines the http and https versions of a site:
Trending of a property set after an https migration.

When setting up a property set, you can combine multiple sites in GSC, which can also include multiple domain names. So if you are changing domain names, then you can create a property set with eight different sites combined. For example, the www, non-www, https, and http versions of both domain names (your current domain and the new one you are switching to). Then you can view combined data from across all of the sites in GSC. That means as the domain name migration occurs, you can view trending for clicks, impressions, average position, etc. throughout the domain name change or https migration. You can also view pages ranking in Search, data by device, country, and more.

More About Migrating To HTTPS:
And if you are switching to https, like many are doing now, then property sets can help as well. For example, if you add your http and https version of your site in one property set, then you can view the same continual trending throughout the switch. And just to clarify, you should add the http and https version of the www and non-www sites in GSC. So you would have four sites in one property set.

But again, you should create your property set BEFORE you change domain names or migrate to https. Remember, property sets are not retroactive. You will only see data from the date you create the property set and forward.

How to set up a property set when changing domain names or switching to https:
Creating a property set in GSC is easy to do. I’ll walk you through adding multiple sites to a property set when changing domain names. It should only take you a few minutes.

1. Fire up Google Search Console and visit the homepage. Then click the red button labeled “Create a set” in the upper right corner:

Create a property set in GSC.

2. Name the property set something descriptive and then begin selecting “members” for the set. A member is simply a site you have verified in GSC. For our domain name change example, we are going to select eight different sites (the www, non-www, http and https versions of the site for each domain name). Click the dropdown to select a member and choose each site to include.

Adding members to a property set in GSC.

3. One you have selected all eight sites for the domain name change property set, click “Save changes” at the bottom of the window. Note, you will see a “Changes saved” message at the top of the screen, but the page will not redirect back to the homepage of GSC. Everything is fine, just click the “Search Console” logo in the upper left to return to the homepage of Google Search Console.

Saving a property set in GSC.

4. Once you return to the homepage of GSC, you should see your new property set listed. You will also see a “Manage set” dropdown to the right where you can choose to edit that set or delete the set.

Managing a property set in GSC.

5. Analyze your data. It’s important to note that you will not see any data when you first set up the property set. Google needs to start collecting data first. After a few days, you should be able to view search analytics data for the property set (aggregate data from across all the sites within the set).

Once data comes in, you’ll be able to view trending over time, queries across the property set, pages that are ranking in Search, average position of those pages, data by device, and more. That’s across all the sites that are part of the property set. Awesome. :)

And most importantly, you’ll see trending throughout the domain name change or migration to https. It’s a great way to monitor the domain name change or a move to https versus switching sites in GSC and trying to compare data. In addition, you’ll be able to compare dates. So, you can compare dates after the migration to the timeframe before. Again, it’s a smart way to monitor a domain name change or an https migration. Here are some screenshots of search analytics reporting for the property set.

Viewing queries across the property set in GSC (clicks and position):

Property set search analytics reporting for queries.

Viewing all pages in a property set in GSC (http and https combined):
Viewing all pages in a property set in GSC.

Viewing queries by device in a property set in GSC (mobile data):
Viewing search analytics reporting by device in GSC.

Basically, you’ll have full access to the search analytics reporting, but for all sites combined in a property set. That’s exactly what you need when analyzing a domain name change or migration to https.

Summary – Don’t Forget To Set Up Property Sets When Changing Domain Names or Migrating To HTTPS
Property sets are a great way to combine sites in GSC to view aggregate data across each set. And that’s extremely important when you are changing domain names or migrating to https. Instead of switching back and forth between sites in GSC, you can easily view trending over time across the property set (all sites that are included in the set).

And using the Search Analytics reporting for the property set will enable you to analyze a boatload of data directly from Google, including queries, pages, clicks, impressions, average position, and more. So don’t forget to set up a property set when going through a major change SEO-wise. It will only make your life easier. Now run to set up your first property set. You won’t regret it.

GG

Share
Tweet
Share
Email
71 Shares

Filed Under: google, seo, tools

Connect with Glenn Gabe today!

Latest Blog Posts

  • Continuous Scroll And The GSC Void: Did The Launch Of Continuous Scroll In Google’s Desktop Search Results Impact Impressions And Clicks? [Study]
  • How to analyze the impact of continuous scroll in Google’s desktop search results using Analytics Edge and the GSC API
  • Percent Human: A list of tools for detecting lower-quality AI content
  • True Destination – Demystifying the confusing, but often accurate, true destination url for redirects in Google Search Console’s coverage reporting
  • Google’s September 2022 Broad Core Product Reviews Update (BCPRU) – The complexity and confusion when major algorithm updates overlap
  • Google Multisearch – Exploring how “Searching outside the box” is being tracked in Google Search Console (GSC) and Google Analytics (GA)
  • Sitebulb Server – Technical Tips And Tricks For Setting Up A Powerful DIY Enterprise Crawler (On A Budget)
  • Google’s Helpful Content Update Introduces A New Site-wide Ranking Signal Targeting “Search engine-first Content”, and It’s Always Running
  • The Google May 2022 Broad Core Update – 5 micro-case studies that once again underscore the complexity of broad core algorithm updates
  • Amazing Search Experiments and New SERP Features In Google Land (2022 Edition)

Web Stories

  • Google’s December 2021 Product Reviews Update – Key Findings
  • Google’s April 2021 Product Reviews Update – Key Points For Site Owners and Affiliate Marketers
  • Google’s New Page Experience Signal
  • Google’s Disqus Indexing Bug
  • Learn more about Web Stories developed by Glenn Gabe

Archives

  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • August 2021
  • July 2021
  • June 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • GSQi Home
  • About Glenn Gabe
  • SEO Services
  • Blog
  • Contact GSQi
Copyright © 2023 G-Squared Interactive LLC. All Rights Reserved. | Privacy Policy
This website uses cookies to improve your experience. Are you ok with the site using cookies? You can opt-out at a later time if you wish. Cookie settings ACCEPT
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience. You can read our privacy policy for more information.
Cookie Consent