Skip to content
Exhibit A Media Websites & Marketing

Get Found · Chapter 6 of 12

Technical checks you can do yourself

Most technical SEO problems on a small practice site come down to a short list: pages Google cannot find, pages Google has been told to skip, a slow or awkward mobile experience, and duplicate addresses for the same page. You can find all of them with free tools and no coding. This chapter shows you where to look and which warnings you can safely ignore.

Is Google indexing you?

A page that is not in Google’s index cannot rank. Check this first.

Start with a quick search. Type site:yourdomain.ca into Google (with your real domain and no space after the colon). The results are a rough list of indexed pages, and the count is only an estimate. Look for gaps: a missing service page, or old pages you thought were gone.

Then open Google Search Console, the free tool that shows what Google knows about your site (Chapter 10 covers setup).

  1. Open the Pages report (under Indexing). It splits your pages into indexed and not indexed, and gives a reason for each page left out.
  2. Read the reasons. “Excluded by ‘noindex’ tag” on a service page is a real problem. “Page with redirect” or “Alternate page with proper canonical tag” is usually fine, because those are pages Google is correctly treating as copies of another page.
  3. For any important page, paste its address into the URL Inspection bar at the top of Search Console. It tells you whether the page is indexed, when Google last crawled it, and which version Google considers the main one.
  4. If you have published or fixed a page, use “Request indexing” in the same tool. This asks Google to come back. Pressing it repeatedly does nothing extra.

Bing has its own version, Bing Webmaster Tools, and it is worth setting up too. Bing’s index feeds more than Bing search, and some AI assistants draw on it when they search the web.

Sitemap and robots.txt basics

An XML sitemap is a list of the pages you want indexed. Most website platforms create one automatically, usually at yourdomain.ca/sitemap.xml. Open it in your browser and check that your service pages, location pages and articles are in it, and that old or private pages are not. Then submit the sitemap address in Search Console under Sitemaps, and in Bing Webmaster Tools.

The robots.txt file, at yourdomain.ca/robots.txt, tells crawlers which parts of the site to stay out of. Look for this line:

Disallow: /

That tells every crawler to stay off the whole site. It is often left behind from when the site was being built. If you see it, and it applies to all crawlers, get it removed.

Watch for

Check for a leftover “noindex” after any redesign. Many platforms have a setting such as “Discourage search engines from indexing this site” that developers switch on while building. If it is still on after launch, Google will drop your pages over the following weeks. The Pages report in Search Console will show them as excluded by a noindex tag.

While you are in robots.txt, look for lines that block AI crawlers by name, such as GPTBot, OAI-SearchBot, ClaudeBot or PerplexityBot. Some hosts and security services now block these by default. Blocking a training crawler is a fair business choice, but blocking the crawlers AI assistants use to search the web in real time can keep you out of their answers. Make that choice on purpose.

HTTPS, mobile and speed

Your site should load over HTTPS, with the padlock in the browser bar. Type http://yourdomain.ca (without the s) and check that it sends you to the https:// version. If the browser shows a security warning, fix that before anything else in this guide.

Google ranks your site mainly on its mobile version. Open your site on your own phone and try the things a client would do: find a service, read a page, tap the phone number, use the booking or contact form. If you have to pinch to read the text, or a pop-up covers the page, fix it.

For speed, use PageSpeed Insights, a free Google tool. Test your home page and your top service page, and look at the mobile results.

The top section shows real visitor data from Chrome users, called Core Web Vitals, if your site has enough traffic. Many small sites only get the lab test below it. The three measures are:

Measure What it means in plain terms Google’s “good” threshold
Largest Contentful Paint (LCP) How long until the main content shows up 2.5 seconds or less
Interaction to Next Paint (INP) How quickly the page reacts when you tap or click 200 milliseconds or less
Cumulative Layout Shift (CLS) How much the page jumps around while loading 0.1 or less

On small practice sites the usual causes are oversized photos, heavy page builders, sliders and chat widgets, and cheap hosting. Shrinking images (Chapter 4) is the biggest fix you can make without a developer.

Do not chase a score of 100. A site that loads quickly on a phone and passes Core Web Vitals is fast enough, and going from 85 to 99 will not move you past a competitor with better content.

Duplicate pages, canonicals and redirects

