How to Verify a Search Console URL-Prefix Property

A Google Search Console URL-prefix property verifies ownership of a specific website address, including its exact protocol (HTTP or HTTPS) and subdomain (with or without www). Unlike a Domain property that requires access to your DNS records at your domain registrar, a URL-prefix property can be verified through several web-based methods, such as uploading an HTML file, adding an HTML meta tag, or linking an existing Google Analytics or Google Tag Manager container. In this guide, we will walk through how to choose the right prefix, install the verification asset, confirm ownership, and keep your property active.

Understand the Difference Between Domain and URL-Prefix Properties

When you add a site to Google Search Console, you can choose between two property types: a Domain property and a URL-prefix property. Understanding this distinction is essential because it dictates both how you verify ownership and which pages appear in your performance reports.

A Domain property covers all subdomains (like blog.example.com or shop.example.com) and both http:// and https:// protocols under a single dashboard. However, a Domain property requires you to add a DNS TXT record with your domain name registrar, which you can learn about in How to Verify a Search Console Domain Property With DNS. If your company policy restricts DNS management, if you use a shared hosting platform without DNS editing privileges, or if you only run a specific subfolder on someone else's domain, you cannot use a Domain property.

A URL-prefix property solves this problem. It lets you verify ownership by placing a verification asset directly onto your website hosting server or into your site template. The trade-off is scope: a URL-prefix property strictly captures data for URLs matching the exact prefix you enter, including the protocol and trailing paths.

Step 1: Choose the Exact Protocol and Prefix

Because URL-prefix properties match only the exact path specified, choosing the wrong URL will result in an empty dashboard or missing pages. Google Search Console treats http://example.com, https://example.com, and https://www.example.com as three entirely separate entities.

Follow these steps to choose the correct address:

1. Open your browser and navigate to your website homepage.
2. Look at the address bar to confirm whether your site resolves with http:// or https://.
3. Check whether your live site uses www or a non-www root address.
4. Notice whether your content lives in a subfolder, such as https://example.com/blog/.

In Search Console, data is reported only for URLs that send visitors to the property you have open. For example, performance data for an address hosted on a different subdomain or protocol will not appear in your URL-prefix property How Are You Performing on Google?. If your site serves traffic on both the non-www and www versions without a clean redirect, you will need to add and verify both variations as separate URL-prefix properties.

Illustrative Example: Matching Scope to Site Structure

Let us consider a hypothetical scenario with an online store. Suppose a merchant hosts their main store at https://example.com, but their content team manages a standalone blog hosted in a subfolder at https://example.com/blog/.

• Property A: https://example.com/ — Captures the root store and all subdirectories, including https://example.com/blog/ and https://example.com/products/.
• Property B: https://example.com/blog/ — Captures only pages that start with https://example.com/blog/. It cannot see traffic or indexing data for https://example.com/products/.
• Property C: http://example.com/ — Will show zero impressions if all visitors are automatically redirected to https://.

Step 2: Review Supported Verification Methods and Prerequisites

URL-prefix properties support several verification mechanisms. Before you proceed, review the prerequisites for each method to pick the one that matches your technical permissions.

Verification Method	Prerequisites	Best Suited For
HTML File Upload	FTP, SFTP, cPanel File Manager, or server root directory write access.	Custom servers, VPS hosting, traditional CMS installations.
HTML Meta Tag	Ability to edit the <head> section of your homepage HTML.	WordPress (via theme or header plugin), Shopify, Blogger, static sites.
Google Analytics	Edit permission on the GA4 property; the tracking code (gtag.js) must be in the site <head>.	Sites already running Google Analytics with shared Google account logins.
Google Tag Manager	Publish permission on the GTM container; container code placed in <head> and <body>.	Marketing teams managing tags without direct developer access to theme code.

Step 3: Install the Verification Evidence

Once you select your method, log in to Google Search Console and begin the setup. Let us do this step by step.

1. Go to Google Search Console and open the property selector dropdown in the top left corner.
2. Select Add property.
3. In the modal window, locate the URL prefix box on the right.
4. Enter your full website address, including https://, and click Continue.

Google will now present a list of verification methods. Choose your preferred method below to install the evidence.

Option A: HTML File Upload (Recommended for Webmasters)

