What Google indexes—and what AirGarage should do next

Executive summary

Google indexes about seven in ten frozen-sitemap URLs. Deeper analysis found concrete redirect cleanup and family-level planning opportunities, but not Google’s private reason for individual exclusions.

Separate workstream: 20 redirect sources require owner confirmation and inventory cleanup; three overlap the original 16, so the counts should not be added as 36 priorities.

Recommended sequence

1. Now: Confirm and clean up 20 redirect sourcesOwner-confirm each observed target. Verify the preferred target remains HTTP 200, self-canonical, and currently sitemap-listed; then remove the redirect source from the sitemap and internal links while keeping the redirect.
2. Next: Map and strengthen crawlable hubsIdentify replacement rendered discovery paths. Remove links to retired hub/query URLs and provide clean, direct links to a deliberately selected high-value subset. This is not a claim that retired hubs caused exclusions.
3. Decide: Set a separate inventory strategy by familyFor Gates & Equipment, Solutions, and Parking Payments, decide what to retain, consolidate, or retire based on distinct user and commercial intent.
4. Test: Run a pre-specified controlled pilotWhere feasible, stratify and randomize, retain held-out controls, define the primary transition outcome and fixed schedule, plan the minimum detectable effect, and protect controls from spillover. Otherwise label it operational and non-causal.

Coverage by historical Google status

Successful URL Inspection observations collected August 13–17, 2026.

Family concentration

Three programmatic families account for 88% of all exclusions. Counts and rates should be considered together.

URL performance context

Exact GA4 and Search Console performance is attached to all 4,663 frozen-sitemap URLs in the protected explorer.

GA4 all-available reporting runs through August 17, 2026; Search Console maximum-available reporting covers April 16, 2025 through August 16, 2026. Active users are not summed sitewide.

Outside-sitemap diagnostic: 100 highest-signal safe paths are shown from 5,731 eligible review candidates. This is not automatically an error list or an expansion of sitemap inventory.

Search query tables in the interactive explorer exclude anonymized queries and are top-row limited; average position is not a fixed rank.

Search demand opportunities

Search Insights compares adjacent 90-day periods and publishes an explicitly reviewed 617-query subset from returned page/query rows. Dedicated page totals remain authoritative.

These are returned-query candidates, not forecasts. Search Console omits anonymized and unreturned terms; multi-page observations do not establish cannibalization.

Wave 1 targeted diagnosis

No obvious current technical difference appeared in the limited Wave 1 comparison.

The deeper analysis found actionable inventory and architecture patterns, but neither wave reveals Google’s causal reason for individual index states.

The 78 reviewed exclusions consisted of a 73-page nonterminal comparison cohort plus five historical redirect/404 exceptions. Within the nonterminal cohort, 72 of 73 returned an initial HTTP 200 response; Hempstead was the one current redirect. All 40 of 40 indexed comparison pages returned 200.

Phase 9 deeper findings

We found actionable patterns, not Google’s causal answer.

Same city, different family outcomes

Across 922 shared city slugs, indexed share was Gates & Equipment 45.8%, Solutions 61.5%, Parking Payments 70.9%. Family membership is associated with different shares, but intent, history, links, and business value remain unisolated.

Discovery architecture

Four historical hub roots and four query variants returned 404 on August 18. This confirms those tested historical surfaces are retired now; it does not establish that their removal caused exclusions or that no replacement graph exists.

Text and crawl-timing limits

Full-page server transport text was highly repetitive in several sampled families, but it included boilerplate and indexed controls were equally similar. Older recorded crawl timestamps were associated with crawled-not-indexed pages, but reverse causation remains possible. Neither signal justifies a mass rewrite or causal claim.

Not supported as primary explanations

• City demand alone
• Sitemap position as publication age
• URL depth, slug length, or token cleanup
• Historical activity as a cause

Method and limitations

• Historical Google status: 4,663 successful URL Inspection observations, August 13–17, 2026.
• Historical activity: supporting priority evidence; returned monthly rows begin April 2024.
• Wave 1: 120 limited public requests on August 17; no redirect following or retries.
• Wave 2: 50 limited public requests on August 18; no redirect following or retries.
• Client-approved exact URL-level GA4 and Search Console metrics are available in the protected explorer; the redirect-cleanup cohort remains analytics-free.
• Landing sessions use the first page in a session; page views and active users use page-path reporting. Active users are not additive across URLs.
• URL-level query terms are top-row limited. Search Insights uses fuller returned page/query evidence but still excludes anonymized and unreturned terms; missing rows are not proof of no demand.
• Current HTTP checks do not change or explain the earlier historical Google state.
• Google does not expose a causal reason for discovered/crawled-not-indexed states.
• The null technical result, family associations, similarity measure, and crawl timing do not prove page equivalence or a cause.