URL prefix properties are registered by accurately specifying a specific protocol, subdomain, and path. https://example.com/ and http://example.com/ are counted as different properties. There are various ownership verification methods (HTML file, meta tag, Google tag, DNS, Google Sites), so registration is possible without domain DNS access.
The URL-prefix property is suitable when you want to track performance in a limited range, such as a specific campaign landing directory, blog subsection, or country-specific directory. However, if you migrate to https or mix www/non-www, the data may be split, so it is recommended to run it in parallel with the domain property.
Search Console navigation: → Add property → Select ‘URL prefix’ → Enter the entire URL (including https://). From the list of ownership verification methods, select the most convenient method among HTML file upload, meta tags, and Google Tag Manager.
Key takeaways
- Only pages belonging to the entered URL prefix range (including path) are counted.
- It supports various ownership verification methods such as HTML files, meta tags, Google tags, DNS, and Google Sites.
- Protocol (http/https) and subdomain (www) are distinguished and processed as separate properties.
- The scope of registration is narrower than domain properties, so it is useful when analyzing only specific sections.
- It is the same concept as the site registration method of the UA era, and has been used since before domain properties.