Once you've verified a property in Google Search Console, the Performance report becomes your daily starting point. It shows clicks, impressions, CTR, and average position over a rolling 16-month window, though data is typically delayed by two to three days. You'll want to filter by page, query, country, and device to spot ranking shifts or traffic drops. Keep in mind that the table caps at 1,000 rows per dimension and rare queries can be omitted for privacy, so you won't see every long-tail search. Next, check the Page indexing report under Indexing. It groups URLs by status—indexed, discovered but not indexed, crawled but not indexed, and excluded for technical reasons. Click any status for representative examples and common causes. If a page isn't appearing, use the URL Inspection tool to see how Google's last crawl went and whether it's in the index. You can request indexing from that panel, but that's only a nudge; Google decides whether and when to index the URL based on crawl budget and content quality. For a Domain property you need DNS verification, which rolls up all protocols and subdomains. For a URL-prefix property—say, https://www.example.ca—you verify just that prefix and can use methods like HTML file upload or tag. Both types share the same reports, but Domain properties simplify analysis when you run www and non-www or HTTP and HTTPS in parallel. Review submitted sitemaps regularly and investigate reported processing or fetch issues. Use Page indexing, URL Inspection, server responses, and crawler evidence together when examining canonical or indexing cases. For a reliable workflow, record the property type, report filters, comparison dates, and representative URLs behind each observation. Confirm important cases with URL Inspection, server responses, or a crawler, then note the action taken and the later result. This preserves context around delayed, limited report data and prevents a diagnostic signal from being presented as a guarantee of indexing or ranking.