Blog

If your WordPress site is not connected to Google Search Console, you are guessing how Google sees your website.

Google Search Console is one of the most useful free tools for small business SEO. It shows which pages Google can find, which search terms bring people to your site, whether your pages are indexed, and whether technical issues are holding you back.

For WordPress website owners, it is also one of the first tools you should set up after launching a new site, redesigning an old one, changing domains, or moving to a new host.

What Google Search Console Actually Does

Google Search Console, often called GSC, is not the same as Google Analytics.

Google Analytics focuses on what visitors do after they arrive on your website. Google Search Console focuses on what happens before and during Google search visibility.

With Search Console, you can see:

• Which search queries your website appears for
• Which pages get clicks from Google
• Whether Google has indexed your pages
• Whether your sitemap has been found
• Mobile usability and page experience issues
• Core Web Vitals signals
• Security warnings or manual actions
• Pages blocked by robots.txt or noindex settings

It will not magically improve your rankings by itself. Think of it more like a dashboard and diagnostic tool.

If your SEO strategy is the vehicle, Search Console is the instrument panel telling you when something needs attention.

Before You Start

You do not need to be a developer to set up Search Console, but you do need access to a few things.

Before starting, make sure you have:

• A Google account you are comfortable using for business tools
• Access to your WordPress admin dashboard
• Access to your domain DNS settings, if possible
• Your preferred website version, such as https://example.ca or https://www.example.ca
• An active SSL certificate so your website loads over HTTPS

If your website still loads over HTTP, fix that first. Google Search Console treats HTTP and HTTPS as separate versions, and Google generally expects modern business websites to use HTTPS.

If you need a refresher, we explain the basics here: SSL Certificates Explained: Why You Need HTTPS.

Step 1: Decide Which Property Type to Use

When you add a website to Google Search Console, Google will usually give you two main property options: Domain and URL-prefix.

This choice matters because it affects what data you see.

Domain Property

A Domain property covers the whole domain, including different versions and subdomains.

For example, a Domain property for example.ca can include:

• https://example.ca
• https://www.example.ca
• http://example.ca
• http://www.example.ca
• blog.example.ca

This is usually the best option if you have DNS access. It gives you the cleanest overall picture and reduces the chance of missing data because you verified the wrong version of your site.

The tradeoff is that Domain verification normally requires adding a DNS record. If you are not comfortable editing DNS, ask your host, web designer, or maintenance provider to help. A small mistake in DNS can affect email or website access, so do not guess.

URL-Prefix Property

A URL-prefix property tracks only the exact version you enter.

For example, if you verify https://www.example.ca, that does not automatically include https://example.ca unless you add it separately.

This option is often easier for WordPress users because you can verify using an HTML tag, an HTML file, Google Analytics, Google Tag Manager, or sometimes a WordPress SEO plugin.

Practical recommendation: Use a Domain property if you have DNS access. Use a URL-prefix property if you need the fastest setup and only have WordPress admin access.

Step 2: Add Your Website to Google Search Console

Sign in to Google Search Console using your business Google account.

Choose the option to add a new property. Then select either Domain or URL-prefix, depending on the approach you chose above.

If you are using a URL-prefix property, check your WordPress settings first:

1. Log in to WordPress.
2. Go to Settings > General.
3. Look at the WordPress Address and Site Address fields.
4. Use the same HTTPS and www/non-www version in Search Console.

This avoids a common problem where the owner verifies one version but Google mainly indexes another.

For example, if your live site redirects to https://www.example.ca, do not verify only http://example.ca and assume the data will be complete.

Step 3: Verify Ownership

Google needs proof that you own or manage the website before it shows private search data.

The most common verification methods are:

• DNS record: Best for Domain properties and long-term reliability.
• HTML file upload: Works if you have hosting file access.
• HTML meta tag: Common for WordPress SEO plugin verification.
• Google Analytics: Works if the correct Analytics property is already installed.
• Google Tag Manager: Works if the correct container is installed properly.

DNS Verification

DNS verification typically involves copying a TXT record from Google Search Console and adding it to your domain DNS settings.

This method is reliable because it stays in place even if you redesign the website, change WordPress themes, or switch SEO plugins.

The downside is that DNS changes can take time to propagate. Sometimes verification works quickly, and sometimes you may need to wait a while before Google confirms it.

If your domain email runs through the same DNS zone, be careful. Do not delete or change existing MX, SPF, DKIM, or DMARC records unless you know exactly what they do.

HTML Meta Tag Verification

This is a popular option for WordPress websites.

Google gives you a meta tag. You then add it to your site’s header, usually through an SEO plugin or theme settings.

Many SEO plugins, such as Yoast SEO, Rank Math, All in One SEO, and SEOPress, include a place to paste Google verification codes. The exact label and location can change, so check the plugin’s official documentation if you are unsure.

Be careful to paste the correct part of the tag. Some plugins ask for the full meta tag, while others ask only for the verification code inside it.

