Why Google Can't Find Half Your Website

One of the first things I check in every audit is how many pages a business has indexed in Google. The number is almost always lower than the business owner expects, and sometimes dramatically so.

I audited a Metro Vancouver property manager recently and found a familiar pattern: far fewer pages indexed than the site actually had. Some of that gap was a content-volume problem, which is fixable. But when I dug further, I found pages that should have been indexed but weren’t, city pages, a contact page, dedicated landlord pages. Pages that existed on the site, but that Google had never processed.

That’s an indexation problem. And it’s the most foundational issue I find in property management audits, because a page Google can’t find cannot rank. Content quality doesn’t matter. Schema doesn’t matter. Nothing else matters until Google can access and process the page.

What does it mean for a page to be indexed?

It means a Googlebot crawler visited the page, read its content, and added it to Google’s search index, the database of pages Google can serve as results. An indexed page is eligible to appear in search results. An unindexed page is invisible to search, no matter what it says or how well it’s written.

Indexation is not automatic or guaranteed. Google decides which pages to crawl and when, based on a range of signals: the quality of your site’s internal links, the clarity of your sitemap, your server’s response, and whether Google trusts your site enough to spend crawl budget on its pages.

Why isn’t Google indexing my property management pages?

Five causes account for nearly all of it. Each one is a different failure, and the fix for each is different, so the diagnosis matters more than the general worry.

A missing or outdated sitemap

A sitemap is an XML file listing every page on your site and when it was last updated. Without one, Google has to discover your pages by following links, which is slower and less reliable. Many property management sites either have no sitemap at all or have one that’s gone stale, listing pages that no longer exist and missing the pages added since the site launched.

An accidental noindex tag left over from the build

The noindex meta tag instructs Google not to index a specific page. It’s a legitimate tool for a thank-you page or a duplicate. But I regularly find it on pages that should absolutely be indexed: service pages, location pages, the homepage itself. It usually happens when a developer sets noindex across the site during the build and misses one when clearing them at launch.

Pages blocked in robots.txt

The robots.txt file tells crawlers which parts of your site they may access, and a misconfigured one can block Googlebot from entire sections. Like noindex tags, these blocks are often set during development and never cleaned up. The same file governs whether AI engines can reach you, so it’s worth reading properly rather than glancing at.

Orphan pages with no internal links pointing to them

An orphan page is one that nothing else links to. Google discovers pages by following links, so a page with no inbound link, not from your navigation, not from your homepage, not from any related page, is unlikely to be found at all. Property managers create city pages and then fail to link to them from anywhere, and the pages sit dormant and unindexed for years.

Slow or failing server responses

If your server responds slowly or returns errors when Googlebot visits, Google reduces how often it crawls the site. Persistent server problems don’t just slow indexation down, they can cause pages already in the index to be dropped out of it.

How do you check your indexation in ten minutes?

Five checks, in order. The first is the most informative and the rest confirm what it tells you.

1. Open the Coverage report in Google Search Console. If you don’t have Search Console set up, set it up today, it’s free. The report shows which pages are indexed, which were excluded, and why. The “Excluded” category is where problems hide: look for “Excluded by noindex tag,” “Crawled, currently not indexed,” and “Discovered, currently not indexed.”
2. Run a site search. Search site:yourdomain.com in Google for an approximate count of indexed pages, then compare it to how many pages you know you have. Thirty pages and twelve results is an indexation gap.
3. Read your robots.txt. Visit yourdomain.com/robots.txt. Look for Disallow rules covering important sections. A line like Disallow: /services/ stops Googlebot crawling your service pages entirely.
4. Search your page source for noindex. On any important page, view source and search for noindex. Finding <meta name="robots" content="noindex"> on a page you want indexed is your answer.
5. Open your sitemap. Visit yourdomain.com/sitemap.xml. If nothing loads, you have no sitemap. If it loads, check that it lists your important pages and that the URLs match your live URLs exactly.

What does good indexation look like on a property management site?

Every revenue-driving page discoverable and processed by Google. Concretely, that means:

• All city and landlord pages indexed, since each area you serve deserves its own page
• All neighbourhood pages indexed
• The homepage indexed with the correct canonical URL
• A clean sitemap submitted to Google Search Console
• No accidental noindex or robots.txt blocks on important pages
• Internal links connecting pages so Google can navigate the structure

For most property managers, getting indexation right is a one-time fix followed by ongoing vigilance as new pages are added. It doesn’t require ongoing budget. But without it, every other technical investment, content, schema, link building, is spent on pages Google can’t find.

---

Indexation issues are one of the gaps I find consistently in Metro Vancouver property management audits. The fix is usually faster than owners expect, and a free audit tells you which pages are affected. The audit is the next step.