Google Search Console: setup, diagnosis, and reporting that actually goes somewhere

You can read the reports yourself, and GSC is designed to be accessible. The gap is in interpretation and method. Knowing that 1,400 URLs are in the "Discovered, currently not indexed" state is not the same as knowing whether that is a crawl-budget problem, a site-quality signal, a content issue, or a sitemap error, and which fix to run first. We have diagnosed this across hundreds of sites and can tell you which cluster your case falls into and what the fix looks like, rather than leaving you to work through it by trial and error.

The SEO Site Audit takes a wide view: technical health, content quality, backlink profile, competitor gap analysis. Google Search Console is one of several data sources it uses. This service goes deep into the GSC tool itself: every report, every flagged item, every indexing state, the validate-fix workflow, and data retention. If your primary problem is inside Search Console, start here. If you need a full picture including backlinks and competitive positioning, the SEO Site Audit covers more ground. Some clients do both in sequence.

No. Indexing is Google's decision, and no one outside Google can guarantee it. What we can do is identify the specific reason a page is not indexed, apply the correct fix for that state, submit the URL for reindexing, and monitor the validate-fix loop. Once the technical cause is removed, most pages do move into the index, but the timing and the final decision remain with Google.

Yes, read-only access is required. We request it by email invite through the Google Search Console permissions panel, the same way you would add any team member. We never ask for your Google account password. Access is scoped to the specific property and the specific team members on your project. You can revoke it with one click at any time. We are EU-registered (CyberLab.Team OÜ, Estonia) and operate under GDPR. A Data Processing Agreement is available on request.

There are several common causes. A URL-prefix property can verify successfully but miss data if the wrong scope was chosen (http vs https, www vs non-www). A Domain property may have verification that silently fails after a DNS change. A missing or malformed sitemap means pages are not being presented to Google systematically. A brand-new property is also normal: GSC backfills around 16 months of data, but a recently connected property starts with very little. We work through each possibility and find the actual gap.

It matters a lot. A Domain property covers all protocols and subdomains under a root domain (www, non-www, https, http, subdomains) and is verified only via DNS. A URL-prefix property covers one specific URL prefix, verified by DNS, HTML file, HTML tag, Google Analytics, or GTM. If your site has meaningful traffic on both www and non-www, or if you use subdomains for different language versions, a Domain property gives you the complete picture. Most sites should use Domain properties, but the DNS verification requirement stops people from setting them up correctly.

It means Google visited the page, was able to read it, and chose not to include it in the index. The cause is rarely a single technical setting. Google may have judged the content too thin, too similar to other pages on your site, or not useful enough to rank for anything in particular. It can also be a signal from accumulated low-quality pages elsewhere on the same domain. We look at the affected URL group, assess the likely signal, and recommend either a content improvement path, a consolidation approach, or a different canonical strategy.

Discovered, not indexed means Google found the URL (usually from a sitemap or internal link) but has not visited it yet. That is often a crawl-budget or internal-linking signal. Crawled, not indexed means Google visited but chose not to include the page. They are different diagnoses with different fixes. Hitting Request Indexing on large volumes of pages does not address the underlying cause and provides only a temporary signal. For most sites, working on the root cause produces more durable results than manually requesting individual URLs.

We can help you prepare a clean, well-documented reconsideration request, but the decision to revoke a manual action is Google's and can take several weeks to months. The most common reason reconsideration requests fail is that the underlying issue was not fully cleaned up before submitting. We scope the trigger carefully, work through the cleanup checklist, and structure the request in line with what Google's guidelines specify. What we cannot do is promise the outcome or the timeline.

When Google ignores your canonical tag and selects a different URL as the preferred version, it usually means Google found a stronger signal pointing elsewhere: a redirect, internal links pointing to a different URL, the sitemap listing a different version, or a hreflang tag pointing to an alternate. Your stated canonical is treated as a hint, not an instruction. We identify which competing signal is winning and help you bring them into alignment so Google picks up your intended canonical.

Both can be correct because they measure different things. PageSpeed Insights (lab mode) simulates a single load under controlled conditions. The GSC Core Web Vitals report uses field data: real-user measurements from Chrome across all devices and connection types on your site over the past 28 days. A page can pass the lab test and still fail field data if most real visitors are on slow mobile connections, if a slow third-party script runs in the background, or if layout shift happens during a scroll interaction that the lab does not replicate. Field data is what Google uses for ranking signals.

Yes, and this is one of the more methodical things we do. The Performance report can show you whether the drop affected all queries or a specific cluster, all countries or one market, all page types or one section of the site. We look at whether impressions fell alongside clicks (suggesting Google's index changed or a ranking dropped) or clicks fell while impressions held (suggesting CTR changed, which points to a title or snippet issue). We also cross-reference against known Google update dates to tell you whether what you are seeing is a broad algorithm shift or something specific to your site.

Yes. The Search Console to BigQuery Bulk Data Export streams your property data continuously into a BigQuery dataset on your own Google Cloud project. Once it is running, you own the data and can keep it indefinitely. We configure the export, set up appropriate permissions, and optionally connect a Looker Studio dashboard for trend analysis. The BigQuery and Google Cloud project remain yours; we never hold your data.

If the problem you are trying to solve lives inside the Search Console interface, such as indexing states, manual actions, validate-fix loops, or data retention, order this service. If your problem is at the WordPress platform layer, things like plugin conflicts, taxonomy duplication, permalink changes, theme-level Core Web Vitals, or Yoast and Rank Math configuration, the WordPress SEO audit is the right fit. The two do not overlap. Some clients run both.

Not directly. This page is about the Google Search Console tool and its reports: search performance, indexing, and Core Web Vitals. Ranking and getting cited inside Google AI Overviews and AI Mode is covered by our separate AI SEO service. Visibility inside AI assistants like ChatGPT and Perplexity is our AI Visibility service. A well-functioning GSC setup is a prerequisite for almost everything else, but those are separate engagements.

The deliverable is a written diagnosis and a prioritised action plan, with a walkthrough call. We do not write content, build links, or make changes inside your WordPress installation, Google Ads account, or CMS. Implementation is quoted separately based on the fix list and involves no obligation. About half of our clients implement with their own developer or existing agency using the report directly. We give an exact quote after a free preliminary check, typically within 24 hours.