1. Download the custom verification file provided in the Search Console interface (for example, google1234567890abcdef.html). Do not change the filename or file contents.
2. Connect to your web hosting server via FTP, SFTP, or your hosting control panel file manager.
3. Upload the file to the root directory of your site. This is typically the public_html, www, or htdocs folder.
4. Verify the upload by opening a browser tab and navigating directly to the file path (e.g., https://example.com/google1234567890abcdef.html). You should see the confirmation string displayed on screen.

Option B: HTML Meta Tag (Recommended for CMS Platforms)

1. Select the HTML tag option in the Search Console verification list.
2. Copy the meta tag provided. It will resemble: <meta name="google-site-verification" content="your_verification_string" />.
3. Open your content management system (such as WordPress or Shopify).
4. Paste the tag into the <head> section of your homepage template, before the opening <body> tag. If you use WordPress, you can place this code using an SEO plugin or a dedicated header-injection plugin.
5. Save and publish your changes. Purge any server-level or plugin cache so the live page updates immediately.

Option C: Google Analytics (GA4)

1. Ensure your site already contains the Google tag (gtag.js) snippet in the <head> section of the homepage.
2. Confirm that the Google account you are using for Search Console has Administrator or Editor rights on the GA4 property.
3. In Search Console, expand the Google Analytics verification section.
4. Click Verify.

Option D: Google Tag Manager

1. Ensure the <noscript> and <script> snippets for your container are properly placed in the site template.
2. Confirm that your current Google account has Publish permission for that Tag Manager container.
3. In Search Console, expand the Google Tag Manager section and click Verify.

Step 4: Confirm Property Ownership

After installing the required token or file, return to the Search Console verification screen and click the green Verify button. Search Console will make a live request to your site to detect the verification token.

If the verification succeeds, you will see an "Ownership verified" popup. You can click Go to property to open your new dashboard. If the check fails, the screen will display an error message explaining why Google could not find the token (such as a 404 response for the file or an altered meta tag).

Step 5: Preserve Required Verification Assets

A common operational mistake is treating verification as a one-time event. Google Search Console performs periodic background checks to confirm that you still control the site. If Google cannot find your verification asset during these automated checks, your property ownership will be revoked.

Keep these operational rules in place:

• Do not delete verification files: If you used the HTML file method, leave the file in your root folder permanently. Instruct your team or deployment scripts not to wipe it during site updates.
• Protect your theme code: If you used the HTML tag method inside a WordPress theme file, avoid editing header.php directly. A theme update will overwrite your changes and delete the meta tag. Instead, place the tag via a child theme or a header management plugin.
• Maintain account access: If you verified via Google Analytics or Google Tag Manager, losing access to that Google account or altering container permissions will invalidate your Search Console ownership.

How to Verify Your Result

Once your property is confirmed, verify that Search Console is interacting properly with your live URLs:

1. Check the Property Settings: In the left sidebar, scroll down to Settings. Click Ownership verification. You should see a green checkmark next to your active verification method.
2. Test with the URL Inspection Tool: Use the URL inspection search bar at the top of the interface. Enter a live page URL from your site. Because the URL inspection tool only analyzes pages belonging to the currently opened property, entering a matching URL should return an index status report or allow you to request a live test URL Inspection Tool.
3. Submit Your Sitemap: If you hold owner permissions, open the Sitemaps report in the left sidebar. Enter your sitemap path (such as sitemap.xml) and click Submit to inform Google about your site structure Search Console Sitemaps Report.

Common Mistakes and How to Avoid Them

• Mismatched trailing slashes or subdomains: Registering http://example.com when your server forces redirects to https://example.com will show zero search data. Always verify the live canonical URL version.
• Blocking Googlebot via robots.txt: If your robots.txt file blocks crawler access to your root directory or verification file, Google cannot confirm ownership. Ensure your verification file is publicly accessible.
• Security plugin interference: Some security plugins block direct access to standalone .html files in the root folder, returning a 403 Forbidden error. Test the file in an incognito window to ensure it returns an HTTP 200 status code.
• Redirect loops: If your server redirects the verification file URL to your homepage, the verification crawler will fail because it receives unexpected page content instead of the token.
• Removing assets during redesigns: When migrating CMS platforms or launching a new theme, verification meta tags are frequently forgotten. Always audit your verification status immediately after a site redeploy.

What to Do Next

Now that your URL-prefix property is active and verified, wait a few days for Google to populate your performance charts. Once clicks and impressions begin appearing, you can review search queries to see how visitors find your site, optimize underperforming pages, and submit updated XML sitemaps to keep your index status fresh.

Frequently Asked Questions

Can I verify a Search Console URL-prefix property without DNS access?

Yes. While Domain properties strictly require DNS TXT records, URL-prefix properties support several web-based verification methods that do not require DNS changes. You can upload an HTML file to your server root, insert an HTML meta tag into your homepage header, or authenticate through an existing Google Analytics or Google Tag Manager installation.

What happens if I delete my verification HTML file or meta tag?

Google Search Console periodically checks for the presence of your verification token. If you remove the verification file, delete the meta tag, or lose administrative permissions on your linked Google Analytics account, Google will revoke your ownership. You will lose access to the site's data and reporting until you reinstall the verification asset.

Why does my verified URL-prefix property show zero clicks and impressions?

A URL-prefix property only tracks URLs that match its exact protocol and subdomain. If your property is set to HTTP but your site automatically redirects visitors to HTTPS, the HTTP property will not record traffic. Check that your verified property matches the exact live URL format that appears in your browser address bar.