Site Search Operator Not Working
This guide explains the problem of site search operator not working — what causes it, what to check, and when it's worth spending money to fix it.
Why This Happens
- Configuration gaps between tools or services
- Missing integrations or manual workarounds that weren't designed to scale
- Changes in vendor behavior, pricing, or API that weren't communicated clearly
What To Check First
- Verify your current setup matches the vendor's latest documentation
- Look for recent changes — platform updates, new team members, configuration drift
- Check if the problem is consistent or intermittent (different root causes, different fixes)
When To Escalate
- The problem is costing you money or customers per week
- You've spent more than 2 hours on it without progress
- A vendor quoted you more than $500 and you're not sure if it's necessary
Dealing with this right now?
Text PJ a quick description — real human, San Diego, straight answer.
Why is my Google Search Console showing webhook or crawl errors? +
GSC errors related to webhooks or fetch failures: (1) If you're using GSC to verify your site and seeing crawl errors, check that your robots.txt isn't blocking Googlebot. (2) Fetch errors in GSC mean Google couldn't load the page — check server response codes, 5xx errors, and redirect chains. (3) If you added a URL Inspection webhook to GSC via a third-party tool, verify the OAuth token hasn't expired. (4) GSC Coverage errors (Crawl anomaly, Server error) require checking your server logs for 5xx responses on the day of the error.
How do I fix 'URL not indexed' or 'Crawled but not indexed' in Search Console? +
Indexing fix path: (1) Request indexing via the URL Inspection tool for important pages — Google prioritizes submitted URLs. (2) Check for 'noindex' meta tags on the page — if present, remove them. (3) Verify the canonical tag points to the correct URL (not a different page or www vs. non-www). (4) Ensure the page has genuine unique content — thin or duplicate pages get 'crawled but not indexed' deliberately. (5) Check your XML sitemap includes the URL and submit it under Sitemaps in GSC.
How do I interpret Google Search Console performance data? +
GSC data interpretation: (1) Impressions = how many times your page appeared in search results. (2) Clicks = how many times someone clicked. (3) CTR (Click-Through Rate) = clicks / impressions — under 3% on position 10+ is normal; under 1% on position 1-3 is a problem. (4) Average Position = the average ranking position across all queries — below 10 means you're on page 1 for some queries. (5) Filter by page to see which URLs are gaining or losing impressions over time — impressions dropping before clicks is often a SERP feature (Featured Snippet, SGE) stealing visibility.
How do I set up Google Search Console correctly for my site? +
GSC setup: (1) Go to search.google.com/search-console, (2) Add a property — use 'Domain property' for the most complete data (requires DNS verification), or 'URL prefix' property for easier setup. (3) Verify ownership via DNS TXT record, HTML file, or Google Tag Manager. (4) Submit your XML sitemap under Sitemaps. (5) Set up the Index Coverage report and check it weekly. (6) Add your entire team as users (Settings → Users and permissions) — never rely on one person's Google account for access.
Can SideGuy help with Google Search Console issues or SEO? +
Yes. Text 858-461-8054 — most GSC issues (coverage errors, indexing problems, sitemap failures) get diagnosed in one conversation. SideGuy runs morning GSC diagnostic laps for San Diego businesses and builds longtail SEO pages that actually rank. Hourly or monthly retainer available.
