Verify the correct property, submit the live sitemap, then inspect a few important pages. After data accumulates, use page and query reports to choose improvements. Search Console reports on Google Search; it does not replace sales records or guarantee indexing.
1. Add the property you actually control
Open Google Search Console using the Google account the business intends to keep. A Domain property covers the domain's protocols and subdomains and uses DNS verification. A URL-prefix property covers the specified prefix and offers different verification methods. Google's property setup instructions explain the available options.
For a Domain property, enter the bare domain rather than a full page URL. Copy the exact DNS record Google provides into the domain's DNS management system. Keep the record after verification. DNS changes may take time to be recognized; do not repeatedly replace records because verification is not instant. Give a provider appropriate Search Console access instead of sharing your Google password.
2. Submit the live sitemap
Open the sitemap in a normal browser first. It should return XML containing public, preferred URLs. A login page, error response, old domain, or list of private admin routes needs correction before submission. For this website, the sitemap is colbytechnologies.com/sitemap.xml.
In the correct property, open Sitemaps and submit the sitemap URL or relative path accepted by the interface. Check the processing result later. A successfully read sitemap helps discovery; it does not mean every URL has been indexed. If pages are added regularly, maintain the sitemap automatically instead of submitting each page manually.
3. Inspect the pages that matter most
Start with the homepage, principal service pages, pricing information, portfolio, and the strongest resources. Inspect the final canonical URL rather than a redirect or preview address. Compare the indexed information with a live test when troubleshooting a recent change. A live test describes current access; it does not prove that Google's stored result already reflects the update.
Record the reported reason when a page is not indexed. A duplicate canonical, noindex directive, server error, and discovered-but-not-indexed page call for different responses. Use Google's URL Inspection documentation to interpret the result. Request indexing after a meaningful correction where appropriate; repeated requests are not a strategy for forcing inclusion.
4. Read Performance by page and query
Begin with a useful date range and review impressions, clicks, click-through rate, and average position together. Filter to a service page, then examine the queries associated with it. Does the page answer those searches? Are the searches relevant to customers you can serve? A large impression count for an unrelated topic is not necessarily valuable.
Separate branded searches from broader service searches when evaluating discovery. Compare mobile and desktop if the customer path differs. Changes in query mix, seasonality, and reporting delays affect comparisons, so write down context rather than interpreting every short-term movement as a win or loss. Some queries are omitted for privacy, and report totals do not tell the entire customer journey.
5. Turn a finding into a specific improvement
Example: impressions without useful inquiries
A service page appears for relevant questions but attracts few clicks. First review the title and description for clarity and fit. If people do click, review the actual offer, service boundaries, examples, and contact action. Record what changed and compare a later period; do not change everything daily and lose the ability to learn.
If two pages repeatedly answer the same question, consider clarifying their purposes or consolidating overlapping material. If an important resource has no internal links, connect it from a relevant service or resource page. If the wrong URL appears as canonical, fix conflicting signals before writing more content. See the visibility troubleshooting guide for the technical sequence.
What changes when your domain changes?
Keep ownership verification for both domains. Permanent redirects, new-domain canonicals, updated internal links, and a new sitemap should agree before you submit a domain move through the eligible old property's Change of Address tool. Google's Change of Address instructions explain the supported moves and checks. The tool supports the migration; it does not replace redirects.
Monitor old and new properties during the transition. Keep the old domain and redirects active and investigate broken destination URLs. Do not remove all old URLs through the Removals tool simply because the business rebranded.
Keep the review manageable
Maintain a short change log: date, page, issue, action, and the signal to review. Pair search data with qualified inquiries and the business's actual priorities. Colby Technologies offers SEO implementation and ongoing review for businesses that want help turning the reports into useful work.
Talk through your next step.
Share the business goal and the problem you want to solve. Colby Technologies can help define a practical scope.