{"id":266,"date":"2026-07-13T14:26:42","date_gmt":"2026-07-13T05:26:42","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/search-console-property\/"},"modified":"2026-11-15T18:46:51","modified_gmt":"2026-11-15T09:46:51","slug":"search-console-property","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/search-console-property\/","title":{"rendered":"Search Console Property (Domain vs. URL Prefix)"},"content":{"rendered":"<h2 class=\"wp-block-heading\">What is a property?<\/h2>\n<p class=\"wp-block-paragraph\">In Search Console, a property is the individual unit in which you view and manage search performance data. Simply put, it is a single container where data is collected. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">When you first create a property, you have to choose between a Domain property and a URL-prefix property. This choice determines the scope in which all your future data is collected, so it is the most important fork in the setup process. For a general overview of Search Console, see the <a href=\"\/en\/seo-glossary\/google-search-console\/\">Google Search Console<\/a> entry.<\/p>\n<h2 class=\"wp-block-heading\">Domain property vs. URL-prefix property<\/h2>\n<p class=\"wp-block-paragraph\">A Domain property gathers every address under a domain in one place, while a URL-prefix property covers only URLs that start with the address you specify. The table below summarizes the differences. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<figure class=\"wp-block-table\"><table><thead><tr><th>Item<\/th><th>Domain property<\/th><th>URL-prefix property<\/th><\/tr><\/thead><tbody><tr><td>Coverage<\/td><td>The entire domain (all subpaths combined)<\/td><td>Only URLs starting with the specified prefix<\/td><\/tr><tr><td>Protocol and www<\/td><td>Groups http, https, with and without www, into one<\/td><td>Treats each protocol and www variant as a separate property<\/td><\/tr><tr><td>Subdomains<\/td><td>Includes all subdomains, such as m. and support.<\/td><td>Includes only the specified address<\/td><\/tr><tr><td>Viewing a subfolder separately<\/td><td>Limited (partly possible only with the page filter in the Performance report)<\/td><td>Possible (e.g., example.com\/blog\/)<\/td><\/tr><tr><td>Verification methods<\/td><td>One: DNS record<\/td><td>Several: file upload, meta tag, DNS, Analytics, Tag Manager<\/td><\/tr><tr><td>Purpose<\/td><td>A unified, domain-wide view<\/td><td>A narrow view of a specific address, folder or protocol<\/td><\/tr><\/tbody><\/table><\/figure>\n<p class=\"wp-block-paragraph\">For example, the Domain property example.com matches URLs with any protocol or subdomain, such as http, https, www., m. and support. In contrast, the URL-prefix property http:\/\/example.com\/ does not match URLs that start with https or include www.; each of those needs its own property. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h2 class=\"wp-block-heading\">When to use which<\/h2>\n<p class=\"wp-block-paragraph\">Unless you have a specific reason, a Domain property is the more convenient choice in most cases. It solves the problem of data being split when the same site is spread across addresses like http, https, www and m. Google also advises creating a Domain property if you want to see any protocol or subdomain as one. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">There are cases where a URL-prefix property is actually better.<\/p>\n<ul class=\"wp-block-list\"><li>When you want to analyze a specific subfolder on its own (e.g., example.com\/blog\/ or a language folder like example.com\/en\/).<\/li><li>When you do not have access to the domain&#8217;s DNS and want to verify ownership more easily with a file upload or meta tag.<\/li><li>When you deliberately want to see data separately by protocol, such as http and https.<\/li><\/ul>\n<p class=\"wp-block-paragraph\">Having both a Domain property and URL-prefix properties for the same site is valid and recommended in practice. You can use the Domain property for the unified view and URL-prefix properties to zoom in on specific folders or protocols. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/google-search-console\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/p>\n<h2 class=\"wp-block-heading\">Adding a property and verifying ownership<\/h2>\n<p class=\"wp-block-paragraph\">To add a property, open the property selector dropdown at the top left of Search Console, click Add property, choose Domain or URL prefix, and then follow the verification steps. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h3 class=\"wp-block-heading\">Domain property &#8211; DNS record only<\/h3>\n<p class=\"wp-block-paragraph\">A Domain property can be verified in only one way: a DNS record. Because you must add a record to the DNS settings at your domain registrar, you need DNS access for the domain to create a Domain property. If Search Console recognizes your registrar in its list, you can select it, click Start verification and follow the instructions; if it is not listed, you add the record yourself. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h3 class=\"wp-block-heading\">URL-prefix property &#8211; one of five methods<\/h3>\n<p class=\"wp-block-paragraph\">For a URL-prefix property, you can choose from several methods. The main ones are HTML file upload, HTML meta tag, DNS record, Google Analytics tracking code and Google Tag Manager. Of these, file upload, meta tag, Analytics and Tag Manager are available only for URL-prefix properties, not for Domain properties. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">The HTML meta tag method means adding one line like the one below inside your homepage&#8217;s head. If you use a CMS like WordPress, you can add it by editing the theme&#8217;s head or in the verification code field of an SEO plugin.<\/p>\n<pre class=\"wp-block-code\"><code>&lt;meta name=\"google-site-verification\" content=\"token_value_from_google_here\" \/&gt;<\/code><\/pre>\n<p class=\"wp-block-paragraph\">To use the Analytics or Tag Manager method, you must use the same Google account as Search Console, and that account needs edit permission in Analytics or publish or admin permission for the Tag Manager container. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h2 class=\"wp-block-heading\">Practical cautions and security<\/h2>\n<p class=\"wp-block-paragraph\">A Domain property combines all subdomains, protocols and subpaths. You can see data for a specific folder by filtering the Performance report by page path, but if you want to split other reports, such as indexing, by folder, it is better to create a separate URL-prefix property. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">Conversely, if you create multiple URL-prefix properties for one site, such as http, https, www and non-www, your data gets split across those properties. <a href=\"\/en\/seo-glossary\/xml-sitemap\/\">Sitemap<\/a> submission and the <a href=\"\/en\/seo-glossary\/url-inspection-tool\/\">URL Inspection tool<\/a> also work per property, so if you want a unified overall picture, a Domain property is better. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/google-search-console\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a><\/p>\n<p class=\"wp-block-paragraph\">Ownership verification stays valid as long as the verification token remains on the site. Put the other way, removing the token revokes verification, so keep the DNS record or HTML file or tag in place even after verification succeeds. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">There is one point that matters especially for security. Removing an unauthorized owner from the user list is not enough. You must also remove every verification token that person planted; if a token remains, the removed owner can verify ownership again and regain access. If one person used several verification methods, you must remove all of their tokens. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7687615\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">A verified owner has full control: not only viewing data but also adding and removing users, changing settings and using every tool. That is why you should make a habit of regularly checking the Users and permissions screen in Settings for unfamiliar owners. An owner you do not recognize may be a sign of a hack. However, a property must always have at least one verified owner, so when cleaning up tokens, be careful not to accidentally remove a legitimate owner&#8217;s token. <a class=\"jt-src jt-src--official\" href=\"https:\/\/support.google.com\/webmasters\/answer\/7687615\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h2 class=\"wp-block-heading\">References<\/h2>\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/34592\" target=\"_blank\" rel=\"noopener\">Add a website property to Search Console (defining Domain and URL-prefix properties) &#8211; Google Search Central Help<\/a><\/li><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" target=\"_blank\" rel=\"noopener\">Verify your site ownership (DNS, file, meta tag, Analytics, Tag Manager) &#8211; Google Search Central Help<\/a><\/li><li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/7687615\" target=\"_blank\" rel=\"noopener\">Managing owners, users and permissions, and removing verification tokens &#8211; Google Search Central Help<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/google-search-console\/\" target=\"_blank\" rel=\"noopener\">The complete guide to Google Search Console (Domain vs. URL-prefix properties) &#8211; Ahrefs Blog<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>A Search Console property is the individual unit in which you view and manage search performance data. There are two types: a Domain property, which groups all subdomains and protocols together, and a URL-prefix property, which covers only URLs that start with the address you specify. Which type you choose determines how data is collected and how ownership is verified.<\/p>\n","protected":false},"template":"","glossary_categories":[17],"class_list":["post-266","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-search-console"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/266\/revisions"}],"predecessor-version":[{"id":2351,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/266\/revisions\/2351"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=266"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}