Google gets confused when the same page is available at more than one address. These are common:

  • http:// and https:// versions of the same page
  • www.yourdomain.ca and yourdomain.ca
  • An address with and without a trailing slash
  • The same page with tracking codes added to the end of the address

Each should lead to one main version. Type the first two variations into your browser and check that you land on the same address.

A canonical tag is a line in a page’s code that says “this is the main version of this page”. Most platforms add one automatically. In Search Console’s URL Inspection tool, compare “User-declared canonical” with “Google-selected canonical”. If they differ on an important page, Google disagrees with your site about which version counts, and that is worth raising with whoever maintains the site.

Redirects matter when you change addresses. Say a physiotherapy clinic in Burlington renames /services/sports-injury to /sports-physiotherapy. Without a redirect, old links and bookmarks hit an error page and the old address’s history with Google is lost.

  1. Before you change any page address, list the old address and the new one.
  2. Set up a permanent redirect (a “301”) from each old address to its closest new match. Your platform or developer can do this.
  3. Do not send all old pages to the home page. Match each one to the page that covers the same topic.
  4. After the change, test a few old addresses in your browser and check the Pages report in Search Console over the next few weeks.

Structured data worth adding

Structured data (also called schema markup) is code that states facts about a page in a format machines read easily: this is a law firm, here is its address, this article was written by this person. It helps Google and AI systems match your site to the right business and people, though it does not raise rankings by itself.

For a small practice, a few types are worth having:

Type Where it goes What it says
LocalBusiness, or a specific type such as LegalService, Dentist or Physiotherapy Home page or contact page Name, address, phone, hours, service area
Organization Home page Your practice name and logo, with links to your official profiles
Person Each professional’s bio page Name, job title, credentials, links to the regulator’s register
Article Each article Headline, author, publish and update dates
BreadcrumbList Most pages Where the page sits in your site’s structure

The facts in your structured data must match what visitors see on the page. Marking up reviews or hours that are not on the page can earn a manual penalty from Google.

Test any page with Google’s Rich Results Test or the Schema Markup Validator, both free.

A note on FAQ markup: Google stopped showing FAQ rich results for most sites in 2023. Adding FAQ schema will not give your page the drop-down questions in search results, and there is no good evidence that it gets you into AI answers. Clear questions and answers on the page still help readers.

What to ignore

Free SEO tools produce long lists of warnings. You can safely put these aside:

  • Overall “SEO scores” or “site health” percentages from third-party tools
  • Keyword density figures, and warnings that a page is “too short” by a fixed word count
  • Meta keywords tags, which Google does not use
  • Sitemap “priority” and “change frequency” values, which Google ignores
  • Advice to create an llms.txt file as a must-have (it is optional, and no major AI search engine has said it relies on it)
  • Disavow files, unless Google has sent you a manual action about links

An indexed, secure site with one clear address per page is the foundation the rest of this guide builds on.

Try this with AI

Use this to make sense of the Pages report in Search Console:

I run a small [profession] practice in [city], Ontario. Below is a list of reasons from the "Why pages aren't indexed" section of my Google Search Console Pages report, with the number of pages for each. For each reason, tell me in plain English whether it is normal or a problem for a site like mine, and what I should check next. Do not assume anything about my site that is not in the list.

[paste the reasons and counts]

Use this to check your robots.txt file:

Here is my website's robots.txt file. Explain each line in plain English. Tell me if anything blocks Google, Bing, or the crawlers that AI assistants use to search the web. Do not suggest changes I did not ask for unless something is blocking my whole site.

[paste robots.txt]

Check the answers against Search Console and Google’s own help pages before you change anything on your site.

Your checklist

  • Run a site:yourdomain.ca search and note any important page that is missing.
  • Open the Pages report in Search Console and read the reasons for every excluded page.
  • Open your robots.txt and sitemap.xml in a browser, check for Disallow: / and missing pages, and submit the sitemap in Search Console and Bing Webmaster Tools.
  • Test that the http:// and non-www versions of your address land on one main https:// version.
  • Run your home page and top service page through PageSpeed Insights on mobile and note the largest problems.
  • Use your site on your phone as a client would, including tapping the phone number and submitting the contact form.
  • Test your home page and one bio page in the Rich Results Test and ask your developer to add any missing LocalBusiness or Person markup.