Site icon Impact Digital

How to Set Up Google Search Console on a WordPress Site

Illustration of a WordPress dashboard connected to a Google Search Console performance chart

This guide is for bloggers, small business owners and agency staff who run a WordPress site and have not yet connected it to Google Search Console. It covers choosing the right property type, the verification methods Google offers, submitting your sitemap, giving colleagues access, and what to look at during the first week. It stays on setup. If you are already seeing indexing problems, the posts linked below go deeper on those.

Step 1: Choose a property type

Search Console organises data into “properties”. According to Google’s “Add a website property” help page, you can add either a Domain property or a URL-prefix property. The choice affects what data you see and how you can verify.

FeatureDomain propertyURL-prefix property
ScopeAll subdomains, protocols (http, https, ftp) and subpaths of the domainOnly URLs that start with the exact prefix, including the protocol
Example entryexample.comhttps://example.com/
VerificationDNS record onlySeveral methods
www and non-wwwBoth covered automaticallyEach version needs its own property

Do not type “www”, a protocol or a path into a Domain property; Google says the domain is enough. For URL-prefix properties, the prefix should end in a slash, and you need a separate property for each protocol and subdomain you want to track.

Trade-off: a Domain property gives the most complete picture, especially if your site has moved between http and https or runs on a subdomain such as a blog or shop. The cost is that you must be able to edit DNS records. If you cannot (for example, a client controls the domain), a URL-prefix property verified with a file or tag is the practical route.

Step 2: Add the property

  1. Sign in to Search Console and open the property selector, then choose + Add property.
  2. Choose Website property, then Domain or URL-prefix.
  3. Enter your domain or prefix and pick a verification method.
  4. Verify now, or choose Verify later and return through the property selector.

Google says data should begin to appear within a few days, so an empty report on day one is normal.

Step 3: Verify ownership

Google’s “Verify your site ownership” page describes five methods. Only the DNS method works for Domain properties; the other four work for URL-prefix properties only.

DNS TXT record (Domain or URL-prefix)

If Search Console lists your DNS provider, you can choose it, start verification and sign in. Otherwise pick Any DNS provider, copy the string that starts with google-site-verification=, and add it at your registrar or DNS host as a TXT record. Leave the Host/Name field blank or set it to “@”, and paste the string into the Value field. Google notes that manually added records can take two to three days to propagate. If the wizard instead tells you to use a CNAME record (it does this when a CNAME already exists and points to a parent domain), follow that variant.

HTML file upload (URL-prefix only)

Download the unique file from the Ownership verification page and upload it to your site’s root directory at the exact address shown, using your host’s File Manager or SFTP. Open the address in a private window to confirm it loads without logging in, then click Verify. Do not rename or edit the file.

HTML meta tag (URL-prefix only)

Search Console gives you a <meta name="google-site-verification"> tag that must sit in the homepage’s <head>. On WordPress, the easiest way is usually an SEO plugin that has a webmaster-verification field in its settings: paste the tag or its content value there, save, then confirm the tag appears in the live page source before clicking Verify. The exact menu name differs between plugins, so check your plugin’s documentation. Google says the tag must be in the first 2MB of the page and the homepage must be viewable without logging in.

Google Analytics or Tag Manager (URL-prefix only)

If your site already runs the unmodified Google Analytics (gtag.js or analytics.js) snippet, or a Tag Manager container snippet, you can verify with it. Search Console and the other product must use the same Google account, and for Tag Manager that account needs Publish or Admin permission on the container. Use the code exactly as provided; modified code fails verification. If you have not set up Tag Manager yet, see our Google Tag Manager setup guide for small business sites.

Keep verification alive

Step 4: Submit your XML sitemap

Since WordPress 5.5, core generates a sitemap index at /wp-sitemap.xml and adds a reference to it in robots.txt, according to the WordPress core team’s announcement. By default it includes public post types and taxonomies, author archives and the homepage. Each sitemap holds up to 2,000 entries by default. Two caveats from that same post: rendering needs the SimpleXML PHP extension, and if you tick “Discourage search engines from indexing this site” in WordPress settings, core sitemaps are disabled.

Many SEO plugins replace the core sitemap with their own, often at a different address such as /sitemap_index.xml. Open the sitemap settings of your plugin to get the correct URL, and avoid submitting two overlapping sitemaps. To submit:

  1. Open the sitemap URL in your browser and confirm it loads as XML.
  2. In Search Console, open the Sitemaps report for the property.
  3. Paste the sitemap URL into Add a new sitemap and submit.
  4. Check the status. “Success” means it was fetched and read without errors; “Has errors” means some parsing problems; “Couldn’t fetch” means Google could not retrieve it.

Submitting does not guarantee crawling or indexing. Google says crawling listed URLs can take time and that not every URL may be crawled. It also recrawls read sitemaps on its own schedule, so resubmit only after significant changes. Limits per sitemap are 50 MB uncompressed and 50,000 URLs. You need owner permission to submit; without it, you can list the sitemap in robots.txt.

Step 5: Add users and set permissions

Open Settings > Users and permissions (visible only to owners), click Add user, enter a Google Account email (groups are not allowed), pick a level and save. Google’s permissions page describes these levels:

Give contractors and writers the lowest level that lets them do their job. Because Google warns that all users lose access if every verified owner loses access, consider having a second owner on the account. When someone leaves, use Remove access, and if they were a verified owner, also remove their unused ownership tokens. (This is separate from WordPress logins; for those, see WordPress user roles explained.)

What to check in week one

If the Page indexing report lists “Crawled” or “Discovered” statuses, read Crawled vs Discovered: Not Indexed in Search Console before changing anything. Once data has built up, our Performance report guide shows how to find quick wins.

Key takeaways

FAQ

Should I choose Domain or URL-prefix?

Choose Domain if you can edit DNS, because it covers all subdomains and protocols in one place. Choose URL-prefix if you cannot access DNS or want to track one section separately. You can add both.

How long does DNS verification take?

If you sign in through a supported provider, Google says verification should happen immediately. For manually added records, Google says propagation can take two to three days.

Does submitting a sitemap get my pages indexed?

No. It helps Google discover URLs, but Google states that listed URLs are not guaranteed to be crawled or indexed.

Why is my sitemap missing in WordPress?

Per the WordPress core team, core sitemaps are disabled when search engine visibility is discouraged, and they need the SimpleXML PHP extension (otherwise the server returns a 501 error). An SEO plugin may also have replaced the core sitemap with its own address.

Sources

Exit mobile version