Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Google Search Console
Defines source-aware organic search monitoring and diagnosis, evidence handling, and action boundaries.
Read the fileOverview
Google Search Console overview
Use this bundle to structure organic search monitoring and diagnosis while keeping official-source context separate from account, organization, project, document, or environment evidence.
Read the fileWorkflow
Google Search Console source-aware triage
1. State the requested decision or deliverable. 2. Inventory evidence: property type, verified scope, and ownership, report, date range, search type, country, device, query, and page.
Read the fileTemplate
Search Console diagnosis brief
Review-ready brief for organic search monitoring and diagnosis, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- SEO practitioners, site owners, publishers, ecommerce teams, developers, and analysts reviewing organic-search evidence
When to use it
- Search clicks or impressions changed and the property, report, date range, search type, country, device, query, and page filters must be checked.
- An indexing issue needs URL inspection, canonical, robots, sitemap, deployment, and enhancement evidence reconciled in one brief.
- Search Console findings must be compared with analytics, server, rank-tracking, or another source of record before action.
What you need to provide
- Property type and verified scope, report export or screenshots, date range, search type, filters, metric definitions, and freshness context.
- URL inspection or live-test evidence, declared and selected canonicals, robots and sitemap state, relevant deployments, and comparison-source data.
Tasks and expected outputs
Questions it helps answer
- Prepare a search console diagnosis brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce review-ready decisions with explicit verification and approval boundaries.
What it helps produce
- Search Console diagnosis brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Load the Google Search Console bundle and provide the verified property scope, performance export, filters and dates, sitemap status, representative URL inspections, canonical and robots evidence, and deployment history. Ask the agent to separate verified facts from assumptions and produce a Search Console diagnosis brief with the smallest next verification steps.
Context path: bundles/tools/google-search-console
What the bundle includes
Tools
- Google Search Console
Frameworks
- source-evidence matrix
- organic-search-monitoring-and-diagnosis evidence matrix
- qualified-review gate
Evaluations
- Google Search Console source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Inferring property access, ranking causes, indexing state, canonical selection, crawl behavior, or sitemap processing without current evidence, or submitting removals and validation requests without confirmation.
Known limitations
- Use official Google Search Console sources for general context; local organic search monitoring and diagnosis, configuration, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for property type, verified scope, and ownership, report, date range, search type, country, device, query, and page filters, metric definitions, freshness, and aggregation behavior, URL inspection and live-test evidence, indexing, canonical, robots, sitemap, and enhancement evidence, site changes and deployment dates, and analytics, server, rank, and source-of-record comparisons.
- Do not infer property scope, verification, performance values, indexing state, canonical selection, crawl state, sitemap state, site changes.
Safety notes
- Minimize personal, customer, employee, financial, credential, and other sensitive data.
- Require explicit confirmation before changing users, submitting removals or validation requests, modifying sitemaps or site configuration, or publishing unsupported ranking claims.
- Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.