After saving the setting, clear your site cache if you use a caching plugin. Then return to Search Console and click verify.

HTML File Upload

Google may let you download a small verification file and upload it to your website.

This works well if you have cPanel, SFTP, or file manager access. It is less convenient if you only have WordPress admin access.

Do not upload the file into a random theme folder. It needs to be accessible where Google expects it. If you are not comfortable with file access, use a plugin-based or DNS-based method instead.

Step 4: Submit Your WordPress Sitemap

Once your site is verified, submit your sitemap.

A sitemap is a file that lists important URLs on your website so search engines can discover them more easily. It does not force Google to index every page, but it helps Google understand what exists.

WordPress has a built-in sitemap feature, and many SEO plugins generate their own sitemap. Depending on your setup, your sitemap may use a URL similar to:

• /wp-sitemap.xml for the WordPress default sitemap
• /sitemap_index.xml for some SEO plugin-generated sitemaps

Do not assume these are correct for your site. Open the sitemap in your browser first and make sure it loads.

Then in Google Search Console:

1. Open your property.
2. Go to the sitemap section.
3. Enter the sitemap path.
4. Submit it.
5. Check back later for processing status.

If Google reports an error, do not panic. Sitemap errors are often caused by caching, security rules, redirects, or a plugin conflict.

If your sitemap includes pages you do not want indexed, fix the sitemap settings in WordPress or your SEO plugin. Search Console reports the issue, but WordPress is usually where you solve it.

Step 5: Check Indexing Status

After setup, give Google some time to process your website. Search Console is useful, but it is not always instant.

The indexing reports show which pages are indexed, which are not, and why.

Common reasons pages are not indexed include:

• The page has a noindex tag
• The page is blocked by robots.txt
• Google discovered the page but has not crawled it yet
• Google crawled it but chose not to index it
• The page redirects somewhere else
• The page is a duplicate or near-duplicate
• The page returns an error

Not every page needs to be indexed.

For example, thank-you pages, internal search results, cart pages, checkout pages, login pages, and some tag archives usually do not need to appear in Google.

Focus first on the pages that actually matter:

• Your homepage
• Main service pages
• Location or service area pages
• Important blog posts or guides
• Product and category pages for WooCommerce stores
• Contact and booking pages

When not to request indexing: Do not request indexing for every tiny edit, every blog tag, or every low-value page. Use it for new important pages, major updates, or pages that should clearly be in Google but are not.

Step 6: Connect Search Console to Your SEO Workflow

Search Console becomes more valuable when you use it regularly, not when you set it up once and forget it.

A simple monthly routine is enough for most small businesses.

Check these areas:

• Performance: Which queries and pages are getting impressions and clicks?
• Indexing: Are important pages missing from Google?
• Sitemaps: Is Google reading your sitemap successfully?
• Experience: Are mobile or Core Web Vitals issues showing up?
• Security and manual actions: Has Google detected anything serious?

If you are new to SEO, start with the basics before obsessing over advanced reports. This guide is a good next step: SEO Basics: How to Get Found on Google.

What to Look for in the Performance Report

The Performance report shows search queries, pages, countries, devices, impressions, clicks, click-through rate, and average position.

For a Canadian small business, pay attention to location-based searches.

Examples might include:

• “plumber in Calgary”
• “family lawyer Toronto”
• “restaurant near me”
• “dentist in Halifax”
• “web hosting Canada”

If you serve a local market, impressions from the wrong country or city may not mean much. A smaller number of qualified local searches can be more valuable than thousands of irrelevant impressions.

Look for pages that get impressions but few clicks. That often means the page is showing in Google, but the title or meta description may not be compelling enough.

Also look for queries where your average position is close to page one. Those are often good candidates for content improvements, internal links, FAQs, or stronger location signals.

Canadian SEO Notes for WordPress Sites

If your business serves Canada, Search Console can help you spot whether Google understands your market.

Here are a few practical things to watch:

• .ca domains: A .ca domain can help communicate Canadian relevance, but it is not a replacement for useful local content.
• City and province pages: Make sure your service areas are clearly written on-page, not hidden only in images.
• Bilingual websites: If you serve English and French audiences, make sure each language version has its own crawlable URL.
• Local terms: Canadians may search by city, neighbourhood, province, or “near me.” Watch your query data for patterns.
• Privacy expectations: If you use forms, tracking tools, or marketing platforms, your privacy policy should explain how visitor data is handled.

Search Console itself does not show you personally identifiable information about individual searchers. Still, your website may use forms, analytics, cookies, or third-party tools that trigger privacy obligations.

For Canadian privacy basics, see How to Comply with PIPEDA: Essential Privacy Policy Requirements for Canadian Websites.

Core Web Vitals and Page Experience

Google Search Console may show Core Web Vitals data if your site has enough field data available.

Core Web Vitals measure real-world user experience signals such as loading speed, responsiveness, and visual stability. They are not the only ranking factor, but they are worth watching because they affect both SEO and conversions.

If Search Console flags poor URLs, do not assume the problem is only one plugin or one image. WordPress speed issues are usually a combination of hosting, theme weight, plugins, images, caching, scripts, and database overhead.

For a deeper explanation, read Core Web Vitals for WordPress: What to Know.

Ambrite’s cloud web hosting uses LiteSpeed, NVMe SSD storage, and Imunify360, which can help with performance and security foundations. Hosting alone will not fix bad content or bloated design, but it does give WordPress a better base to run on.

Common WordPress Search Console Problems

“Submitted URL marked noindex”

This usually means your sitemap includes a page that tells Google not to index it.

Check the page’s SEO settings in WordPress. Many SEO plugins let you set individual pages to index or noindex.

If the page is important, remove the noindex setting. If the page should stay private or low-value, remove it from the sitemap instead.

“Page with redirect”

This means Google found a URL that redirects somewhere else.

Redirects are not automatically bad. They are normal after redesigns, URL changes, and HTTP-to-HTTPS migrations.

The problem is when your sitemap contains redirected URLs. Your sitemap should generally list the final destination URLs, not the old ones.

“Crawled - currently not indexed”

This means Google visited the page but has not indexed it.

Sometimes this resolves on its own. Other times, it means the page is thin, duplicate, low-value, or too similar to other pages on your site.

Improve the page before repeatedly requesting indexing. Add useful information, original photos, FAQs, service details, local context, pricing guidance where appropriate, and stronger internal links.

“Discovered - currently not indexed”

This means Google knows the URL exists but has not crawled it yet.

For new websites, this can be normal. For established websites, it can point to crawl priority issues, weak internal linking, slow server response, or too many low-value URLs.

If important pages sit here for a long time, review your sitemap, internal linking, page quality, and site performance.

Security Issues or Manual Actions

If Search Console shows a security issue or manual action, take it seriously.

Security warnings can appear when Google detects malware, hacked content, deceptive pages, or other dangerous behaviour. Manual actions can affect your search visibility directly.

Do not just hide the warning or request review before fixing the cause. Clean the site, patch vulnerabilities, update WordPress, review admin users, and scan for backdoors.

If you are not technical, this is a good time to get help. Ambrite offers WordPress maintenance and security plans from $49/month CAD, including ongoing care that helps reduce the risk of neglected updates and avoidable site issues.

Who Should Have Access?

Search Console access should be treated like business access, not casually shared with everyone who asks.

Google typically provides different permission levels, such as owner-level and lower access levels. The exact labels can change, so review Google’s current permission settings when adding users.

Good access habits:

• Use a business-owned Google account where possible
• Give agencies or contractors only the access they need
• Remove access when a vendor relationship ends
• Avoid relying only on one employee’s personal Google account
• Keep a record of who has access

If your web designer or SEO provider sets up Search Console for you, make sure your business is also an owner. You should not lose access to your own search data if you change providers later.

How Often Should You Check Search Console?

Most small businesses do not need to check Search Console every day.

A reasonable schedule is:

• Weekly: Check for major errors, security warnings, or sudden traffic drops.
• Monthly: Review performance, indexing, and top search queries.
• After major changes: Check after redesigns, migrations, plugin changes, URL changes, or new service page launches.

Daily checking often leads to overreacting. Search data naturally moves around, especially on smaller sites where a few clicks can make graphs look dramatic.

Look for patterns, not tiny day-to-day changes.

When Search Console Is Not Enough

Search Console tells you what Google sees, but it does not do the work for you.

It will not write better service pages, fix a slow theme, clean malware, optimize images, repair broken forms, or build local landing pages.

You may need extra help if:

• Your important pages are not getting indexed
• Your traffic dropped after a redesign or migration
• Your site has security warnings
• Your Core Web Vitals are poor across many pages
• Your sitemap is full of junk URLs
• Your SEO plugin settings are confusing or inconsistent
• You are not sure which pages should be indexed

For simple sites, you may be able to handle Search Console yourself after setup. For business-critical WordPress sites, especially WooCommerce stores, law firms, clinics, real estate sites, restaurants, and service businesses, it is worth having someone review the data regularly.

Quick Setup Checklist

1. Make sure your WordPress site loads over HTTPS.
2. Decide whether to use a Domain property or URL-prefix property.
3. Verify ownership using DNS, meta tag, file upload, Analytics, or Tag Manager.
4. Submit your WordPress sitemap.
5. Confirm your important pages are indexable.
6. Check for security issues and manual actions.
7. Review performance data monthly.
8. Use the data to improve real pages, not just stare at reports.

If you want help setting up Search Console, reviewing indexing issues, or making sure your WordPress site is technically healthy, you can contact Ambrite. We work with Canadian small businesses on WordPress hosting, maintenance, and web design, with hosting plans starting at $7.99/month CAD.

This article was written with the help of AI and reviewed by the Ambrite team. Pricing, features, and technical details may change — always verify with official sources before making decisions.